Revenue Recognized Too Soon
A software company signs a three-year contract for $1,200,000, billed annually in advance at $400,000. The contract bundles a perpetual license, two years of unspecified upgrades, and a hosted support service. Standalone selling prices are: license $900,000, upgrades $300,000, support $300,000 (total $1,500,000). The company currently recognizes the full $400,000 annual billing as revenue when invoiced, arguing that 'cash is coming in and the client is committed.' The controller is preparing year-end statements and a bank covenant tests EBITDA. The auditor flags the policy. Management asks the valuation analyst, who is using these statements as an input, whether the reported revenue and margin are usable.
1. Under a principles-based revenue standard, how should the $1,200,000 be allocated and recognized, and what is wrong with the current policy?
Read the worked answer
Current policy is wrong on two counts: it recognizes on billing (cash timing) rather than on transfer of control, and it ignores the multiple performance obligations.
Allocation: allocate the $1,200,000 transaction price by relative standalone selling price:
- Total SSP = $1,500,000.
- License: 900/1500 × 1,200,000 = $720,000
- Upgrades: 300/1500 × 1,200,000 = $240,000
- Support: 300/1500 × 1,200,000 = $240,000
Recognition:
- License (perpetual, control transferred at inception): recognized when delivered.
- Upgrades (unspecified, provided over time): recognized over the two-year upgrade period (~$120,000/yr).
- Support: recognized over the service period.
Billing of $400,000/yr has no bearing on the pattern. The company has been front-loading revenue and overstating early-period margin.
2. The analyst is valuing the business using a market multiple on EBITDA derived from the reported statements. How should the misstatement affect the valuation inputs, and what adjustment is defensible?
Read the worked answer
The analyst must normalize before applying any multiple.
Steps:
- Reconstruct revenue timing. Replace billed amounts with allocated, control-based recognition. Early years are overstated, later years understated; the cumulative total over the contract life is unchanged.
- Check the margin effect. Because the license (highest-margin item) was effectively being spread across billings, the pattern of margin is distorted even if lifetime totals reconcile. A multiple applied to a single distorted year misprices the business.
- Normalize EBITDA to a steady-state recognition pattern, and disclose the adjustment.
- Assess covenant impact. If the covenant tests reported EBITDA, the misstatement may have created a false cushion; the analyst should not treat a covenant headroom that depends on misstated figures as a valuation positive.
Defensible position: use restated figures, footnote the adjustment, and flag that the company's own reported numbers are unreliable until the policy is corrected. Recall alone won't resolve this - the analyst must reason about which year is distorted and in which direction.
3. A colleague argues the total revenue over three years is identical either way, so the valuation is unaffected. Evaluate that claim.
Read the worked answer
The claim is false for valuation even though lifetime cash and lifetime revenue match.
Why it matters:
- Valuation multiples are applied to period earnings, not lifetime totals. If year 1 is inflated and year 3 depressed, a multiple on year-1 EBITDA overstates value.
- Discounting: earlier revenue is worth more. Mis-timing shifts value toward the present, inflating a DCF even with identical nominal totals.
- Risk signal: a policy that recognizes on billing suggests weak controls, which raises the discount rate independent of the numbers.
- Contract assets/liabilities: the balance sheet will show deferred revenue that the current policy ignores, affecting net debt and enterprise value bridge.
The colleague is conflating 'same total' with 'same value.' The analyst should correct the timing, re-run the multiple on a normalized year, and note the control weakness.