ASC 606 revenue recognition is where Senior Accountants prove their value at US software, services, and subscription companies. The five-step model is straightforward to recite, and the judgment calls inside it are what drive audit adjustments, restatements, and technical interview questions. This guide covers the areas that need senior-level judgment most often: variable consideration, contract modifications, standalone selling price allocation, principal versus agent determinations, and contract costs.
Variable consideration includes discounts, rebates, refunds, credits, price concessions, performance bonuses, and usage-based fees. The standard asks you to estimate it using either the expected value method, which suits a large population of similar contracts, or the most likely amount method, which suits outcomes with two possible results. The choice should match how the contract behaves, and you should apply it consistently to similar contracts.
The constraint then limits how much of that estimate enters the transaction price. You include variable consideration only to the extent it's probable that a significant reversal of cumulative revenue won't occur when the uncertainty resolves. Factors that increase reversal risk include susceptibility to outside influence, a long time before resolution, limited experience with similar contracts, and a wide range of possible outcomes. A SaaS company with tiered volume rebates, for example, estimates the expected rebate, reduces the transaction price accordingly, and updates the estimate each reporting period with the true-up recorded in revenue.
Auditors look for documentation of the method, the historical data supporting it, and the reassessment process. A one-page policy memo with an annual back-test of estimates against actual outcomes covers most of what they ask.
A contract modification changes the scope or price of an existing contract, and the accounting depends on a short decision sequence. When the modification adds distinct goods or services at a price that reflects their standalone selling price, it's accounted for as a separate contract. When the remaining goods or services are distinct from those already delivered, the original contract is treated as terminated, and a new one begins, with the remaining consideration allocated prospectively. When the remaining goods or services aren't distinct, the modification becomes part of the original contract and a cumulative catch-up adjustment is recorded.
Mid-term seat upgrades show how the tests play out. Additional seats priced at the standard rate form a separate contract. The same seats sold at a steep discount fail the pricing test and move you into the prospective treatment. Enforceability matters too: an approved change order with an unpriced scope change still requires you to estimate the price and apply the standard, so keep the approval trail in the file.
Allocation spreads the transaction price across performance obligations based on the relative standalone selling price. The best evidence is the observable price when the company sells the item separately. Without that, the standard permits an adjusted market assessment, an expected cost plus margin approach, or, in limited situations where prices are highly variable or uncertain, the residual approach.
Bundled software deals create most of the judgment. Implementation or configuration services may or may not be distinct from the subscription, depending on whether the customer can benefit from them on their own and whether they're separately identifiable in the contract. Discounts get allocated proportionally unless there's observable evidence that the discount relates to specific obligations. A documented SSP analysis, refreshed at least annually and whenever pricing changes, keeps the allocation defensible.
Principal versus agent determinations decide whether revenue is reported gross or net. The test centers on control: does the company control the specified good or service before it transfers to the customer? Indicators include primary responsibility for fulfillment, inventory risk, and discretion in setting the price. Marketplace and reseller arrangements frequently hinge on these facts, and the conclusion should be documented for each arrangement type.
Licensing adds another layer. A right to access intellectual property that changes over the license period is recognized over time, while a right to use intellectual property as it exists at the point of transfer is recognized at a point in time. Hosting arrangements and software licenses sit on this boundary, so the contract terms around customer control of the software deserve a careful read.
ASC 340-40 covers the costs associated with revenue contracts. Incremental costs of obtaining a contract, sales commissions being the common example, are capitalized when the company expects to recover them. A practical expedient allows immediate expensing when the amortization period would be one year or less. Capitalized costs are amortized over the period of benefit, which often includes anticipated renewals when renewal commissions aren't commensurate with the initial commission.
Disclosures complete the picture: disaggregation of revenue, contract balances, remaining performance obligations, and the significant judgments applied. Senior accountants who maintain these schedules during the close avoid scrambling at year-end.
Fluency in ASC 606 at the senior level comes down to a repeatable discipline: each judgment area needs a documented policy, supporting evidence, and periodic reassessment. Accountants who can show that discipline in an interview, an audit, or a month-end review stand out because they demonstrate that every revenue number rests on a defensible basis.
The standards are largely converged, which is why IFRS-trained accountants adapt quickly. The remaining differences are narrow: the threshold for 'probable' in the collectibility criterion is higher under US GAAP, nonpublic entities get some disclosure relief, and a few practical expedients differ.
Use an adjusted market assessment or an expected cost plus margin approach, document the inputs, and set a range around the estimate. Revisit it when pricing, product mix, or discounting patterns change.
Contract modifications, variable consideration, and distinct performance obligations in software bundles are the most common. Preparing one worked example for each gives you ready answers.
A policy memo for each significant judgment, a contract review checklist, the SSP analysis, and evidence of periodic reassessment. Consistent files let auditors test the approach once instead of re-deriving it each period.
A policy memo for each significant judgment, a contract review checklist, the SSP analysis, and evidence of periodic reassessment. Consistent files let auditors test the approach once instead of re-deriving it each period.