managing-revenue-recognition

# Managing Revenue Recognition

Applies the ASC 606 five-step revenue recognition model to contracts, identifying performance obligations, determining transaction prices, allocating consideration, and documenting the timing of revenue recognition with audit-ready support.

## When To Use

- Onboarding a new customer contract or contract modification that includes bundled deliverables, variable consideration, or multi-period performance
- Performing periodic revenue recognition assessments (quarterly close, annual audit prep)
- Evaluating whether a contract contains a license, service, or combined arrangement
- Documenting management's conclusions on principal-vs-agent determinations
- Responding to auditor inquiries on allocation methodology or significant judgments

## Inputs To Gather

- **Executed contract and amendments** — full agreement text including SOWs, order forms, side letters, and change orders
- **Pricing details** — list prices, discounts, volume tiers, credits, refund rights, and any variable consideration components (bonuses, penalties, royalties)
- **Delivery schedule** — milestones, acceptance criteria, renewal/termination provisions
- **Historical data** — standalone selling prices (SSP) for each deliverable, historical estimates-at-completion for similar arrangements
- **Entity-specific context** — company's ASC 606 accounting policy memo, SSP methodology election, and any prior-period analogous conclusions

## Workflow

### Step 1 — Identify the Contract (ASC 606-10-25-1)

- Confirm the arrangement meets all five contract existence criteria: approval/commitment, identifiable rights, identifiable payment terms, commercial substance, and collectibility of consideration
- For modifications, determine whether the change is treated as a separate contract, prospective adjustment, or cumulative catch-up [VERIFY against entity's modification policy]

### Step 2 — Identify Performance Obligations (ASC 606-10-25-14)

- List each promised good or service in the contract
- Apply the "distinct" test: (a) the customer can benefit from the good or service on its own or with readily available resources, and (b) the promise is separately identifiable from other promises in the contract
- Flag bundled deliverables that may require combination into a single performance obligation (e.g., significant integration, customization, or high interdependence)
- For series arrangements (e.g., daily SaaS access), assess whether the series guidance applies

### Step 3 — Determine the Transaction Price (ASC 606-10-32-2)

- Start with fixed consideration stated in the contract
- Identify variable consideration components and estimate using the expected-value or most-likely-amount method; apply the constraint (include only amounts not subject to significant reversal) [VERIFY method elected in entity policy]
- Account for significant financing components if payment timing diverges materially from delivery timing (threshold typically > 1 year)
- Deduct amounts payable to the customer (e.g., slotting fees, co-marketing credits) unless they represent payment for a distinct good or service

### Step 4 — Allocate the Transaction Price (ASC 606-10-32-28)

- Determine SSP for each performance obligation using observable prices; where not directly observable, use adjusted market assessment, expected cost plus margin, or residual approach [VERIFY SSP methodology per entity elections]
- Allocate total transaction price proportionally based on relative SSP
- If a discount or variable consideration relates entirely to one or more (but not all) performance obligations, allocate accordingly with supporting rationale

### Step 5 — Recognize Revenue (ASC 606-10-25-27)

- For each performance obligation, determine whether control transfers over time or at a point in time
- Over-time criteria: customer simultaneously receives and consumes benefits; entity's performance creates or enhances a customer-controlled asset; entity's performance does not create an asset with alternative use and entity has enforceable right to payment for performance completed to date
- Select the appropriate measure of progress for over-time obligations (output method vs. input method) and document the rationale
- For point-in-time obligations, identify the specific transfer-of-control indicators met (e.g., physical possession, legal title, risks and rewards, acceptance, right to payment)

## Output

Produce a **Revenue Recognition Analysis Memo** containing:

- **Contract summary** — parties, effective date, total consideration, term, renewal/termination provisions
- **Performance obligation matrix** — each obligation identified, distinct/combined rationale, SSP used, allocated transaction price
- **Variable consideration analysis** — components identified, estimation method, constraint assessment, amounts included/excluded
- **Revenue timing schedule** — recognition pattern per obligation (over time with progress measure, or point in time with trigger event), projected recognition by period
- **Key judgments and estimates** — principal-vs-agent conclusions, SSP estimation rationale, modification treatment elections, significant financing assessment
- **Open items** — unresolved questions marked with [VERIFY], items requiring further client or auditor input

## Quality Checks

- Every performance obligation has a documented distinct-or-combined conclusion with specific reference to the contract language supporting it
- SSP allocations sum to total transaction price (reconciliation check, no rounding gaps)
- Variable consideration constraint analysis addresses both the likelihood and magnitude of potential reversal
- Revenue timing aligns with the delivery schedule and acceptance provisions in the contract
- Modification accounting treatment is consistent with the entity's disclosed policy and prior-period positions
- All significant judgments are supported by contemporaneous evidence rather than post-hoc rationalization
- Amounts and dates cross-reference to source contract provisions (section/exhibit numbers cited)
- [VERIFY] any jurisdiction-specific or industry-specific guidance overlays (e.g., ASC 606-10-55 implementation guidance for software, construction, telecom, or licensing)