Why Sales and Finance Report Different Revenue Numbers (and How to Fix It)
Sales says revenue is one number, finance says another, and both are reading correctly from systems that count things differently. No dashboard fixes that on its own.
It is a definition problem, not a technical one
Most reporting problems are definition problems wearing a technical costume. Sales says revenue is one number, finance says it is another, and both are reading correctly from systems that count returns, tax and unfulfilled orders differently. No dashboard fixes that. Agreeing the definition does, and the dashboard is straightforward afterwards.
What comes first
A written metric definition — what counts, what is excluded, which date field decides the period — signed off by the people who will argue about it later. After that, the pipeline and the dashboard are ordinary engineering.
What gets built from there
- Data pipelines — scheduled extraction from the POS, ERP, accounting package, CRM and the spreadsheets into one warehouse you own
- Data cleaning and de-duplication, with the rules documented rather than buried in a script
- A defined metric layer — one calculation per number, used by every report
- Dashboards by role, because a branch manager needs something different from a director
- Automated reporting — the recurring pack delivered on schedule, with variance flagged
Charts that get read, not admired
One question per screen, answered above the fold. Comparison built in — a number without last period or a target beside it is not information. Every figure traceable to the rows behind it, one click away.
Where this stops
We build the pipelines, the definitions, the dashboards and the forecasts. We do not licence third-party BI platforms on your behalf, and keeping the data clean at source stays with your team unless it is contracted — a pipeline cannot invent a field the till was never configured to record.