Finance teams run into trouble fast with bundled goods and services, subscription pricing, contract modifications, variable consideration, and long-term arrangements. Add inconsistent documentation to the mix, and even straightforward contracts can turn into audit headaches.
This article covers U.S. GAAP's ASC 606, IFRS 15, the five-step recognition model, the judgment calls that trip up finance teams most often, and the controls that keep revenue reporting defensible.
Key Takeaways
- Revenue recognition hinges on satisfying performance obligations, not on invoicing or cash receipt
- ASC 606 governs U.S. GAAP revenue recognition; IFRS 15 serves the same function internationally
- Both standards use a five-step model to identify contracts, allocate pricing, and time recognition
- Complex deals demand documented judgment on timing, allocation, and variable pricing
- Weak documentation creates real audit and restatement risk for growing companies
Revenue Recognition Standards: ASC 606, IFRS 15, and GAAP
Revenue recognition is the accounting process for determining when, and in what amount, revenue from customer contracts gets recorded. It operates within accrual accounting but is not the same thing.
Accrual accounting recognizes revenue and expenses when they are earned or incurred. Revenue recognition rules specify exactly when that earning event happens for contracts with customers.
ASC 606, officially titled Revenue from Contracts with Customers, is the U.S. GAAP standard. The Financial Accounting Standards Board (FASB) issued it through ASU 2014-09 in May 2014. It is codified in the FASB Accounting Standards Codification, the authoritative source; the ASU only communicated the change.
IFRS 15, sharing the identical title, is the international counterpart. The International Accounting Standards Board (IASB) issued it the same month, and it's used broadly across jurisdictions that follow IFRS.
How Different Are They, Really?
Not very, at the model level. Both use the same five-step structure. But differences surface in the details:
| Area | ASC 606 | IFRS 15 |
|---|---|---|
| Collectability threshold | "Probable" means likely | "Probable" means more likely than not |
| Contract-cost impairment | No reversal allowed | Reversal required if conditions improve |
| Noncash consideration | Measured at contract inception | No fixed measurement date |
| Shipping after control transfer | Election to treat as fulfillment | No equivalent election |
KPMG's 2022 comparison describes the two standards as "substantially converged," not identical. That distinction matters for any company reporting under both frameworks or comparing itself to international peers.
Why This Matters Beyond Compliance
Public companies, private companies, lenders, investors, and auditors all rely on consistent revenue recognition to:
- Compare performance across companies and industries
- Assess whether reported growth reflects actual business activity
- Evaluate debt covenant compliance and credit decisions
- Support audit conclusions with defensible, rules-based logic
The Five-Step Revenue Recognition Model
Both ASC 606 and IFRS 15 build on the same five-step framework. The IASB's own published text confirms this structure in IFRS 15's standard text, originally issued in 2014. Here's how it breaks down.
Step 1: Identify the Contract With a Customer
A contract exists when all of the following are met:
- Both parties approve the agreement
- Rights and obligations are enforceable
- Payment terms are identifiable
- The arrangement has commercial substance
- Collection is probable
Contract inception is separate from billing or cash receipt. A signed statement of work can create a contract well before an invoice goes out.
Step 2: Identify the Performance Obligations
This step asks: what are you actually promising to deliver? A performance obligation is a promise to transfer a distinct good or service. Multiple promises get combined into one obligation when they aren't separately identifiable, such as highly interrelated installation and customization work that only has value together.
Step 3: Determine the Transaction Price
Transaction price covers more than the sticker price. It includes:
- Fixed consideration stated in the contract
- Variable consideration, such as rebates or performance bonuses
- Significant financing components (when payment timing differs materially from delivery)
- Noncash consideration
- Amounts payable to the customer, which can reduce the transaction price
Variable consideration gets constrained: estimates are included only when a significant revenue reversal is unlikely once uncertainty resolves.
Step 4: Allocate the Transaction Price
For contracts with multiple performance obligations, the transaction price gets allocated based on relative standalone selling prices. When observable prices aren't available, companies estimate using an adjusted market assessment, an expected-cost-plus-margin approach, or (in limited circumstances) a residual approach.
Step 5: Recognize Revenue When or As Obligations Are Satisfied
This is where point-in-time and over-time recognition diverge. Over-time recognition applies when any of these conditions hold:
- The customer simultaneously receives and consumes the benefits
- Performance creates an asset the customer controls as it is built
- The asset has no alternative use to the entity, and the entity has an enforceable right to payment for work completed
Everything else is recognized at a single point in time, based on transfer of control.
Judgment Areas and Practical Application
A simple product sale is easy: ship it, customer accepts it, revenue recognized. Multi-element arrangements, such as a subscription bundled with implementation, training, and usage-based add-ons, require real analysis.
Point-in-Time vs. Over-Time: The Core Question
Finance teams need to assess:
- Whether the customer benefits from work as it happens or only once complete
- Whether the customer controls an asset as it's being created
- Whether the entity has an enforceable right to payment for partial work
- Which indicators (legal title, physical possession, risks and rewards, acceptance) point to control transfer
Contract Modifications
Not every change to a contract gets treated the same way:
- Separate contract: additional goods or services are distinct, and the added price reflects standalone value
- Prospective modification: remaining goods or services are distinct from what's already delivered; treat it as ending the old contract and starting a new one
- Cumulative catch-up: remaining items aren't distinct from what's already transferred, so the original contract gets adjusted retroactively
Getting this classification wrong skews the timing of revenue in ways that auditors catch quickly.
Principal vs. Agent
If your company controls a good or service before it transfers to the customer, you report gross revenue. If you're facilitating someone else's sale, you report only your net fee or commission. Indicators include who holds fulfillment responsibility, who bears inventory risk, and who sets the price.
Licensing, Subscriptions, and Variable Pricing
Licensing arrangements split into two buckets: a right to access intellectual property (recognized over time) versus a right to use it as it exists at a point in time (recognized at that point). Subscriptions, usage-based fees, rebates, refunds, and warranties all introduce variability that can shift both timing and amount.
A common example: a customer pays $120,000 upfront for a 12-month service contract. That payment doesn't become revenue immediately. It creates a contract liability (deferred revenue) on the balance sheet, recognized as revenue in $10,000 monthly increments as the service is actually delivered.
Stratum Advisory Partners' Technical Accounting Advisory work frequently centers on exactly these judgment calls, building documented, supportable conclusions for revenue recognition questions that don't have an obvious answer.
Financial Statement Effects, Disclosures, and Controls
Revenue recognition touches more line items than most finance teams initially expect. Walk through the flow: a contract is executed, delivery or service occurs, an invoice is sent, cash is collected. Along the way, you're tracking:
- Billed amounts: what's been invoiced
- Accounts receivable: what's owed but not yet collected
- Recognized revenue: what's actually been earned under ASC 606/IFRS 15
- Contract assets: revenue recognized before billing rights exist
- Contract liabilities: cash received before revenue is earned
Premature or delayed recognition distorts profit, assets, liabilities, margins, and forecasts. It can also trip debt covenants or mislead investors evaluating growth trends.
Disclosure Requirements
ASC 606 disclosure requirements cover:
- Disaggregation of revenue by category
- Contract balances and significant changes
- Performance obligation details, including timing and payment terms
- Remaining performance obligations and expected recognition timing
- Significant judgments underlying timing and allocation decisions
Nonpublic entities can elect certain disclosure relief, but it's not a blanket exemption: opening and closing contract balances, for instance, generally still need disclosure even when detailed quantitative breakdowns are omitted.
Practical Controls Worth Building
- Contract review and approval workflows before signing
- Performance obligation mapping for every new deal type
- Standalone selling price documentation, updated periodically
- Variable consideration reassessment each reporting period
- Cutoff testing around period-end
- Modification tracking tied to original contract terms
Stratum's Financial Close & Internal Control Improvement work often starts here, remediating control deficiencies before they become material weaknesses that auditors flag publicly.
Implementing a Revenue Recognition Policy
A workable revenue recognition policy isn't a one-page memo. It should spell out:
- Scope and which standards apply
- Contract criteria and performance obligation analysis steps
- Transaction price determination and allocation methodology
- Timing rules for point-in-time vs. over-time recognition
- Required journal entries and disclosure checklists
- Review and sign-off responsibilities
New products, pricing models, sales incentives, and nonstandard contract language should all go through a quick accounting review before they go to market, not after a quarter close surfaces a problem.
This requires coordination across departments. Sales negotiates terms, legal drafts language, billing issues invoices, and accounting has to translate all of it into a consistent recognition schedule. When these teams work in silos, mismatches show up fast.
When to Bring in Outside Help
Some situations warrant technical accounting support beyond what an internal team can absorb:
- Complex or unusual revenue arrangements
- Acquisitions or divestitures changing the revenue base
- Contract modifications affecting multiple periods
- Unresolved questions surfacing during an audit
- Reporting deadlines that exceed current team capacity
Stratum Advisory Partners works alongside existing finance teams on these situations. That can mean Technical Accounting Advisory for a specific revenue question, Transaction Accounting & Post-Acquisition Support following an acquisition, or Interim CAO & Controller Leadership during a transition. Engagements are scoped around the specific issue, not sold as a fixed package.
Frequently Asked Questions
What are the accounting standards for revenue recognition?
ASC 606 governs revenue recognition under U.S. GAAP, while IFRS 15 applies under IFRS. Both use a five-step, principles-based framework, though applying it correctly still requires entity-specific analysis.
What is the GAAP standard for revenue recognition?
ASC 606, Revenue from Contracts with Customers, is the primary U.S. GAAP standard. It requires identifying the contract, the performance obligations, the transaction price, allocating that price, and recognizing revenue as obligations are satisfied.
How does IFRS 15 recognize revenue?
IFRS 15 recognizes revenue as an entity satisfies performance obligations, reflecting the actual transfer of promised goods or services to the customer rather than the timing of invoicing or payment.
Are ASC 606 and IFRS 15 the same?
They share the same five-step core model and are substantially converged, according to KPMG's comparison. Differences in collectability thresholds, licensing assessments, and elective disclosures mean each arrangement still needs individual review.
