Revenue reconciliation: a practical operating model for finance and sales, by Malek Damiri

Finance, sales, and analytics each report a different revenue number, and usually none of them is wrong. This deck lays out an operating model for reconciling them: what each system is authoritative for, who owns each number, a monthly cadence tied to the close, tolerance thresholds, and default answers for timing, scope, and identity disputes. Condensed from the essay by Malek Damiri at https://malekdamiri.com/writing/revenue-reconciliation-operating-model/

Transcript

1. An essay in slides Revenue reconciliation A practical operating model for finance and sales Malek Damiri · Head of Revenue Operations malekdamiri.com
2. The problem Three systems, three revenue numbers Finance Closes the month from the billing system. Sales Reports from the CRM. Analytics Builds its dashboards from the warehouse. And a recurring argument about which one is right. Revenue reconciliation malekdamiri.com 2
3. Usually none of them is wrong. They measure different things at different moments. Nobody has written down which number is for what, so every gap looks like an error. Revenue reconciliation malekdamiri.com 3
4. The systems Three systems, three jobs Billing The record of what was invoiced and collected. CRM The record of what was sold and what is expected to close. Warehouse Joins the two, keeps history, and is where the analysis happens. Each is authoritative for something and none is authoritative for everything. Revenue reconciliation malekdamiri.com 4
5. Authority Which system wins when they disagree System Billing CRM Owns In a disagreement Invoiced and recognized revenue Wins over the warehouse on revenue Bookings and pipeline Wins over the warehouse on what was booked Warehouse The reconciliation between the other Owns nothing on its own two and the reporting built on top Saying that out loud once saves a lot of meetings. Revenue reconciliation malekdamiri.com 5
6. Owners One owner per number, a person rather than a team Every number that reaches an executive deck needs one owner. Revenue reconciliation Finance Owns revenue. Sales operations Owns bookings. RevOps Owns the mapping between them: which closed-won deal became which invoice, and which CRM account is which billing customer. malekdamiri.com 6
7. The mapping The mapping is the real work Deals and invoices rarely line up one to one. A deal becomes several invoices An invoice covers several deals An account gets renamed in one system and not the other Keep the mapping as its own table in the warehouse, owned by one person, and treat every unmapped record as a task with a due date. Revenue reconciliation malekdamiri.com 7
8. Cadence Put it on the calendar and tie it to the close 1 2 3 Finance closes billing and publishes recognized revenue by customer. RevOps pulls bookings from the CRM and invoices from billing, joins them in the warehouse, and produces the variance report. Open items are reviewed, disputes settled, and the report signed off by both owners. First few business days after month end Over the next few days By the end of the following week Monthly is the minimum. For large deals I’d also check bookings against invoicing weekly. A big contract that never gets invoiced is a gap to find in week one, not at close. Revenue reconciliation malekdamiri.com 8
9. Tolerance Not every gap deserves a ticket Decide in advance what counts as a difference worth chasing. Set it two ways As an absolute amount and as a percentage, at the customer level and at the total level. Noise Pattern A small timing difference on one invoice. Inside tolerance Outside tolerance Logged and left alone. The same difference repeated across dozens of customers. The total-level threshold is what catches it. Gets an owner and a date. Both thresholds get written down, agreed by finance and sales operations, and revisited once a year. Revenue reconciliation malekdamiri.com 9
10. Disputes Most disputes fall into three categories Category What it looks like Timing Scope The deal closed in one month and the invoice went out in the next. The invoice date drives revenue and the close date drives bookings. Both are correct. The CRM says one amount and the signed contract says another. The signed contract wins and the CRM is corrected to match. Identity The same customer exists under two names, or two customers share one. Revenue reconciliation Default answer The billing customer ID is the master and the CRM carries it as a field. malekdamiri.com 10
11. The goal is that the same argument never happens twice. When a dispute fits none of the categories, the two owners meet, decide, and the decision becomes a new rule. Revenue reconciliation malekdamiri.com 11
12. The record Revenue reconciliation Four things get written down Variance report The report itself, every month, archived where anyone can find it. Exception log Each item outside tolerance, its root cause, who fixed it, and how. Rule book The default answers plus every rule added since. Mapping table With history, so you can see what changed and when. malekdamiri.com 12
13. Diagnosis After a few months the exception log tells you where the process leaks Mostly identity problems Fix how accounts get created. Mostly scope The CRM amount field needs a control. The log turns reconciliation from cleanup into diagnosis. Revenue reconciliation malekdamiri.com 13
14. None of this is sophisticated, and most of it is not SQL. The hard part is getting two teams to accept that the number each of them produces is right for its purpose and wrong for the other’s. Once that is agreed, reconciliation stops being a monthly argument and becomes a monthly checklist. Revenue reconciliation malekdamiri.com 14
15. Revenue reconciliation: a practical operating model for finance and sales Read the full essay malekdamiri.com/writing/revenue-reconciliation-operating-model/ Malek Damiri Head of Revenue Operations Revenue reconciliation More writing Get in touch malekdamiri.com/writing/ linkedin.com/in/malekdamiri/ malekdamiri.com 15