Revenue Recognition Rules Under Accrual Accounting

Revenue recognition is the part of accrual accounting with the most rigorous external framework — a five-step model under US GAAP and IFRS that determines exactly when a sale becomes revenue. For most operating teams, the question is not what the standard says but what it implies for the close.

The framework in one paragraph

Revenue recognition under accrual accounting is governed by a single principle: revenue is recognized when control of goods or services transfers to the customer, regardless of when cash is received or when an invoice is issued. The framework that operationalizes that principle is the five-step model in ASC 606 revenue recognition guidance under US GAAP and the corresponding IFRS revenue standard under IFRS. The two frameworks were developed jointly and produce substantially the same answers in most operating cases.

The five-step model

The model takes any revenue transaction — simple or complex — and processes it through the same five sequential steps.

Step 1: Identify the contract. A contract is an agreement that creates enforceable rights and obligations. It can be written, verbal, or implied by customary business practice. For most B2B transactions, this is straightforward: a signed order form, a master services agreement, or a purchase order constitutes the contract.

Step 2: Identify the performance obligations. A performance obligation is a distinct good or service the customer is paying for. A SaaS contract typically has one obligation (continuous access). A bundled contract with software, setup, and training might have three. The test for "distinct" is whether the customer can benefit from the item on its own or with other readily available resources.

Step 3: Determine the transaction price. This is the total amount the business expects to receive across all obligations in the contract. It includes the contracted price and adjusts for variable consideration — discounts, rebates, refunds, performance bonuses, anything that could change the final amount.

Step 4: Allocate the transaction price. Split the total across the performance obligations. The allocation is normally based on standalone selling prices — the price each obligation would carry if sold separately. If standalone prices are not directly observable, they are estimated.

Step 5: Recognize revenue as each obligation is satisfied. Each allocated portion is recognized on its own schedule, governed by the pattern in which that obligation is delivered: ratably, at a point in time, or against milestones.

The three recognition patterns

Step 5 is where most operational complexity lives. Three patterns cover almost every case.

Ratable recognition. Used when the customer receives continuous benefit over time. SaaS subscriptions, ongoing support contracts, monthly retainers. Revenue is recognized in equal amounts each period across the term of service. A twelve-month subscription with $24,000 total recognizes $2,000 per month.

Point-in-time recognition. Used when the customer derives benefit at a single moment of transfer. Product sales, conference sponsorships, event-based deliveries. All revenue is recognized on the date of transfer — typically when delivery occurs or when the customer takes control.

Milestone-based recognition. Used when discrete deliverables mark progress. Professional services, custom development, construction-style engagements. Revenue is recognized as each milestone is accepted by the customer. A $100,000 engagement with three milestones — discovery ($30K), build ($50K), launch ($20K) — recognizes each amount as the corresponding milestone is accepted.

Revenue recognition for SaaS

SaaS is the simplest case under the model because the typical subscription contract has one performance obligation (continuous access to the platform) delivered ratably across the contract term.

For a $24,000 annual subscription paid upfront in January:

• January 1: cash collected, deferred revenue increases by $24,000, revenue is unchanged.
• January 31: $2,000 of deferred revenue is reclassified to revenue (one-twelfth of the contract).
• Each subsequent month: another $2,000 is recognized, drawing down deferred revenue.
• December 31: deferred revenue is zero, cumulative revenue is $24,000.

The complication in SaaS comes from add-ons. A subscription with a one-time setup fee, an annual training package, and a usage-based overage component is no longer a single obligation. Each piece needs its own recognition schedule. The setup fee is typically recognized as the setup is performed (point-in-time or milestone). The training is recognized as training sessions are delivered. The overage is recognized based on actual usage.

Revenue recognition for professional services

Professional services engagements vary widely, but they tend to fall into two categories.

Fixed-fee engagements with discrete deliverables use milestone-based recognition. Each deliverable accepted by the customer represents satisfaction of a performance obligation, and the allocated portion of the contract is recognized at acceptance.

Time-and-materials engagements recognize revenue as work is performed, typically using the hours-billed metric as a measure of progress. Revenue equals hours worked × billing rate, regardless of whether the customer has been invoiced yet. Hours worked but not yet billed become unbilled revenue (a contract asset on the balance sheet).

Many real engagements combine both: a fixed-fee scope plus a time-and-materials change order pool. Each piece runs on its own recognition logic.

Revenue recognition for product sales

Product sales are the closest the model comes to looking like cash accounting, but the trigger is still transfer of control rather than cash receipt.

For most physical product sales, control transfers at delivery — when the customer takes possession, signs for receipt, or the goods are FOB delivered to their location. The terms of the shipping arrangement determine the precise moment. FOB shipping point transfers control at the seller's dock; FOB destination transfers control at the customer's dock.

For digital products and software licenses, control transfers when the customer can use the product — typically on activation or download.

Bundled deals and multiple performance obligations

Bundled contracts are the most common source of revenue recognition complexity. The pattern is consistent:

1. Identify each performance obligation the bundle contains.
2. Establish the standalone selling price of each obligation (either observed or estimated).
3. Allocate the total contract price across obligations proportionally to standalone selling prices.
4. Apply the correct recognition pattern to each allocated portion.

A $30,000 contract that includes an annual SaaS subscription (standalone $24,000), a one-time setup (standalone $4,000), and one year of premium support (standalone $4,000) gets allocated proportionally. Total standalone value is $32,000; the customer pays $30,000; so each obligation is allocated 93.75% of its standalone price ($22,500 + $3,750 + $3,750 = $30,000). The subscription recognizes $22,500 ratably; the setup recognizes $3,750 on completion; the support recognizes $3,750 ratably.

Contract modifications and refunds

Contracts change. The accounting depends on the nature of the change.

Expansions that add distinct obligations at standalone prices are treated as separate contracts. A customer adding ten more user seats at the standard per-seat price creates a new contract — the original schedule continues unchanged, and the addition gets its own schedule.

Modifications that change pricing or scope of existing obligations require a prospective adjustment. The remaining deferred revenue is recalculated against the new total, and the new monthly recognition applies from the change date forward. Months already locked in prior periods are not adjusted.

Refunds and cancellations are treated as a reduction of revenue. The cash refund reverses the recognized revenue and any related receivables; deferred revenue for undelivered obligations is reversed to cash.

Variable consideration

Variable consideration is the part of the transaction price that depends on future events — usage-based fees, performance bonuses, volume rebates, retroactive discounts. The standard requires estimating variable consideration at the time of recognition, using either the expected value method (probability-weighted average of possible outcomes) or the most-likely-amount method (the single most likely figure).

The estimate is constrained so that revenue is recognized only to the extent it is "highly probable" that the amount will not need to be reversed. When the actual amount is determined, a true-up adjustment captures the difference.

What lands on the financial statements

Three accounts carry the timing differences between recognized revenue and cash:

• Deferred revenue (liability) holds cash received for obligations not yet satisfied.
• Unbilled revenue / contract assets (asset) holds revenue recognized for obligations satisfied but not yet billed.
• Accounts receivable (asset) holds revenue recognized and billed but not yet collected.

Reconciling all three to a customer-level waterfall is the discipline that makes a recognized revenue figure auditable. The sum of customer-level contract balances should equal the GL balances each period.

Common mistakes

Frequently asked questions

Where to go next

Read these next:

1. The complete accrual accounting pillar
2. Deferred revenue accounting
3. What is accrual accounting?
4. Automating accruals in QuickBooks Online

Related Resources

• Accrual vs cash accounting
• Prepaid expenses
• Accrued expenses
• Payroll accruals