ASC 606 – the FASB's revenue recognition standard – became effective for most private companies in 2019 and fundamentally changed how US GAAP-compliant companies record revenue from contracts with customers. Five years in, it's still the area where growing companies most commonly make material accounting errors.
The standard applies a five-step framework to every revenue contract.
It must have commercial substance, approved terms, and a payment commitment from the customer. For companies with unsigned orders, verbal agreements, or contracts with approval conditions, this step requires genuine judgment.
This is where most complexity originates. A performance obligation is a distinct promise to deliver a good or service. A SaaS contract that includes software access plus implementation plus training likely has three separate performance obligations – each must be identified, documented, and accounted for separately.
The total amount the company expects to receive, including variable elements. Usage-based fees, volume discounts, refund provisions, and contingent payments all require estimation under a specific methodology – constrained to the amount unlikely to result in a significant revenue reversal.
The total is allocated to each performance obligation in proportion to its standalone selling price – the price the company would charge if it sold that element independently. If no observable standalone selling price exists, one must be estimated using an adjusted market assessment, expected cost plus margin, or residual approach.
Revenue is recognized when each performance obligation is satisfied – either at a point in time (for deliverables like a software license) or over time (for services like subscription access). Getting this step wrong is almost always a consequence of getting steps two through four wrong first.
The most frequent error: a company sells a subscription plus onboarding and records the entire contract value as subscription revenue recognized ratably. Under ASC 606, the onboarding is a separate performance obligation – its allocated revenue is recognized when that service is delivered, not over the subscription term. When contract values are large, this timing difference is material.
ASC 606 requires a consistent, documented method for estimating standalone selling prices when they can't be observed directly. Companies that calculate these differently deal-by-deal, or haven't documented their methodology, will fail this test at audit.
When a customer upgrades, renews early, or materially changes contract scope, the modification requires specific analysis – is it a new contract, a prospective change to the existing one, or a combination? Each determination changes how remaining revenue is recognized. Without a policy and someone applying it consistently, modifications routinely get recorded incorrectly.
Companies with usage-based or milestone-based revenue often recognize variable amounts too aggressively – before it's probable that a significant revenue reversal won't occur. The constraint test is a genuine technical requirement, not a formality, and requires documented judgment applied consistently.
The honest answer: someone for whom this is their primary job.
A Controller managing a full finance function, a Senior Accountant running the close cycle, and a CFO focused on strategy can all have strong US GAAP knowledge without the specific technical depth and sustained bandwidth that ASC 606 requires at scale. The standard demands ongoing analysis – not just at year-end but at every contract execution, every modification, every period-end close.
A Senior Revenue Accountant who owns ASC 606 compliance as their core responsibility builds and maintains the infrastructure that makes this systematic: the contract database, the deferred revenue waterfall, the SSP documentation, the modification log, and the period-end entries and disclosures that depend on all of it.
Senior Revenue Accountants in MAVI's network average five to seven-plus years of dedicated revenue accounting experience with specific expertise in the ASC 606 five-step model across SaaS, subscription, and professional services environments.
If your company has never formally documented its ASC 606 policy – the performance obligation identification methodology, the SSP estimation approach, the contract modification policy – that's where to start. A Senior Revenue Accountant's first deliverable in most engagements is building or formalizing that documentation. Deferred revenue accuracy, audit defensibility, and financial statement reliability all depend on it.
Through MAVI, a Senior Revenue Accountant with this technical depth can be placed in as few as five days, at 50–70% less than a US-market equivalent, with a 14-day risk-free trial and no upfront fees.
Yes. ASC 606 is the US GAAP standard for revenue recognition regardless of whether a company is public or private. Private companies were given a later effective date (fiscal years beginning after December 15, 2018), but the standard fully applies to any company preparing financial statements under US GAAP – for investors, lenders, or audit purposes.
Standalone selling price is the price a company would charge for a good or service if it sold that element independently. It's the basis under ASC 606 for allocating the transaction price among multiple performance obligations. Inconsistent or undocumented SSP methodology is one of the most common audit findings in ASC 606 reviews.
A formal ASC 606 policy document covering each step of the five-step model for the company's contract types; a contract database with performance obligation identification; deferred revenue reconciliation and waterfall schedules; SSP analysis and methodology documentation; a contract modification log; and period-end revenue journal entries with supporting calculations.
For a company with no existing documentation, most produce a formal policy document and initial contract database within the first 30–45 days. Full deferred revenue waterfall reconciliation and modification log completion typically takes 60–90 days depending on contract volume and historical data availability.