ASC 606 is the U.S. GAAP standard governing revenue recognition from contracts with customers, and it sets one rule for nearly every industry: recognize revenue when you transfer a promised good or service to a customer, in the amount you expect to be paid for it. Issued as Accounting Standards Update 2014-09, the standard took effect for public companies in fiscal years beginning after December 15, 2017, and for private companies and nonprofits in fiscal years beginning after December 15, 2018. Every revenue transaction runs through the same five-step framework, and the judgment calls inside those steps are where most companies get into trouble.
Who Has to Apply ASC 606
Any entity that enters into contracts to transfer goods or services to customers in exchange for payment falls within the scope. Public companies, private businesses, and nonprofits all apply the same framework, though some disclosure requirements are lighter for nonpublic entities.
Several transaction types are carved out because other guidance covers them. Leases fall under ASC 842. Insurance contracts fall under ASC 944. Financial instruments and related contractual rights or obligations sit under their own topics, including ASC 310 (Receivables), ASC 320 (Debt Securities), ASC 815 (Derivatives and Hedging), and ASC 825 (Financial Instruments). Guarantees other than product warranties follow ASC 460. Nonmonetary exchanges between companies in the same line of business that exist only to facilitate sales to end customers are also excluded.
Nonprofits carry an extra threshold question: is the transaction an exchange or a contribution? Under ASU 2018-08, the deciding factor is whether the resource provider receives “commensurate value” in return. A donor who funds a program that benefits only the public has made a contribution governed by ASC 958, not ASC 606. When the resource provider receives goods or services of roughly equal value, ASC 606 applies. The sentiment of being a donor and the indirect benefit to the public do not count as commensurate value. Third-party payments made on behalf of an identified customer in an existing exchange, such as Medicare reimbursements, do fall under ASC 606.
The Five-Step Framework
Every revenue transaction runs through five sequential steps. Skipping one breaks the analysis, which is where SEC scrutiny tends to land. The steps sound mechanical, but each demands real judgment.
Step 1: Identify the Contract
A contract exists for ASC 606 purposes when five conditions are all met: both parties have approved the arrangement, each party’s rights are identifiable, payment terms are defined, the contract has commercial substance (the transaction actually changes the entity’s expected future cash flows), and collection of the consideration is probable. “Probable” means the entity has evaluated the customer’s ability and intent to pay. If collectability is doubtful from day one, there is no contract under ASC 606, no matter what the signed paperwork says.
Informal amendments and side agreements count. A verbal scope change from the sales team can create accounting consequences even without a formal written amendment.
Step 2: Identify Performance Obligations
Once a contract is established, break it into its individual promises. Each promise to transfer a distinct good or service is a separate performance obligation. A good or service is distinct when two conditions are met: the customer can benefit from it either on its own or together with resources readily available to the customer, and the promise is separately identifiable from other promises in the contract. The first condition is about capability. The second is about whether the contract bundles things so tightly that they function as a single combined deliverable.
A software license bundled with mandatory customization that significantly modifies the software is often a single obligation. A standard off-the-shelf license paired with optional training is typically two obligations, because the customer can use the software without the training.
Step 3: Determine the Transaction Price
The transaction price is the amount the entity expects to receive for delivering on its promises. Fixed-price contracts are straightforward. Contracts with variable components (performance bonuses, volume rebates, penalties, return rights) require estimation.
ASC 606 provides two methods. The expected value method calculates a probability-weighted average across a range of possible outcomes and works best when the entity has many similar contracts and enough data to assign meaningful probabilities. The most likely amount method picks the single outcome with the highest probability, and it works better for binary situations such as hitting a milestone that triggers a bonus. The entity must use whichever method better predicts the amount it will ultimately receive, and it must apply that method consistently throughout the contract.
Variable consideration is subject to a constraint: include it in the transaction price only to the extent that a significant reversal of cumulative revenue is unlikely once the uncertainty resolves. Reversal risk rises when consideration amounts are heavily influenced by external forces like market volatility or third-party decisions, when the entity has limited experience with similar contracts, when there is a history of broad price concessions, and when the range of possible outcomes is wide. This is where management judgment gets tested hardest and where auditors push back most often.
Contracts with payment terms extending well beyond delivery may contain a significant financing component. When the gap between transfer of goods or services and payment exceeds one year, the entity must adjust the transaction price to reflect the time value of money, separating the revenue element from the interest element. A practical expedient allows entities to skip this adjustment when the gap is one year or less.
Step 4: Allocate the Transaction Price
When a contract has multiple performance obligations, the total transaction price is divided among them based on their relative standalone selling prices. The standalone selling price is whatever the entity would charge if it sold that good or service separately. Observable prices from standalone sales are the best evidence. When those do not exist, ASC 606 provides three estimation approaches:
- Adjusted market assessment. Evaluate what customers in the relevant market would pay for the good or service, potentially referencing competitor pricing adjusted for the entity’s own costs and margins.
- Expected cost plus margin. Forecast the cost of satisfying the obligation and add a reasonable margin.
- Residual approach. Subtract the observable standalone selling prices of other items in the contract from the total transaction price. This method is permitted only when the selling price of the item in question is highly variable or has never been sold on a standalone basis.
The residual approach is the most restricted because it effectively treats one item as whatever is left over, which invites manipulation if used loosely. Getting the standalone selling prices wrong cascades through the whole model.
Step 5: Recognize Revenue
Revenue is recognized when the entity satisfies a performance obligation by transferring control of the promised good or service. Control, not delivery or invoicing, is the trigger. The customer has control when it can direct the use of the asset and obtain substantially all the remaining benefits from it.
Control can transfer over time or at a point in time. An obligation is satisfied over time if any one of three criteria is met: the customer simultaneously receives and consumes the benefits as the entity performs (janitorial services, for example), the entity’s work creates or enhances an asset the customer controls as it is built (a contractor building on the customer’s land), or the entity’s work does not create an asset with an alternative use and the entity has an enforceable right to payment for work completed to date. That third criterion covers many custom-manufacturing and professional-services arrangements.
If none of those criteria apply, the obligation is satisfied at a point in time. Five indicators help pinpoint the moment of transfer:
- The entity has a present right to payment.
- The customer has legal title.
- The customer has physical possession.
- The customer bears the significant risks and rewards of ownership.
- The customer has accepted the asset.
These are indicators, not a checklist. Not every one needs to be present. Shipping terms often matter here: an FOB shipping-point contract transfers control at shipment, while FOB destination transfers control on delivery.
Handling Contract Modifications
Contracts change. Customers add scope, negotiate price reductions, or extend timelines. ASC 606 requires entities to evaluate each modification rather than tack changes onto the original numbers. The treatment depends on what the modification does.
A modification is treated as a separate, standalone contract when two conditions are both met: the scope increases because the additional goods or services are distinct, and the price increases by an amount that reflects the standalone selling prices of those additions. The customer is buying more at a fair price. The original contract’s accounting stays untouched, and the new scope gets its own revenue recognition.
When those conditions are not both met, the modification is folded into the existing contract. If the remaining goods or services are distinct from what was already delivered, the entity accounts for it prospectively, essentially treating it as the termination of the old contract and the start of a new one with updated terms. If the remaining goods or services are not distinct from what came before, such as a partially completed custom build, the entity makes a cumulative catch-up adjustment, recalculating its measure of progress and transaction price as of the modification date. Getting this analysis wrong can accelerate or defer substantial revenue.
Principal or Agent: Gross or Net Revenue
When a third party is involved in delivering goods or services, the entity must determine whether it is acting as a principal or an agent. A principal reports revenue on a gross basis (the full amount charged to the customer). An agent reports on a net basis (only the commission or fee it retains). The difference can be enormous on the income statement without changing actual profit by a dollar.
The test is control. If the entity controls the good or service before it transfers to the customer, it is a principal. If it merely arranges for another party to deliver, it is an agent. Three indicators help make the call:
- Primary fulfillment responsibility. The party the customer looks to when something goes wrong (complaints, returns, service issues) is more likely the principal.
- Inventory risk. Economic exposure from holding inventory before a buyer is identified, or from accepting returns, points toward principal status.
- Pricing discretion. Principals set the price the customer pays. Agents typically cannot.
Marketplace businesses, software resellers, and staffing agencies are where the analysis gets contentious. A company that routes customer orders to a third-party warehouse and never takes title to the goods is probably an agent, even if the customer thinks it is buying from the company. Auditors scrutinize the substance of the arrangement, not the label.
Capitalizing Contract Acquisition Costs
ASC 340-40, the companion guidance to ASC 606, addresses costs incurred to obtain and fulfill contracts. Sales commissions are the most common example. If a commission is incremental, meaning the entity would not have incurred it if the contract had not been obtained, and the entity expects to recover that cost, the commission must be capitalized as an asset rather than expensed immediately.
Costs the entity would have incurred regardless of winning the contract (general travel expenses, non-contingent salaries) are expensed when incurred. A discretionary bonus paid to a salesperson regardless of whether deals close is not incremental. A per-deal commission triggered only by a signed contract is.
The capitalized asset is amortized on a systematic basis consistent with how the related goods or services transfer to the customer. The amortization period is not always the initial contract term. If the entity pays no commission or a materially lower commission on renewals, the original commission likely relates to anticipated renewal periods as well, and amortization should reflect the expected total customer relationship. Switching costs, the significance of the commission relative to contract value, and expected product changes all influence the period.
A practical expedient simplifies this for shorter arrangements: if the amortization period would be one year or less, the entity can expense the costs immediately. The expedient must be applied consistently to similar contracts and disclosed. It cannot be applied selectively to some costs in a contract but not others.
What Has to Be Disclosed
ASC 606 imposes substantial disclosures designed to show the nature, amount, timing, and uncertainty of revenue and cash flows from customer contracts.
On the balance sheet, contract assets and contract liabilities must be presented separately from ordinary accounts receivable. A contract asset arises when the entity has performed work but does not yet have an unconditional right to payment (the right depends on something other than the passage of time). A contract liability arises when the customer has paid in advance of the entity satisfying its obligation. Opening and closing balances of receivables, contract assets, and contract liabilities must be disclosed.
Revenue must be disaggregated into categories that show how economic factors affect the nature, amount, timing, and uncertainty of cash flows. Common categories include product line, geographic region, customer type, contract duration, and timing of transfer (over time versus point in time). Entities applying ASC 280 must reconcile disaggregated revenue with segment reporting. Nonpublic entities can elect out of the quantitative disaggregation requirements.
Entities must disclose the aggregate transaction price allocated to performance obligations not yet satisfied and when they expect to recognize that revenue. Qualitative disclosures must explain the significant judgments made in applying the standard, including how the transaction price was determined, how it was allocated, and how the entity decided whether obligations are satisfied over time or at a point in time. Any assets recognized for contract acquisition or fulfillment costs under ASC 340-40 also require separate disclosure.
What Goes Wrong When You Get It Wrong
Revenue recognition errors are one of the most common triggers for SEC enforcement actions and financial restatements. Regulators do not treat misapplication of ASC 606 as a technicality; they view it as a potential indicator of deeper internal control failures or fraud.
The SEC has charged companies with financial reporting violations tied specifically to ASC 606 misapplication. In an action against CPI Aerostructures, the company faced a civil penalty of up to $400,000 for revenue recognition errors that included incorrect application of the standard and led to multiple restatements. SEC actions can include cease-and-desist orders, officer and director bars, disgorgement, and civil money penalties. In serious cases, executives face parallel criminal charges from the U.S. Attorney’s Office.
Under Sarbanes-Oxley Section 302, management must certify the effectiveness of internal controls and disclose material weaknesses. Section 404 requires both management assessment and independent auditor verification of those controls. Revenue recognition is among the most scrutinized control areas. A material weakness does not require an actual error to have occurred: a “reasonable possibility” that a material misstatement could go undetected is enough to trigger reporting obligations and potential enforcement.
Market consequences compound the regulatory ones. Restatements tied to revenue recognition can cause immediate stock price declines, loss of investor confidence, and increased cost of capital. In severe cases, restatements have preceded bankruptcy proceedings. Companies that draw SEC attention often endure multiple rounds of comment letters, each demanding detailed justification of the judgments made under the five-step framework. Getting the implementation right upfront is dramatically cheaper than defending it after the fact.