Pretend you are the revenue accountant so recognition gaps, deferred revenue blur, and booking theater fail before a finance package absorbs them.
Optimistic revenue packages optimize for "ARR will clear." The revenue accountant seat does the opposite. It asks which deal invents recognized revenue the contract will not support, which schedule dual-counts the same invoice as booked and as deferred, which "required" cutover is already optional in practice, and which cohort still lacks a named audit owner. A neat waterfall chart is not evidence that next quarter's books will clear.
Mandate the seat
Name a real job: underwrite a recognition change without inventing contract speed, clear a booking claim that audit can reconcile under load, or defend a cutover without dual-counted ARR. Give constraints: the evidence standard for performance obligations, the cohorts you will refuse to leave unowned, and the booking claims you will not teach when systems are not ready. Without constraints the seat becomes cartoonish. With constraints it produces questions you might actually hear in a close review, a board prep, or a fight over who owns multi-element allocations.
Prompt example: "Revenue accountant: list the top reasons to delay this recognition package, the schedule with the weakest owner, the booking claim that worries you most, and the ten diligence questions you would send after review. Stay inside a realistic mandate."
Outputs worth keeping
- Top reasons to challenge, delay, or rewrite this revenue package.
- The recognition or ARR claim that looks strongest and is least evidenced.
- The cohort, SKU, or region that would break first under a close spike.
- What would make you accept residual recognition risk in writing.
- The ten hardest follow-up questions after the meeting.
Run that brief in Pingpong against the real contract samples, revenue schedules, system cutover notes, and open risk list. Follow with a home-team response pass so you leave with edits and source packs. When the decision is a public earnings claim, run this seat after controller and sales attacks so it can use earlier objections as ammunition.
When the plan leans on a single cutover weekend, a single "systems will catch up" promise, or a single large deal still in negotiation, force the seat to price concentration risk in writing. Ask what happens if the ERP still hosts retired SKU codes, if deferred balances cannot be tied to invoices, or if sales keeps teaching recognition language finance already retired. Pair with pretend you are the finance controller, pretend you are the treasury lead, pretend you are the CFO, war-game a deal desk rule, and the war-game decisions hub. See how to run a Pingpong.
If the package coincides with a pricing or packaging change, ask the revenue accountant seat to map every claim that still assumes last quarter's SKU codes. Invoices, partner portals, and sales decks count. A recognition memo that looks clean in a slide while billing still posts retired plan IDs will fail on the first close.