M&A · Exit Readiness & Vendor Due Diligence

Revenue Proof for Recurring and Project Businesses: Contract-to-Cash Vendor Diligence

An evidence architecture for customer, contract, delivery, billing and collection quality.

Revenue Proof for Recurring and Project Businesses: Contract-to-Cash Vendor Diligence
Quick answer

Trace recurring and project revenue from customer and contract through delivery, billing, ledger and cash, then stress durability, margin and collectability.

Abstract

Revenue diligence becomes difficult when commercial systems describe bookings, delivery, billing and cash differently. Recurring businesses may blend contracted, renewable, repeat, usage and services revenue. Project businesses may recognise progress before billing, carry unpriced change, depend on estimates to complete and collect through retentions or disputed claims. This paper develops a contract-to-cash vendor-diligence architecture that creates transaction-level revenue proof across both models.

It starts with controlled customer and contract populations covering legal customers, groups, channels, signed agreements, statements of work, purchase orders, changes, renewals and terminations. Source systems spanning CRM, pricing, contracts, projects, delivery, billing, ledgers, collections and banks are frozen and ranked. Data lineage links each customer promise to contract, performance, acceptance, invoice, ledger and cash. Revenue streams are classified through a controlled dictionary.

Contract analysis tests existence, rights, payment terms, commercial substance, collectability, combinations and modifications. Transaction price analysis covers fixed fees, usage, indexation, rebates, credits, penalties, claims and financing effects. Allocation and recognition analysis identifies performance obligations, standalone selling prices, point-in-time or over-time treatment and the evidence supporting progress.

Project analysis tests budgets, commitments, labour, procurement, forecast-at-completion, milestones, change orders, claims and liquidated damages. Recurring analysis rebuilds annual and monthly recurring revenue through opening, new, expansion, contraction, churn, reactivation, price and currency movements. Retention is measured by logo, gross revenue, net revenue, cohort and product. Usage revenue is traced from entitlements and metering through rating, billing and cash.

Bookings, backlog and pipeline remain separately defined. Principal-agent, channel, cut-off, credit-note and reversal tests address common quality failures. Receivables, unbilled revenue, contract assets, deferred revenue, advances and retentions are rolled forward and connected to subsequent collection. Customer concentration, pricing, discount and margin analysis links revenue growth to economic contribution. Bank receipts, gateway settlements and offsets corroborate the record.

A decision-led proof pack organises evidence around buyer questions. Downside analysis stresses renewals, churn, usage, backlog conversion, project completion, pricing, credit and concentration. The valuation map connects revenue durability, margin and cash conversion to forecast confidence while keeping transaction-specific price judgements separate. Five figures, five tables, eight frequently asked questions and twenty-six primary or authoritative sources support company-specific assessment.

Quantified figures are illustrative evidence indices rather than forecasts. The framework does not determine accounting treatment, audit evidence, assurance, valuation, tax, legal entitlement, contract enforceability or buyer reliance and does not replace authorised accounting, audit, legal, tax, valuation, commercial, operational or transaction advice.

JEL Classification: G34, M41, M42, L14, D82

Keywords: revenue diligence, contract to cash, recurring revenue, project revenue, ARR, backlog, M&A

This Matchpoint Insight presents the web edition of Matchpoint Partners' research. The supporting paper contains the full framework, structures, worked examples and source material.

Read the full research paper   Explore our M&A Exit Readiness practice

1. Define the revenue proof question

State which revenue claims buyers must verify across recurring, usage, project and transactional models.

The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a revenue-proof charter.

The principal failure occurs when reported revenue alone establishes quality. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.

The decision pack for define the revenue proof question should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.

2. Set the customer perimeter

Reconcile legal customers, groups, channels, geographies, products, projects and related parties.

The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a controlled customer master.

The principal failure occurs when the billing account uniquely identifies economic customers. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.

The decision pack for set the customer perimeter should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.

3. Set the contract perimeter

Identify signed agreements, statements of work, purchase orders, changes, renewals and terminations.

The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a contract population.

The principal failure occurs when the contract repository contains all enforceable terms. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.

The decision pack for set the contract perimeter should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.

4. Freeze source systems

Map CRM, configure-price-quote, contract, project, delivery, billing, ledger, collections and bank sources.

The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a source-system register.

The principal failure occurs when one commercial system contains the complete contract-to-cash record. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.

The decision pack for freeze source systems should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.

5. Create contract-to-cash lineage

Link customer promise, contract, delivery, acceptance, invoice, ledger and cash at transaction level.

The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a transaction lineage model.

The principal failure occurs when aggregate reconciliations prove individual revenue events. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.

The decision pack for create contract-to-cash lineage should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.

6. Reconcile revenue to the ledger

Bridge source transactions to subledgers, general ledger, consolidation and reported accounts.

The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a revenue reconciliation.

The principal failure occurs when total invoices equal recognised revenue. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.

The decision pack for reconcile revenue to the ledger should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.

7. Define revenue taxonomies

Classify recurring, usage, licence, service, project, milestone, maintenance and pass-through streams.

The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a controlled revenue dictionary.

The principal failure occurs when management labels are consistent across periods. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.

The decision pack for define revenue taxonomies should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.

8. Govern revenue data

Set field definitions, ownership, source priority, exception handling, version and approval.

The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a revenue-data control framework.

The principal failure occurs when spreadsheet cleaning creates durable data control. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.

The decision pack for govern revenue data should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.

Table 1. Revenue data control

FieldSource priorityControl
customerlegal and CRM mastergroup mapping
contractexecuted agreementversion control
deliveryoperational evidenceacceptance
cashbank settlementinvoice match

Illustrative analytical design; company-specific evidence and professional advice govern.

Figure 1. Contract-to-cash lineage
Figure 1. Contract-to-cash lineage

Values are illustrative evidence indices and require company-specific support.

9. Read the customer promise

Identify goods, services, access, integration, support, outcomes and customer options.

The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a promise-to-obligation map.

The principal failure occurs when the invoice description defines the performance obligation. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.

The decision pack for read the customer promise should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.

10. Test contract existence

Verify approval, rights, payment terms, commercial substance and collectability.

The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a contract-validity test.

The principal failure occurs when a signed document always establishes a valid revenue contract. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.

The decision pack for test contract existence should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.

11. Test contract combinations and modifications

Assess linked negotiations, scope changes, price changes, renewals and cumulative catch-up effects.

The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a modification decision tree.

The principal failure occurs when each purchase order is a separate accounting unit. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.

The decision pack for test contract combinations and modifications should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.

12. Determine transaction price

Reconcile fixed fees, usage, indexation, rebates, credits, penalties, claims and financing effects.

The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a transaction-price bridge.

The principal failure occurs when contract headline value equals transaction price. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.

The decision pack for determine transaction price should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.

13. Constrain variable consideration

Test probability, range, experience, reversals, disputes, service levels and customer behaviour.

The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a variable-consideration reserve.

The principal failure occurs when historical averages remove reversal risk. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.

The decision pack for constrain variable consideration should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.

14. Allocate price to obligations

Assess standalone selling prices, discounts, bundles, options and residual methods.

The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is an allocation evidence pack.

The principal failure occurs when invoice line allocation reflects economic value. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.

The decision pack for allocate price to obligations should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.

15. Prove delivery and acceptance

Connect service logs, shipments, milestones, certificates, customer acceptance and production evidence.

The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a delivery-and-acceptance ledger.

The principal failure occurs when billing proves completion. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.

The decision pack for prove delivery and acceptance should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.

16. Test timing of recognition

Distinguish point-in-time and over-time obligations using control, benefits, assets and enforceable payment rights.

The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a recognition-timing memorandum.

The principal failure occurs when project duration determines recognition pattern. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.

The decision pack for test timing of recognition should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.

Table 2. Recognition decision

QuestionRecurring modelProject model
promiseaccess or servicedeliverable or outcome
measuretime or usageinput or output
evidenceentitlement and logsmilestone and acceptance
riskchurn and creditsestimate and change

Illustrative analytical design; company-specific evidence and professional advice govern.

Figure 2. Recognition evidence
Figure 2. Recognition evidence

Values are illustrative evidence indices and require company-specific support.

17. Test project progress

Validate input, output, milestone and survey methods against actual performance and reliable measurement.

The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a progress-measurement model.

The principal failure occurs when cost incurred always measures customer value delivered. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.

The decision pack for test project progress should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.

18. Test project cost estimates

Reconcile budgets, commitments, labour, procurement, contingencies, change orders and forecast-at-completion.

The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a cost-to-complete model.

The principal failure occurs when historic margin is sufficient for remaining-cost estimates. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.

The decision pack for test project cost estimates should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.

19. Test contract assets and liabilities

Roll forward unbilled revenue, deferred revenue, advances, retention and billing schedules.

The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a contract-balance roll-forward.

The principal failure occurs when net balances reveal the underlying rights and obligations. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.

The decision pack for test contract assets and liabilities should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.

20. Test recurring-revenue definitions

Separate contracted recurring, renewable, repeat, usage and non-recurring components.

The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a recurring-revenue taxonomy.

The principal failure occurs when repeat revenue is economically recurring. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.

The decision pack for test recurring-revenue definitions should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.

21. Rebuild ARR and MRR

Trace opening, new, expansion, contraction, churn, reactivation, price and currency movements.

The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is an ARR movement bridge.

The principal failure occurs when period-end run rate explains annual recurring revenue. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.

The decision pack for rebuild arr and mrr should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.

22. Test renewals and churn

Measure logo, gross revenue, net revenue, cohort and product retention using controlled populations.

The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a retention cohort model.

The principal failure occurs when one retention percentage captures customer durability. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.

The decision pack for test renewals and churn should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.

23. Test usage and consumption revenue

Reconcile metering, entitlements, rated events, minimums, overages, credits and cash.

The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a usage-to-bill lineage.

The principal failure occurs when platform-generated usage is complete and accurate. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.

The decision pack for test usage and consumption revenue should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.

24. Test bookings and backlog

Separate signed value, cancellable value, funded backlog, options, pipeline and revenue timing.

The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a bookings-to-revenue bridge.

The principal failure occurs when bookings convert predictably into revenue. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.

The decision pack for test bookings and backlog should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.

Table 3. Forward revenue evidence

MeasureIncludedExcluded
ARRcontracted run rateone-time services
backlogenforceable valueunfunded options
bookingssigned orderspipeline
usagerated eventsforecasts

Illustrative analytical design; company-specific evidence and professional advice govern.

Figure 3. Forward revenue quality
Figure 3. Forward revenue quality

Values are illustrative evidence indices and require company-specific support.

25. Test project change orders

Classify approved, pending, disputed and unpriced scope with entitlement and collection evidence.

The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a change-order register.

The principal failure occurs when operational approval guarantees commercial recovery. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.

The decision pack for test project change orders should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.

26. Test claims and liquidated damages

Assess contractual entitlement, probability, measurement, counterclaims, caps and cash consequences.

The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a claims evidence matrix.

The principal failure occurs when management's best estimate belongs in revenue. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.

The decision pack for test claims and liquidated damages should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.

27. Test gross versus net

Assess control, inventory risk, supplier responsibility, pricing discretion and customer promise.

The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a principal-agent assessment.

The principal failure occurs when pass-through billings are always principal revenue. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.

The decision pack for test gross versus net should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.

28. Test channel revenue

Map reseller, distributor, marketplace, referral and agent terms through sell-in, sell-through and returns.

The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a channel evidence model.

The principal failure occurs when channel invoices prove end-customer demand. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.

The decision pack for test channel revenue should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.

29. Test cut-off

Trace delivery, acceptance, billing, credits, returns and cash around period ends.

The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a cut-off exception log.

The principal failure occurs when ledger close ensures correct revenue timing. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.

The decision pack for test cut-off should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.

30. Test credit notes and reversals

Analyse causes, timing, customers, products, projects, approvers and subsequent cash.

The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a reversal diagnostic.

The principal failure occurs when post-period credits are unrelated to reported revenue quality. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.

The decision pack for test credit notes and reversals should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.

31. Test receivables and collections

Connect invoices to ageing, disputes, offsets, subsequent receipts, expected losses and concentration.

The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a collectability model.

The principal failure occurs when recognised revenue is collectible at face value. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.

The decision pack for test receivables and collections should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.

32. Test deferred and unbilled positions

Explain the commercial event, billing right, fulfilment, ageing and expected conversion of each balance.

The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is an unbilled-deferred quality map.

The principal failure occurs when growth in contract assets confirms future cash. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.

The decision pack for test deferred and unbilled positions should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.

Table 4. Contract-balance quality

BalanceRequired proofRisk
receivableinvoice and receiptcredit
contract assetperformance and rightbilling dependency
deferred revenuecash and obligationfuture delivery
retentionacceptance and releasecollection delay

Illustrative analytical design; company-specific evidence and professional advice govern.

Figure 4. Balance and collection quality
Figure 4. Balance and collection quality

Values are illustrative evidence indices and require company-specific support.

33. Test customer concentration and terms

Measure revenue, margin, backlog, cash, renewal and termination exposure by customer group.

The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a concentration heat map.

The principal failure occurs when diversified invoice count means diversified economics. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.

The decision pack for test customer concentration and terms should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.

34. Test pricing and discount quality

Reconcile list, contracted, realised, renewal and cohort pricing with credits and concessions.

The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a realised-price bridge.

The principal failure occurs when average selling price captures pricing power. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.

The decision pack for test pricing and discount quality should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.

35. Test margin by revenue stream

Allocate direct labour, hosting, materials, commissions, warranty and fulfilment consistently.

The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a revenue-to-margin bridge.

The principal failure occurs when revenue growth has uniform contribution quality. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.

The decision pack for test margin by revenue stream should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.

36. Corroborate through cash

Trace receipts, payment gateways, settlements, bank records, offsets and timing differences.

The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a cash corroboration pack.

The principal failure occurs when cash receipts automatically validate revenue recognition. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.

The decision pack for corroborate through cash should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.

37. Build the revenue proof pack

Assemble customer, contract, delivery, billing, ledger, balance and cash evidence around buyer questions.

The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a decision-led revenue dossier.

The principal failure occurs when document volume signals diligence readiness. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.

The decision pack for build the revenue proof pack should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.

38. Stress sustainability

Test renewals, churn, usage, backlog, project completion, pricing, credit and concentration under downside cases.

The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a sustainable revenue range.

The principal failure occurs when the latest run rate survives plausible change. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.

The decision pack for stress sustainability should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.

39. Connect revenue proof to valuation

Translate durability, margin, cash conversion and risk into forecast confidence and valuation implications.

The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a revenue-quality valuation map.

The principal failure occurs when all reported revenue deserves the same multiple. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.

The decision pack for connect revenue proof to valuation should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.

40. Govern buyer challenge

Control definitions, versions, updates, evidence, concessions, unresolved issues and transaction consequences.

The controlled record should identify the relevant customer, revenue stream, contract, cohort, relationship owner, commercial dependency, evidence source, baseline, trend, scenario, control, exception, accountable executive, deadline and approval. The immediate deliverable is a buyer revenue challenge register.

The principal failure occurs when management can answer buyer questions without a source-controlled response log. Reviewers should connect the evidence to revenue durability, gross margin, cash conversion, renewal probability, switching behaviour, counterparty credit and transaction value; distinguish contractual protection from observed customer behaviour; and test whether the conclusion survives a downside scenario.

The decision pack for govern buyer challenge should state the commercial question, measurement perimeter, historical evidence, customer-specific facts, forecast logic, sensitivity, management action, buyer implication, residual uncertainty and next gate. Material exceptions should flow into the valuation model, quality-of-earnings work, diligence room, sale-process narrative, transaction protections and board reporting.

Table 5. Buyer-ready revenue certificate

GateEvidenceTransaction use
existencecustomer and contractpopulation
deliveryacceptance and logsrecognition
billinginvoice and ledgerreconciliation
cashsettlement and ageingquality

Illustrative analytical design; company-specific evidence and professional advice govern.

Figure 5. Sustainable revenue confidence
Figure 5. Sustainable revenue confidence

Values are illustrative evidence indices and require company-specific support.

References

  1. IFRS Foundation, IFRS 15 Revenue from Contracts with Customers, https://www.ifrs.org/issued-standards/list-of-standards/ifrs-15-revenue-from-contracts-with-customers/
  2. IFRS Foundation, IFRS 9 Financial Instruments, https://www.ifrs.org/issued-standards/list-of-standards/ifrs-9-financial-instruments/
  3. IFRS Foundation, IAS 1 Presentation of Financial Statements, https://www.ifrs.org/issued-standards/list-of-standards/ias-1-presentation-of-financial-statements/
  4. IFRS Foundation, IAS 7 Statement of Cash Flows, https://www.ifrs.org/issued-standards/list-of-standards/ias-7-statement-of-cash-flows/
  5. IFRS Foundation, IAS 8 Accounting Policies, Changes in Accounting Estimates and Errors, https://www.ifrs.org/issued-standards/list-of-standards/ias-8-accounting-policies-changes-in-accounting-estimates-and-errors/
  6. IFRS Foundation, IFRS 8 Operating Segments, https://www.ifrs.org/issued-standards/list-of-standards/ifrs-8-operating-segments/
  7. Financial Accounting Standards Board, Revenue Recognition Topic 606, https://asc.fasb.org/topic&trid=2129707
  8. US Securities and Exchange Commission, Revenue Recognition guidance, https://www.sec.gov/corpfin/accounting-financial-reporting-guidance
  9. US Securities and Exchange Commission, Non-GAAP Financial Measures, https://www.sec.gov/rules-regulations/staff-guidance/corporation-finance-interpretations/non-gaap-financial-measures
  10. US Securities and Exchange Commission, Regulation S-X, https://www.ecfr.gov/current/title-17/chapter-II/part-210
  11. PCAOB, AS 1105 Audit Evidence, https://pcaobus.org/oversight/standards/auditing-standards/details/AS1105
  12. PCAOB, AS 2301 Responses to Risks of Material Misstatement, https://pcaobus.org/oversight/standards/auditing-standards/details/AS2301
  13. PCAOB, AS 2310 The Confirmation Process, https://pcaobus.org/oversight/standards/auditing-standards/details/AS2310
  14. PCAOB, AS 2501 Auditing Accounting Estimates, https://pcaobus.org/oversight/standards/auditing-standards/details/AS2501
  15. PCAOB, Staff Audit Practice Alert 8 Revenue Recognition, https://pcaobus.org/Standards/QandA/SAPA-15-revenue-accounting-standard.pdf
  16. International Auditing and Assurance Standards Board, ISA 505 External Confirmations, https://www.iaasb.org/publications/isa-505-external-confirmations
  17. International Auditing and Assurance Standards Board, ISA 540 Revised, https://www.iaasb.org/publications/isa-540-revised-auditing-accounting-estimates-and-related-disclosures
  18. International Auditing and Assurance Standards Board, International Standards on Auditing, https://www.iaasb.org/publications/2023-2024-handbook-international-quality-management-auditing-review-other-assurance-and-related-services
  19. International Valuation Standards Council, International Valuation Standards, https://ivsc.org/standards/
  20. COSO, Internal Control Integrated Framework, https://www.coso.org/internal-control
  21. International Organization for Standardization, ISO 9001 Quality Management, https://www.iso.org/iso-9001-quality-management.html
  22. International Organization for Standardization, ISO/IEC 27001 Information Security, https://www.iso.org/isoiec-27001-information-security.html
  23. International Organization for Standardization, ISO 31000 Risk Management, https://www.iso.org/iso-31000-risk-management.html
  24. OECD, Guidelines for Multinational Enterprises on Responsible Business Conduct, https://mneguidelines.oecd.org/mneguidelines/
  25. Project Management Institute, Standards and Guides, https://www.pmi.org/standards
  26. Global Reporting Initiative, Standards, https://www.globalreporting.org/standards/
Questions, answered

Revenue Proof for Recurring and Project Businesses: frequently asked questions

It is a controlled evidence chain connecting the economic customer and enforceable contract to delivery, acceptance, billing, ledger recognition, balance-sheet positions and cash collection.

Recurring models emphasise entitlements, service delivery, usage, renewals, churn and recurring definitions. Project models emphasise scope, milestones, progress measurement, cost to complete, change orders, acceptance and claims.

Billing can precede or follow performance, include pass-through amounts, reflect deposits, contain errors or remain disputed. Recognition follows the relevant reporting framework and transaction facts.

Opening ARR plus new, expansion and reactivation, less contraction and churn, with price, currency, acquisitions, disposals and definition changes shown separately and reconciled to controlled customer-contract data.

Separate enforceable funded commitments from cancellable orders, options and pipeline; test timing, obligations, remaining cost, credit, termination rights and historical conversion.

Scope, approval, entitlement, pricing, cost, timing, recognition and collection may diverge. Pending and disputed changes require controlled classification and scenario treatment.

Evidence influences confidence in durability, growth, margin, working capital, cash conversion and forecasts. Valuation and price consequences remain buyer, structure and market specific.

When customer, contract, delivery, billing, ledger, balance and cash populations reconcile; definitions and exceptions are controlled; and recurring and project claims survive downside and buyer testing.

This publication is general information for professional audiences. It is not investment, legal or tax advice, and it is not an offer or solicitation. Readers should verify current legal, regulatory and tax requirements with qualified advisers.

Apply this insight to a live decision

Discuss the financing, capital allocation or transaction implications with a Matchpoint partner.

WhatsApp