ASC 606 Disclosures for IPO: Build the S-1 Revenue Note
Controllers preparing ASC 606 disclosures for IPO need more than a longer version of last year's revenue note. They need to identify which private-company elections no longer apply, preserve exemptions that remain available, and reconstruct evidence for the periods presented.
A compliant private-company note can need expansion without any change to recognized revenue. Start by separating that disclosure work from accounting conclusions that actually need correction.
Key takeaway: Registration changes the disclosure checklist. It doesn't make every historical private-company revenue note wrong, and it doesn't eliminate every RPO exemption.
Can a compliant private-company revenue note need expansion?
Yes. Eligible nonpublic entities have deliberately narrower disclosure requirements. FASB's 2014 basis for conclusions, BC506 through BC517, explains the cost-benefit rationale for differences covering disaggregation, contract balances, remaining performance obligations, contract costs and selected judgments.
That creates two separate review questions: was the old note appropriate for its reporting basis, and what must the registration financial statements now disclose? A missing public-entity disclosure is not, by itself, evidence that historical revenue was misstated.
Keep separate issue lists. Put unavailable comparative detail on the disclosure list; put unsupported contract duration, allocation or recognition conclusions on the accounting list. Adding paragraphs won't repair a measurement error.
If the recognition model itself needs a refresher, Finrep's ASC 606 revenue recognition guide provides the broader starting point. This article addresses the conversion of the note and its supporting evidence.
Which reporting status controls ASC 606 disclosures for IPO?
Assess the reporting entity and accounting framework before choosing disclosure elections. Form S-1 Item 11(e) requires financial statements meeting Regulation S-X. The relevant test is not whether the shares have started trading.
The public business entity definition in ASU 2013-12 includes entities filing or furnishing financial statements with the SEC. An entity meeting that definition solely through inclusion in another entity's SEC filing has a filing-purpose limitation; don't extend that exception to the registrant itself.
An emerging growth company's extended transition election concerns adoption dates. SEC staff guidance in FRM 10230.2 says that relief does not exempt EGCs from standards applicable to public entities. It is staff guidance, and the scope of each standard still matters.
Document the framework, entity status and adoption elections separately. This guide addresses a domestic US GAAP issuer; the IASB IFRS exception in Rule 4-01(a) requires a different framework analysis, not transplantation of ASC nonpublic elections into IFRS reporting.
What belongs in the disclosure and evidence matrix?
Map each note requirement to an actual historical election and a reproducible schedule. The table summarizes disclosure areas in FASB's ASC 606 and ASC 340-40 amendment text. Its evidence column is a suggested preparation method, not an additional GAAP requirement.
| Area and reference | Public-entity disclosure focus | Suggested supporting evidence |
|---|---|---|
| Disaggregation, 606-10-50-5 and 50-6 | Economic categories and relationship to segment revenue | Category definitions, ledger reconciliation, segment mapping |
| Contract balances, 50-8 through 50-10 | Opening/closing balances, beginning-liability revenue, timing relationships and significant changes | Balance tie-outs, release cohorts, acquisition and modification explanations |
| Performance obligations, 50-12 | Satisfaction timing, payment terms, goods/services, agency, refunds and warranties | Contract families, clause references, delivery evidence |
| RPO, 50-13 through 50-15 | Remaining transaction price and expected recognition timing, subject to exemptions | Enforceable duration, allocation and exclusion memo |
| Significant judgments, 50-17 through 50-20 | Timing, transaction price, constraints and allocation | Control/progress conclusions, standalone selling prices, estimate history |
| Contract costs, 340-40-50 | Judgments, balances, amortization, impairment and expedient use | Commission/fulfillment schedules, recovery support, amortization lives |
Historical elections need their own column in the working version. Eligible nonpublic entities can use timing-based disaggregation plus economic-factor narrative, retain only opening/closing contract-balance disclosures, and omit RPO disclosures under specified elections. Selected judgment relief still retains variable-consideration constraint disclosures; performance-obligation descriptions are not wholly optional. FASB's discussion of nonpublic relief also contain specific contract-cost and expedient-disclosure elections.
Add a period-availability column and an owner. A polished current-year table won't answer a comparative-period question if the historical extraction hasn't been built.
How should revenue be disaggregated in an S-1?
Choose categories with an economic explanation, then test that explanation against the company's other reporting. A chart of accounts provides the population; it doesn't automatically provide the right categories. Compare the proposed grouping with segment information, management packs, MD&A and the offering narrative.
Black Rock Coffee Bar's 27 June 2025 response, comment 15, illustrates the question. Responding to 13 June comments on its 19 May draft S-1, the company addressed why it separated store revenue and other revenue rather than beverage and food revenue.
The issuer described differences between in-store and online channels involving traffic, fulfillment, delivery and platform risks. It also explained its view that beverage and food shared economic factors, fulfillment and revenue patterns, and were not separately used by its chief operating decision maker for resource allocation.
That is a company-specific rationale, not a rule that channel categories always suffice. The response alone doesn't establish how review concluded.
For your category memo, record the alternatives considered and the information each grouping would reveal. Explain why a dimension prominent in investor materials is included, combined or omitted; unexplained inconsistency invites a second conversation.
What contract-balance evidence needs reconstruction?
Track the opening contract-liability cohort separately from total releases. The following illustrative example shows why a movement schedule and beginning-liability revenue answer different questions. All amounts are in thousands of dollars, with no acquisitions, foreign exchange, refunds or other movements.
| Illustrative contract-liability movement | $000 |
|---|---|
| Opening liability | 120 |
| New amounts deferred during the period | 80 |
| Revenue released from liabilities | (150) |
| Closing liability | 50 |
The arithmetic is $120 + $80 - $150 = $50. Assume $90 of the releases relates to the opening balance and $60 relates to amounts deferred during the period; those components total $150.
The opening-cohort figure is therefore $90, not $150. Of the closing $50, $30 remains from the opening cohort and $20 from current-period additions.
A controller's useful schedule preserves that lineage instead of estimating it from the net movement. A movement table helps explain the balances, but ASC 606 does not prescribe a complete rollforward in one mandatory format.
Also track revenue relating to obligations satisfied or partly satisfied in earlier periods. The 2016 amendment moved that requirement to ASC 606-10-50-12A; don't carry forward 50-8(c) as the current reference. Keep catch-up adjustments and transaction-price changes identifiable.
When can a public entity omit RPO information?
Loss of the nonpublic election doesn't remove contract-specific exemptions. Under ASC 606-10-50-14 through 50-15, as amended in 2016, test original expected duration of one year or less, qualifying right-to-invoice treatment, and specified variable-consideration exemptions.
The latter cover qualifying IP royalties and variable amounts allocated entirely to wholly unsatisfied obligations or qualifying series promises. Right-to-invoice and those added variable-consideration exemptions don't exempt fixed consideration. Explain exemptions used and excluded obligations and consideration; omission of the amount doesn't mean silence about the arrangement.
Build the memo by contract family, then separate fixed and variable components. “We invoice monthly” isn't enough to establish right-to-invoice treatment, and a contract with three months left isn't automatically short duration: the test uses its original expected duration.
Consider an illustrative 36-month noncancelable, fixed-fee service contract. Monthly invoicing doesn't turn its original duration into one month, and the fixed fee cannot disappear under a variable-consideration exemption.
Contrast that with a three-year commercial relationship that creates only separate 12-month enforceable subscription obligations. The legal agreement's headline term may not answer the accounting duration question. Have legal and technical accounting validate termination rights and enforceability before using either conclusion.
Which judgments need more than policy language?
Explain the evidence behind the judgment, not just the policy's name. Hinge Health's 17 January 2025 response, comments 9 and 11, addressed December 2024 staff questions on its November 2024 draft S-1.
Staff asked how typical three-year contracts interacted with termination rights and contract duration, and requested RPO disclosure if required. The issuer explained that enforceable rights and obligations began with individual 12-month member subscriptions and cited the short-duration exemption.
Staff separately asked how it constrained variable consideration. Hinge Health described cohort conversion history, client-specific billing rules and quarterly lookbacks, and stated that it revised its disclosure.
The useful lesson is the supporting detail. Neither that response nor the exemption it invoked establishes SEC approval for another company's contracts.
For your review package, connect each judgment to the relevant contract clauses, operational data and dated accounting conclusion. For estimates, preserve the assumptions used at each reporting date, subsequent outcomes and reasons for changes.
If AI helps extract clauses, require a person to compare them with the executed contract. Finrep's four ASC 606 risks for controllers discusses that separate validation problem.
What should the controller hand to the reviewer?
Hand over a traceable package, with open issues visible. Organize it so a reviewer can move from disclosure sentence to accounting conclusion to supporting population without requesting a fresh spreadsheet for each question.
- Status and election register: framework, entity assessment, adoption dates and historical disclosure elections.
- Population and period map: contracts, revenue and balances reconciled to the ledger, with historical gaps assigned to owners.
- Decision memos: disaggregation categories, enforceable duration, RPO exclusions and significant judgments.
- Schedules and draft note: cohort releases, catch-ups and contract costs linked to the proposed wording.
- Consistency and open-issue log: differences across the note, segments, MD&A and business description, with required decisions and dates.
Use source-linked research and comparable filings to challenge the draft. Peer wording is a reference point; your contracts and evidence determine the answer.
Confirm the current Codification paragraphs and the requirements for each annual and interim period before sign-off. FASB's issued updates explain the amendments, but they are not a substitute for the consolidated standard.
Frequently asked questions
Does expanding the note require a restatement?
Not automatically. Disclosure expansion and correction of recognition or measurement errors are separate assessments. Resolve the underlying issue before choosing how it appears in the registration financial statements.
Can an EGC retain private-company revenue disclosure elections?
An extended adoption-date election doesn't itself preserve those elections. Evaluate public-entity scope separately, as FRM 10230.2 explains.
Is RPO the same as backlog or ARR?
Don't assume equivalence. Reconcile differences in contract populations, enforceability, consideration and exclusions before using a management metric as support for the note.
Must every company disaggregate by product?
The Black Rock Coffee exchange shows why the category choice needs explanation. It doesn't establish a universal product split or a universal channel exemption.
What if comparative evidence is missing?
Assign the gap, identify retained contract and billing records, and agree a reconstruction approach with the audit team. A copied peer table cannot supply missing historical evidence.
