How a SaaS Company Tied Its Billing System to the Books and Found Lost Revenue
Sam's List Editorial | 2026-06-23
How a SaaS Company Tied Its Billing System to the Books and Found Lost Revenue Most SaaS founders assume their billing platform and their accounting system agree with each other. They almost never do. The numbers drift apart quietly. Stripe says one thing, QuickBooks says another, and the gap gets explained away as "timing" until nobody remembers what's actually in there. This SaaS billing reconciliation case study walks through what happens when somebody finally chases the difference — and finds real money sitting in it. A quick flag before we start: this is an illustrative composite, built from the kind of engagements The SaaS Bookkeeper handles, not an audited result for one named client. The mechanics are real. The dollar figures are representative. The billing system and the books had never agreed, and nobody had time to fix it The company was a Series A SaaS business doing about $4M in ARR, billing monthly and annually through Stripe. Standard setup. Their books showed revenue. Stripe showed revenue. The two numbers were always a few percent apart, and every month the founder told himself he'd dig in "after the next release." He never did. That's the trap. A 3% gap on $4M is $120K floating around with no name on it. But it never feels urgent, because nothing is on fire. The cash still lands in the bank. The dashboard still looks fine. Here's the thing nobody tells you: the gap isn't one problem. It's usually three or four problems pointing in different directions, partially canceling each other out. Which is exactly why a casual glance never catches it. What a real SaaS billing reconciliation case study starts with: a line-by-line tie-out The SaaS Bookkeeper's first move was unglamorous: a monthly reconciliation tying the billing platform to the general ledger, line by line. Not "do the totals roughly match." A real Stripe GL reconciliation maps every category of activity — new subscriptions, upgrades, downgrades, refunds, failed payments, processing fees, disputes — from the billing system into the corresponding GL account, then explains every remaining dollar of difference. This matters because of how SaaS revenue is supposed to work. Under ASC 606 , the accounting standard for revenue from contracts with customers, you recognize revenue as you deliver the service — ratably over the subscription term — not when the cash hits. An annual plan billed in January is earned one-twelfth at a time. The amount you've billed but not yet earned sits as deferred revenue, a liability, until you've delivered it. If your billing system and your GL aren't...
