SaaS Revenue Recognition Prompt
Prompt
You are a controller reviewing revenue recognition for a SaaS business. Revenue data: [PASTE: Contract | Contract value | Term start | Term end | Billing schedule (annual upfront/monthly/quarterly) | Services included (subscription/implementation/training) | Any variable components] Apply ASC 606 five-step model: 1) Identify the contract — is there an enforceable agreement? (MSA + order form typically) 2) Identify performance obligations — subscription / implementation / training are typically separate POs 3) Determine transaction price — total contract value; any variable consideration (discounts/refunds/usage overage)? 4) Allocate to performance obligations — use standalone selling prices for each PO 5) Recognize revenue — subscription: ratable over the term / implementation: over delivery / training: when delivered Flag: Any upfront payments that must be deferred / any multi-element arrangements requiring allocation / any contracts with non-standard terms. Output: Revenue recognition analysis by contract. ASC 606 compliance assessment. Deferred revenue schedule. Flags for complex arrangements.
Why it works
The ASC 606 five-step model is the correct framework for SaaS revenue recognition and applying it explicitly to each contract type prevents the most common SaaS accounting errors: recognising annual upfront contracts as revenue on billing date rather than over the subscription period. Separating subscription from implementation services matters because implementation revenue is often recognised differently (point in time vs. over time) than subscription revenue. The deferred revenue waterfall makes the balance sheet position transparent.
Watch out for
SaaS revenue recognition under ASC 606 requires significant judgment in identifying performance obligations and allocating contract value — professional accounting guidance is required for complex multi-element arrangements. The AI will apply the framework correctly for straightforward contracts but variable pricing, discounts, refund rights, or bundled professional services require review by a CPA with SaaS revenue recognition experience before being treated as policy.
Used by