AI Playbook for Revenue Recognition Acceleration
You are engaged by a PE sponsor reviewing a portfolio company's $32M ARR SaaS business ahead of a secondary sale. The target recognized $2.1M in revenue from multi-year contracts in Q4—a quarter in which the CFO received a transaction bonus tied to trailing 12-month revenue.
When to use this playbook
- Use this playbook when the decision looks like the situation above: You are engaged by a PE sponsor reviewing a portfolio company's $32M ARR SaaS business ahead of a secondary sale.
- It is a fit when you have source files in hand and need a structured, reviewable analysis — not a generic chat answer about "Revenue Recognition Acceleration".
- Do not use it as a substitute for licensed, legal, clinical, or authorized official judgment in the domain.
What you'll need
- Multi-year contract file (all contracts with annual value >$50K)
- Deferred revenue schedule
- Q4 revenue recognition entries and supporting memos
- CFO compensation agreement including bonus triggers
Attachments: Documents (Documents)
The Prompt
You are a forensic accountant conducting a revenue quality review for a PE sponsor evaluating a $32M ARR SaaS company. I am attaching: Work only from the attached source files. If a conclusion is not supported, say so. Produce: 1. Identify all contracts where revenue was accelerated from a future period into Q4 and assess whether the acceleration is supportable under ASC 606. 2. Calculate the adjusted ARR if revenue recognition is restated to contractual delivery schedules. 3. Assess whether the CFO's bonus trigger creates a material incentive that should be disclosed to the buyer. 4. Identify any contracts where the performance obligations have not been met as of the recognition date. 5. Tell me the adjusted purchase price range I should recommend to the sponsor if Q4 revenue is restated. Call out where independent models are likely to disagree, and list follow-up documents a reviewer should request.
What to expect
- Revenue restatement schedule by contract
- Adjusted ARR with confidence interval
- Incentive compensation risk disclosure language
- Recommended purchase price adjustment range
Review before you act
- Validate this output against source files before relying on it: Identify all contracts where revenue was accelerated from a future period into Q4 and assess whether the acceleration is supportable under ASC 606.
- Validate this output against source files before relying on it: Calculate the adjusted ARR if revenue recognition is restated to contractual delivery schedules.
- Validate this output against source files before relying on it: Assess whether the CFO's bonus trigger creates a material incentive that should be disclosed to the buyer.
- Validate this output against source files before relying on it: Identify any contracts where the performance obligations have not been met as of the recognition date.
- Confirm every cited figure, date, counterparty, or requirement against the attached originals — models compress and can drop a qualifier.
- Treat disagreement between models as a review item, especially on classification, materiality, and recommended next action.
- Do not authorize an operational, clinical, legal, credit, or enforcement action solely because the models agree.
Why compare models on this
For Revenue Recognition Acceleration, running the same attachments across independent models is useful because the hard part is classification and completeness, not fluency. The workflow is already designed to surface revenue restatement schedule by contract; adjusted arr with confidence interval; incentive compensation risk disclosure language; recommended purchase price adjustment range. Those are comparison artifacts — they only exist if more than one model runs. Models often split on qualitative materiality, intent versus error, and whether a newly formed counterparty is a red flag or a legitimate intermediary. Those splits are the review queue — not noise.
See governed multi-model AI on your own prompt
Compare GPT-5, Claude, and Gemini side by side, with human review and a decision record built in.

