Quick Reference: ASC 606 in 60 Seconds

ASC 606 standardizes revenue recognition across industries using a 5-step model. For SaaS companies, this means properly identifying performance obligations, allocating transaction price, and recognizing revenue as services are delivered. This comprehensive checklist ensures your compliance.

Understanding ASC 606 for SaaS Companies

The Financial Accounting Standards Board (FASB) introduced ASC 606 to create a single, comprehensive revenue recognition standard across all industries. For SaaS and subscription businesses, proper implementation is critical for:

The 5-Step Revenue Recognition Model

ASC 606 requires a structured approach to revenue recognition:

1

Identify the Contract with a Customer

A contract exists when there's approval, rights are identified, payment terms are clear, commercial substance exists, and collection is probable.

SaaS Example:

A customer signs a 12-month SaaS subscription agreement for $60,000/year with monthly billing. This is a valid contract under ASC 606.

2

Identify Performance Obligations

Separate distinct promises to transfer goods or services. Each performance obligation must be distinct and separately identifiable.

SaaS Example:

A contract includes: (1) Software access - $50,000, (2) Implementation services - $10,000, (3) Annual support - included. These represent 2-3 distinct performance obligations depending on whether support is separately identifiable.

3

Determine the Transaction Price

Calculate the amount you expect to receive, including variable consideration, time value of money, and non-cash consideration.

SaaS Example:

Base price $60,000 + variable usage fees (estimate $5,000) - likely discount (estimate -$3,000) = Transaction price of $62,000

4

Allocate Transaction Price to Performance Obligations

Allocate based on standalone selling price (SSP) for each performance obligation. Use observable prices or estimation techniques.

SaaS Example:

Software SSP: $55,000 (89%), Implementation SSP: $7,000 (11%). Allocate $62,000 proportionally: Software gets $55,180, Implementation gets $6,820.

5

Recognize Revenue When Performance Obligations Are Satisfied

Revenue is recognized over time or at a point in time based on transfer of control to the customer.

SaaS Example:

Implementation: Recognize $6,820 upon completion (point in time). Software subscription: Recognize $55,180 ratably over 12 months ($4,598/month) as service is provided (over time).

Complete ASC 606 Compliance Checklist

Use this comprehensive checklist to ensure your SaaS company is fully compliant:

Contract Management

Performance Obligations

Transaction Price & Allocation

Revenue Recognition Timing

Deferred Revenue & Contracts

Documentation & Disclosures

Systems & Processes

Common SaaS Revenue Recognition Scenarios

Scenario 1: Annual Subscription with Upfront Payment

Contract: $120,000 annual subscription paid upfront on January 1

Treatment:

Scenario 2: Software + Implementation Services

Contract: $100,000 total ($80,000 software annual subscription + $20,000 implementation)

Treatment:

Scenario 3: Usage-Based Pricing

Contract: $5,000 base fee + $10 per API call

Treatment:

Scenario 4: Multi-Year Contract with Annual Renewals

Contract: 3-year agreement, billed annually, customer can cancel after each year

Treatment:

Automating ASC 606 Compliance

Manual revenue recognition is error-prone and time-consuming. Modern ERP systems automate ASC 606 compliance:

Manual Process Challenges

Automated Era Platform

Automate ASC 606 Compliance with Era

Era's AI-native platform automatically handles ASC 606 revenue recognition, from contract analysis to schedule generation to financial reporting. Reduce compliance costs by 80% and eliminate manual errors.

See ASC 606 Automation DemoMonth-End Close Checklist