A ledger, not a dashboard.
Finance solved its trust problem 600 years ago with double entry bookkeeping. Every transaction was recorded twice, so errors had nowhere to hide.
Revenue operations still runs on single entry.
The CRM records its version of the deal. The ERP records another. Billing keeps a third, and the channel program a fourth. Each system is internally consistent, yet nobody is responsible for whether they agree. We built an entire RevOps discipline around pipeline dashboards and forecast accuracy, and we left everything after the signature essentially unaudited.
Where the money actually goes
Not in dramatic failures, but in small divergences between systems that each look fine on their own. A quote says one number and the order is entered at another. A discount runs deeper than peer deals, approved by habit rather than by decision. A chargeback gets paid because verifying it costs more than the credit memo. An invoice is billed off the contract price, and customers never call when the error favors them.
Across our engagements with configure-to-order manufacturers, our planning rates — engagement-derived, not survey statistics — put configuration and discounting errors at 3% of quoted value, and channel claim leakage at 5% of channel revenue with roughly 40% recoverable once claims are validated line by line.
The ledger, itemized
This is why every Nteli engagement starts with a Leak Ledger: join every quote, order, invoice and claim on one deal ID, then itemize what is slipping, line by line. The model below shows what the ledger looks like for an illustrative mid-market manufacturer — around $90M revenue, dealer and distributor channels, an acquired division on a second ERP.
| Ledger line | Leak | Recoverable |
|---|---|---|
| Wrong configurations reworked after the order | $412K | $338K |
| Required options and adders left off the quote | $286K | $251K |
| Discounting beyond peers on similar deals | $538K | $392K |
| Order-entry errors against the accepted quote | $174K | $161K |
| Orders won below the price quoted | $221K | $168K |
| Invoices billed off the customer's contract price | $196K | $172K |
| Pass-through costs absorbed, no surcharge applied | $143K | $119K |
| Service and spare parts quoted off the price book | $127K | $94K |
| Rebates and commissions overpaid | $264K | $211K |
| Channel deductions and chargebacks unrecovered | $318K | $233K |
| Total | $2.68M | $2.14M |
Almost none of this appears on any report, because every report is drawn from a single system's version of the truth. The divergences live between the systems — which is exactly where nobody looks.
Quote to cash is a reconciliation discipline
This is why I believe quote to cash is not a software category. The category fragmented years ago: CPQ vendors solved quoting, billing vendors solved invoicing, rebate vendors solved programs. Each silo got better, and the joins between them stayed unowned.
The unit of management is not the funnel stage or the invoice. It is the deal, threaded from quote to cash, with every line checked against the agreement behind it. A ledger, not a dashboard.
Recovery does not come from another dashboard. It comes from checks that run before the money moves: configurations validated against cited rules before the quote goes out, orders built from the accepted quote, invoices matched to the contract behind them, claims matched to agreements or disputed with evidence. The result is a recovery report a CFO can trace, line by line, down to the deal.
Double entry did not make merchants better at selling. It made their numbers trustworthy enough to build banks on. Revenue operations should be held to the same standard.
If you cannot trace a dollar from quote to cash, you do not have revenue operations. You have revenue observations.
Build your own ledger.
The Leak Ledger Workshop: one day, your CRM and ERP exports, a dollar ledger of what is leaking between your systems — itemized like the table above, with your numbers.