Three systems, three versions of one customer, and all of them reported honestly. Why revenue risk hides in the gaps between them, and what it takes to close those gaps.
Ask three people in a quarterly review to describe the same account and you will get three answers. Revenue says the renewal is in negotiation and closing next month. Support says the account has had escalations open for weeks. Finance says the contract renews earlier than that and the invoice is overdue.
Nobody is wrong. Each is reading their own system correctly. The problem is that no system holds the whole account, and the work of assembling it falls to whoever has time — usually days later, usually after the decision that needed it has already been made.
Why the gap exists at all
The three systems were bought at different times to solve different problems, and each defines a customer differently. A CRM organises around the opportunity, because that is what a seller works. A support desk organises around the requester, because that is who files a ticket. A finance system organises around the legal entity, because that is who signs and pays.
Those are three different objects wearing the same name. The mismatch shows up in the ordinary details first:
- Legal name. Finance holds the entity on the contract; the CRM holds whatever the seller typed.
- Renewal date. The CRM date is a forecast the seller maintains. The contract date is a fact.
- Hierarchy. One buying group can be several CRM accounts, several support organisations and one paying entity.
- Status. An account can be green in the CRM, red in the support queue and overdue in the ledger on the same afternoon.
Why it stays unsolved
Most attempts fail in one of two ways. Either the reconciliation is done by hand, which means it is accurate the day it is done and stale the day after, or a system quietly picks a winner and overwrites the others, which produces one clean answer and destroys the evidence that there was ever a disagreement.
The second failure is worse than the first, because the disagreement is the signal. An account whose renewal date differs by two weeks between the CRM and the contract is telling you something specific about how well that relationship is understood internally.
What closing the gap actually requires
- Match accounts across systems that share no common identifier, and be explicit about how confident each match is.
- Resolve each field to the system that is authoritative for it — the contract for renewal dates and legal names, the support desk for ticket volume — rather than picking one winner per record.
- Keep every disagreement. Surfacing a conflict is more useful than silently resolving it.
- Refresh it on a schedule. A reconciliation is a position, not a snapshot, and it is only worth acting on if it reflects this morning.
Everyone was telling the truth. Nobody was looking at the same account.
That is the gap worth closing, and closing it is upstream of every other question — which accounts are at risk, what that risk is worth, and who needs to hear about it while there is still time to act.
See it against your own book.
Thirty minutes to walk through what your executives would receive, what it takes to run, and whether your book is a fit.