Write down the scope of both reports
Before reconciling a difference, record each report's start and end date, timezone where relevant, entity, currency, accounting basis, and status filters. A report of paid invoices will not necessarily agree with one of all issued invoices. A rolling thirty-day dashboard is not the same as a calendar month.
Save the reports as they were produced, including extraction time. A live dashboard can update while the accounting export remains unchanged. Without those snapshots, the number you are trying to reconcile may move during the investigation.
Check the transaction date each system uses
A single sale can have an order date, invoice date, service date, payment date, and settlement date. Identify which one drives inclusion in each report. Then review transactions near the boundary rather than immediately checking every entry in the year.
Suppose an illustrative payment occurs at 11:30 p.m. in one timezone and after midnight in the reporting timezone of another system. Both exports can contain the same payment in different daily periods. The remedy is a consistent reporting convention or an explicit timing bridge, not a fabricated ledger adjustment.
Separate scope differences from missing records
Compare stable transaction identifiers for the affected population. Group differences into items present only in one report, items with different values, and items with different dates or statuses. This makes the investigation more manageable than comparing two totals with no detail.
Look for voided invoices, test accounts, archived customers, manual journals, and delayed imports. Do not assume the dashboard is wrong because the ledger is authoritative for accounting; the ledger can also be missing a legitimate transaction. Trace material exceptions to the underlying evidence.
Correct the definition or the data at its source
If the reports answer different questions, label them and retain a reconciliation. If a filter or timezone is wrong, fix the report configuration and review previously shared periods affected by the error. If data is missing or duplicated, repair the integration or posting process with accounting approval.
Save the agreed report definitions and a small boundary-date test for future changes. Before closing the issue, regenerate both reports for the same fixed period and confirm that the remaining difference is explained. Do not leave an unexplained adjustment in the books to compensate for a presentation problem.
Sources
Requirements and product details can change. Check the linked guidance for the facts that apply to your situation.
Related reading
Need help with this work?
General information, not personalized accounting, tax, legal, or investment advice. Have the appropriate qualified professional review decisions that depend on your circumstances.