ASC 606: The 5-Step Model, Who It Applies To and Where Implementation Goes Wrong

‍Key Takeaways

• ASC 606 applies to all US entities that enter into contracts with customers to transfer goods or services. There is no small business exemption.
• The standard uses a 5-step model: identify the contract, identify performance obligations, determine transaction price, allocate the price, and recognize revenue when obligations are satisfied.
• Step 4, allocating transaction price to performance obligations, is the most commonly misapplied step in multi-element arrangements.
• Revenue must be allocated based on standalone selling price, not the price charged for each component.
• SaaS and subscription businesses face the most complexity under ASC 606 because contracts often bundle multiple performance obligations with variable consideration.

What Is ASC 606?

ASC 606 is the Financial Accounting Standards Board (FASB) standard titled "Revenue from Contracts with Customers." It establishes a unified framework for recognizing revenue that replaces more than 200 pieces of industry-specific guidance that existed under the previous standards.

The core principle is straightforward: recognize revenue in a way that reflects the transfer of promised goods or services to customers in an amount that reflects the consideration the entity expects to receive in exchange for those goods or services.

According to Stripe, ASC 606 was designed to improve comparability across industries and eliminate the inconsistency that came from different sectors following different revenue recognition rules. A software company and a construction firm now apply the same framework to their contracts.

Who Does ASC 606 Apply To?

Every US entity that has contracts with customers to provide goods or services. Public companies, private companies, nonprofits, startups, and small businesses all fall under ASC 606 if they have customer revenue.

There is no revenue threshold, no size exemption, and no industry carve-out except for specific contract types like insurance, leases, and financial instruments that are covered by separate standards.

The most common misconception is that ASC 606 is an enterprise or public company concern. It is not. A two-person SaaS startup with annual subscription contracts is subject to ASC 606. So is a freelance consultant with a retainer agreement. The complexity of implementation scales with contract complexity, but the requirement does not disappear at smaller sizes.

The ASC 606 Five-Step Model

Where ASC 606 Implementation Goes Wrong

Step 4 is where most errors accumulate, specifically in multi-element arrangements.

Here is the problem. A SaaS company charges $12,000 per year structured as $10,000 for software access, $1,500 for onboarding, and $500 for support. The natural response is to allocate revenue exactly as priced: $10,000, $1,500, and $500.

ASC 606 requires allocation based on standalone selling price, which is what the business would charge if it sold each element independently. If the standalone price for onboarding is $3,000 when sold separately, the ASC 606 allocation to onboarding is higher than $1,500 regardless of what the bundled contract shows.

The difference matters because performance obligations are satisfied at different times. Onboarding is completed in month one. Software access is delivered over 12 months. Support is available throughout the year. If onboarding revenue is understated in the allocation, revenue is deferred longer than it should be. If it is overstated, it is recognized too early.

Most clients who have been bundling deliverables without a formal standalone selling price analysis have an ASC 606 compliance gap they do not know about. Discovering this during an audit or acquisition due diligence is a significantly more expensive problem than finding it during a proactive contract review. (This is also, for what it's worth, the advisory conversation that clients remember.)

Three additional errors that show up consistently:

Recognizing revenue at contract signing. Revenue is recognized when performance obligations are satisfied, not when contracts are signed or invoices are issued. A client who recognizes annual subscription revenue upfront on January 1 is recognizing it incorrectly under ASC 606.

Ignoring variable consideration. Refund rights, performance bonuses, and volume discounts are variable consideration that must be estimated and included in the transaction price at contract inception, not when they are settled.

Treating all obligations as satisfied over time. Some performance obligations are satisfied at a point in time, others over time. Software licenses may transfer control at a point in time. Ongoing SaaS access transfers control over time. Getting this distinction wrong affects the entire recognition pattern.

ASC 606 for SaaS and Subscription Businesses

SaaS and subscription businesses face the most complexity under ASC 606 because their contracts routinely bundle multiple performance obligations, include variable consideration, and span multiple periods.

The most common SaaS-specific issues:

Implementation and onboarding fees. These are separate performance obligations if the customer can benefit from them independently. Recognizing them over the subscription term rather than when the service is delivered is one of the most frequent errors in SaaS revenue recognition.

Free trial periods and discounts. Variable consideration constraints require careful estimation of whether and how much revenue to recognize when pricing includes trial periods or usage-based billing.

Contract modifications. When a customer upgrades, downgrades, or extends a subscription, ASC 606 has specific rules for whether the modification is treated as a new contract or a continuation of the existing one. Each treatment produces a different revenue recognition pattern.

For accountants managing SaaS clients, keeping deferred revenue schedules accurate across contract modifications and multi-element arrangements is one of the highest-complexity month-end tasks. Accountants who have explored ASC 606 automation tools for Stripe revenue eliminate most of the manual schedule maintenance that creates errors. And for clients on annual subscription contracts, automating deferred revenue recognition is what keeps the recognition schedule current across contract changes without a manual rebuild every period.

The tools that handle SaaS revenue recognition correctly are the ones that automate the allocation and recognition steps rather than leaving them to manual journal entries that depend on someone remembering to post them at the right time.

Finlens runs on top of QuickBooks with no migration and automates the categorization and reconciliation that ASC 606-compliant revenue recognition depends on across every client you manage.

Before Finlens: Maintain manual recognition schedules for each SaaS client, track contract modifications by hand, post monthly journal entries from a spreadsheet, and hope the deferred revenue balance ties at close.

After Finlens: Revenue recognition is automated. Deferred revenue schedules update as contracts change. Monthly entries post correctly. The close ties without a manual reconciliation project.

ASC 606 has been the standard for over six years. Clients who are still recognizing revenue the way they did under ASC 605, or not thinking about it at all, have a compliance problem that compounds quietly until someone external asks a question the books cannot cleanly answer.

FAQ

What is ASC 606?

‍ASC 606 is the FASB revenue recognition standard that requires businesses to recognize revenue based on when performance obligations are satisfied, not when cash is received or invoices are issued. It applies to all US entities with customer contracts.

What is the 5-step model under ASC 606?

‍The five steps are: identify the contract, identify performance obligations, determine the transaction price, allocate the transaction price to performance obligations, and recognize revenue when each obligation is satisfied.

Does ASC 606 apply to small businesses?‍

Yes. There is no size exemption. ASC 606 applies to any US entity with contracts with customers regardless of size, industry, or revenue level.

What is a performance obligation under ASC 606?

‍A performance obligation is a promise in a contract to transfer a distinct good or service to a customer. A single contract can contain multiple performance obligations that are recognized at different times.

What is standalone selling price in ASC 606?

‍Standalone selling price is the price at which a business would sell a good or service separately if it were not bundled in a contract. ASC 606 requires allocating the transaction price based on relative standalone selling prices, not the prices listed in the bundled contract.

How does ASC 606 affect SaaS businesses?

‍SaaS businesses face the most complexity because contracts typically bundle software access, implementation, and support as separate performance obligations. Each must be identified, allocated a standalone selling price, and recognized when its specific obligation is satisfied.