Revenue and ROAS Reconciliation
Compare platform-attributed results with store, payment, fulfilment, and finance records using declared definitions and visible unmatched cases.
When to use it
Ad platforms, analytics, the store, and finance show different revenue or order totals and a team needs a reproducible comparison.
Prepare these inputs
Reporting period, timezone, currency, order/payment/refund/COD sources, platform exports, and each system’s event and attribution definitions.
A practical workflow
- 01
Define the business outcome and its source, then declare period, timezone, currency, tax, discount, shipping, and refund treatment.
- 02
Record export time, filters, event and status definitions, and attribution settings for every source.
- 03
Match records only in a restricted environment with an approved key. Keep unmatched cases visible.
- 04
Compare counts and amounts by status and period; explain differences only when evidence supports it.
- 05
Keep attribution separate from business revenue and incrementality, and use findings only for decisions supported by the data.
What the toolkit includes
Metric definitions, a source-field map, a reconciliation report, and review cases for refunds, COD, currency, timing, overlap, and unmatched records.
Review boundaries
Attribution matching does not establish causality or incrementality. Keep personal data restricted and route accounting or tax decisions to qualified owners.