skills/accounting-analysis/references/modules/M012-revenue-recognition-analysis.md

<!-- Generated loss-aware reference mirror from God_Level_Public_Company_Financial_Analyst_Job_Guide_V6_99_ALL_SUB70_FIXED.docx. Canonical source remains the bundled DOCX. -->

<!-- Module: 012 | Title: Revenue Recognition Analysis -->

## PART III - ACCOUNTING FOUNDATION | MODULE 012

# Revenue Recognition Analysis

> Mission. Understand contract economics, timing, variable consideration, principal-agent issues, and revenue quality.

## Decision output

Objective: Understand contract economics, timing, variable consideration, principal-agent issues, and revenue quality. The completed work product must be reproducible from evidence, show the downstream financial or decision effect when material, state the strongest contrary case, and define a dated update rule.

## Explicit operating procedure

1. Identify each material revenue stream, customer contract, performance obligation, transaction price, variable consideration, and timing of control transfer.

1. Separate bookings/order intake, billings, cash collections, contract assets, contract liabilities/deferred revenue, RPO/backlog, and recognized revenue. Do not treat them as interchangeable demand measures.

1. Test principal-versus-agent presentation, gross-to-net deductions, rebates, returns, warranties, concessions, usage/consumption, and contract modifications where material.

1. Reconcile reported growth into organic scope, acquisition/divestiture, FX, price, volume, mix, and accounting/presentation effects.

1. Inspect changes in contract assets/liabilities and unbilled receivables for timing shifts that can make revenue growth diverge from cash or underlying delivery.

1. Forecast revenue from economic delivery drivers and contract terms, then reconcile the forecast to backlog/RPO only after adjusting for cancellation, renewal, and timing risk.

## Required evidence and model bridge

- Primary-source set: audited statements, footnotes, accounting policies, roll-forwards, segment disclosures. Preserve exact document/version, date, period, and source location for every material factual input used in revenue recognition analysis.

- For each key concept - performance obligations, over-time versus point-in-time, variable consideration, principal-agent, contract assets, deferred revenue - state whether it is a reported fact, analyst calculation, management claim, external estimate, or judgment. Quantitative concepts must retain raw components and units; qualitative concepts must retain the specific evidence and counterevidence.

- Map only economically relevant findings into the model or decision record. Process-control modules such as revenue recognition analysis may have no direct valuation line; in that case document the downstream error or governance risk the control prevents.

## Metrics and calculation controls

| Metric / concept | Construction | Required validation |
| --- | --- | --- |
| deferred-revenue conversion | Revenue recognized from beginning deferred revenue or billings cohort divided by the applicable opening deferred-revenue balance; track by term/cohort where available. | deferred-revenue conversion: Tie the dollar measure to filed statements/footnotes; reconcile classification adjustments, one-time items, acquisitions/FX, and period consistency before using it analytically. |
| contract-asset growth versus revenue | contract-asset growth versus revenue = current period / comparable prior period - 1; decompose organic, price, volume, mix, FX, and M&A where material. | contract-asset growth versus revenue: Recalculate contract-asset growth versus revenue from cited inputs; reconcile definition, period, units, signs, and source version; investigate and document any variance before use. |
| RPO coverage | Remaining performance obligations divided by next-twelve-month expected revenue, with current RPO separated from long-dated commitments. | RPO coverage: Recalculate from same-scope numerator and denominator; confirm period, units, cohort/geography, and issuer definition; reconcile material differences to filings or operating data. |



## Revenue recognition laboratory

- For a multi-year contract, separate signed contract value, billings, cash collections, deferred revenue/contract liability, contract asset, and GAAP revenue. A booking is not revenue and a billing is not necessarily revenue.

- Build a remaining-performance-obligation schedule only when issuer definitions are understood. Model variable consideration, returns/rebates, principal-agent presentation, and contract modification separately when material.

- Reconcile organic growth both as reported and on a constant-definition basis when acquisitions, FX, or gross/net presentation change comparability.

## Worked application

> Case: a marketplace changes presentation from net to gross.

- Reconstruct the relevant reported fact from primary evidence before interpreting the case. For revenue recognition analysis, show the raw components rather than only the resulting ratio or narrative.

- Build the causal chain through performance obligations, over-time versus point-in-time, variable consideration, principal-agent, then identify which link is directly observed and which link remains an assumption.

- Calculate deferred-revenue conversion, contract-asset growth versus revenue, RPO coverage from sourced components under the reported/base interpretation and at least one skeptical alternative interpretation.

- Translate the difference between cases into the variable that matters for revenue recognition analysis: evidence quality, revenue, operating profit/NOPAT, free cash flow, invested capital, financing/dilution, risk, or valuation. Mark non-applicable links instead of inventing them.

- Expert consistency test: separate billings, cash collection, and GAAP revenue because each can move on a different timeline.

- Precommit the specific future filing, KPI, customer/supplier observation, regulator action, or market input that would materially invalidate the revenue recognition analysis conclusion.

## Failure tests

- FAIL if performance obligations cannot be defined and reproduced from the source pack.

- FAIL if bookings, billings, cash collections, backlog/RPO, contract balances, and recognized revenue are treated as interchangeable without contract-timing reconciliation.

- FAIL if the revenue recognition analysis conclusion depends on an unstated assumption, unreconciled definition, or evidence that cannot be traced to its source/version.

- FAIL if evidence materially inconsistent with the revenue recognition analysis conclusion is omitted, reclassified, or dismissed without a documented definition, materiality, causal, timing, and source-quality analysis.

## Completion test

A senior reviewer must be able to reproduce the revenue recognition analysis conclusion, vary the most sensitive assumption independently, trace the change through the model, understand the strongest opposing case, and identify the next evidence that would force an update. If any link is missing, the module remains open.