Revenue Recognition

What Is Revenue Recognition?

Revenue recognition is the accounting principle that determines when and how revenue is recorded in financial statements. Under modern accounting standards (ASC 606 / IFRS 15), revenue is recognized when a company satisfies its performance obligations to customers—not necessarily when cash changes hands.

Getting revenue recognition right is critical because:

• Revenue is the top line of the income statement
• Investors and analysts scrutinize revenue closely
• Improper recognition can constitute fraud
• Complex contracts require careful analysis

The ASC 606 Five-Step Model

ASC 606 provides a framework for recognizing revenue:

Step 1: Identify the Contract

A contract exists when:

• Parties have approved and committed to the contract
• Rights and payment terms are identifiable
• Contract has commercial substance
• Collection is probable

Step 2: Identify Performance Obligations

Separate obligations exist for each distinct good or service:

• Customer can benefit from it on its own
• It’s separately identifiable from other promises

Examples:

• Software license (distinct)
• Implementation services (may be distinct or combined)
• Ongoing support (distinct)

Step 3: Determine Transaction Price

Total consideration expected, including:

• Fixed amounts
• Variable consideration (bonuses, penalties)
• Non-cash consideration
• Financing components

Step 4: Allocate Transaction Price

Allocate to each performance obligation based on:

• Standalone selling prices
• Or estimates if standalone price not available

Step 5: Recognize Revenue

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

• Point in time: Control transfers at a specific moment
• Over time: Control transfers gradually (e.g., construction projects)

Common Revenue Recognition Scenarios

SaaS Subscriptions

• Annual subscription paid upfront: $12,000
• Performance obligation: Access to software over 12 months
• Recognition: $1,000/month over the subscription period

Product with Support

• Product sale: $10,000
• 1-year support included: Standalone value $2,000
• Allocate $8,333 to product (recognized at delivery)
• Allocate $1,667 to support (recognized over 12 months)

Long-Term Contracts

• Construction contract: $1,000,000 over 18 months
• Performance obligation satisfied over time
• Recognition: Based on percentage of completion (cost or output method)

Licenses

• Functional license (software): Recognize at delivery
• Symbolic license (brand): Recognize over license period

Revenue Recognition Challenges

Multiple elements: Contracts with products, services, and support bundled together

Variable consideration: Discounts, rebates, and performance bonuses

Contract modifications: Changes to scope or price mid-contract

Judgments required: Standalone selling prices, completion percentages

System limitations: ERP may not support complex recognition rules

Audit scrutiny: Revenue recognition is a high-risk audit area

Deferred Revenue

When cash is received before revenue is earned:

• Record as deferred revenue (liability)
• Recognize revenue as performance obligations are satisfied
• Common in subscriptions, prepaid services, and deposits

Example:

Receive $12,000 annual subscription payment:
  Debit:  Cash                    $12,000
  Credit: Deferred Revenue        $12,000

Each month, recognize 1/12:
  Debit:  Deferred Revenue        $1,000
  Credit: Revenue                 $1,000

How Go Fig Helps with Revenue Recognition

Go Fig supports revenue recognition analysis:

Revenue tracking: Monitor recognized vs. deferred revenue across contracts

Schedule visibility: See future revenue recognition schedules

Multi-system consolidation: Combine revenue data from multiple ERPs

Variance analysis: Identify differences between expected and actual recognition

Reporting: Generate revenue reports by period, product, and customer

Audit support: Maintain documentation for revenue recognition decisions