How to reconcile Stripe payouts to bank deposits

Use the payout as the bridge

Reconciling each Stripe charge directly to the bank is usually the wrong level of detail. Card transactions settle into the Stripe balance first. Stripe then creates a payout from available balance activity and sends a net amount to a bank account. The payout identifier and payout amount provide the bridge from detailed Stripe activity to cash.

Your reconciliation therefore has two related checks. First, confirm that the transactions assigned to a payout explain its net amount. Second, match that payout to the bank deposit. If your Stripe export already provides a reliable payout-level net, begin with the second check and retain the detailed balance activity as support.

Export files with enough overlap

From Stripe, obtain a payout report that includes payout identifier, created or arrival date, status, currency, and amount. If you need to explain the composition of a payout, also export balance transactions or the payout reconciliation detail available for the account. From the bank, export the statement lines with posting date, description, debit, credit, and currency.

Include several business days on both sides of month end. Stripe can create a payout in one accounting period and the bank can post it in the next. Weekends, bank holidays, payout schedules, manual payouts, and account review can extend the ordinary delay. An overlap prevents a normal timing difference from appearing as missing.

Confirm that the Stripe payout destination matches the bank account under review. Businesses with multiple legal entities, currencies, or bank accounts can accidentally compare a valid payout with the wrong statement. Also confirm whether the Stripe account uses automatic or manual payouts and whether instant payouts occur, since those settings change expected timing and fees.

Normalize dates, signs, and currencies

Stripe dates may represent creation, expected arrival, or paid status, while the bank supplies a posting date. Choose the date that best represents payout initiation, retain the other dates as reference, and compare within a documented business-day window. Do not rewrite dates to make records match.

Normalize the sign convention before matching. A positive Stripe payout should normally correspond to a bank credit, even if the bank CSV expresses credits as negative values in a signed amount column. Verify the bank export convention with a known deposit. Handle reversals as separate records rather than deleting both sides.

Keep currencies separate. A USD payout and an EUR deposit are not an amount match, even if their numeric values happen to agree. When Stripe performs conversion or sends a settlement currency different from the transaction currency, use the payout settlement amount and document the conversion evidence. Foreign exchange gains, losses, and fees require accounting treatment outside a simple amount match.

Match exact payouts first

1. Filter to Stripe payouts with a paid status and bank credits in the expected destination account.
2. Match exact currency and amount within the normal posting window.
3. Use the bank description and Stripe payout identifier when either source exposes a useful reference.
4. Remove confirmed pairs from the open list.
5. Review repeated amounts carefully so date proximity does not create a false match.

Stripe fees are normally reflected in balance activity before the payout amount is created. In that common setup, the payout net should equal the bank deposit without subtracting the same fees again. If the bank receives an amount different from the payout report, investigate instant payout fees, bank fees, currency conversion, a split deposit, or an incorrect source column before classifying the variance.

Explain common Stripe differences

Payout still in transit

A paid or pending payout near month end may not have reached the bank by the statement cutoff. Record the payout identifier, amount, initiation date, expected arrival, and destination. Carry it forward and confirm the bank posting in the next period. If the payout becomes failed or canceled, update the classification rather than leaving it as in transit.

Refunds, disputes, and reserves

Refunds and disputes can reduce the Stripe balance before a payout. A negative balance can delay a payout or cause later activity to fund prior obligations. Reserves and balance adjustments can also change the amount available. Use Stripe balance transaction detail to support these movements. Do not assume every amount difference is a processing fee.

Multiple payouts or combined bank lines

Manual or instant payout behavior can produce several deposits on one day. Conversely, bank feeds can combine or summarize postings. Preserve the individual Stripe payouts, list every bank component, and document any one-to-many relationship. The sum should agree by currency, and the grouping should be supported by dates and references rather than amount alone.

Failed, canceled, or returned payouts

A failed payout should not be matched to an unrelated bank deposit. Trace the original payout status, any reversal, and the replacement payout. If the bank posted and returned the funds, retain both bank lines. This preserves the cash trail and avoids hiding a failed settlement inside a later successful batch.

Prepare review-ready support

A completed file should show the Stripe payout identifier, settlement currency, payout amount, relevant Stripe date, bank posting date, bank description, match status, and exception explanation. Attach or retain the original reports. For open items, include an owner and next action. Reviewers should be able to distinguish ordinary settlement timing from an item that requires processor or bank follow-up.

Compare the total of matched and open Stripe payouts with the source report, then compare matched and unexplained bank deposits with the statement. These completeness checks catch records omitted by filters or import ranges. The goal is a supported zero difference after timing and other documented items, not a spreadsheet made to balance through plugs.

Using ReconcileCSV for the comparison

ReconcileCSV accepts a Stripe payout CSV and bank statement CSV, lets you map date and amount columns, proposes deterministic matches, and surfaces ambiguous or unmatched rows. The preview is free. Full ledger, print, and exception exports are available after a one-time $39 purchase. CSV processing and matching run in the browser.

ReconcileCSV does not connect to Stripe, retrieve live payout status, post entries to accounting software, or determine the proper account for fees, reserves, disputes, or foreign exchange. It cannot repair incomplete exports. A preparer must review ambiguous matches and support every accounting conclusion with the original source data.