Why sales reports disagree across teams

Before appointing one spreadsheet as the answer, establish the question each figure is intended to answer. Then investigate whether the difference comes from definitions, timing or an error introduced while combining records.

Confirmed order value describes work the business has accepted. Delivered value describes work that has reached a later operational stage. Money received describes payment activity. These measures are related, but one should not silently stand in for another.

Consider an order confirmed at the end of a month, delivered the following month and paid later. The same order appears in different reporting periods depending on the selected date. Forcing every team to count it in the same month could make each report less useful for its own purpose.

Start by giving the measure a precise name, such as “confirmed order value”, and documenting its inclusions and exclusions. For a figure used in financial statements or tax reporting, the responsible accounting team should confirm the specific treatment. An operational reconciliation does not determine those rules.

Keep both report versions, their extraction times, active filters and definition versions. Comparing a live report with a file downloaded before transactions were corrected can create a moving target before the investigation begins.

Check currency and time zones when multiple countries are involved. Preserve the original unit and the conversion rule. Identical-looking numbers are not necessarily comparable, and changing a conversion method should not silently rewrite the meaning of earlier reports.

Choose an order with a known history and trace it from its source. Inspect its references, dates, states, item amounts and corrections at each stage. This distinguishes a record that has not arrived from one excluded by a filter or absorbed into a different grouping.

A common aggregation problem is joining an order-level total to several item rows and then adding that order total once per item. Each row may appear plausible while the overall amount is wrong. Decide whether the calculation belongs at order or item level, and treat discounts and shipping consistently.

Microsoft's data-model guidance explains consistent fact-table detail and the different roles a date can play. The practical lesson is to establish what one row represents before combining tables.

Returns and partial cancellations also need references back to the original transaction. If earlier records are deleted and only the latest values remain, historical reports can change without a clear explanation. Preserve the history and apply the adjustment rules confirmed by the responsible team.

Once a defect is found in one order, inspect the other records affected by the same rule. Editing a cell in the final spreadsheet may resolve today's meeting while leaving the next import to reproduce the discrepancy.

Separate matching records, records present in only one source, and records present in both with different values. Give each unresolved difference a reason category and an owner: timing, delayed refresh, inconsistent state, or still under investigation.

Not every difference is an error. Some correctly follow the reports' different definitions. What matters is being able to identify the underlying records and explain which event would make them enter the other report.

When there are many differences, begin with groups that matter to a decision and can be traced to source records. Keep unexplained amounts visible. Do not insert a balancing adjustment merely to make the grand totals agree without understanding why.

Before adopting a shared report, test ordinary orders, partial deliveries, cancellations, returns and retrospective corrections. Repeat an extraction for the same reporting period: either the result should be reproducible or the changes should have an identifiable explanation.

Make the definition owner part of the ongoing process. A new sales channel or status can otherwise reintroduce the disagreement after the initial cleanup. Record the change, identify affected reports and decide how readers will distinguish old and revised definitions.

Once the totals can be explained, design the dashboard around the decisions it supports. If deliveries also disagree with stock records, use the inventory reconciliation guide to separate sales-reporting questions from stock-movement problems.