Stripe Payout Reconciliation: Match Bank Deposits, Fees, Refunds and Net Payouts
Review Stripe bank deposits, deductions, net payouts, and accounting handoff support from exported files.
Try with sample files | View sample report
Problem statement
Stripe dashboard totals can be gross, but the bank usually receives a net payout after fees, refunds, disputes, adjustments, and payout timing. A direct payment-to-bank comparison usually hides the real review work.
Numeric example
| Line item | Amount |
|---|
| Gross Stripe payments | $1,000.00 |
| Refunds | -$100.00 |
| Stripe fees | -$32.00 |
| Disputes or adjustments | -$15.00 |
| Expected payout | $853.00 |
| Bank deposit | $853.00 |
Why Stripe payout does not match the bank deposit
- Stripe dashboard totals may show gross payments while the bank receives the net payout.
- Refunds, disputes, and adjustments can reduce a later payout cycle instead of the original charge day.
- Stripe fees reduce the payout before the cash reaches the bank.
- One payout can group several payment days into one bank deposit.
- Payout arrival date and bank settlement date may differ even when the payout is correct.
What files to export
- Stripe payments or charges export with gross customer payments, dates, amounts, and references.
- Stripe balance transactions export with fees, refunds, disputes, adjustments, and payout IDs.
- Stripe payouts export with payout ID, arrival date, status, and net payout amount.
- Bank statement CSV/XLSX with deposit date, amount, and description for Stripe transfers.
- Optional orders or invoices export when you need customer-facing references behind the payout.
Manual workflow
- Export Stripe payments, balance transactions, and payouts.
- Group payments by payout where the export supports it.
- Subtract refunds, fees, disputes, and adjustments from the gross payment total.
- Compare the expected net payout to the Stripe payout report.
- Match the payout report to the bank deposit by amount, date, and reference.
Common mistakes
- Matching the bank deposit directly to gross customer payments instead of the payout net amount.
- Ignoring refunds, disputes, or adjustments inside the balance transaction export.
- Assuming the payout date and the bank settlement date must always match exactly.
- Calling every shortfall a fee when the source data only proves a broader amount difference.
How Reconcile Locally helps
- Keeps Stripe payments, payout rows, and bank rows in one payout-first review flow.
- Separates matched deposits from unknown bank payments, grouped-payment cases, and open amount differences.
- Keeps the wording conservative when the export only proves a possible fee, refund, tax, or payout adjustment.
- Exports a payout-level report you can hand to accounting or operations before you change entries.
What still needs manual review
- Exact fee, refund, tax, and payout breakdowns may still require manual review depending on the available export files.
- Very messy bank labeling and grouped settlement timing can still require a human to confirm the final match.
- Unknown deposits and weak-reference rows should stay open until the payout support is complete.
Content review and sources
Written and reviewed by the Reconcile Locally product team. Last reviewed June 7, 2026.
Guidance is checked against current product behavior and first-party documentation where available. Reconciliation results still require human review.
Frequently asked questions
Why does Stripe bank deposit differ from the payment total?
The bank usually receives the net payout after Stripe fees, refunds, disputes, adjustments, and payout timing differences. Gross payments should be reviewed through the payments and balance-transaction exports.
Should I compare each customer payment directly to one bank deposit?
Usually no. Start from the payout ID and the net payout amount, then work backward into the payment and balance-transaction exports.