Revenue Recognition Standards: Practical ASC 606 and IFRS 15 Implementation Guide

Revenue recognition errors are the number one cause of financial restatements, accounting for 37 percent of all SEC-required restatements since ASC 606 took effect. The standard's principles-based approach gives businesses flexibility, but that flexibility creates judgment calls that trip up even experienced accounting teams.

This guide cuts through the theoretical complexity to provide practical implementation guidance for ASC 606 (U.S. GAAP) and IFRS 15 (international standards). Both standards share the same five-step framework, with minor differences in application that we address throughout.

---

The Five-Step Revenue Recognition Model

Step 1: Identify the Contract

A contract exists when all five criteria are met:

1. Approval and commitment --- Both parties have approved the contract (written, oral, or implied)
2. Rights identified --- Each party's rights regarding goods/services are identifiable
3. Payment terms identified --- Payment terms for goods/services can be identified
4. Commercial substance --- The transaction has commercial substance (risk, timing, or amount of cash flows will change)
5. Collectibility probable --- It is probable the entity will collect the consideration

Common issues:

• Verbal agreements with long-standing customers --- still valid contracts if all criteria met
• Contracts with variable consideration --- include if criteria met at inception
• Contracts requiring customer credit approval --- may need to defer until approval obtained

Step 2: Identify Performance Obligations

A performance obligation is a promise to transfer a distinct good or service.

Distinct test (both must be met):

1. Capable of being distinct --- Customer can benefit from the good/service on its own or with readily available resources
2. Distinct within the contract --- The promise is separately identifiable from other promises (not highly interrelated or highly dependent)

Step 3: Determine the Transaction Price

The transaction price is the amount of consideration the entity expects to receive in exchange for transferring goods or services.

Components to consider:

• Fixed consideration --- Contract price, list price
• Variable consideration --- Discounts, rebates, refunds, performance bonuses, penalties
• Constraining variable consideration --- Include only amounts highly probable (IFRS 15) or probable (ASC 606) of not reversing
• Significant financing component --- Adjust if payment timing differs significantly from delivery (>12 months)
• Non-cash consideration --- Measure at fair value
• Consideration payable to customer --- Reduce transaction price unless payment is for distinct goods/services

Variable consideration estimation methods:

1. Expected value --- Probability-weighted sum of possible outcomes (best for large populations)
2. Most likely amount --- Single most likely outcome (best for binary outcomes)

Step 4: Allocate the Transaction Price

When a contract has multiple performance obligations, allocate the transaction price based on relative standalone selling prices (SSP).

SSP determination hierarchy:

1. Observable price --- Price charged when sold separately
2. Adjusted market assessment --- Price competitors charge for similar goods/services
3. Expected cost plus margin --- Expected costs plus appropriate margin
4. Residual approach --- Allowed only when SSP is highly variable or uncertain

Example allocation:

A software company sells a bundle for $120,000 containing:

Step 5: Recognize Revenue

Recognize revenue when (or as) a performance obligation is satisfied by transferring control.

Point in time recognition (control transfers at a specific moment):

• Customer has physical possession
• Customer has legal title
• Customer has accepted the asset
• Customer has significant risks and rewards
• Entity has present right to payment

Over time recognition (control transfers continuously):

• Customer simultaneously receives and consumes benefits (services)
• Entity's performance creates or enhances an asset the customer controls (construction)
• Entity's performance creates an asset with no alternative use AND entity has an enforceable right to payment for performance completed to date

---

Industry-Specific Implementation

SaaS and Subscription Businesses

SaaS revenue recognition is recognized over time because customers simultaneously receive and consume the benefits of the software service.

Key considerations:

• Setup fees --- Generally not distinct; allocate to the software access obligation and recognize over the contract term
• Implementation services --- Distinct if customer could hire a third party; recognize as delivered. Not distinct if highly customized; combine with software access
• Usage-based pricing --- Recognize as usage occurs (sales-based royalty exception for IP licenses)
• Contract renewals --- Evaluate whether renewal option is a material right (if significantly discounted)

Journal entry pattern (monthly SaaS):

Contract value: $12,000/year
Monthly recognition: $1,000

Dr. Accounts Receivable  $1,000
  Cr. SaaS Revenue        $1,000

Manufacturing and Product Sales

Product revenue is typically recognized at a point in time when control transfers.

Shipping terms matter:

Bill-and-hold arrangements --- Revenue recognized before delivery only when:

• Arrangement has substantive business reason
• Product separately identified as belonging to customer
• Product currently ready for transfer
• Entity cannot use the product or direct it to another customer

Construction and Long-Term Contracts

Construction contracts typically satisfy performance obligations over time using input or output methods.

Input method (cost-to-cost):

Revenue recognized = (Costs incurred to date / Total estimated costs) x Total contract price

Output method (milestones, units delivered):

Revenue recognized = (Output delivered to date / Total expected output) x Total contract price

Loss contracts: If total estimated costs exceed the contract price, recognize the entire expected loss immediately.

Professional Services

Fixed-fee engagements:

• Recognize over time using hours incurred / total estimated hours
• Reassess total estimated hours at each reporting date
• If estimate changes, account as a change in estimate (cumulative catch-up)

Time-and-materials engagements:

• Recognize revenue as hours are billed (practical expedient available if right to invoice equals value delivered)

---

Key Differences: ASC 606 vs. IFRS 15

---

ERP Configuration for Revenue Recognition

Odoo Revenue Recognition Setup

1. Enable revenue recognition module in Accounting settings
2. Configure recognition rules per product category:
   • At delivery (point in time)
   • Over contract period (time-based)
   • Based on milestones (output method)
   • Based on percentage of completion (input method)
3. Set up deferred revenue accounts in chart of accounts
4. Create recognition schedules for subscription and long-term contracts
5. Automate journal entries for monthly/quarterly recognition
6. Configure reporting to show recognized vs. deferred revenue by period

Checklist for ERP Revenue Recognition

• Products categorized by recognition method (point-in-time vs. over-time)
• Standalone selling prices documented for bundled products
• Deferred revenue accounts created for each revenue stream
• Recognition schedules tested with sample contracts
• Period-end cutoff procedures documented
• Disclosure reports configured (disaggregation, contract balances, remaining obligations)
• Integration with billing system validated

---

Common Revenue Recognition Errors

1. Recognizing revenue before control transfers --- Shipping FOB destination but recognizing at shipment
2. Ignoring variable consideration --- Not estimating rebates and volume discounts at inception
3. Improper bundling --- Combining performance obligations that should be recognized separately
4. Missing material rights --- Failing to identify renewal discounts as separate obligations
5. Inconsistent SSP determination --- Using different methods for same products without justification

---

Related Resources

• Revenue Recognition Guide: ASC 606 in Odoo --- Platform-specific Odoo configuration
• Financial Reporting Dashboard Guide --- Visualizing revenue metrics
• Audit Preparation Checklist --- Revenue recognition audit readiness
• Odoo Accounting Module Setup --- Foundation configuration

---

Revenue recognition under ASC 606 and IFRS 15 requires thoughtful analysis of each contract type, but the five-step model provides a consistent framework. With proper ERP configuration and documented policies, your organization can achieve compliant, accurate revenue recognition without the month-end scramble. Contact ECOSIRE for expert guidance on revenue recognition implementation.