CRM vs ERP: where does your real revenue come from?
Why your CRM and ERP show different revenue figures, which figure is right for what, and how to use the difference between them to find leaks.
Your real revenue comes from the ERP and the accounts, not from the CRM. The CRM records what was sold and what sales expects; the ERP records what was delivered and invoiced, and only the latter turns into money. Yet the CRM still matters: the difference between what the CRM shows as won and what the ERP shows as invoiced is exactly where revenue leaks. Look at only one of the two and you miss that difference.
Two systems, two kinds of revenue
A CRM such as Salesforce, HubSpot or Pipedrive is built to manage sales. It records leads, opportunities, stages and deal values. When a deal moves to won, it counts towards sales revenue. That deal value is an agreement, or an estimate of an agreement, at the moment the customer says yes.
An ERP such as SAP, NetSuite, Dynamics, AFAS or Exact is built to manage delivery. It records orders, deliveries, hours, projects, invoices and payments. Revenue in the ERP is what was actually charged, and in the accounts it is what counts as income in a period under the reporting rules.
| CRM | ERP and accounts | |
|---|---|---|
| What it records | Expectations and agreements | Deliveries, invoices, payments |
| When revenue counts | Deal marked as won | Invoice or recognition in the period |
| Who fills it | Sales | Operations, finance |
| How precise | Depends on salespeople's discipline | Controlled, tied to the general ledger |
| What you use it for | Steering pipeline and sales | Financial reporting, cash flow |
The CRM answers "how much did we sell?". The ERP answers "how much did we invoice?". Those are different questions, and both answers are true. Why the data in a CRM is fundamentally different from financial data is explained in why CRM data is not the same as financial data.
Why do CRM and ERP figures differ?
If the two systems measured the same thing with a delay, the difference would disappear on its own. It does not, for a handful of reasons that recur in almost every B2B company.
Timing. A EUR 90,000 deal won in March may be invoiced in three instalments, in April, June and September. The CRM counts March, the ERP three other months.
Scope changes. After the agreement, the job changes. Something is dropped, something is added. The ERP invoices what is delivered. The CRM stays at the original deal value, because nobody updates a deal once it is won.
Deals that fall through. A deal is marked as won, but the customer pulls out before anything is delivered. In the CRM it stays won; in the ERP nothing ever appears.
Revenue that never reaches the CRM. Extra work, repeat orders, orders that come straight in through the sales office. The ERP invoices them; the CRM does not know about them.
Different customer structure. The CRM has one account for a group. The ERP has five debtors, one per operating company. Revenue per customer is something different in each system.
Deals won and never invoiced. The leak. The deal is won, delivery has happened or is under way, but no invoice was ever raised, or one that was too low.
The first five can be explained. The sixth is money you have earned and are not receiving. The problem is that they are all mixed together in a total comparison. A EUR 400,000 difference between CRM and ERP over a year may be entirely timing, or half leakage. Without looking deal by deal, you cannot tell. The leakage side of this difference is covered in revenue leakage between CRM and billing.
Which figure do you use for what?
A practical split:
- For the annual accounts, VAT and the bank: the accounts. No discussion.
- For cash flow planning: invoiced revenue and outstanding receivables from the ERP, supplemented by the invoicing schedule of running contracts.
- For steering sales: the CRM, with the agreement that won deals are reconciled against billing.
- For forecasting: the CRM for what is still to come, the ERP for what is already in. A forecast based only on CRM data structurally overestimates if deals are marked as won that are never invoiced. See CRM forecast vs actual revenue.
- For customer value and retention: the ERP or billing, because that is where you see what a customer really pays, across all operating companies.
The underlying question of which system is the source for which data item goes beyond revenue alone. It is worked out in which data source leads for revenue.
Worked example
Worked example: suppose the CRM shows EUR 11.4 million in won deals for last year, and the ERP EUR 10.6 million in invoiced revenue. A difference of EUR 800,000. After a deal-by-deal analysis:
| Cause | Amount |
|---|---|
| Instalments still to be invoiced this year | EUR 420,000 |
| Deals marked as won that did not go ahead | EUR 150,000 |
| Scope reduced after agreement | EUR 90,000 |
| Revenue in the ERP without a deal in the CRM (extra work, repeat orders) | minus EUR 110,000 |
| Won and delivered, not invoiced or under-invoiced | EUR 250,000 |
The last line is the leak: EUR 250,000, more than 2 percent of invoiced revenue. Part of it may still be invoiceable. The other lines tell you something about the quality of your CRM: deals that did not go ahead belong on lost, and extra work belongs in the CRM too if you want to measure customer value.
This is an example. In your business the proportions may be entirely different.
How do you keep the difference under control?
- Record per deal when and how it will be invoiced. An invoicing schedule as a field in the CRM, or as a link to the contract.
- Have every won deal refer to an order or project number in the ERP. That is the key for setting the two side by side.
- Reconcile monthly. All won deals from the period against the invoices. Every difference gets a reason or an action.
- Update deals after they are won. Scope changes and cancellations belong in the CRM too, otherwise the difference grows every year.
- Integrate where you can. An integration that automatically creates won deals as orders in the ERP prevents the most common forgotten handover. How to go about it is covered in how to connect CRM to ERP.
Why do you need both?
It is tempting to say: the ERP is the truth, so ignore the CRM. But the ERP only knows what was invoiced. It does not know what was sold and still has to be invoiced, and it does not know what was sold and forgotten. The ERP shows what is coming in. The CRM shows what should be coming in. The difference between the two is what you are looking for.
A single source of truth for revenue therefore does not come from choosing one of the two, but from reconciling them. That is the subject of how to get a single source of truth for revenue.
Frequently asked questions
Should my CRM show the same revenue figure as my accounts?
No. They measure something different, at a different moment. What you do need is to be able to explain the difference deal by deal.
Can I not just invoice from the CRM?
Some CRMs have invoicing modules, and for small companies with simple products that can work. Once you have projects, stock, instalments, multiple entities or complex VAT, you need an ERP or accounting package. Reconciliation then remains necessary.
Which figure do I report to the board?
Invoiced or recognised revenue from the accounts for the result, and booked revenue from the CRM for commercial progress. Show both, with the difference and the explanation. That stops two stories circulating.
How often should I reconcile CRM and ERP?
Monthly is a good minimum. With many deals or recurring revenue, weekly or continuously is better.
More in this cluster
- How do you get a single source of truth for revenue?Start here
- Why CRM data is not the same as financial data
- CRM-to-billing reconciliation explained
- How do you connect CRM to billing?
- How do you connect CRM to ERP?
- How do you check CRM data automatically?
- How do you check billing automatically?
- How do you connect sales data with financial data?