ASC 605 vs ASC 606: The Shift in Revenue Recognition Standards

H

Heena Jain

Executive Director & SVP, Strategic Accounts

News and Updates 14 min readAugust 24, 2026
asc-605-vs-asc-606-revenue-recognition

ASC 605 was a fragmented, rules-based system of industry-specific revenue guidance. ASC 606 replaced it with a single principles-based model applying to all industries. The central change is the recognition trigger: ASC 605 asked whether risks and rewards had transferred to the customer, while ASC 606 asks whether the customer has obtained control. ASC 606 also requires identifying distinct performance obligations within each contract and allocating the transaction price across them by standalone selling price. It took effect for public companies in fiscal years beginning after December 15, 2017, and for private companies after December 15, 2018.

Revenue recognition is not a passive compliance obligation. How and when a company records revenue determines what its financial statements say about profitability, what investors and lenders see, and what triggers covenant tests, earnout calculations, and investor reporting milestones.

The transition from ASC 605 to ASC 606 was the most significant overhaul of revenue recognition in U.S. GAAP in decades. Issued jointly by FASB and the IASB in 2014 as ASU 2014-09, it replaced ASC 605 along with the large body of industry-specific revenue guidance that had accumulated over preceding decades.

What matters for a finance leader is not the chronology. It is knowing where ASC 606 changes outcomes rather than procedures, and where the judgment calls that create audit risk actually sit.

ASC 605: Understanding the Old Standard and Why It Failed

ASC 605 was not a single coherent standard. It was a collection of industry-specific guidance, interpretive releases, and sector rules that had evolved in response to particular transactions and industries. Software companies operated under ASC 985-605. Real estate had its own rules. Construction contractors applied percentage-of-completion or completed-contract methods under separate guidance. Long-term service contracts had their own interpretations.

The result was a system in which two companies offering economically similar arrangements could recognize revenue on materially different schedules depending on how their contracts were structured and which industry rules applied. Peer comparison became unreliable, and there was real opportunity to structure transactions for a desired accounting outcome rather than an economically justified one.

The core criteria were conceptually simple: revenue was recognized when realized or realizable and earned. In practice, most registrants operationalized this through the SEC's SAB 104 criteria, which asked whether persuasive evidence of an arrangement existed, delivery had occurred, the price was fixed or determinable, and collectibility was reasonably assured.

For simple point-in-time transactions, this worked. For multi-element arrangements, subscription models, and contracts with variable consideration, it produced inconsistency.

The distortion ran in both directions

A point worth making carefully, because it is commonly stated backward.

ASC 605 is often described as having front-loaded revenue. In some fact patterns it did. But in software, the industry most affected by the change, the distortion generally ran the opposite way.

Under ASC 985-605, a vendor could account for a delivered element separately only if it had vendor-specific objective evidence of fair value (VSOE) for the undelivered elements. Without VSOE, the delivered and undelivered elements were combined into a single unit of accounting and the entire arrangement was deferred, typically recognized ratably over the post-contract support term. A perpetual license delivered on day one could end up recognized over three years because the vendor could not establish VSOE for support.

ASC 606 removed the VSOE requirement entirely. The order of delivery and availability of VSOE no longer determines whether promises qualify as separate performance obligations. For many software companies, adoption accelerated revenue that had been deferred under legacy guidance.

The accurate framing is not that ASC 605 was permissive. It is that ASC 605 produced recognition patterns driven by contract structure and evidentiary technicalities rather than by economic substance, in both directions.

ASC 606: The Shift From Rules to Principles

ASC 606 replaced the fragmented system with a single principles-based model applicable to all industries and contract types. The core principle: recognize revenue to depict the transfer of promised goods or services to customers in an amount reflecting the consideration the entity expects to be entitled to.

The conceptual shift is from risks and rewards to control. Under ASC 605, the question was whether risks and rewards had substantially transferred. Under ASC 606, the question is whether the customer has obtained control, meaning the ability to direct the use of the asset and obtain all of its remaining benefits substantially. This is not semantic. It moves the recognition point for a meaningful category of transactions in technology, software, and professional services.

The second shift is contract-level analysis of performance obligations. Rather than evaluating transactions under industry rules, ASC 606 requires teams to identify every distinct promise in every customer contract, establish a standalone selling price for each, allocate the transaction price proportionally, and recognize as each obligation is satisfied, at a point in time or over time.

ASC 605 vs ASC 606: A Quick Side-by-side Comparison

DimensionASC 605ASC 606
Framework typeRules-based; industry-specific guidancePrinciples-based; single cross-industry model
Core recognition triggerTransfer of risks and rewardsTransfer of control
Multiple deliverablesInconsistent; software required VSOE to separate elementsDistinct performance obligations; allocation by standalone selling price
Effect of missing fair-value evidenceWithout VSOE, entire arrangement combined and deferredVSOE requirement eliminated
Variable considerationGenerally recognized when determinableEstimated by expected value or most likely amount, subject to constraint
Sales commissionsTypically expensed as incurredCapitalized under ASC 340-40; amortized over the expected benefit period
DisclosureLimitedExpanded: contract balances, disaggregation, significant judgments
IFRS alignmentNoneConverged with IFRS 15
Industry-specific rulesExtensiveEliminated

 

The Five-step Model: Where Theory Becomes Judgment

Stop Guessing on Revenue Recognition

Is your team still managing ASC 606 allocations in fragile spreadsheets? Partner with DNA Growth’s controller-level experts to build defensible, audit-ready revenue models.

Audit-Proof Your Books

Step 1: Identify the contract

A contract exists when five criteria are met: both parties have approved and are committed; each party's rights are identifiable; payment terms are identified; the arrangement has commercial substance; and collection of substantially all consideration is probable.

The collectibility criterion is not a formality. For businesses with meaningful bad-debt exposure it determines whether a contract enters the model at all. Arrangements failing any criterion sit outside ASC 606 until they meet it.

Step 2: Identify the performance obligations

A performance obligation is a promise to transfer a distinct good or service. Distinct means the customer can benefit from it on its own or with readily available resources, and the promise is separately identifiable from other promises in the contract.

This is where the largest structural differences from ASC 605 appear. A SaaS contract covering platform access, implementation, and premium support requires assessing each element for distinctness. Implementation that a third party could perform is generally a separate obligation. Support delivering ongoing value is recognized over the service period. Getting the boundary wrong misstates the revenue waterfall for the entire contract.

Step 3: Determine the transaction price

The transaction price is what the entity expects to be entitled to. Complexity arises with variable consideration: discounts, rebates, bonuses, usage-based fees, rights of return, performance incentives.

ASC 606 requires estimation using either the expected value method or the most likely amount, subject to a constraint. Variable consideration is included only to the extent it is probable that a significant reversal of cumulative recognized revenue will not occur once the uncertainty resolves.

Step 4: Allocate the transaction price

Allocation is made in proportion to relative standalone selling price, the price at which the entity would sell each good or service separately.

Under ASC 605, the residual method was common and could push a disproportionate share of revenue to one element. Under ASC 606, allocation must rest on observable or estimated standalone prices applied consistently. For SaaS companies with tiered pricing, bundled features, and negotiated enterprise discounts, this requires documented SSP methodology and periodic recalibration.

Step 5: Recognize revenue as obligations are satisfied

Revenue is recognized when control transfers, either over time or at a point in time. Over-time recognition applies when the customer simultaneously receives and consumes the benefit, when performance creates or enhances an asset the customer controls, or when performance creates no asset with alternative use and the entity has an enforceable right to payment for work completed to date. Where none apply, recognition is at a point in time.

This determination shapes the revenue curve across every reporting period in the contract.

Where Finance Teams Still Get It Wrong

Misidentifying performance obligations in bundles

The most common material error is treating a bundle as a single obligation when its components are distinct. A SaaS contract covering platform access, onboarding, and support usually contains at least two and often three obligations. Treating it as one recognized at commencement front-loads revenue and understates deferred revenue, a presentation auditors and investors both scrutinize.

Stale standalone selling price documentation

SSPs must be established and applied consistently. Many companies set a methodology at implementation and never revisit it. As discounting, bundling, and market pricing shift, stale SSP assumptions produce allocation errors that compound across a contract portfolio. Spreadsheet-managed SSP is a recognized high-risk area, and it remains common years into adoption.

Underestimating commission accounting

This one is misunderstood more often than any other, partly because it does not live in ASC 606 at all. The cost guidance is codified separately, in ASC 340-40.

Incremental costs of obtaining a contract, most commonly sales commissions, must be capitalized where the entity expects to recover them. Three points that catch teams out:

  • It is not a policy election. Unlike historical practice, capitalization is required where the criteria are met.
  • The resulting balance is a capitalized contract cost, not a contract asset. A contract asset under ASC 606 is a right to consideration conditioned on something other than the passage of time. The two are different line items and conflating them is a presentation error.
  • The amortization period may exceed the contract term. The asset is amortized over the period of expected benefit, which includes anticipated renewals. A commission on a five-year contract expected to renew twice may amortize over seven years, not five.

The practical expedient permitting immediate expensing applies only where the amortization period would be one year or less. It should not be applied by default across all commission arrangements.

Misapplying the variable consideration constraint

The constraint requires genuine judgment. Teams err in both directions: excluding variable amounts highly likely to be realized, or including optimistic usage estimates that later reverse. Both produce statements that do not fairly present revenue, and both create audit risk.

What Finance Leaders Should Be Reviewing Now?

Ensure Your Financials Stand Up to Due Diligence

Don't wait for an audit to uncover revenue recognition errors. DNA Growth provides fractional CFO oversight and offshore execution to keep your accounting policies perfectly aligned with U.S. GAAP.

Schedule a Consultation

ASC 606 is no longer new. The ongoing risk comes from treating compliance as a completed transition project rather than a continuing obligation.

Revenue recognition requires reassessment as contracts evolve. A SaaS company moving from per-seat to consumption-based pricing has changed its performance obligation structure and must revisit its methodology. A professional services firm adding a managed services component to an existing implementation contract may have created a new obligation mid-arrangement.

The practical mandate for CFOs and controllers is threefold:

  • Embed contract review in the revenue workflow rather than performing it retrospectively at quarter-end.
  • Maintain and test SSP documentation for consistency, on a defined cadence.
  • Document the judgment behind each of the five steps well enough to withstand audit scrutiny.

For fractional CFOs and CPA firms advising growth-stage companies, the more pressing question is usually not whether ASC 606 was adopted but whether it was adopted rigorously. A company that treated every multi-element contract as a single obligation, or capitalized commissions selectively, may be carrying a material misstatement in its historical financials. That surfaces in due diligence, at audit, or in the first serious lender review, which are the three worst moments to find it.

Frequently Asked Questions Around ASC 605 vs ASC 606

What is the main difference between ASC 605 and ASC 606? 

The recognition trigger. ASC 605 asked whether risks and rewards had transferred to the customer. ASC 606 asks whether the customer has obtained control, meaning the ability to direct the use of the good or service and obtain all its remaining benefits substantially. ASC 606 also replaced industry-specific guidance with a single model that applies to all industries.

When did ASC 606 take effect? 

For public business entities, fiscal years beginning after December 15, 2017. For all other entities, annual reporting periods beginning after December 15, 2018.

Is ASC 605 still used? 

No, it has been superseded for financial reporting under U.S. GAAP. It remains relevant when analyzing historical financial statements prepared before adoption, or in diligence where prior-period comparability is at issue.

What are the five steps of ASC 606? 

Identify the contract, identify the performance obligations, determine the transaction price, allocate the transaction price to the obligations, and recognize revenue as each obligation is satisfied.

How does ASC 606 treat sales commissions? 

Incremental costs of obtaining a contract are capitalized under ASC 340-40 where the entity expects to recover them, then amortized over the expected period of benefit, which can include anticipated renewal periods. Capitalization is required rather than elective. The practical expedient permitting immediate expensing applies only where the amortization period would be one year or less.

Did ASC 606 accelerate or delay revenue recognition? 

Both, depending on the fact pattern. In software it frequently accelerated recognition, because ASC 985-605 required VSOE for undelivered elements and, absent it, deferred the entire arrangement. In other arrangements, particularly bundles previously recognized at a single point in time, ASC 606 spread recognition across obligations.

Is ASC 606 the same as IFRS 15? 

They are converged and substantially aligned, having been developed jointly by FASB and the IASB. Some differences remain in areas including collectibility assessment, interim disclosure, and certain practical expedients.

ASC 605 vs ASC 606 Revenue Recognition ASC 606 GAAP Compliance Five-Step Model SaaS Accounting
H
Heena Jain

Executive Director & SVP, Strategic Accounts

Every major account I've managed has reinforced one truth: when clients feel genuinely understood, they grow with you. At DNA Growth, we don't just serve clients — we become their strategic advantage. That's the standard I hold myself and our team to, every single day.

Turn Finance Into a Growth Engine

Join 1,200+ companies that rely on DNA Growth for outsourced CFO, FP&A, and accounting support.