
ASC 606 Revenue Recognition Analyzer
Analyze complex revenue contracts against ASC 606 criteria and document defensible conclusions
What You Can Do
You can decompose complex revenue contracts into their component performance obligations, apply the ASC 606 five-step model consistently, and document your accounting conclusions with supporting analysis that withstands audit scrutiny. This skill handles bundled offerings, variable consideration, contract modifications, and hybrid arrangements where standard pricing doesn't exist.
Features
systematically work through contract identification, performance obligation recognition, transaction price determination, allocation, and revenue timing
distinguish between performance obligations and other contract elements, including licensing arrangements and right-of-use considerations
evaluate contingent pricing, usage-based fees, performance penalties, and returns rights to establish transaction price bounds
document whether your company acts as principal or agent in platform, marketplace, or intermediary transactions
analyze side letters, amendments, and scope changes to reassess performance obligations and pricing
assess time-based, usage-based, and achievement-based payment structures for recognition timing
generate structured analysis that justifies conclusions with specific contract language citations and technical references
surface hidden complexity like warranties, extended support, return rights, and performance guarantees requiring separate evaluation
Example Output
Example 1: SaaS Multi-Year Contract with Usage-Based Overages
Contract Elements: 3-year agreement for base software ($10K/month) + usage-based overage fees (tiered pricing)
Analysis:
- Performance Obligations: (1) Monthly SaaS access (satisfied over time), (2) Usage overage services (satisfied as incurred)
- Transaction Price: Base consideration = $360K fixed; variable overage component estimated using most likely amount method based on historical usage patterns
- Recognition Timing: Base revenue recognized ratably monthly; overage revenue recognized when usage threshold is exceeded
- Conclusion: Dual obligation structure with different satisfaction patterns
Example 2: Bundled Software License + Implementation Services
Contract Elements: Perpetual license ($50K) + 6-month implementation ($30K) + annual support (3 years, $5K/year)
Analysis:
- Performance Obligations: (1) License transfer (point in time upon go-live), (2) Implementation services (over 6 months), (3) Annual support (satisfied over each 12-month period)
- Standalone Selling Price: License allocated 50% of total; implementation 30%; support 20% based on observable pricing in similar standalone transactions
- Recognition Pattern: $25K recognized at implementation completion; $15K recognized over 6-month period; support revenue recognized $5K annually
- Documentation: Side letter confirms implementation acceptance criteria and support SLA commitments
Example 3: Platform Transaction with Principal/Agent Assessment
Finding: Marketplace transaction where you facilitate seller-buyer transactions (15% commission)
Analysis:
- Principal Assessment: You control goods before transfer to customer (inventory risk) and set final pricing → principal
- Revenue Recognition: Recognize at gross consideration amount; not net commission
- Judgment: Supports higher revenue line but requires inventory valuation and seller payable accruals
What's Included
- SKILL.md: Core framework file with five-step ASC 606 methodology and when-to-use guidance
- Contract Analysis Template: Structured worksheet for documenting each step of the model with field guidance and common pitfalls
- Performance Obligation Checklist: Identification matrix for distinguishing performance obligations from other contract elements
- Variable Consideration Estimation Guide: Framework for estimating variable fees using most-likely-amount vs. expected-value methods with decision tree
- Principal-vs-Agent Assessment Tool: Structured questions and documentation requirements for determining economic classification
- Audit Trail Documentation Template: Format for creating defensible accounting conclusions with contract citations and technical references
Who It's For
- Revenue Accountants — managing complex contract portfolios requiring ASC 606 documentation and audit support
- Technical Accounting Specialists — evaluating non-standard arrangements and providing guidance to business units
- External Auditors — validating client revenue recognition conclusions and testing transaction sampling
- Finance Controllers — overseeing revenue recognition policies and identifying high-risk contract categories requiring specialist review
- SaaS and Software Company Finance Teams — evaluating subscription, usage-based, and bundled software licensing arrangements
Best For
- Multi-element contracts with bundled products/services requiring allocation methodology
- Contracts with variable consideration (performance fees, contingent payments, usage-based pricing)
- Long-term agreements with material modifications or side letters requiring reassessment
- Principal-vs-agent and marketplace/platform transaction classification
- Contracts with extended warranties, support obligations, or contingent deliverables
- License arrangements requiring evaluation of licensing vs. right-of-use classification







