DSDillon / Business applications
Why Business Dashboards and Source Reports Disagree
Begin with one disputed figure and its definition. Compare the contributing records before changing the chart or adding another data source.
Align the period and event
An order date, invoice date and receipt date can place the same business activity in different periods. Agree which event the measure describes, its time zone and whether the end date is inclusive.
Currency conversion, tax inclusion and refunds also affect totals. The report needs an explicit definition for each.
Compare the underlying rows
Match identifiers, statuses and amounts between systems. Check whether a one to many relationship has multiplied rows during a join. Review cancelled, merged and archived records.
A delayed import should show its last successful update. A partial import needs an exception record and a visible coverage gap.
Build a reconciliation view
Use a completed period with a known source export. List missing, extra and changed records and reconcile the agreed total. Retain the mapping so the next discrepancy follows the same process.
The finished dashboard should let the reader inspect its records and filters. Forecast assumptions and actual figures remain explicitly labelled.
Project questions
Can a dashboard update automatically?
Yes, using supported data access and an agreed refresh schedule. The last update and failed imports should remain visible.
Can we keep the original reports?
Yes. They provide comparison evidence during testing and may remain part of the ongoing reconciliation.
DSDillon / Buyer guide / Updated 26 September 2026
Start with the business problem
Tell us what needs to change.
Bring the current process, the software you use and the result you need. We will work through the scope, connections and delivery requirements.
