Revenue Reporting Breaks at the Definition Before It Breaks in the Dashboard

Marketing may call a booked meeting qualified, sales may require accepted need and timing, and finance may recognize revenue only after invoicing. A dashboard cannot settle that disagreement. It can only hide it behind one field name.

Write a contract for each consequential event: business meaning, required fields, source system, creation rule, owner, event time, allowed transitions, value basis, currency, deduplication key, and correction behavior. Include examples that should and should not qualify.

Store when the business event occurred, when the source recorded it, when the pipeline ingested it, and when the report processed it. These timestamps answer different questions. Replacing event time with sync time can make last month’s revenue appear to happen today.

Use cohort reconciliation for delayed outcomes. Start with leads created in a fixed period, then follow their eligible, qualified, opportunity, won, refunded, and uploaded states as the window matures.

A person, account, opportunity, order, subscription, and advertising click are not interchangeable identities. Define the merge hierarchy, household or account rules, source precedence, and what happens after a CRM merge or deletion request.

Keep raw identifiers out of routine dashboards. Use governed internal keys, restrict access, and retain only what the stated operational and measurement purpose requires.

When qualification criteria or revenue logic changes, publish an effective date and assess whether history should be restated. If it is not restated, mark the discontinuity. A silent semantic change can look like campaign improvement, sales deterioration, or seasonality.

Give every important metric an owner and a reconciliation route. The monthly review should include unresolved breaks, their affected cohorts, and the decision risk—not only a green status badge for the data pipeline.