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.

itsual Updated 7 repo stars

File contents

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

itsual/agent-skills-collection commit 93ab194b10

Frequently asked questions

npx get-skill add itsual/revenue-recognition