CRM-to-billing reconciliation explained

CRM-to-billing reconciliation is the regular matching of what the CRM shows as sold against what the billing system has invoiced, deal by deal or customer by customer. Every won deal belongs to one or more invoices, every invoice belongs to a deal or contract, and every difference is explained or resolved. It is the same technique as a bank reconciliation in accounting, applied to the handover from sales to finance, and it is the most direct way to find revenue that was sold but never invoiced.

Why is CRM-to-billing reconciliation needed?

Between the sale and the invoice there is a handover. A salesperson marks a deal as won in Salesforce, HubSpot or Pipedrive. Then someone has to create an invoice or subscription in Exact, AFAS, Xero, NetSuite or a subscription platform, with the right amount, the right start date and the right customer. Sometimes that happens through an integration, often through an email, a form or a conversation.

Every handover can go wrong. The salesperson has already moved on to the next deal, the email lands in the wrong inbox, the amount on the form differs from the quote, or the start date is entered later than agreed. Nobody notices, because both systems do what they should: the CRM shows a won deal, and billing invoices whatever is in it. Only when you set the two side by side do you see that they do not match. Reconciliation is that setting side by side, systematically and regularly.

How is it different from a one-off check?

A one-off check, as described in how to check CRM against billing, shows what went wrong over a period. Reconciliation is a process: it happens every month or more often, explained differences are recorded so they do not come back, and open differences are tracked until they are resolved. The first time is a check. From the second time on, it is a reconciliation.

How does CRM-to-billing reconciliation work?

Step 1: decide on the key

You need to be able to link deals and invoices. The best key is a unique number present in both systems: an order, project or contract number recorded in the CRM at won and repeated on every invoice. Without one, you match on customer plus amount plus period, which works but is less reliable.

Step 2: set the expectation per deal

What should be invoiced for each deal, and when? For a one-off deal that is simple: the deal amount, within an agreed period after won. For instalments, subscriptions and projects, you need an invoicing schedule. Without an expectation you cannot establish whether there is a difference.

Step 3: pull both sides

From the CRM: all deals won in the period, plus all earlier won deals whose invoicing is not yet complete. From billing: all invoices for the period, with their lines.

Step 4: match and compare

For each deal, find the matching invoices and compare expected with actual. For each invoice, check whether a deal or contract belongs to it.

Step 5: classify the differences

Step 6: record and follow up

Every difference gets a category, an owner and a status. Explained differences are marked so they do not reappear next month. Open differences stay on the list until they are resolved.

Step 7: close the period

At the end of the reconciliation you know: this much won, this much invoiced, this much still to be invoiced on schedule, this much explained, this much open. The open amount is your direct risk.

What about recurring revenue?

With subscriptions and fixed-term contracts, one invoice per deal is not enough. The question is not only whether the first invoice was raised, but whether the right amount is invoiced every following month, and whether upgrades, downgrades and cancellations from the CRM reach billing. That calls for a reconciliation at the level of changes: opening MRR, plus new and expansion, minus contraction and cancellation, against what was actually invoiced. That approach is worked out in how to find errors in recurring revenue.

Worked example

Worked example: suppose you win an average of 50 deals a month with an average value of EUR 18,000, together EUR 900,000. The first monthly reconciliation shows:

• 38 deals fully invoiced.
• 7 deals with instalments still running: expected, no action.
• 2 deals wrongly marked as won: update the CRM.
• 2 deals won and delivered, not invoiced: together EUR 31,000.
• 1 deal under-invoiced, a forgotten line of EUR 4,500.

Open: EUR 35,500 in one month. If that pattern repeats every month and nobody sees it, that is well over EUR 400,000 a year. With reconciliation, most of it is still invoiced, because it is spotted within a month rather than at year-end or never. The figures are an example, not an average.

What do you need?

• An export or connection from both systems. Read access is enough.
• A key or a reliable matching rule.
• An invoicing schedule per deal or a fixed rule.
• An owner. Often someone in finance or RevOps, with the authority to ask sales for explanations.
• A fixed date. For example the fifth working day of every month, before the monthly report.

At first this can be done in Excel or Power BI. As volumes grow, it pays to automate the matching and the first classification, so the owner only has to assess the real differences. AI helps mainly with linking records that have no shared key; see can AI see when CRM and billing do not match. Checks on billing itself, independent of the CRM, complement this: how to check billing automatically.

Reconciliation or integration?

Not one or the other. An integration between CRM and billing prevents many differences by passing won deals through automatically. But an integration can fail, fields can be empty, and exceptions do not fit the rule. Reconciliation catches what the integration misses. Conversely, reconciliation shows where an integration would pay off most. The two reinforce each other. How to set up the integration itself is covered in how to connect CRM to billing.

The pattern of deals marked as won that never become an invoice is worked through, with the numbers, on the use cases page. Reconciliation is the foundation of a single source of truth for revenue: without it, the CRM and the accounts each keep telling their own story.

Frequently asked questions

How often should I reconcile?

Monthly is the minimum. With many deals or recurring revenue, weekly or daily is better, because a difference is spotted sooner and is easier to put right.

Who should do it, sales or finance?

Finance or RevOps carries it out, because that is where the invoice data and the discipline of reconciling sit. Sales provides the explanations. Responsibility for resolving a difference lies with the deal's account owner.

What if more than half of the deals show a difference?

Then your key or your expectation is not good enough. Start by recording invoicing schedules and a unique number per deal. The number of differences then falls quickly, and what remains is what matters.

Is reconciliation the same as an audit?

No. Reconciliation is a recurring process between two systems. An audit is a one-off, broader review of processes and risks. An audit can reveal that reconciliation is missing; reconciliation stops the same problem coming back every month.