Subscription revenue recognition

Direct answer

Recognize subscription revenue when the promised service is provided, not automatically when a customer signs, is billed, or pays. Check each contract’s performance obligations and service period, then reconcile recorded revenue and deferred revenue to the underlying schedule.

Why this question comes up

An annual prepayment may fund months of future service. An upgrade, cancellation, or credit may change what remains to be delivered. Neither change can be judged from an invoice total alone.

Records to gather

• Signed contracts or order forms with service dates and performance obligations
• Invoices issued, with billing period clearly distinct from service period
• Deferred revenue schedule with opening balance, additions, releases, adjustments, and closing
• Any mid-term changes: upgrades, downgrades, pauses, cancellations, credits
• Payment records, kept separate from revenue recognition

Review workflow

1. Identify the promises. Read the agreement for service dates, distinct obligations, and variable or non-standard terms.
2. Check the recognition method. Revenue follows satisfaction of each obligation. A straight-line pattern may suit a stand-ready subscription; setup work or usage-based charges may need different treatment.
3. Reconcile contract balances. Tie the deferred revenue schedule, including contract changes and adjustments, to the balance sheet. Investigate rather than plugging differences.
4. Keep operating metrics separate. ARR and MRR are run-rate measures, not GAAP revenue. Explain changes in scope and timing instead of presenting one as the other.

What a useful answer should include

• The recognition period and method, stated per contract type
• A deferred revenue rollforward that ties to the balance sheet
• Billings, cash collected, and recognized revenue shown separately
• Treatment of mid-term upgrades, downgrades, and cancellations
• ARR or MRR labeled as operating metrics, with timing and scope differences explained
• Any contract with non-standard terms flagged rather than averaged in

Common failure modes

• Recognizing on invoice. Billing does not establish that all contracted services have been provided.
• Reporting ARR as revenue. A current annualized run rate is not the amount earned during a past reporting period.
• Plugging the schedule. Trace differences to contracts, credits, journals, or reclassifications before adjusting balances.
• Averaging unlike contracts. Separate material setup, usage, multi-year, and amendment terms from a standard subscription schedule.

Community context

The linked discussion reflects practitioner questions, not accounting authority. Use the contracts, your accounting policy, and Topic 606 for recognition decisions.