Revenue tie-out
The customer file counts only once its recognized revenue agrees with the P&L, month by month, with billing timing shown separately.
Also Tie-out · Revenue reconciliation · Billed vs recognized vs reported
Every report reconciles recognized revenue to reported revenue, month by month, and separately bridges billed to recognized so that timing differences are visible rather than netted. A report built from a file that does not tie to the financial statements is not complete under this standard.
- Formula
gap = reported − recognized · billing timing = billed − recognized- Unit
- currency · % of reported
- Bounded
- n/a
- Defaults
- warn when the gap exceeds 2% of reported · pause-held MRR isolated
- Biggest lever
- Comparing all-types recognized against a recurring-only reported figure — manufactures a gap the size of the non-recurring business
- Read with
- MRR · ARR · The register
- Appears in
- Data room · Quality of earnings · Monthly close
- Switches
- 1 · 0 locked — see the choices
What it measures
Every metric in this standard is computed from a customer-level revenue file. That file is an operational export. It has no inherent authority: it was not audited, it may exclude entities, it may include revenue the accounts treat differently, and it may simply be incomplete.
Tie-out is the step that gives the file standing. It asks: does the sum of the customer-level data agree with the revenue the company reports? If it does not, every downstream metric — ARR, retention, cohorts, concentration — is computed on a population that does not match the business being discussed, and the size of the mismatch bounds how much any of them can be trusted.
This is the check most often skipped in self-prepared metrics reports, and the first one an experienced diligence reader turns to. Skipping it does not remove the discrepancy; it removes the disclosure.
How it is computed
Three quantities per month, from the same customer-month data:
- Recognized — the rev-rec view: recurring revenue with prepaid contracts spread over their term and prorated months as billed, plus usage, services, one-time, transactional, credits and other non-recurring. This is the figure that should agree with the P&L.
- Billed — raw billed amounts at the period they were invoiced, lump sums intact.
- Reported — monthly revenue as stated by management, supplied separately.
From these:
- Gap = reported − recognized, in currency and as a percentage of
reported. Months where the absolute relative gap exceeds
thresholds.tieout_gap_warnare flagged. - Billing timing = billed − recognized. Not an error: it is prepayment and proration, and it should be large in a business that bills annually in advance. A billing-timing line near zero in an annual-billing business is itself a signal that lump sums were not spread.
- Pause-held MRR — MRR held through qualifying pauses, which by design appears in the run-rate series and not in recognized revenue. Isolating it explains a gap between run-rate and rev-rec views that would otherwise look like an error.
Where no reported financials are supplied, the gap column is empty, the table says so plainly, and the limitation is recorded in the register. The tie-out is never silently omitted.
Worked example
| Month | Recognized | Reported | Gap | Gap % | Billed | Timing |
|---|---|---|---|---|---|---|
| Jan | 100,000 | 100,000 | 0 | 0.0% | 340,000 | +240,000 |
| Feb | 102,000 | 102,000 | 0 | 0.0% | 12,000 | −90,000 |
| Mar | 104,000 | 118,000 | 14,000 | 11.9% | 105,000 | +1,000 |
January and February are healthy: recognized ties exactly, and the large billing swing is annual invoicing being spread correctly.
March is the finding. A 14,000 gap at 11.9% means the P&L contains revenue the customer file does not — a business line excluded from the export, a non-customer revenue stream, an acquired entity not yet in the operational system, or a manual accounting adjustment. Until it is explained, every March metric rests on 88% of the actual revenue base, and the report must say so.
The choices that change the number
- Which reported figure is used. Total revenue, or recurring revenue only. Comparing recognized (all types) against a recurring-only reported figure manufactures a gap the size of the non-recurring business.
- Contract data availability. Without contracts, prepaid lump sums cannot be spread and recognized approaches billed — which widens the gap against a P&L that does spread them. The absence of contracts is thus visible in the tie-out, not only in the register.
- Cutoff alignment. A data cutoff mid-period against a reported figure for a full period produces a gap that is purely a boundary artifact.
How it is misread
A gap treated as an error to be plugged. The gap is a finding. Adjusting the data to match the P&L destroys the only independent check in the report.
Billing timing read as a discrepancy. It is the expected consequence of annual billing and should be large; the question is whether its pattern matches the stated billing terms.
A perfect tie treated as complete validation. Tie-out proves the file’s totals agree with reported totals. It says nothing about whether revenue is attributed to the right customers or the right months within those totals — a file with two customers’ revenue swapped ties perfectly and produces entirely wrong retention.
No tie-out at all, presented as a clean report. The absence is the finding.
What it cannot tell you
Tie-out compares the operational file to management’s reported figures. It cannot validate the reported figures themselves — that is what an audit is for — and it cannot detect an error that exists identically in both. It establishes consistency, which is a necessary condition for trusting the metrics and not a sufficient one.
How to state it
A disclosure that travels with the number. Replace the braces; keep the parenthesis.
Tie-out: recognized {x} vs reported {y}, gap {z}% (SoF Standard v1.0: monthly · billed-to-recognized bridged) Before you quote it
- Every month reconciled, gaps explained rather than plugged?
- Reported figure is total revenue, matching the file's scope?
- Billing timing large and positive in prepaid months?
- Cutoffs aligned?
Related questions
- Why doesn't ARR tie to GAAP revenue?
- Because they are different quantities. ARR is a run rate; recognized revenue is a flow that includes services, usage, one-time fees, prorations and credits; billed revenue is what was invoiced. The tie-out reconciles recognized to reported and bridges billed to recognized, so the differences are explained rather than netted.
- Should I bother reconciling the customer file to the P&L?
- Yes, monthly. The customer file is an operational export with no inherent authority; the tie-out is what gives it standing. Under this standard a report built from a file that does not tie is not complete, and a gap above two percent in any month is flagged.
- Is a tie-out gap an error?
- It is a finding. A P&L that contains revenue the customer file does not points at an excluded business line, an acquired entity, a non-customer revenue stream or a manual adjustment. Adjusting the file to match the P&L destroys the only independent check.
- Why is billed revenue so different from recognized?
- Annual invoicing. Billed minus recognized should be large and positive in months with prepaid invoices and negative afterwards. A billing-timing line near zero in an annual-billing business means the lump sums were never spread.
- What does a quality-of-earnings review do with the customer file?
- Rebuilds ARR from it, ties it to the financial statements, then samples the rest. Buyers routinely find management ARR overstated where the file was never tied. A seller who ran the tie-out first knows the gap and its explanation before the buyer does.
- Does a perfect tie mean the metrics are right?
- No. It proves the file's totals agree with reported totals. Two customers' revenue swapped ties perfectly and produces entirely wrong retention. Tie-out is a necessary condition, not a sufficient one.
Strategy of Finance. “Revenue tie-out.” SoF Standard Definitions v1.0 (2026-09-18). https://www.strategyoffinance.com/standards/revenue-tie-out/