Short answer
Revenue recognition applies the organization's defined accounting policy to determine the amount and period recorded as revenue, supported by evidence. Use it for revenue accounting judgments and execution, not for commercial forecasting or general control design.
About Revenue recognition
Applies defined accounting rules to recognize revenue accurately and support the treatment with evidence. The work connects contract terms, delivery evidence, accounting periods, calculations, and documented review.
Use this competency for
- Roles that prepare, review, or document revenue accounting under the organization's defined policies.
- Work that evaluates contract terms, delivery evidence, timing, or changes affecting recorded revenue.
Do not use this competency for
- Roles that forecast sales or bill customers without responsibility for the accounting treatment of revenue.
Important distinctions
Accounting controls
Revenue recognition determines and supports a revenue treatment, while accounting controls govern the checks and authorization around financial processes.
Financial planning
Revenue recognition records revenue under defined accounting policy, while financial planning forecasts possible future revenue from business assumptions.
Expectations by level
IC1
Standard revenue processing
Processes standard revenue items with guidance, applies the documented policy and checklist, ties calculations to source records, and routes exceptions for review.
Observable behaviors
- Matches contract, billing, and delivery records for assigned items.
- Calculates recognized and deferred amounts using the approved method.
- Flags terms or evidence that do not fit the standard procedure.
Examples
- Prepares a monthly schedule for a standard service period and ties the total to the signed order record.
- Stops processing an item when the delivery date conflicts with the supporting record and requests review.
IC2
Independent treatment assessment
Independently assesses nonstandard revenue items within established policy, documents the relevant facts and conclusion, and reconciles the resulting entries and balances.
Observable behaviors
- Identifies contract terms that affect amount or timing.
- Writes a treatment memo that links facts, policy, calculation, and conclusion.
- Reconciles recognized, billed, collected, and deferred balances.
Examples
- Documents the treatment of a contract modification and updates the remaining recognition schedule.
- Investigates a deferred balance difference and traces it to an amendment omitted from the source file.
IC3
Revenue policy application
Leads revenue accounting for material or ambiguous arrangements across teams, defines repeatable application guidance, and coordinates review before close or reporting deadlines.
Observable behaviors
- Frames ambiguous arrangements around the facts and policy questions that require a decision.
- Creates guidance and review thresholds for recurring contract patterns.
- Assesses how process or product changes affect revenue data and evidence.
Examples
- Coordinates finance, legal, and operations facts for a new contract structure and records the approved treatment.
- Introduces a review rule for recurring modifications after identifying inconsistent treatment across teams.