What is ASC 606 Revenue Recognition? (Definition + accounting example)
ASC 606 (Revenue from Contracts with Customers) is the accounting standard that governs how and when companies recognize revenue. It requires revenue to be recognized when control of goods or services transfers to the customer, following a five-step model. For SaaS companies, ASC 606 determines how subscription revenue, implementation fees, and multi-element arrangements are recognized over time.
The Five-Step Model
Step 1: Identify the Contract
A contract exists when there is commercial substance, the parties have approved it, payment terms are identifiable, and collectibility is probable. In SaaS, this is typically the signed subscription agreement or online terms of service accepted at checkout.
Step 2: Identify Performance Obligations
Each distinct promise in the contract is a separate performance obligation. Common SaaS performance obligations:
| Obligation | Distinct? | Recognition Pattern |
|---|---|---|
| Software subscription access | Yes | Ratably over subscription period |
| Implementation / onboarding | Usually yes | Upon completion or over service period |
| Training | Usually yes | Upon delivery |
| Premium support (above standard) | Depends | Ratably over support period |
| Data migration | Usually yes | Upon completion |
Step 3: Determine the Transaction Price
The total amount the company expects to receive. In SaaS, this includes the subscription fee, implementation charges, and any variable consideration (usage-based fees estimated using the expected value or most likely amount method).
Step 4: Allocate to Performance Obligations
Allocate the total transaction price to each obligation based on relative standalone selling prices (SSP). If a $15,000 contract includes a $12,000 subscription and $3,000 implementation, each is allocated proportionally.
Step 5: Recognize Revenue
Recognize revenue as each obligation is satisfied:
| Obligation | Satisfaction | Revenue Timing |
|---|---|---|
| Subscription ($12,000/year) | Over time | $1,000/month for 12 months |
| Implementation ($3,000) | Point in time | $3,000 when complete |
| Total contract | $15,000 over 12 months |
Worked SaaS Example
A SaaS company signs a 12-month enterprise contract on January 1:
| Component | Amount | SSP | Allocated Price | Recognition |
|---|---|---|---|---|
| Platform subscription | $36,000/yr | $36,000 | $34,286 | $2,857/month × 12 |
| Implementation | $6,000 | $8,000 | $5,714 | On completion (Feb) |
| Total | $42,000 | $44,000 | $40,000 |
Note: The contract price ($40,000 after discount) is allocated based on relative SSPs of $36,000 and $8,000.
Revenue recognition schedule:
| Month | Subscription | Implementation | Total Recognized |
|---|---|---|---|
| Jan | $2,857 | $0 | $2,857 |
| Feb | $2,857 | $5,714 | $8,571 |
| Mar–Dec | $2,857/mo | $0 | $2,857/mo |
| Full Year | $34,286 | $5,714 | $40,000 |
Why ASC 606 Matters for SaaS
Finance teams must comply with ASC 606 to produce GAAP-compliant financial statements. For SaaS companies, the standard's biggest impact is on the timing of revenue recognition — cash received upfront from annual contracts cannot be recognized immediately, and multi-element deals require careful allocation. This creates a permanent gap between cash received and revenue reported.
In investor reporting, ASC 606 compliance is table stakes for any company seeking institutional investment, audit opinions, or public listing. Revenue restatements due to recognition errors damage credibility and can materially impact valuation. The standard also affects key SaaS metrics — deferred revenue balances, recognized MRR, and billings-to-revenue ratios.
A common mistake is treating all contract components as a single performance obligation. A SaaS contract that bundles subscription + implementation + training should identify each distinct obligation and recognize revenue separately. Lumping everything together and recognizing ratably either accelerates or defers revenue incorrectly.
ASC 606 directly governs how deferred revenue is created and unwound — every prepaid SaaS contract generates a deferred revenue liability that is released to the income statement as performance obligations are satisfied. It also impacts accrued revenue when revenue is earned before invoicing, as is common with usage-based billing models.
See how JustPaid automates ASC 606 compliance
Frequently Asked Questions
Step 1: Identify the contract with the customer. Step 2: Identify the performance obligations in the contract. Step 3: Determine the transaction price. Step 4: Allocate the transaction price to the performance obligations. Step 5: Recognize revenue as each performance obligation is satisfied.
Related Terms
Deferred Revenue
Deferred revenue is payment received for goods or services that have not yet been delivered, recorded as a liability on the balance sheet until the obligation is fulfilled. In SaaS, deferred revenue arises when a customer pays upfront for an annual subscription but the service is delivered monthly over 12 months.
Accrued Revenue
Accrued revenue is revenue that has been earned by delivering goods or services but has not yet been invoiced or received as payment. In SaaS, accrued revenue occurs when a company delivers service before billing — the opposite of deferred revenue, where payment is received before delivery.
MRR (Monthly Recurring Revenue)
Monthly Recurring Revenue (MRR) is the predictable revenue a SaaS company earns each month from active subscriptions. MRR normalizes different billing periods — annual, quarterly, and monthly — into one consistent monthly figure, making it the foundational metric for SaaS financial planning.
