Skip to content
ADVISORY RECONCILIATION · STRIPE ↔ ENTITLEMENTSRun the browser-only CSV audit

THE JOURNAL

Technical notes from
the reconciliation layer.

Definitions, connector design, identity mapping, policy boundaries, and the failure modes that make billing audits untrustworthy. Written for the person who has to defend the finding.

Original technical writing

No gated PDFs, no fabricated benchmarks, and no “ultimate guide” padding. Every article states its scope and its limits.

8 articles · updated 2026-11-14

FeaturedFundamentalsNovember 14, 2026 · 7 min read

What subscription revenue leakage actually means

Revenue leakage is not a single number. It is a class of gaps between what a customer was billed and what the product actually allowed. This piece defines the categories and the evidence needed to investigate them.

Read the article

The short version

Revenue leakage is a class of disagreements between billing and access, not a single number. Separate the direction, verify the evidence, and only then discuss value.

Start here if you are new

Detection8 min read

How to detect premium access without an active subscription

Stale premium access is one of the clearest revenue leaks — and one of the easiest findings to get wrong. The difference is policy and evidence, not a clever query.

November 14, 2026
Architecture7 min read

Mapping Stripe customers to application users without guessing

A billing audit is only as reliable as the link between a Stripe customer and an application account. Email matching is not an identity strategy.

November 14, 2026
Integration9 min read

Designing a signed Supabase entitlement export

The entitlement side of the audit needs a trustworthy snapshot. A narrow, signed, customer-owned export is safer than collecting a service-role key.

November 14, 2026
Policy6 min read

Trials, grace periods, and dunning: decide the policy first

Most “billing mismatches” are actually policy mismatches. The database is doing what it was told; the policy was never written down.

November 14, 2026
Quality7 min read

Why billing audits produce false positives

A false positive is not harmless. It trains the team to ignore the audit. Here are the failure modes worth designing against.

November 14, 2026
Security6 min read

Read-only Stripe keys: scopes, verification, and rotation

The right integration is narrow, read-only, and revocable. A key prefix is not a permission model — verify the actual reads you need.

November 14, 2026
Engineering8 min read

How to audit an access-control migration

Access-control migrations fail quietly. The old path keeps working, the new path has an exception, and a subset of users lands in the gap. Audit the transition, not just the destination.

November 14, 2026

CORRECTIONS

Found an error?

Technical writing ages. If a Stripe behavior, API shape, or security claim is wrong, open an issue with the article URL and a source. Corrections are published, not quietly patched.

PUT THE NOTES TO WORK

Compare two exports before you trust any article.

The browser audit is the fastest way to see whether your billing and entitlement data disagree in a way that matters.