Controller vs CFO: who actually owns revenue reconciliation?
In most mid-market companies, the question "who is responsible for revenue reconciliation?" has an honest answer: nobody, clearly. The Controller produces reconciliations. The CFO signs off on the accounts. The sales team manages the CRM. None of these three parties has an explicit mandate to ensure that what the CRM records actually matches what the billing system invoices and what the ERP books. That accountability gap has a measurable price: industry research converges on 1 to 3 percent of annual revenue going unbilled or misbilled in companies with complex pricing (McKinsey, 2023). For a company at $30M ARR, that is between $300,000 and $900,000 per year circulating in a space no one is systematically watching.
The goal here is not to assign blame. It is to map how responsibility actually falls in practice, identify where organizational friction concentrates, and propose three models calibrated to company size.
How responsibility actually divides, not how it should
In a mid-market company without a formalized RevOps function, responsibilities distribute as follows in practice.
The Controller is the person who produces the reconciliations. They extract data from the ERP, compare it against issued invoices, and flag discrepancies. They do this under the time pressure of month-end close, using tools that do not give them native access to the CRM. Their view is financial and retrospective: they see what was billed, not what should have been billed according to contracts currently in force.
The CFO holds ultimate responsibility for financial accuracy and compliance. In theory, they should ensure the CRM-billing-ERP chain is coherent. In practice, a mid-market CFO is simultaneously managing cash flow, bank relationships, financial planning, board reporting, and team development. Revenue reconciliation is on the priority list, rarely at the top.
The sales lead or head of Revenue Operations manages the CRM. They see signed contracts, renewals, amendments. They do not typically notify Finance when a contractual condition changes, because that is not perceived as part of their role, and no process systematically requires it.
The structural result of this division: Finance sees discrepancies in accounting exports but has no access to the CRM to understand their cause. The commercial side sees anomalies in the CRM, such as a client whose terms were amended, but does not report them to Finance consistently. The information needed to close the loop is held by two teams that do not naturally speak the same language and have no defined coordination process.
Where the friction concentrates: Finance does not speak CRM
This is not a goodwill problem. It is a tooling and organizational convention problem.
The Controller works in the ERP. Their native instruments are accounting journals, aging reports, account-level reconciliations. Those instruments do not give them direct access to the contractual logic sitting in the CRM: which discounts were granted, which indexation clause applies to a particular renewal, which variable usage component was consumed and how it should be billed.
The sales team works in the CRM. Their native instruments are pipelines, opportunities, contracts. They do not see issued invoices or accounting entries. They do not know, except in unusual cases, whether the invoice sent to their client accurately reflects the commercial terms they negotiated.
The gap between these two worlds is where revenue leakage compounds. An amendment not communicated to Finance. A quarter-end discount forgotten at the next billing cycle. A volume threshold crossed that should have triggered a pricing step-up, not detected because no one had a consolidated view of both data sources.
In companies with a formalized RevOps function, generally starting at around 20 sales reps, RevOps structurally bridges CRM and Finance. But even in those configurations, reconciliation often remains manual for lack of an automated tool: RevOps produces exports, Finance compares them, and the matching happens in spreadsheets. The coordination exists, but it remains brittle and time-consuming.
Three organizational models by company size
There is no universal model, but three configurations cover the large majority of situations encountered in mid-market.
Under $50M ARR: Controller supported by an automated reconciliation tool
At this scale, a dedicated RevOps hire is rarely economically justified. The right configuration is a Controller whose scope explicitly includes revenue reconciliation, supported by a tool that bridges the CRM, billing platform, and ERP.
The tool does not replace the Controller's judgment: it gives them the visibility they currently lack. It aggregates data from multiple sources, automatically detects discrepancies between what was contractually expected and what was actually invoiced, and produces targeted alerts that let the Controller focus on genuinely problematic cases rather than comparing exports line by line.
In this model, the CFO validates decisions on the most significant discrepancies and oversees the process. They are not in the daily operational loop but are kept informed of trends and recurring anomalies through a regular summary.
$50M to $200M ARR: Controller, RevOps, and an alerting tool
At this scale, a RevOps function or equivalent is generally in place. The model evolves: RevOps ensures data integrity in the CRM and manages the link to Finance, the Controller handles detected discrepancies and produces analysis, and the CFO makes decisions on substantive issues including repricing, client disputes, and process adjustments.
The tool plays a coordination role in addition to detection. It needs to route alerts to the right person based on the nature of the discrepancy. A discrepancy on a renewal contract surfaces to RevOps for CRM verification. An unreconciled accounting entry surfaces to the Controller. A discrepancy above a defined threshold triggers a CFO alert.
This model only works when responsibilities are precisely defined. RevOps and the Controller need to know exactly who handles which type of discrepancy, within what timeframe, and with what documentation of the decision taken.
Above $200M ARR: dedicated Revenue Operations team
Beyond $200M ARR, pricing complexity and transaction volume typically justify a dedicated Revenue Operations team, distinct from commercial RevOps. This team's exclusive mandate is ensuring coherence across contractual commitments, invoicing, and accounting.
In this configuration, the Controller retains ownership of accounting and compliance. The CFO oversees Revenue Integrity policy and arbitrates complex cases. The Revenue Operations team is the daily process operator.
This is the large-enterprise model. It is included here to mark the trajectory, not as a target for smaller companies.
What stays constant regardless of size
All three models share one requirement that company size cannot eliminate: a defined process that specifies precisely who does what.
That process must answer four questions without ambiguity.
Who detects discrepancies? Detection must be automated, or at minimum anchored in a recurring control point with a defined frequency. "We catch it when it surfaces" is not a detection process.
Who analyzes discrepancies? Analysis requires a cross-functional view of CRM and accounting data. It should be assigned to whoever has access to both sources, or can obtain them quickly. In smaller organizations, that is typically the Controller with input from the relevant account owner.
Who corrects, and in which system? Correcting a discrepancy may require action in the CRM (updating contractual terms), in the billing platform (issuing a corrective invoice), in the ERP (posting an adjustment entry), or in all three. It must be clear in advance who is authorized to intervene in each system.
Within what timeframe? An unresolved discrepancy generates two problems: it creates a billing statute of limitations risk, and it contaminates interim financial statements. Resolution timelines must be defined, not assumed.
Without documented answers to these four questions, known to every party involved, the organizational model chosen, whether the first, second, or third, remains fragile. Revenue Integrity is not an org chart question. It is a process question.