How to match a Stripe payout CSV to a bank statement
The bank normally receives a net payout, not each underlying charge. Match one payout batch to one bank deposit first, then investigate the components that explain the net amount.
1. Choose the Stripe export for the question
For automatic payouts, Stripe’s Payout reconciliation report is designed to show the balance activity associated with a payout. A payout-level export is useful for the bank comparison; detailed rows help explain fees, refunds, disputes and adjustments. Stripe’s report shape and available columns vary by account.
2. Build the two sides of the comparison
| Stripe side | Bank side |
|---|---|
| Payout ID or reference, payout date, net amount, currency | Posting date, deposit amount, currency, description/reference |
| Optional detail explaining fees, refunds, disputes or adjustments | One deposit may be posted later than the Stripe event date |
Do not compare gross charges directly with the bank deposit. Fees, refunds, disputes, reserves and other balance activity can make the net payout different from sales.
3. Match in a controlled order
- Filter the bank statement to likely Stripe deposits.
- Compare currency before amount; never silently convert currencies.
- Compare net amount and a reasonable date window around the expected or posting date.
- Use payout IDs or bank references when present, but treat descriptors as evidence rather than proof.
- Keep one-to-one matches, unmatched payouts, unmatched deposits and ambiguous candidates separate.
What a file comparison can and cannot tell you
Payout Reconciler can compare user-supplied payout data with bank-statement transactions and surface amount, currency, date-window, unmatched and ambiguous cases. It does not explain why a bank rejected a transfer, provide tax advice, or recreate transaction attribution that Stripe does not expose.
For date differences, see why a Stripe payout may differ from a bank deposit. For export choices, read the Stripe report guide; supported bank inputs are listed on Formats.