Revenue Recognition
Revenue recognition is the process of recording revenue in the period performance obligations are satisfied, not when cash changes hands — governed by ASC 606 for US GAAP companies and IFRS 15 internationally. This cluster covers every step: identifying contracts, allocating transaction price, handling variable consideration, and producing the disclosures auditors will test.
Revenue recognition determines when — not just how much — revenue hits the books. Under ASC 606 (US GAAP) and its international counterpart IFRS 15, revenue is recorded as a company satisfies its performance obligations to a customer, not simply when cash arrives or an invoice goes out. Getting the timing right, contract by contract, is what this cluster is about: the five-step model both standards share, the journal entries and schedules it produces, and the specific, sourced answers to where it actually goes wrong in practice.
The five-step model, at a glance
Every ASC 606 and IFRS 15 question in this cluster traces back to one of these five steps. Knowing which step a question actually belongs to is the fastest way to find the right answer.
| Step | What it answers | Where it commonly goes wrong |
|---|---|---|
| 1. Identify the contract | Is there an enforceable agreement to account for? | Verbal or partially executed agreements treated as firm contracts too early |
| 2. Identify performance obligations | What distinct goods or services is the company actually promising? | Bundled services (software plus onboarding) treated as one obligation when they're distinct |
| 3. Determine the transaction price | How much consideration does the company expect in total? | Variable consideration (discounts, bonuses, refunds) left out of the estimate |
| 4. Allocate the price | How is the total price split across each performance obligation? | Allocated by list price instead of standalone selling price |
| 5. Recognize revenue | When is each obligation actually satisfied, and how much is recognized then? | Recognized on invoice or cash receipt instead of on delivery |
Why deferred revenue is where most of the pain shows up
Deferred revenue is the liability created the moment a customer is billed for something not yet delivered — the mechanism the five-step model uses to hold revenue back until it's actually earned. It's also the single account most likely to silently drift from the general ledger, because it sits at the intersection of two systems that don't always agree: whatever calculates the recognition schedule (a billing platform, a spreadsheet, a dedicated revenue tool) and the general ledger itself, which only reflects what's actually been posted. A contract modification, a manual adjustment made outside the schedule, or a sync gap between the two systems all produce the same symptom — a deferred revenue balance that no longer ties to the GL — which is why reconciling it, contract line by contract line rather than invoice by invoice, is one of the highest-value recurring checks in this cluster.
What's in this cluster
The pages below cover what ASC 606 and IFRS 15 actually require, how to calculate a contract's transaction price, why deferred revenue stops matching the general ledger, how the two standards differ in practice, which billing platforms automate the schedule, and what a controller specifically checks when closing revenue at month-end.
What are the five steps in the ASC 606 revenue recognition model?
ASC 606 requires identifying the contract, identifying the performance obligations, determining the transaction price, allocating that price across obligations, and recognizing revenue when each obligation is satisfied. Every SaaS, professional services, and multi-element arrangement must run this analysis. The five-step model is the framework controllers use to decide whether a dollar belongs in revenue this period or in deferred revenue.
How do you allocate transaction price when a contract bundles software, implementation, and support?
When a contract contains multiple performance obligations — a software license, an implementation service, and ongoing support — the total transaction price must be allocated to each obligation in proportion to its standalone selling price. The allocation determines when each piece is recognized: upfront for licenses, over time for support, at milestones for services. Getting the standalone selling prices wrong is one of the most common sources of revenue misstatement.
What happens to recognized revenue when a contract is upgraded mid-term?
A mid-term contract modification under ASC 606 is either a separate contract (if it adds a distinct good or service at its standalone price) or a modification of the existing contract (which may require cumulative catch-up or prospective recognition). The right treatment depends on whether the new performance obligation is distinct, and controllers who default to the same accounting for every modification face restatement risk.
Why does deferred revenue in the billing system not match the general ledger balance?
Billing systems and ERPs often account for the same contract differently: the billing system records when invoices are issued; the ERP records when performance obligations are satisfied. Timing differences, unapplied credits, manual journal entries, and cutoff mismatches all produce a gap. A deferred revenue reconciliation that can't tie out to the subledger is a disclosure risk under ASC 606.
Which SOX controls are typically required around revenue recognition?
For public companies, PCAOB-audited internal controls over revenue recognition typically include: a documented allocation methodology and its supporting standalone selling price analysis, period-end cutoff procedures, a reconciliation of the deferred revenue subledger to the general ledger, and management review of the revenue journal entries. Private companies preparing for an exit or debt round face substantially the same evidence requests from auditors.
When does this not apply?
ASC 606 was written for companies with contracts and performance obligations. IFRS 15, the international equivalent, shares the same five-step model — it is not a different framework. Cash-basis accounting, single-transaction commodity sales, and regulated industries using gross-receipts or excise-tax accounting follow different frameworks. If your revenue consists entirely of spot sales where the transaction price is fixed and the obligation is fulfilled at delivery, many of the allocation and variable-consideration questions in this cluster do not apply.
More in this topic
- How do you calculate a contract's transaction price under ASC 606?
- ASC 606 vs IFRS 15: what's the difference?
- Which billing platforms support automated ASC 606 revenue recognition?
- How should a controller close revenue at month-end under ASC 606?
- What are the required ASC 606 disclosures?
- How do I recognize revenue for milestone-based professional services billing?
- What is deferred revenue?
- How do I true up estimated variable consideration under the ASC 606 constraint?
- How do I set up a refund/returns reserve, and how does it affect revenue recognition?
- What is a performance obligation under ASC 606?
- What's the difference between a contract asset and a contract liability under ASC 606?
- What's the difference between recognizing revenue over time vs. at a point in time?
- What is unbilled AR, and how does it differ from a contract asset?
- How do I recognize revenue for a SaaS contract with a built-in price ramp?
- What is bill-and-hold revenue recognition, and when does it apply?
- How do I recognize revenue for a multi-year SaaS contract billed annually?
- How do I recognize revenue for usage-based/consumption pricing?
- What is ASC 340-40 commission capitalization, and how does it interact with revenue recognition?
- How do I determine standalone selling price (SSP) when I never sell the item separately?
- What is the residual approach to SSP and when am I allowed to use it?
- How do I account for a mid-contract downgrade or seat reduction under ASC 606?
- Principal vs agent: do I recognize revenue gross or net for resold third-party items?
- SaaS + implementation: is it one performance obligation or two?
- How to feed DocuSign contract data into contract-to-cash
- How to Automate ASC 606 Revenue Recognition for SaaS and Usage-Based Contracts
- How to automate contract-to-cash in 2026 (step-by-step playbook)
Frequently Asked Questions
By Zuny Fester, Head of Operations and MarketingSources
See how Loopfour runs this: revenue recognition automation.
Next step
Map the finance workflow with the most exposure and prove the automation path.
Bring the invoice, contract, payment reconciliation, or customer finance workflow you have to defend at audit. Loopfour can map the trigger, controls, integrations, and approval loop.