The 5-Stage Diagnostic Protocol

The Dispatch Canvas Diagnostic Protocol is our standardized 5-stage investigative architecture for subscription revenue auditing. Developed over five years of client advisory engagements, this protocol provides an unyielding, step-by-step verification process that ensures no discrepancy, tax drift, or grace period error escapes detection.

Stage 1: Telemetry Ingestion & Schema Normalization

The diagnostic begins with the secure collection of raw transaction records. Rather than relying on aggregated reports, our analysts ingest:

• Server-to-server transaction receipt logs and webhook archives (StoreKit 2 notifications, Google Play Real-Time Developer Notifications, Stripe event payloads).
• Official monthly financial payout summaries from App Store Connect and Google Play Console.
• Database records of user entitlement state transitions (active, in_trial, grace_period, paused, expired).

During this stage, schemas are normalized to establish consistent timestamp standards (UTC), convert historical multi-currency transactions using daily FX closing rates, and isolate test sandbox accounts from production records.

Stage 2: Discrepancy Mapping & Proceeds Reconciliation

With normalized data in hand, we execute a transaction-by-transaction reconciliation between reported billings and settled bank deposits:

• Commission Tier Audit: Verifying whether Apple/Google’s 15% rate for second-year subscribers is accurately attributed versus the standard 30% rate.
• Storefront Tax Deductions: Calculating exact deductions for Value-Added Tax (VAT), Goods and Services Tax (GST), and US state sales taxes across 175 App Store storefronts.
• Refund & Chargeback Attribution: Mapping retrospective store refunds back to the specific subscriber cohort to prevent phantom retention reporting.

Any divergence between recorded revenue and bank deposits is cataloged in a preliminary Discrepancy Ledger.

Stage 3: Longitudinal Cohort Reconstruction

In Stage 3, we reconstruct true subscriber cohort curves stripped of analytical distortion:

• Acquisition Vintage Isolation: Grouping subscribers by their initial payment date (or trial start date) to track retention decay from Month 1 (M1) through Month 36 (M36).
• Billing Cadence Separation: Analyzing monthly, quarterly, and annual subscription renewals independently to model renewal cliff drops accurately.
• Net Revenue Retention (NRR) Calculation: Modeling expansion revenue (tier upgrades, family add-ons) against contraction and cancellations to determine true cohort monetary yield over time.

Stage 4: Involuntary Churn & Failure Root-Cause Isolation

Payment failures often hide within subscription lifecycle transitions. In this phase, we isolate:

• Soft vs. Hard Decline Distributions: Identifying the proportion of failed renewals caused by temporary bank card limits versus permanently closed accounts.
• Grace Period State Transitions: Auditing how your server handles users during Apple’s 16-day or 28-day retry windows. We determine whether expired users receive unwarranted free service or are disconnected before recoverable payment attempts conclude.
• Dunning Communication Timing: Evaluating whether in-app push and email notifications are synchronized with payment retry cycles.

Stage 5: Executive Synthesis & Remediation Blueprint

The final stage translates complex data forensics into strategic clarity:

• The Verified Financial Baseline: An auditable, reconciled ledger of historical subscription revenue, NRR, and true LTV curves.
• The Engineering Remediation Rulebook: Specific, actionable technical instructions for your backend engineers to fix broken webhook handlers, misconfigured tax settings, or faulty grace-period state machines.
• The Executive Debrief: A comprehensive walkthrough with founders, finance leads, and engineering stakeholders to present findings and answer technical questions.