How IFRS 15 revenue recognition shapes financial due diligence: the 5-step model, over-time vs point-in-time, deferred revenue, cut-off testing and the recognition red flags that move QoE.
Almost every argument about earnings quality is, underneath, an argument about when revenue should be recognised. Two companies can sign identical contracts and collect identical cash, yet report profit a full year apart depending on how they read the recognition rules. That is why a financial due diligence team spends so much time on the boundary between a signed order and a recognised sale. Get the timing wrong - deliberately or innocently - and every multiple built on that earnings number is wrong too. IFRS 15 is the framework that governs this boundary, and a candidate who can walk an interviewer through it with a live example, rather than a memorised definition, immediately reads as someone who has sat in a data room rather than only a lecture theatre.
IFRS 15 replaced a patchwork of older standards with a single principle: recognise revenue when you transfer control of a good or service to the customer, in an amount that reflects what you expect to be paid. The standard turns that principle into five sequential steps.
The steps sound mechanical, but each one is a lever. Bundle two obligations that should be separate and you can pull revenue forward. Misjudge variable consideration and you overstate the transaction price. In diligence you are not auditing the arithmetic so much as pressure-testing the judgements, because it is the judgements that flatter or depress the earnings you are pricing.
The five steps are not a compliance checklist to a diligence analyst - they are five places where a management team can, consciously or not, move the reported number. Learn where each lever sits and you know where to look first.
Step 5 is where most of the diligence tension lives. IFRS 15 recognises revenue over time if any one of three criteria is met: the customer receives and consumes the benefit as the seller performs (routine cleaning or SaaS access); the seller creates or enhances an asset the customer controls (building on the customer's land); or the seller creates an asset with no alternative use and has an enforceable right to payment for work done to date. If none of the three holds, revenue is recognised at a single point in time - usually when control passes on delivery.
The distinction is not academic. A construction or long-term services business recognising over time will show smoother, earlier revenue; the same economics recognised point-in-time would lump the revenue at handover. For measuring over-time progress, the standard allows output methods (surveys of work performed, units delivered) or input methods (costs incurred to date against total expected costs). Input methods are common but vulnerable: front-loaded costs or inefficient rework can overstate percentage completion and pull revenue forward. This is a natural bridge to the mechanics covered in long-term contract diligence, where the cost-to-complete estimate becomes the single most important judgement in the accounts.
Takeaway: always establish which recognition pattern a target uses before you read a single revenue trend, because the pattern determines what a rising or falling line actually means.
When a customer pays before the seller has performed, IFRS 15 parks the cash as a contract liability - the balance most practitioners still call deferred revenue. It is released to the P&L as the performance obligation is satisfied. The mechanics matter because interviewers test whether you understand the plumbing, not just the label. Here is a single £24,000 annual support contract billed on 1 January, viewed at 30 June:
| Date | Cash received (£) | Revenue recognised, cumulative (£) | Contract liability balance (£) |
|---|---|---|---|
| 1 Jan (billing) | 24,000 | 0 | 24,000 |
| 31 Mar | - | 6,000 | 18,000 |
| 30 Jun | - | 12,000 | 12,000 |
The cash lands once; the revenue drips out monthly; the liability unwinds in lockstep. That single pattern drives three separate diligence conversations - revenue quality, cut-off, and net debt. Because the buyer inherits an obligation to deliver services already paid for, the deferred balance also has a debt-like flavour that spills into the net debt negotiation and is explored in full in the dedicated deferred revenue in FDD analysis. The mirror-image balance - a contract asset, where the seller has performed but cannot yet bill - is equally worth checking, because a swelling contract-asset balance can signal revenue recognised well ahead of any invoice.
If there is one procedure that defines revenue-recognition work in a quality of earnings exercise, it is cut-off testing - confirming that transactions are recorded in the correct period. The temptation to shift a sale across a period boundary is greatest exactly where it does most damage: the last days of a reporting period and the first days of the next.
A typical cut-off procedure samples invoices either side of the period-end and traces each back to the underlying evidence of delivery - dispatch notes, proof of acceptance, service logs, milestone sign-offs. The question is always the same: did control actually transfer in the period the revenue was booked? A worked mini-example shows how quickly this moves the number. Suppose a manufacturer with a 31 December year-end books five late-December invoices, and diligence traces the dispatch dates:
| Invoice | Amount (£) | Booked in period | Dispatch date | Correct period | Adjustment |
|---|---|---|---|---|---|
| A-1187 | 180,000 | FY (Dec) | 29 Dec | FY (Dec) | - |
| A-1188 | 145,000 | FY (Dec) | 2 Jan | Next FY | (145,000) |
| A-1189 | 96,000 | FY (Dec) | 31 Dec | FY (Dec) | - |
| A-1190 | 210,000 | FY (Dec) | 4 Jan | Next FY | (210,000) |
| A-1191 | 88,000 | FY (Dec) | 30 Dec | FY (Dec) | - |
Two invoices totalling £355,000 were dispatched in January but booked in December. Reversing them removes £355,000 of revenue from the year under review - and, on a typical margin, a meaningful slice of EBITDA. On, say, a 7x multiple, that overstatement alone could be worth over £2m of headline enterprise value if left uncorrected. Cut-off is unglamorous, but it is where a careful analyst earns their fee.
Beyond honest timing errors sits a catalogue of techniques for making revenue appear earlier or larger than the economics justify. Four recur often enough to memorise.
If revenue is growing but cash collection, order backlog and the deferred balance are not moving with it, assume recognition is doing the work until you can prove otherwise.
Each of these belongs on the standing list of FDD red flags, and each is far easier to spot when you already know the IFRS 15 step it exploits.
Every recognition issue eventually lands in the EBITDA adjustments that build the quality-of-earnings bridge. The discipline is to normalise the reported number to a sustainable, run-rate figure stripped of timing games in either direction. A recognition policy quietly accelerated to flatter the current year must be unwound; a genuine over-time profile misread as a one-off must be respected. The goal is the number the business will actually repeat, which is the whole point of a QoE analysis.
Two subtleties trip up candidates. First, a fair-value adjustment at acquisition can write the deferred balance down at completion - the so-called haircut - suppressing post-deal revenue for reasons that are purely accounting rather than performance. Second, a recognition correction that reduces revenue often reduces working capital too, because the contract liability or receivable moves with it, so the same finding can touch both the earnings bridge and the working capital analysis. Trace a recognition adjustment through both statements and you avoid the double-count that betrays a rushed analyst.
A common prompt: "A software company's revenue jumped 30% this year. How would you test whether that growth is real under IFRS 15?"
A strong answer works the five steps as a diagnostic: "First I'd establish the recognition pattern - is the licence recognised at a point in time on delivery, or over the contract term, and has that policy changed this year? A policy change alone can manufacture a step-up. Then I'd separate the performance obligations: if implementation or support has been bundled with the licence and recognised up front, revenue may have been pulled forward, so I'd want it allocated on stand-alone selling prices and released as delivered. I'd run cut-off testing around the period-end to check late deals weren't booked early, tracing to delivery and acceptance evidence. I'd reconcile recognised revenue to billings, cash collected and the deferred-revenue movement - if revenue outran cash and bookings, that's a flag. I'd check for gross-versus-net presentation and for any bill-and-hold or channel-stuffing near the year-end. Whatever fails those tests, I'd normalise out of the EBITDA bridge so we're pricing sustainable, repeatable revenue rather than an accounting event."*
That answer connects the standard, the testing and the bridge in one breath - exactly the integrated thinking that separates a strong candidate from one reciting a definition. It pairs naturally with the structured approach in a good interview preparation plan.
Revenue recognition is the point where accounting judgement, deal value and negotiating leverage all meet on a single line of the income statement. A weak analyst admires the growth; a strong one asks when control transferred, which obligation was satisfied, and whether the timing was honest - and can show the interviewer exactly where in the IFRS 15 model each answer lives. Master the five steps not as a definition but as a map of where earnings can be moved, and you will never again take a revenue line at face value. In a deal, the difference between those two habits is measured in millions.
The Transaction Services Interview Programme (€119.99, one-time) includes a dedicated IFRS 15 module - the five-step model as a diligence diagnostic, over-time versus point-in-time recognition, cut-off testing on real invoices, and the bill-and-hold, channel-stuffing and gross-versus-net red flags, worked through to the EBITDA bridge. Enrol today.
Hundreds of candidates prepared their interviews with this programme. Those who landed the role have one thing in common: they worked the cases before walking into the room.