Revenue Recognition

ASC 606 and IFRS 15 compliant revenue recognition with automated schedules

7 min read

Overview

Revenue recognition determines when and how revenue appears in your financial statements. The AI-Native ERP provides full ASC 606 and IFRS 15 compliance through automated recognition schedules, deferred revenue tracking, and multiple recognition methods.

Why Revenue Recognition Matters

Compliance -- Required by GAAP (ASC 606) and IFRS 15
Accuracy -- Revenue is matched to when it is earned, not when invoiced
Forecasting -- Deferred revenue balances provide visibility into future revenue
Performance -- Measure revenue delivery over time
Audit -- Complete trail of every recognition decision

The ASC 606 Five-Step Model

Identify the contract -- Agreement with a customer
Identify performance obligations -- What you promise to deliver
Determine the transaction price -- Total consideration
Allocate the price -- To each performance obligation
Recognize revenue -- When (or as) each obligation is satisfied

How It Works

Without Revenue Recognition

A customer pays $12,000 upfront for an annual subscription. Recording all $12,000 as revenue in January overstates that month and understates the remaining eleven.

With Revenue Recognition

The $12,000 is recorded as deferred revenue on day one. Each month, $1,000 moves from deferred revenue to earned revenue:

Jan 1: Customer pays $12,000 for annual subscription
       Cash increases by $12,000
       Deferred Revenue increases by $12,000

Monthly (Jan through Dec):
       Deferred Revenue decreases by $1,000
       Revenue increases by $1,000

Result: Revenue recognized evenly over 12 months

Revenue Recognition Flow

STEP 1: CONTRACT & INVOICE CREATION
  Contract with customer, terms, and amount defined
  Invoice posted: Cash or AR debited, Deferred Revenue credited

         |
         v

STEP 2: CREATE RECOGNITION SCHEDULE
  Schedule type selected (straight-line, milestone, etc.)
  Frequency set (monthly, quarterly, annually)
  Period-by-period recognition plan generated

         |
         v

STEP 3: MONTHLY RECOGNITION (Automated)
  Schedule runner processes pending lines each period
  Journal entry created: Deferred Revenue debited, Revenue credited
  Line status updated from "planned" to "posted"

         |
         v

STEP 4: REPORTING & COMPLIANCE
  Monthly recognized revenue reported
  Deferred balance tracked over time
  ASC 606 disclosures generated automatically

Recognition Methods

1. Straight-Line Recognition

Equal amount each period. The most common method for recurring services.

Best for:

SaaS subscriptions
Software licenses (time-based)
Service contracts
Maintenance agreements

Example: A $12,000 annual contract creates 12 monthly lines at $1,000 each.

2. Milestone-Based Recognition

Revenue recognized upon achieving specific milestones. Each milestone represents a deliverable with an allocated portion of the total contract value.

Best for:

Consulting projects
Custom software development
Implementation services
Professional services

Example: A $300,000 digital transformation project with four milestones:

Milestone	Deliverable	Allocation	Amount
M1	Requirements document	30%	$90,000
M2	Technical design	40%	$120,000
M3	System deployed	20%	$60,000
M4	Training complete	10%	$30,000

Revenue is recognized as each milestone is completed and accepted.

3. Usage-Based Recognition

Revenue recognized as usage occurs. Appropriate for metered and consumption-based services.

Best for:

API call pricing
Compute and storage consumption
Transaction-based pricing
Metered services

Example: An API access contract at $0.10 per call:

Month	Usage	Revenue
January	10,000 calls	$1,000
February	15,000 calls	$1,500
March	12,000 calls	$1,200

4. Percentage-of-Completion

Revenue based on project completion percentage. Suited for long-duration projects where progress can be measured.

Best for:

Long-term projects
Construction contracts
Complex implementations

Example: A $500,000 ERP implementation over 12 months:

Checkpoint	Progress	Cumulative Revenue
Month 3	20%	$100,000
Month 6	50%	$250,000
Month 9	75%	$375,000
Month 12	100%	$500,000

Schedule Line States

Each line in a recognition schedule has a status:

Status	Description	Action
Planned	Future recognition period	Awaiting its period
Pending	Ready to post	Can be posted now
Posted	Revenue recognized	Complete
Skipped	Intentionally skipped	Manual review
Voided	Cancelled	No further action

Deferred Revenue from Invoices

When a customer pays upfront, the full amount is recorded as deferred revenue. A recognition schedule then moves the appropriate portion to earned revenue each period.

Accounting flow for an annual prepayment:

Invoice created: AR debited $12,000, Deferred Revenue credited $12,000
Customer pays: Cash debited $12,000, AR credited $12,000
Each month: Deferred Revenue debited $1,000, Revenue credited $1,000
After 12 months: Deferred Revenue balance is zero, Revenue totals $12,000

Contract-Based Recognition

For subscription contracts, the system links revenue schedules to contract terms:

Create the contract with customer, dates, and billing frequency
Add contract lines for each product or service
Activate the contract and generate invoices
Create recognition schedules tied to the contract
Monthly processing automatically recognizes the correct amount

Contracts support annual, quarterly, or monthly billing with separate recognition cadences.

Proration and Amendments

Mid-Period Upgrades

When a customer upgrades mid-contract, the system handles proration:

Calculates remaining value at the original rate
Calculates new value at the upgraded rate
Computes the upgrade charge (difference)
Adjusts the recognition schedule to reflect the new monthly amount

Example: Upgrading from $1,000/month to $1,500/month on May 15:

May is split: 14 days at old rate + 17 days at new rate
June through December: $1,500/month
Additional invoice issued for the upgrade difference

Contract Termination

When a contract ends early:

Recognized revenue to date is preserved
Remaining unrecognized schedule lines are voided
The voided amount is reported for disclosure purposes

Bundled Products (Multiple Performance Obligations)

When a contract includes multiple deliverables, separate recognition schedules are created for each performance obligation:

Example: $15,000 contract with software license + implementation services

Obligation	Amount	Method	Duration
Software license	$10,000	Straight-line	12 months
Implementation	$5,000	Milestone	3 months

Each obligation is tracked and recognized independently, using the method that matches how value is delivered.

Common Use Cases

Monthly Subscription

Revenue is recognized immediately each month as the service is delivered. No deferred revenue needed.

Annual Subscription (Paid Upfront)

Full amount deferred on day one, recognized monthly over the term. Deferred revenue balance decreases each month.

Multi-Year Contract

Each year is invoiced and scheduled separately. The balance sheet shows current deferred revenue (next 12 months) and long-term deferred revenue (beyond 12 months).

Usage-Based with Minimum

A monthly minimum charge is recognized immediately. Overage charges above the included usage are recognized as consumption occurs.

Key Capabilities

ASC 606 / IFRS 15 compliance with the five-step recognition model
Four recognition methods: straight-line, milestone, usage-based, and percentage-of-completion
Automated schedule processing with monthly, quarterly, or annual frequency
Deferred revenue tracking on the balance sheet with period-over-period reporting
Proration handling for mid-period upgrades and amendments
Multiple performance obligations with independent schedules per obligation
Contract termination with proper voiding and disclosure tracking
Complete audit trail of every recognition decision and journal entry

← PREVIOUSBilling & Subscription Management NEXT →Cost Accruals and COGS