Stripe payout reconciliation: from charges to bank deposits

A Stripe payout is a settlement batch. The amount arriving at the bank can include many payments and adjustments, less fees, refunds and disputes. Reconciliation connects that net deposit back to every component that created it.

Start with the payout record, not the bank deposit. For automatic payouts, Stripe keeps an association between a payout and the balance transactions it settles. That relationship is the cleanest audit trail.

What belongs in a Stripe payout

Stripe balance transactions represent the credits and debits that affect the Stripe balance. Depending on your activity, a payout can reflect charges, processing fees, refunds, disputes, adjustments and other balance movements. The bank sees only the resulting net cash transfer.

Stripe's payout reconciliation report groups the transactions associated with automatic payouts. It can also provide itemized CSV data for the transactions summarized in a settlement batch.

A practical accounting workflow

Create a Stripe clearing account. Treat the processor balance as cash in transit rather than recording each bank deposit as revenue.
Import gross activity. Record revenue and other components from the source transactions.
Post fees, refunds and disputes separately. This preserves usable gross-sales and expense reporting.
Record the payout as a transfer. Move the exact net payout from Stripe clearing to the bank.
Match the bank deposit. The transfer recorded in the books should equal the deposit received.
Explain the ending processor balance. Unpaid activity and timing should account for the remainder.

Automatic, manual and instant payouts

Stripe recommends automatic payouts for simpler reporting because the included transactions remain associated with each payout. Manual or instant payout workflows may require a different reconciliation method. Stripe specifically notes that it cannot identify which transactions are included in instant payouts because the user controls their timing and amount.

Exceptions worth flagging

A refund settled in a different period than the original charge
A dispute or dispute reversal changing a later payout
Multiple currencies or separate Stripe balances
Instant payouts and their additional fees
Charges recorded through another sales platform as well as Stripe
A payout that failed, was reversed or landed in a different bank account

What good automation should do

Automation should not hide unexplained differences. It should apply known mappings, create the correct payout transfer, and send uncertain items to an exceptions view. A complete opening-period test should prove that source activity, the processor balance and the bank deposit agree before routine rules are enabled.

If you would rather have this configured and validated for you, see the Stripe payout reconciliation service.

Want a second look at your Stripe workflow?

Send the platforms involved and describe what is not tying out. No credentials or financial records are required for the initial review.

Request a free payout assessment →

Official references

This guide is general educational information, not accounting or tax advice.

Frequently asked questions

What is a Stripe payout reconciliation report?

It is a Stripe report that groups the balance transactions - charges, fees, refunds and disputes - settled in each automatic payout, so you can tie the net bank deposit back to the activity that created it.

Why is my Stripe payout different from my sales total?

A payout is net cash. Stripe subtracts processing fees, refunds, disputes and other adjustments before the deposit reaches your bank, so it rarely equals gross sales for the same period.

Can you reconcile Stripe instant and manual payouts?

Yes, but they need a different method. Stripe cannot associate specific transactions with instant payouts because you control their timing and amount, so those are reconciled by balance movement rather than by settlement batch.