Skip to the guide
ReportPatch↗

REPORTING FIELD NOTES / CHECKED OCTOBER 27 2026

Reconcile source totals with a client report

Why do my report totals differ from source exports?

First confirm that both totals describe the same metric, reporting window, time zone, currency, and filters. Then compare independent source control totals with each transformation stage. Investigate joins, filters, windows, and adjustments in that order after establishing comparability.

A difference you can trace

Synthetic example RP-REC-01. Two source rows contain spend of $600 and $400. The source control is $1,000. The report displays $1,250: report minus source is +$250, or +25% relative to the source. This arithmetic identifies a discrepancy; it does not identify its cause.

StageSpend USDEvidence to retain
Source export1,000Rows S1 = 600 and S2 = 400; export timestamp
After transformation1,250Same window and filter; adjustment A1 = +250
Report total1,250Frozen report version and filter state
After removing unapproved A11,000Recomputed report and approval record

In this fixture, an explicit unapproved +$250 adjustment explains the entire difference. We can verify that cause because the stage record contains A1. A real report needs equivalent evidence before assigning a cause.

Investigate without losing the trail

  1. Joins and grain. Count rows and distinct business keys before and after each join. Repeated source amounts warrant a cardinality check. A repeated number alone does not prove duplication.
  2. Filters and completeness. Compare included campaigns, channels, statuses, currencies, and missing keys. For a Sheets report, check the last populated row, formula ranges, hidden rows, import errors, and expected periods. A blank is unknown until its meaning is agreed; it is not automatically zero.
  3. Windows and refreshes. Freeze extracts from the same cutoff and document the source time zones. A late refresh may make two individually correct snapshots incomparable.
  4. Adjustments and formulas. List every manual override, sign, unit conversion, and rounding rule. Identify its owner and approval. Recompute from full precision before rounding the final output.

What to request next

Collect the frozen source export, metric definition, inclusive start and exclusive end, time zone, filters, transformation output, adjustment log, and report snapshot. Write an explicit comparison rule and tolerance before accepting the difference.

If the source is 0, the absolute difference still exists, but percentage difference relative to source is undefined. If the source is missing, report the comparison as unavailable. Do not divide by zero or treat absent evidence as a pass.

Acceptance checklist

Sources and reproducibility

Technical references checked October 27, 2026. Worked examples are synthetic ReportPatch fixtures, checked by automated calculations.

Download the worksheet ↗