An Opportunity, a sales order and a completed job are not interchangeable
Dynamics 365 Sales runs on Dataverse and supports records such as Opportunities, Quotes, Sales Orders and Invoices. These represent different states of a proposed or accepted sale. A forecast built from opportunities is therefore not the same as a report of invoiced revenue or completed service work.
Consider an engineering supplier that wins a project in September, invoices an advance payment in October, delivers equipment in November and carries out commissioning in December. Treating the opportunity close date, invoice date and job-completion date as one event may distort forecasts, capacity planning or monthly margin analysis.
Trace the transitions, including changes
The potential purchase, expected value and estimated close date.
The accepted scope, price, commercial terms and changes.
What work was performed, when and with which resources.
Recognition, invoices, credits and the recorded costs relevant to the job.
A shared Microsoft environment does not mean these facts are all stored in Dynamics 365 Sales or that finance figures are automatically reconciled with service events. The system of record and links depend on the applications implemented and how the organisation uses them.
The discrepancy is itself information
Compare a sample of won opportunities with the resulting orders, completed jobs and invoices. Differences may arise from legitimate phased delivery, deferred work, cancelled items, unapproved variations or incorrect data mapping. They should not automatically be treated as sales forecasting errors.
Separate commercial timing from operational timing. A quote accepted in one period and fulfilled in another affects pipeline, cash flow and labour demand differently. If management wants to attribute margin to an account or product, the relevant cost information must be linked to the appropriate delivery unit.
Choose the question before the integration
For a forecast, identify which event is being predicted and what stage probabilities mean. For a margin analysis, specify the scope of the job and its attributable costs. For customer development, link service history and installed assets to the account rather than treating every Opportunity as a complete view of the relationship.
Continue with forecast uncertainty and the commercial-to-operational handover.
Platform reference
The product behaviour described here follows the vendor documentation: Microsoft Learn: Dynamics 365 Sales opportunity, quote and order data. Configuration and feature availability can vary. The business situations are explanatory examples, not documented Unsnag client outcomes.