Token导航 LogoToken导航

Agent Skill · 研究检索

revenue-recognition-accounting(收入确认会计)

revenue-recognition-accounting 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

revenue-recognition-accounting 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 51,536。

总安装 582周安装 24GitHub Stars 19下载 190核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:revenue-recognition-accounting(收入确认会计)
来源仓库:https://github.com/finsilabs/awesome-ecommerce-skills
仓库路径:skills/revenue-recognition-accounting
安装命令:
npx skills add https://github.com/finsilabs/awesome-ecommerce-skills --skill revenue-recognition-accounting
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/finsilabs/awesome-ecommerce-skills --skill revenue-recognition-accounting

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

revenue-recognition-accounting 用于查找、检索和筛选收入确认会计准则与实务指南。适用于财务合规、审计准备或 ERP 系统配置的场景。通过 GitHub 安装,使用 npx skills add 命令从指定仓库添加技能。使用前需确认权限范围和维护状态,注意是否涉及法规条文引用或数据修改。

适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/revenue-recognition-accounting

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/finsilabs/awesome-ecommerce-skills --skill rev…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

revenue-recognition-accounting 怎么安装?

在终端执行 npx skills add https://github.com/finsilabs/awesome-ecommerce-skills --skill revenue-recog…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

revenue-recognition-accounting 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

revenue-recognition-accounting 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

revenue-recognition-accounting 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

revenue-recognition-accounting 用的人多吗?

公开数据是累计安装 582 次,近一周安装 24 次,下载 190 次,GitHub 19 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

revenue-recognition-accounting 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
revenue-recognition-accounting

收入确认会计 · 本页

58219只读未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

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 TypeRecognition RuleCommon 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 periodRecognizing full annual payment in month 1
Gift cardsRecognize at redemption; handle unredeemed breakage separatelyRecognizing at sale
Extended warrantyRecognize ratably over the warranty periodRecognizing 100% at product shipment
Bundle (product + service)Allocate price across components; recognize each independentlyRecognizing 100% at shipment of physical component
Buy Now Pay LaterRecognize 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 revenueNet revenue recognition (agent treatment) when you control inventory
Marketplace sales (as agent)Recognize only your net commissionGross 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 Finaloop
  3. In Xero, revenue from subscription orders is recognized when the order is created (each billing cycle) — for monthly subscriptions billed monthly, this is correct
  4. For annual subscriptions: You need to spread the payment across 12 months. In Xero:

- Create the invoice when the subscription starts (e.g., $120 annual) - Post the full $120 to a Deferred Revenue liability account - Each month, create a recurring journal entry: DR Deferred Revenue $10 / CR Subscription Revenue $10 - Use Xero's Repeating Transactions feature to automate this

QuickBooks Online approach for annual subscriptions:

  1. When annual payment received: create an invoice for $120, post to "Deferred Revenue" (liability account)
  2. Create a recurring journal entry (monthly): DR Deferred Revenue $10 / CR Subscription Revenue $10
  3. QuickBooks recurring transactions: + New → Journal Entry → Make recurring

Dedicated revenue recognition tools:

  • Younium or Chargebee (if using subscription billing): Both have built-in revenue recognition that automatically defers and releases subscription revenue on the correct schedule; export to accounting system
  • Recurly + Sage Intacct: For larger subscription businesses; Recurly handles billing, Sage Intacct handles automated GAAP-compliant revenue recognition

For gift cards

Shopify:

  1. When a gift card is purchased, Shopify records it as a sale in the platform — but for accounting purposes, this is a liability (deferred revenue), not revenue
  2. In your accounting system: post gift card sales to Gift Card Liability (liability account), not revenue
  3. When a gift card is redeemed (applied to an order): transfer from Gift Card Liability to Revenue
  4. Breakage: For gift cards that are never redeemed, recognize the expected breakage amount as revenue either:

- Proportionally as cards are redeemed (preferred if you can estimate breakage reliably), OR - When redemption is considered remote (typically after 3–5 years of inactivity)

  1. Practical setup in QuickBooks/Xero: Create a "Gift Card Liability" account; when the accounting integration posts a gift card sale, manually reclassify it to the liability account; when redeemed, reclassify to revenue

A2X for Shopify: A2X allows you to configure how different Shopify transaction types post to your accounting system — set gift card sales to post to a deferred revenue account and gift card redemptions to post to a revenue account.


For product bundles with warranties

Manual approach (most common for small-to-mid-size merchants):

  1. Determine the standalone selling price (SSP) of each component:

- Product SSP: What you would sell it for without the bundle - Warranty SSP: What you would charge for the warranty alone (or estimate using cost-plus-margin)

  1. Allocate the bundle price proportionally: Example: Bundle = $150 (product + 1-year warranty) Product SSP: $130, Warranty SSP: $30, Total SSP: $160 Product allocation: $150 × ($130/$160) = $121.88 Warranty allocation: $150 × ($30/$160) = $28.12
  2. Post journal entries:

- At payment receipt: DR Cash $150 / CR Deferred Revenue $150 - At shipment: DR Deferred Revenue $121.88 / CR Product Revenue $121.88 - Monthly (over 12 months): DR Deferred Revenue $2.34 / CR Warranty Revenue $2.34

  1. In QuickBooks/Xero: Create a Deferred Revenue – Warranty liability account for the warranty component; set up a recurring journal entry to release $2.34/month per warranty sold

Step 3: Handle the physical product timing issue

The most common revenue recognition error for ecommerce: recognizing revenue at order placement instead of delivery.

Under ASC 606: For physical goods, revenue is recognized when the customer obtains control — typically at delivery, not at checkout.

Practical impact:

  • Orders placed December 30 but delivered January 3 should be recognized in January, not December
  • If you have many orders in transit at period-end (year-end or quarter-end), this creates a timing difference

How to handle in practice:

For most merchants with short transit times (1–3 days), the difference between order date and delivery date is immaterial and auditors typically accept recognition at shipment. However, if you have:

  • Long transit times (>7 days)
  • Significant holiday rush shipping in late December
  • GAAP audited financials

...then you need to accrue for in-transit revenue:

  1. At period-end, pull a list of all shipped but undelivered orders (from your shipping carrier or ShipStation)
  2. Calculate their total value
  3. Record a journal entry: DR Revenue / CR Deferred Revenue – In Transit (for the in-transit amount)
  4. Reverse the entry on the first day of the next period

Step 4: Set up deferred revenue tracking

Maintain a running deferred revenue balance to verify your accounting is correct.

Monthly deferred revenue reconciliation (in a spreadsheet):

Opening Deferred Revenue Balance
+ New deferrals this month (gift cards sold + subscription annual billings + warranty components)
- Revenue released this month (gift card redemptions + monthly subscription recognition + warranty releases)
- Refunds/cancellations
= Closing Deferred Revenue Balance

Should equal: Deferred Revenue balance on your balance sheet

If the calculated balance does not match your balance sheet, there is a missing journal entry.

Review checklist each month:

  • All gift card sales posted to liability account (not revenue)
  • Monthly subscription revenue recognition journal entries posted
  • Warranty component deferrals released for the month
  • In-transit accrual reversed from prior month; new in-transit accrual posted
  • Deferred revenue reconciliation ties to balance sheet

Step 5: Principal vs. agent determination for marketplace revenue

If you sell through Amazon, eBay, or other marketplaces, determine whether you are a principal or an agent:

You are a principal if:

  • You control the inventory before it is transferred to the customer (i.e., Amazon FBA inventory is yours)
  • You bear inventory risk (unsold items are your problem)
  • You set the selling price

→ Recognize gross revenue (full selling price); record Amazon fees as cost of revenue

You are an agent if:

  • A third party controls the inventory
  • The marketplace sets the price or has primary pricing authority
  • You earn a commission only

→ Recognize only your net commission

Most Amazon FBA sellers are principals and should recognize gross revenue. If you are unsure, consult your accountant.

Best Practices

  • Automate deferred revenue releases — build recurring journal entries in QuickBooks or Xero for all subscription and warranty revenue recognition; monthly manual entries will be missed eventually
  • Maintain a contract obligation register — for any bundle or subscription with multiple performance obligations, maintain a spreadsheet tracking the allocated price, recognition schedule, and amount remaining
  • Separate revenue accounts by obligation type — use distinct GL accounts for product revenue, subscription revenue, warranty revenue, and gift card redemptions; simplifies disclosure and audit support
  • Reconcile deferred revenue to cash receipts monthly — the ending deferred revenue balance should reconcile to cash received less revenue recognized; any gap indicates missing journal entries
  • Document your SSP methodology — auditors will ask how you determined standalone selling prices; use observable market prices where available and document the approach for every bundle type
  • Apply a variable consideration constraint for returns — based on historical return rates by category, reduce recognized revenue at delivery by expected returns; record a refund liability for the expected return amount

Common Pitfalls

ProblemSolution
Revenue recognized at checkout instead of deliveryFor physical goods, recognize when the carrier marks the shipment as delivered; post a deferred revenue entry at order placement and recognize at the delivery trigger event
Full bundle price recognized at shipmentSplit the bundle price across performance obligations using SSPs; defer the warranty/service component and release ratably over the service period
Gift card revenue recognized at saleGift card revenue is a deferred liability until redemption; post to a liability account at sale; recognize at redemption
Subscription prorations done by calendar month instead of by dayMid-month subscription starts should be recognized pro-rata by exact days, not calendar month; a subscription started on the 15th of a 30-day month recognizes 16/30 of the monthly fee in month 1
Not reassessing variable consideration (returns) each periodReturn rates change over time; re-estimate expected returns monthly and record a catch-up adjustment in the current period
Recording Amazon payout net of fees as revenueIf you are a principal on Amazon, record the full selling price as gross revenue and Amazon's fees as cost of revenue/selling expenses separately

Related Skills

  • @financial-reporting-dashboard
  • @financial-analytics-dashboard
  • @cash-flow-forecasting
  • @marketplace-fee-reconciliation

平台分布

Codex

34.95%
按下载量换算66

Claude

29.08%
按下载量换算55

Cursor

21.68%
按下载量换算41

Gemini CLI

10.95%
按下载量换算21

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills