Stripe Payout Does Not Match Your Bank Deposit

Review Stripe payouts, balance transactions, payout status, Trace ID clues, and bank deposits when Stripe payout totals do not match the bank deposit one to one.

Try with sample files | View sample report

Problem statement

Your Stripe dashboard may show gross payments, while your bank usually receives a net payout after fees, refunds, disputes, adjustments, and payout timing. This means individual Stripe payments often do not match the bank deposit one to one.

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 may not match bank deposit

The bank deposit is usually payout-level, while Stripe payments are transaction-level rows.
A single bank deposit may include many payments, fees, refunds, disputes, and adjustments.
Stripe balance transactions can reduce the payout before the cash reaches the bank.
Payout status and expected arrival date can show a timing issue before it becomes a true bank mismatch.
Payout arrival date and bank deposit date may differ even when the payout is correct.
Weak bank descriptions or grouped settlement timing can leave a possible payout difference that still needs review.

What files to export

Stripe payments or charges export with gross customer payments, dates, amounts, and payment references.
Stripe balance transactions export with fees, refunds, disputes, adjustments, and payout IDs.
Stripe payouts export with payout ID, arrival date, status, Trace ID or bank-reference details when available, 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, payouts, and the bank statement.
Identify the payout ID, expected arrival date, status, and payout amount.
If the payout is pending, in transit, canceled, or failed, keep the bank side unresolved until the status becomes clearer.
Check Trace ID or bank-reference details before treating the issue as a true bank mismatch.
Group related Stripe balance transactions by payout where possible.
Use gross, fee, refund, dispute, adjustment, and net fields from balance transactions before comparing to the bank deposit.
Compare the expected net payout to the bank deposit.
Review unmatched payments, unknown deposits, and amount differences.

Common mistakes

Comparing gross Stripe payments directly to bank deposits.
Ignoring payout status or expected arrival date.
Assuming a payout marked paid must already be easy to identify in the bank statement.
Ignoring refunds, disputes, or adjustments.
Treating every amount difference as a confirmed fee.
Matching customer payments directly to one bank deposit without checking payout grouping.

How Reconcile Locally helps

Keeps payout support, timing context, and bank rows in one local review flow.
Shows clear matches, unknown bank payments, and grouped-row cases without forcing a final explanation.
Keeps amount-difference wording conservative when the export does not fully prove the exact cause.
Exports a reconciliation report for follow-up or accounting review.

What still needs manual review

Exact fee, refund, dispute, tax, and payout breakdowns may still require manual review depending on which Stripe exports are available.
Grouped settlement timing, weak references, and partial Trace ID coverage can leave a possible payout difference that still needs review.
Some payouts that eventually fail can appear paid first, so payout status history may need review before you call the bank side complete.
Trace ID and arrival details can narrow the issue, but they do not replace payout support or reviewer judgment.

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 payout not match the bank deposit one to one?

Because the bank deposit is usually a payout-level net amount after fees, refunds, disputes, adjustments, and timing differences, while Stripe payments are transaction-level rows.

What Stripe exports should I review first?

Start with Stripe payouts and balance transactions, then use the payments or charges export and the bank statement to confirm the expected net payout.

Does every Stripe payout difference mean a fee?

No. The difference may reflect a possible fee, refund, tax, timing, or payout adjustment, so unresolved cases should stay in review until the exports prove more.

What if the short deposit looks more like a reserve than a fee?

Check the balance or processor export for held-funds or reserve-style rows before finalizing the explanation. Reserve timing often belongs in its own review path, especially when the release lands in a later payout cycle.

When should I use the Stripe payout Trace ID page?

Use it when the payout appears valid in Stripe but the bank deposit is late, unclear, or hard to identify from the bank export. That workflow helps separate timing from a true mismatch.

Can a Stripe payout still need review even if it shows paid?

Yes. A paid status does not guarantee the bank deposit will be obvious immediately, and some payouts that later fail can briefly appear paid first. Keep weak-reference or late-bank cases in review until payout support and the bank side line up.

When should I use the broader Stripe payout guide instead?

Use the broader guide when you still need the normal payout-first workflow across Stripe deposits. Stay on this mismatch page when the issue is a late, unclear, Trace-ID-driven, or unresolved bank mismatch after the basic payout explanation is already understood.