Revenue Recognition Guide

Complete Guide to ASC 606 Revenue Recognition

Master the ASC 606 five-step model for revenue recognition. This comprehensive guide covers compliance requirements, common scenarios, and modern automation strategies.

See Automated Revenue RecognitionEra's Solution

In This Guide

What is ASC 606?

ASC 606 (Accounting Standards Codification Topic 606) is the revenue recognition standard issued by the Financial Accounting Standards Board (FASB). It establishes a comprehensive framework for determining when and how much revenue to recognize.

The standard applies to nearly all revenue contracts with customers, replacing previous industry-specific guidance with a single, principles-based approach. Public companies adopted ASC 606 in 2018, while private companies began in 2019.

Who Needs to Comply?

All U.S. companies following GAAP must comply with ASC 606. This includes SaaS companies, professional services firms, manufacturers, and any business that generates revenue from customer contracts.

The Five-Step Revenue Recognition Model

ASC 606 requires companies to follow a five-step process for every customer contract:

1

Identify the Contract

Determine if a valid contract exists with commercial substance and collectability is probable.

Examples:

  • Signed subscription agreement
  • Purchase order acceptance
  • Master service agreement + SOW
2

Identify Performance Obligations

Identify distinct goods or services promised in the contract.

Examples:

  • Software license
  • Professional services
  • Ongoing support/maintenance
  • Training services
3

Determine Transaction Price

Calculate the total consideration expected from the customer, including variable amounts.

Examples:

  • Fixed subscription fee
  • Usage-based charges
  • Volume discounts
  • Performance bonuses
4

Allocate Transaction Price

Allocate transaction price to each performance obligation based on standalone selling prices.

Examples:

  • Software 70% of total price
  • Implementation 20% of total price
  • Support 10% of total price
5

Recognize Revenue

Recognize revenue when (or as) performance obligations are satisfied.

Examples:

  • Point in time (software delivered)
  • Over time (subscription period)
  • Percentage of completion (services)

Common Revenue Recognition Scenarios

SaaS Subscriptions

For SaaS subscriptions, revenue is typically recognized ratably over the subscription period as the service is provided continuously. A $12,000 annual subscription is recognized at $1,000 per month.

Example: Customer signs a 12-month $12,000 SaaS contract on July 1.

  • • Deferred Revenue (July 1): $12,000
  • • Monthly Recognition: $1,000
  • • Remaining Deferred Revenue (Dec 31): $6,000

Multi-Element Arrangements

When a contract includes multiple distinct performance obligations (software + implementation + support), you must allocate the transaction price based on standalone selling prices.

Example: $100,000 contract for software ($70K standalone), implementation ($20K standalone), and support ($15K standalone).

  • • Allocate to Software: $100K × ($70K / $105K) = $66,667
  • • Allocate to Implementation: $100K × ($20K / $105K) = $19,048
  • • Allocate to Support: $100K × ($15K / $105K) = $14,285

Usage-Based Revenue

For usage-based pricing (API calls, storage, compute), revenue is recognized as usage occurs since the amount is variable and contingent on customer activity.

Automating Revenue Recognition with Era

Manual revenue recognition in spreadsheets is error-prone and doesn't scale. Era automates the entire ASC 606 process:

Contract Management

Automatically identify performance obligations and calculate standalone selling prices from your contract data.

Allocation Engine

AI-powered transaction price allocation across multiple performance obligations using residual or relative standalone selling price methods.

Recognition Schedules

Automated revenue schedules for subscriptions, professional services, and complex arrangements with modification tracking.

Waterfall Reporting

Real-time revenue waterfall showing beginning balance, bookings, recognized revenue, and ending deferred revenue.

Best Practices & Compliance Tips

Document Your Revenue Recognition Policy

Create written policies for how you identify performance obligations, determine transaction prices, and recognize revenue for different contract types.

Review Contracts for New Obligations

When adding new products or services, assess whether they're distinct performance obligations requiring separate revenue recognition.

Track Contract Modifications

Maintain audit trails for all contract changes, amendments, and modifications with proper revenue recognition adjustments.

Reconcile Monthly

Reconcile deferred revenue balances monthly. Ensure beginning balance + bookings - recognized revenue = ending balance.

Automate Your Revenue Recognition

See how Era automates ASC 606 compliance for subscriptions, professional services, and complex multi-element arrangements.

Schedule a Demo