Why CRM data is not the same as financial data
The five fundamental differences between your CRM and your accounts, why they matter for revenue and forecasts, and how to work with them.
CRM data is not the same as financial data because a CRM records expectations and the accounts record facts. A deal value in the CRM is what a salesperson thinks a customer will pay, entered at a moment when not everything is settled and never checked afterwards. An amount in the accounts is what was invoiced or received: checked, tied to a general ledger and unchangeable once the period is closed. Both are valuable, but whoever treats CRM data as financial data makes decisions on figures that do not exist.
What are the differences between CRM data and financial data?
1. Who enters it and why
In the CRM, a salesperson enters the data. Their goal is to win a deal and manage their pipeline. Fields that do not serve that goal are often left empty or estimated. Deal values are filled in at the start and rarely updated afterwards.
In the accounts, finance enters the data, or it comes in automatically from billing and the bank. The goal is accurate reporting. Every amount has to be explainable, and is ultimately looked at by an auditor.
2. When something counts
A deal counts in the CRM the moment it is marked as won. That moment is decided by the salesperson, sometimes at the end of a quarter to hit a target. In the accounts, revenue counts once it has been invoiced or the service has been delivered, under fixed rules. The same transaction therefore often falls in a different month, and sometimes in a different year.
3. How final it is
A CRM record can always be changed. A deal value can be adjusted after the fact, a date moved, a deal switched from won to lost. There is often no trail of who changed what and when. A posted invoice in the accounts is not changed: you credit it and post it again. The history stays visible.
4. How detailed it is
A deal in the CRM often has one amount, sometimes a few product lines. An invoice has lines with item, quantity, price, discount, VAT and period. A EUR 60,000 deal may break down in billing into a one-off implementation, an annual licence and monthly maintenance, each with its own timing and its own accounting treatment.
5. What it covers
The CRM contains only what went through sales. Extra work, repeat orders, orders through a web shop or the sales office, indexation and subsequent adjustments are often not in it. The accounts contain everything that was invoiced, however it came in.
Why does your CRM not show your full revenue picture?
It follows from those five differences that the CRM gives a limited view of your revenue. It shows what sales has done and expects. It does not show:
- What was actually invoiced. A deal can be won and never invoiced, or invoiced for less than the deal value.
- What a customer brings in overall. Because extra work, repeat orders and recurring revenue often run outside the CRM.
- What happens after the sale. Upgrades, downgrades, discounts, indexation, cancellations of individual components. The CRM stops at won.
- Whether anyone is paying. A customer with overdue invoices looks like any other customer in the CRM.
- What the margin is. The CRM knows the selling price, not the cost of delivery.
A managing director who steers by the CRM dashboard sees a company that sells more than comes in, customers who look healthier than they are, and a pipeline that feels like revenue. Why that last point is dangerous is explained in why pipeline is not revenue. The reverse is true as well: the accounts do not show what was sold and is still to come. Each system has a blind spot exactly where the other one sees. The practical difference between the two systems is set out in CRM vs ERP: where does your real revenue come from.
Where does it go wrong in practice?
- Forecasts based on CRM data. The forecast says the quarter will be hit. Two months later the accounts show a shortfall, because some of the won deals were invoiced later or for less.
- Bonuses based on won deals. Salespeople are rewarded on deal value in the CRM. Deals that are never invoiced still earn a bonus. That is a direct cost leak and an incentive to mark deals as won too early.
- Customer value based on the CRM. A customer looks small because they have one deal, while through repeat orders and extra work they are one of your largest buyers. Or the other way round.
- Board reports with two numbers. Sales and finance come with different revenue figures, and the meeting is about which figure is right rather than what to do about it.
Worked example
Worked example: suppose your sales team is paid 5 percent of won deal value. The CRM shows EUR 6 million in won deals. Reconciliation with billing shows that EUR 300,000 of that was never invoiced: deals that did not go ahead but stayed marked as won, and scope reductions that were never processed.
- Bonus paid on uninvoiced revenue: 5 percent of EUR 300,000 is EUR 15,000.
- On top of that: if part of that EUR 300,000 was delivered but not invoiced, that is direct revenue leakage.
The first is a cost that disappears once you tie bonuses to invoiced or collected revenue. The second you only find by reconciling CRM and billing deal by deal. Both amounts are example figures.
How do you work with the difference?
The aim is not to make the CRM look like financial data. That will not work and is not necessary. The aim is to know what each system tells you and to be able to connect the two.
- Call the numbers by their name. "Booked revenue" for the CRM, "invoiced revenue" for billing. Never just "revenue".
- Make the link per deal possible. An order, project or contract number in the CRM that also appears on the invoice.
- Update deals after they are won. Scope changes and cancellations belong in the CRM. Agree who does this.
- Check the fields billing needs. Customer, amount, term, product lines. Preferably automatically; see how to check CRM data automatically.
- Reconcile monthly. Won deals against invoices, deal by deal, with a reason for every difference.
- Bring the two together in one view. Per customer: sold, invoiced, paid. See how to connect sales data with financial data.
What does a CRM do well?
The CRM is not the problem. It is the best system for what it does: recording the commercial relationship, steering sales, knowing who discussed what with whom. It is also the only place that shows what is still to come. It only becomes a problem when it is used for questions it cannot answer. Where the line lies between what a CRM can do and what a Revenue Intelligence approach adds is covered in Revenue Intelligence vs CRM.
A single source of truth for revenue comes from connecting the CRM and the accounts, not from choosing one of them. How to build that is explained in how to get a single source of truth for revenue.
Frequently asked questions
Can I use the CRM for revenue reporting to the bank or the auditor?
No. The accounts are the only source for that. The CRM can add information about expected development, but not about realised revenue.
Should the deal value in the CRM always equal invoiced revenue?
Not necessarily at the same moment, but over the life of the deal, yes. A EUR 50,000 deal should ultimately produce EUR 50,000 in invoices, or an explanation of why not.
How do I stop salespeople marking deals as won too early?
By defining won (for example: a signed contract or order confirmation is in place), by making fields mandatory at that stage, and by not basing bonuses solely on deal value.
Is it a problem if extra work is not in the CRM?
For invoicing, no, as long as it is in the ERP. For customer value and upsell, yes: sales then does not see what a customer really buys, and misses signals for expansion.
More in this cluster
- How do you get a single source of truth for revenue?Start here
- CRM vs ERP: where does your real revenue come from?
- 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?