你的 Stripe 支出不是你的收入：如何将 Stripe 与账簿核对

Arron Bennett, Founder of Bennett Financials

Most bootstrapped SaaS books I open have the same quiet error. Every Stripe payout landed in the bank, and someone booked each one as revenue. The bank matches. The books look clean. The revenue number is still wrong, and so is every margin built on top of it.

A Stripe payout isn't a sale. It's a bundle of sales, minus fees, minus refunds, minus disputes, sent a few days after the money came in. This post covers what a payout actually contains, how to split one apart with a short script, and the bookkeeping setup that keeps the two in step.

Key takeaways

• A Stripe payout is a net number. Gross charges, Stripe fees, refunds and disputes are all inside it.
• Booking payouts as revenue understates revenue, hides fees, and buries refunds.
• Book gross charges as revenue and fees as an expense, then run both through a Stripe clearing account.
• The balance transactions API (or the Payout reconciliation report) tells you exactly what each payout contains.

What does Stripe reconciliation actually mean?

Stripe reconciliation means proving that every payout in your bank equals the charges, fees, refunds and disputes Stripe says made it up, and that each piece is booked in the right account. Revenue goes to revenue, fees to expenses, refunds against revenue. When the clearing account nets to zero, you're reconciled.

Your bank only ever sees the net. Your books need the gross.

Why are Stripe payouts not the same as revenue?

Stripe takes its fees out before it pays you. Refunds and lost disputes come out of the same balance, and payouts arrive on a schedule, so charges from the last days of a month land in next month's bank account. Book the deposit as revenue and every one of those differences disappears into a single wrong number.

Here's a hypothetical example. A two-founder developer-docs hosting SaaS at $29,000 of MRR, all on Stripe. Every number below is made up to show the mechanics. Swap in yours.

In one month the business charges customers $31,200. It refunds $640, loses one $480 dispute plus a $15 dispute fee (an assumed figure, so check your own), and pays $1,150 in processing fees.

So the payouts total $28,915, which is $31,200 − $640 − $480 − $15 − $1,150.

If the bookkeeper records $28,915 as revenue, revenue is understated by $2,285. That's $1,165 of fees and dispute costs that never show up as an expense, and $1,120 of refunds and lost disputes that never show up as anything. The fees alone are 3.7% of gross, and they have no line on the P&L.

How do you see what's inside a Stripe payout?

Every movement in your Stripe balance is a balance transaction with a gross amount, a fee and a net, all in the smallest currency unit, so cents for USD. For automatic payouts, you can list every balance transaction that was paid out in one payout and group them by reporting_category.

Here's a minimal Python version. Use a restricted, read-only key.

import os
from collections import defaultdict
import stripe

stripe.api_key = os.environ["STRIPE_READ_KEY"]  # restricted, read-only

def explain_payout(payout_id):
    payout = stripe.Payout.retrieve(payout_id)
    totals = defaultdict(lambda: {"gross": 0, "fee": 0, "net": 0})
    txns = stripe.BalanceTransaction.list(payout=payout_id, limit=100)
    for t in txns.auto_paging_iter():
        if t.type == "payout":
            continue  # the payout itself, not what's inside it
        row = totals[t.reporting_category]
        row["gross"] += t.amount
        row["fee"] += t.fee
        row["net"] += t.net
    net_sum = sum(r["net"] for r in totals.values())
    for cat, r in sorted(totals.items()):
        print(f"{cat:<12} gross {r['gross']/100:>11,.2f}  fee {r['fee']/100:>9,.2f}  net {r['net']/100:>11,.2f}")
    print(f"payout {payout.amount/100:,.2f} | sum of nets {net_sum/100:,.2f} | match: {net_sum == payout.amount}")

explain_payout("po_...")

The last line is the check that matters. If the sum of nets equals the payout amount, you know exactly what's in that deposit. If it doesn't, the gap is something you need to find, such as an adjustment, a reserve or a manual payout. The payout filter only works for automatic payouts. If you trigger payouts by hand, use the Payout reconciliation report in the Stripe Dashboard instead.

You don't need to run this on every payout forever. Run it on one month, prove the method, then let your bookkeeping tool's Stripe integration or a monthly report do the routine work.

How should Stripe be set up in the books?

Treat Stripe like a bank account. Create a "Stripe clearing" account, record gross charges into it as revenue, take fees out of it as an expense, take refunds out of it against revenue, and record each payout as a transfer from clearing to the bank. At month end, the clearing balance should equal the Stripe balance.

For the docs-hosting example, the month books like this:

• Revenue: $31,200 of gross charges.
• Refunds and lost disputes: $1,120, against revenue.
• Payment processing fees: $1,165, as an operating expense.
• Transfers to the bank: $28,915, which revenue never touches.

The clearing account goes up by $31,200 and down by $1,120, $1,165 and $28,915, so it lands on zero. If payouts lag the month end, it won't be zero. It'll equal whatever Stripe still holds for you, and that's correct. A balance that drifts every month means something is being missed.

One more thing worth watching. If Stripe ever holds a reserve on your account, that money is yours but you can't spend it. It belongs in clearing, not in your cash forecast. I've written more on processor reserves and available cash.

This short isn't about Stripe. It's about the same gap from the other side: a profitable P&L and a bank account that can't cover payroll. That gap is the reason I want the books and the bank telling the same story.

What changes when the books are right?

Three things get honest at once. Revenue shows what customers really paid. Processing fees show up as a cost you can manage. And refunds become visible, so a product or onboarding problem stops hiding inside a smaller deposit.

That matters the first time you look at gross margin, price a plan, or talk to anyone who will read your numbers closely, such as a lender, an investor or a buyer. Diligence on a SaaS business reconciles Stripe to the bank and the books. Better that you find the gaps first.

It also makes refunds a number you can act on. If you find refunds climbing, look at failed payments and recovery in the same review. Both are revenue leaving quietly.

What should you do on Monday?

Pick last month. Pull every payout, run the script or the Payout reconciliation report, and total gross charges, fees, refunds and disputes. Compare gross charges with the revenue in your books. If the books show the payout total instead, set up a Stripe clearing account and rebook the month the right way. Then make it the rule for every month after.

It's a two-hour job. It fixes your revenue line for good.

FAQ

Should I record Stripe fees as an expense or net them against revenue?

Record them as an expense. Revenue should be what customers paid. Fees are a cost of collecting it, and you can only manage a cost you can see.

Why doesn't my Stripe payout match my sales for the month?

Because payouts are net of fees, refunds and disputes, and they arrive on a schedule. Sales from the last few days of a month often land in next month's bank deposits.

Does a Stripe payout include refunds and disputes?

Yes. Refunds and lost disputes reduce your Stripe balance, so they come out of the next payout. A payout can even come out negative if refunds outrun charges.

Do I need software to reconcile Stripe?

Not to start. The Payout reconciliation report or a short script covers one month. After that, most accounting tools' Stripe integrations can post gross, fees and refunds for you, once the clearing account is set up.