Process
How an audit engagement runs
From scoping call to closing briefing — the steps we use for app analytics and financial audit applications on subscription revenue performance.
Why this page exists
Teams often ask what happens between “hello” and a findings memo. This is the sequence we follow for subscription revenue engagements — especially the flagship Subscription Revenue Performance Audit.
1. Scoping call (45–60 minutes)
We confirm the months in scope, the decision the work supports (board pack, lender update, plan freeze), and which systems hold invoices, credits, and product events. You leave with a written scoping note and a fee range.
2. Data room checklist
We send a field list: invoice grain, credit notes, plan catalogue with effective dates, and the event tables behind your “active subscriber” definition. Incomplete fields are fine — we label provisional findings rather than invent joins.
3. Source reconciliation
Our team rebuilds the paid base from billing truth, then compares it to analytics cohorts. Edge cases — pauses, prorations, multi-currency tax lines — are logged as exceptions with cash impact estimates where possible.
4. Findings draft
You receive a severity-ranked memo and the worksheets. Product and finance owners get a joint review window before the closing briefing so corrections happen on paper, not in the live room.
5. Closing briefing
A ninety-minute session walks through what is safe to report, what must be caveated, and which definitions should be frozen. For clients who continue with a Quarterly Revenue Health Review, we lock the metric set here.
What we need from you
A single liaison who can obtain exports, plus calendar time from both product analytics and finance. Without both rooms, findings stay one-sided.
Natural next actions
- Browse audit engagements
- Request a briefing with your billing provider and months in mind