revenue-recognition

Featured

Determines when and how revenue is recognized — performance obligations, contract terms that change the answer, and the deal structures that create accounting problems. Use this to work out how a contract should be recognized, review a non-standard deal before it is signed, understand deferred revenue, or spot terms that would delay or reverse recognition.

AI & Automation 1,356 stars 209 forks Updated 1 weeks ago MIT

Install

View on GitHub

Quality Score: 91/100

Stars 20%
100
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Revenue recognition Cash received is not revenue earned. The gap between them is where deals get restructured after signature and where quarters get restated. **This structures the question and tells you what to ask. Revenue recognition is a technical accounting matter under standards such as ASC 606 and IFRS 15 — conclusions on a material or unusual contract need your auditors or a qualified accountant, not a checklist.** ## The shape of the question Recognition follows the transfer of control to the customer, worked through in five steps: identify the contract, identify the distinct performance obligations, determine the transaction price, allocate it across the obligations, then recognize as each is satisfied. Most disputes happen at step two and step four. What sales sold as one thing is frequently several obligations for accounting purposes — software plus implementation plus support — and the price has to be allocated across them on standalone selling price, not on how the quote was written. ## Terms that change the answer These belong in a pre-signature review, because after signature the only remedy is an amendment the customer has no reason to agree to: - **Acceptance clauses** — a customer right to reject can defer recognition until acceptance. - **Termination for convenience** — a short-notice exit can shorten the contract term for accounting purposes, however long the stated term is. - **Contingent or milestone fees** — variable consideration, constrai...

Details

Author
cbrock84
Repository
cbrock84/headcount
Created
1 weeks ago
Last Updated
1 weeks ago
Language
Markdown
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

DevOps & Infrastructure Solid

revenue-recognition-advisor

Apply the ASC 606 / IFRS 15 five-step revenue recognition model to described arrangements. Provides the complete five-step framework with paragraph citations, judgment-area reference tables, confidence-scoring guidance, common restatement triggers, GAAP/IFRS delta checklist, and official documentation URLs. Use when analyzing revenue recognition treatment for SaaS, licenses, professional services, multi-element arrangements, and channel partnerships. Advisory only — all outputs require external auditor review for material amounts.

22 Updated 3 days ago
Raishin
DevOps & Infrastructure Solid

revenue-recognition-advisor

Apply the ASC 606 / IFRS 15 five-step revenue recognition model to described arrangements. Provides the complete five-step framework with paragraph citations, judgment-area reference tables, confidence-scoring guidance, common restatement triggers, GAAP/IFRS delta checklist, and official documentation URLs. Use when analyzing revenue recognition treatment for SaaS, licenses, professional services, multi-element arrangements, and channel partnerships. Advisory only — all outputs require external auditor review for material amounts.

22 Updated 3 days ago
VincentChuWaiChow
AI & Automation Listed

revenue-analytics

Revenue analytics architecture - ARR / NRR / GRR decomposition, cohort retention, expansion drivers, segment economics, and CAC payback diagnostics. Use when: revenue analytics, ARR waterfall, NRR analysis, GRR, expansion analysis, cohort revenue retention, CAC payback, magic number, segment economics, revenue diagnostics.

6 Updated 1 months ago
varunk130