revenue-recognition-accounting

Este extracto es una copia guardada durante la revisión. La fuente externa contiene la versión completa y actual.

---
name: revenue-recognition-accounting
description: "Implement ASC 606 / IFRS 15 revenue recognition for subscriptions, bundles, and multi-element arrangements with deferred revenue tracking and journal entries"
category: data-analytics
risk: safe
source: curated
date_added: "2026-03-12"
tags: [revenue-recognition, asc-606, accounting]
triggers: ["implement revenue recognition", "ASC 606", "IFRS 15", "deferred revenue", "subscription revenue accounting", "multi-element arrangement", "revenue schedule"]
tools: [claude-code, cursor, gemini-cli, copilot, codex-cli]
platforms: [shopify, woocommerce, bigcommerce, custom]
difficulty: advanced
---

# Revenue Recognition Accounting (ASC 606 / IFRS 15)

## Overview

Revenue recognition determines when you can record revenue in your financial statements. Under ASC 606 (US GAAP) and IFRS 15, revenue is recognized when — or as — performance obligations are satisfied, not simply when cash is received. This matters enormously for subscriptions (revenue earned monthly even if billed annually), gift cards (revenue earned only on redemption), and bundled products (where a warranty component must be deferred).

Getting revenue recognition right protects you from audit findings, builds investor trust, and ensures your financial statements accurately reflect business performance.

This skill guides you through the practical setup of revenue recognition using your accounting system, platform integrations, and relevant apps.

## When to Use This Skill

- When you sell subscription products (monthly boxes, replenishment subscriptions, memberships)
- When you sell bundled offers (product + warranty + service in one SKU)
- When you issue gift cards, store credit, or prepaid plans
- When you recognize revenue from third-party marketplaces (Amazon, eBay)
- When preparing GAAP or IFRS financials for investors, auditors, or a financing round
- When building a data pipeline that automatically posts revenue recognition journal entries
- When you need to separate recognized revenue from cash receipts in your financial model

## Core Instructions

### Step 1: Identify which revenue types require special treatment

Most standard ecommerce product sales (order placed → shipped → delivered) are straightforward: recognize revenue at delivery. The complexity arises with these arrangements:

| Revenue Type | Recognition Rule | Common Mistake |
|-------------|-----------------|----------------|
| **Physical product (single sale)** | Recognize at delivery (when control transfers to customer) | Recognizing at order placement instead of delivery |
| **Subscription (annual or multi-month)** | Recognize ratably over the subscription period | Recognizing full annual payment in month 1 |
| **Gift cards** | Recognize at redemption; handle unredeemed breakage separately | Recognizing at sale |
| **Extended warranty** | Recognize ratably over the warranty period | Recognizing 100% at product shipment |
| **Bundle (product + service)** | Allocate price across components; recognize each independently | Recognizing 100% at shipment of physical component |
| **Buy Now Pay Later** | Recognize at delivery (BNPL provider pays you immediately; installment risk is theirs) | No special treatment needed; straightforward |
| **Marketplace sales (as principal)** | Recognize gross revenue; record fees as cost of revenue | Net revenue recognition (agent treatment) when you control inventory |
| **Marketplace sales (as agent)** | Recognize only your net commission | Gross revenue recognition when you do not control inventory |

### Step 2: Set up your accounting system for proper revenue recognition

The right tool depends on your business complexity and accounting system:

---

#### For subscription businesses

**Shopify (subscription apps):**
1. Use **Recharge** or **Skio** for subscription management on Shopify — both apps create orders in Shopify for each billing cycle
2. Connect Shopify to **Xero** via A2X or to **QuickBooks** via Fin