How to Apply the ASC 606 Five-Step Model: A Working Guide for Small-Cap Finance Teams

As of July 2026 · Written by Rohit Goel, US CPA · From the filing seat of a US-listed public company

ASC 606 is not five sequential checkboxes. It is five judgment gates, and at a sub-$500M public company each gate is one the SEC staff has comment-lettered somebody your size on in the last twelve months. This guide walks the model the way a reviewer walks it: what the standard actually requires, where the citation lives, and where small-cap filings break. If you want to pressure-test a live contract against each step, run it through the ASC 606 five-step wizard as you read.

Step 1: When do you actually have a contract under ASC 606?

You have a contract when all five criteria in ASC 606-10-25-1 are met: approval and commitment by both parties, identifiable rights, identifiable payment terms, commercial substance, and, the one that bites, probable collection of the consideration you expect to be entitled to.

That last criterion, ASC 606-10-25-1(e), is a gate, not a measurement input. Under US GAAP, "probable" means the future event is likely to occur, in practice, auditors read that as roughly 75–80% likely, a materially higher bar than the greater-than-50% reading of "probable" under IFRS 15. Two traps:

• The assessment is against the amount you expect to collect, not the stated price. If you routinely grant price concessions, the expected consideration is already net of them. A customer who reliably pays 80 cents on the dollar can still pass the gate, for 80 cents.
• Failing the gate does not mean you never recognize revenue. It means you apply ASC 606-10-25-7: recognize only when you've collected consideration that is nonrefundable and either the contract is terminated or you have no remaining obligations. Cash-basis-like, and painful.

Reassess only if there is a significant change in facts and circumstances (ASC 606-10-25-5), a customer sliding into bankruptcy mid-contract, for example.

Step 2: How do you identify distinct performance obligations?

A promised good or service is a separate performance obligation only if it is distinct, and ASC 606-10-25-19 imposes a two-part test: (a) the customer can benefit from the good or service on its own or with readily available resources, capable of being distinct, and (b) the promise is separately identifiable from other promises in the contract, distinct within the context of the contract.

Part (b) is where judgment lives. ASC 606-10-25-21 gives three indicators that promises are not separately identifiable: you provide a significant integration service, one good or service significantly modifies or customizes another, or the goods and services are highly interdependent or highly interrelated. A license plus mandatory customization that transforms the software is usually one obligation. A license plus routine post-contract support is usually two.

Get this wrong and everything downstream is wrong: the allocation in Step 4 and the timing pattern in Step 5 both hang off the unit of account. This is the single highest-leverage judgment in the model, which is why the wizard forces you through the 25-19 test promise by promise before it lets you touch pricing.

Step 3: How do you determine the transaction price when consideration is variable?

The transaction price is the consideration you expect to be entitled to, excluding amounts collected for third parties (ASC 606-10-32-2). Rebates, refunds, credits, performance bonuses, penalties, price concessions, and usage-based fees all make it variable, and ASC 606-10-32-8 gives you two estimation methods: expected value (probability-weighted, suited to large populations of similar contracts) or most likely amount (suited to binary outcomes like a single milestone bonus). Pick per contract, per uncertainty, and apply consistently.

What does the variable consideration constraint actually require?

ASC 606-10-32-11 says you include variable consideration only to the extent it is probable that a significant reversal of cumulative revenue will not occur when the uncertainty resolves. Read that twice: it is a double negative, and it is deliberately asymmetric. You are not estimating the most accurate number; you are estimating the highest number you can defend against reversal.

ASC 606-10-32-12 lists the factors that make constraint more likely: consideration highly susceptible to factors outside your influence (market volatility, third-party actions, weather), long resolution periods, limited experience with similar contracts, a practice of granting concessions, and a broad range of possible outcomes. A small-cap with two years of history on a new product line and a habit of quarter-end concessions should expect its auditor to constrain hard, and should document the reassessment required each reporting period (ASC 606-10-32-14).

Step 4: How do you allocate the transaction price across performance obligations?

Allocate on relative standalone selling price (SSP) at contract inception (ASC 606-10-32-31 through 32-32). The best evidence of SSP is an observable price when you sell the item separately (ASC 606-10-32-32). Absent that, ASC 606-10-32-33 and 32-34 require an estimate, using all reasonably available information, via three sanctioned approaches: adjusted market assessment, expected cost plus margin, or, only when the selling price is highly variable or uncertain, the residual approach.

The small-cap failure mode: using stated contract prices as a proxy for SSP because "that's what we charged." Stated price is not SSP when discounting is uneven across the bundle. If you sell support at list to standalone renewals but bury a 40% discount in bundled new deals, an allocation at stated price front-loads revenue into the license. Build an SSP analysis once, refresh it annually, and keep the workpaper, this is a recurring auditor request and a recurring SEC comment area for software and life-science registrants.

Step 5: Do you recognize over time or at a point in time?

Over-time recognition is not an election. You recognize over time if, and only if, one of the three criteria in ASC 606-10-25-27 is met:

1. The customer simultaneously receives and consumes the benefits as you perform (routine services: payroll processing, monitoring, SaaS hosting).
2. Your performance creates or enhances an asset the customer controls as it is created (construction on the customer's land).
3. The asset has no alternative use to you (ASC 606-10-25-28) and you have an enforceable right to payment for performance completed to date (ASC 606-10-25-29), the criterion that governs custom manufacturing, and the one where the contract's termination clause decides the accounting. "Right to payment" means cost plus a reasonable margin at all times, enforceable under the contract and the governing law, not just deposits.

If none of the three is met, you recognize at a point in time, when control transfers, assessed using the indicators in ASC 606-10-25-30: present right to payment, legal title, physical possession, risks and rewards, customer acceptance. Shipping terms matter here (FOB shipping point vs destination), and so do synthetic FOB-destination practices like routinely replacing in-transit damage.

Why do principal-vs-agent conclusions attract so many SEC comments?

Because gross-vs-net presentation can double or halve reported revenue without changing a dollar of income, and revenue is the metric small-cap valuations trade on. The test is control: you are a principal if you control the specified good or service before it transfers to the customer (ASC 606-10-55-37). ASC 606-10-55-39 gives three indicators, primary responsibility for fulfillment, inventory risk, and discretion in establishing price.

The SEC staff's recurring question, verbatim from comment letters: "Tell us how you considered ASC 606-10-55-36 through 55-40 in concluding you are the principal." If your response leans on pricing discretion alone while a third party fulfills and carries inventory risk, expect a second-round comment. Marketplace, drop-ship, reseller, and ad-tech arrangements deserve a documented control analysis per specified good or service, not per contract, per good or service (ASC 606-10-55-36). Note that after ASU 2016-08, credit risk is no longer an indicator; do not cite it.

What should a small-cap controller document for each of the five steps?

A one-page memo per material contract type covering: the 25-1 collectibility conclusion and evidence; the promise inventory and the 25-19/25-21 distinct analysis; the variable consideration method and constraint rationale under 32-11/32-12; the SSP methodology and refresh date; and the 25-27 criterion relied on (or the 25-30 control-transfer analysis), including the termination-for-convenience payment terms if you rely on criterion three. That memo is what stands between you and a restatement conversation when the auditor rotates or the SEC staff asks. The ASC 606 wizard generates the skeleton of exactly that memo from your answers.

FAQ