Guides / Stripe payouts
How to reconcile Stripe payouts with a bank statement
A Stripe payout is one bank credit that bundles many charges, refunds and fees. To reconcile it, check that the payout's net amount equals one credit on your bank statement, then check that the charges, refunds and fees inside the payout add up to that net amount.
What a payout bundles
Your bank never sees your customers' charges. It sees one deposit per payout, for the net amount: charges, minus refunds, minus Stripe's fees. That is why a statement line cannot be matched to a charge, and why a payout has to be matched as a whole.
Here is one payout, with made-up numbers.
| Item | Type | Gross | Fee | Net |
|---|---|---|---|---|
ch_3Qa1 | Charge | 1,200.00 | −35.10 | 1,164.90 |
ch_3Qa2 | Charge | 450.00 | −13.35 | 436.65 |
ch_3Qa3 | Charge | 89.90 | −3.01 | 86.89 |
re_3Qa4 | Refund | −120.00 | 0.00 | −120.00 |
| Payout | 4 items | 1,619.90 | −51.46 | 1,568.44 |
The bank statement shows one line for it: a credit of EUR 1,568.44, booked on 13 November. The payout's arrival date was 12 November. One day apart is normal. Stripe's docs say the payout report is grouped by estimated arrival date, not the day your bank posts the deposit, and weekends and holidays move it.
Two checks, in this order
- Payout against bank. Same net amount, to the cent, in the same currency, within a few days. This is the check that finds a missing deposit.
- Items against payout. Charges, refunds and fees add up to the payout's net amount. This is the check that finds a missing refund or a fee you did not expect.
Do the first check for every payout, every month. Do the second only for payouts that fail the first, or when your ledger records charges and fees separately.
Three ways to do it
| Option | Better when | Worse when | Cost |
|---|---|---|---|
| A spreadsheet | You have a few payouts a month. You can see and change every step. | You have hundreds of lines. Lookups need exact values, and a duplicate amount is easy to miss. | Free |
| Stripe's own reports and Bank reconciliation | You are a US account on automatic payouts. Stripe links to your bank and tracks each payout's status for you. | You are outside the US, use Connect, or use manual or instant payouts. Stripe's docs say its Bank reconciliation does not cover these. It sees only Stripe, not your ledger. | Included in Stripe. We found no price in the docs. |
| Milyo's free matcher | You want a payout list and a bank file matched in your browser, with the reason for each match, and nothing uploaded. | You need one payout matched to its many charges (1:N). That is not built. | $0, no account |
How to do it with the free matcher
The free matcher at try.milyo.app matches two files, one row to one row. It runs in your browser and nothing is uploaded. That fits check 1, payout against bank, because a payout is one row on each side.
- Get two files. In Stripe, open Reports, then Payout reconciliation, and download the Summary for the month as CSV. Download your bank statement for the same dates as CSV, CAMT.053 or MT940. Stripe's docs say this report needs automatic payouts. Open the Summary and check that it has one row per payout, with a net amount and a date.
- Load them. Put the Stripe file in File A and the bank file in File B. Map the columns: date, amount (use the payout's net amount), currency, and a reference.
- Keep the default rules. The default has two passes. The key pass matches rows whose references are equal. The fallback pass matches rows with the same amount and a date within 3 days.
- Read the result. Each match names the pass that made it. Anything the rules could not settle is an exception, with the reason.
Which pass will find your payouts? It depends on what your bank writes. The key pass compares whole values. It works only if one bank column holds exactly the payout id, for example po_1Rk4TzA. Some banks do put it in the end-to-end reference. Our MT940 test file has a line with /EREF/po_1Q8xLm. In the matcher, set the bank file's Reference to that column.
Most banks write only a descriptor such as STRIPE PAYMENTS UK. Then the fallback pass does the work, on amount and date. The sample files on the matcher show this: the ledger's Stripe payout of 2,353.40 on 4 November matches the statement credit of 2,353.40 on 5 November, one day apart.
When two payouts look the same
Say two payouts of EUR 4,210.00 land in the same week, and the bank shows two credits of EUR 4,210.00. Either payout could fit either credit. Milyo does not pick. It flags all four rows as exceptions, with the reason More than one possible match. You decide, using the arrival dates or the payout ids.
What is not built
Planned, not built: matching one payout to the many charges, refunds and fees inside it (1:N), and reading Stripe directly without a file. Both are in the paid plans, which are in private beta. The free matcher does 1:1 only, so check 2 is still a spreadsheet job today: filter the itemized Stripe report by payout id and sum the net column. The sum should equal the payout's net amount.
Common reasons a payout does not match
- Instant payouts. Stripe's docs say it cannot tell which transactions an instant payout contains, so you have to reconcile those against your transaction history.
- Currency. A payout in EUR and a credit in another currency will not match. Milyo treats mixed currencies as different, and never converts.
- Gross against net. Compare the payout's net amount with the credit, not the gross. Gross still includes Stripe's fees.
- Timing. A payout that arrives after a weekend can fall outside a tight date window. The default window is 3 days. You can widen it in the matching rules step.
Try it on this month's payouts. No account. Your files stay in your browser.
Open the free matcherRelated guides
- 1:N matching: one bank credit, many transactions, how a payout is matched to its items.
- CAMT.053 to CSV: the fields that matter, if your bank sends XML.
- MT940 explained: the :61: and :86: lines, if your bank sends MT940.