Case studies

Proof you can re-run.

Every finding here comes from real data, with the method shown in full. Nothing is asserted that can't be reproduced — take the data, run the code, reach the same number. This is the discipline of revenue integrity: not opinion, evidence.

B2B SaaS · revenue reconciliation

Flow Audit

Built on a synthetic 500-account book with a known ground-truth ledger, Flow Audit reconciles CRM, contracts, billing, and commissions against one another and surfaces every place value leaks — silent churn, duplicate revenue, commission overpayment, under-billing, and more. Because the truth is known in advance, detection can be proven exact, not merely plausible.

4.6M
Leakage surfaced · demo run
100% / 100%
Precision & recall, calibrated
267
Leaks across six types

The pain

A deal closes in the CRM, a contract is signed, invoices go out, commission is paid. Four systems that should agree — and quietly don't. Revenue that's counted but never collected; commission paid above plan; the same revenue booked twice.

Why it persists

Each system is correct on its own terms. No single tool sees across all four, so the disagreements between them are invisible — and what no one can see, no one fixes.

The method

Reconcile the systems against each other, classify every unexplained variance by type, and price it. A calibration layer with planted, known leaks proves the detection catches everything and invents nothing.

The proof

Against the ground-truth ledger, detection reaches 100% precision and 100% recall — zero misses, zero false alarms — surfacing €4.6M across 267 leaks in six categories. The full pipeline is on GitHub.

Retail · currency consolidation

The $252K in the exchange rate

Applied to a public Maven “Global Electronics Retailer” dataset: $54.7M of revenue, 46.6% of it booked in foreign currencies. Reconciling every order to its transaction-date exchange rate — against the common shortcut of one year-end rate — surfaces a $252,477 revenue misstatement hiding entirely in rate timing.

$252K
Revenue misstated · rate timing
46.6%
Revenue in foreign currency
$54.7M
Revenue reconciled

The pain

Almost half of revenue is earned in EUR, GBP, CAD, and AUD. Before it reaches a report it must be converted to one currency — and the rate chosen for that conversion quietly changes the number.

Why it persists

Currency conversion looks like plumbing, so it's treated like plumbing. Applying a single year-end rate to a whole year of transactions feels harmless; no system flags the gap, because every system did as it was told.

The method

A documented DuckDB pipeline aligns the raw files, rebuilds line-level revenue, joins each order to its transaction-date spot rate, and reconciles that against the year-end shortcut — pricing the difference.

Reproduce it

Download the public dataset, run reconcile.py, and you reach $252,477. The finding isn't asserted — it's falsifiable, and the script is published for anyone to check.

More case studies are added as new datasets are analyzed — each a real reconciliation, each reproducible. Bring a dataset →