# Revenue Recognition

> Apply revenue recognition principles (including ASC 606 / IFRS 15 concepts) so revenue is recorded when performance obligations are satisfied. Use when designing billing models, reviewing contracts, or ensuring revenue is not recognized too early or late.

- Skill: `itsual/revenue-recognition` (Agent Skill)
- Install (CLI): `npx get-skill add itsual/revenue-recognition`
- Raw SKILL.md: https://api.skillmd.com/api/skills/itsual/revenue-recognition/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Finance & Business
- Author: itsual (https://skillmd.com/u/itsual)
- Updated: 2026-11-15
- Page: https://skillmd.com/skills/itsual/revenue-recognition

---


# Revenue Recognition

## Overview

Revenue recognition determines when sales become revenue. Getting it wrong creates restatements, investor distrust, and broken incentives.

## When to Use

- New pricing or contract models
- SaaS, multi-element, and long-term contracts
- Audit readiness and policy documentation
- Deal desk reviews with non-standard terms

## Core Practices

- Identify contracts and performance obligations
- Determine transaction price (including variable consideration)
- Allocate price to obligations
- Recognize as obligations are satisfied (point in time or over time)
- Document policies and exceptions

## Principles

- Cash collected ≠ revenue earned
- Side agreements and unusual terms are red flags
- Systems must support the policy, not only the invoice
- Conservative, consistent application builds credibility

## Verification

- [ ] Policy matches business model and standards framework
- [ ] Non-standard deals get review
- [ ] Deferred revenue and contract assets are tracked

