Stripe Balance Transactions Export Guide
Use Stripe balance-transaction fields to separate charges, fees, refunds, adjustments, and payout links before matching the bank deposit.
Try with sample files | View sample report
Problem statement
Stripe bank deposits are payout-level cash movements, but the supporting export is usually the balance-transactions file. Reviewers need the fields that explain net payout composition before they compare the bank row.
Numeric example
| Line item | Amount |
|---|
| Identity | Balance transaction ID and payout ID |
| Classification | Type, source, description |
| Amounts | Gross amount, fee, net amount |
Why Stripe payout may not match bank deposit
- Payout ID groups charge, fee, refund, and adjustment rows into one deposit review.
- Transaction type separates charges from fees, refunds, disputes, and other non-gross activity.
- Available date and created date help separate payout timing from payment timing.
- Net amount is useful, but gross and fee-related fields explain why the deposit is smaller than the payments total.
What files to export
- Stripe balance transactions export with type, amount, fee, net amount, payout ID, and timing fields.
- Stripe payouts export with payout ID, status, arrival date, and net payout amount.
- Bank statement export with deposit date, amount, and description for Stripe transfers.
Manual workflow
- Filter or group the balance-transactions export by payout ID.
- Separate charges, fees, refunds, disputes, and other adjustments.
- Compare the grouped net amount to the Stripe payout report before the bank match.
- Match the payout report to the bank deposit by amount, date, and reference.
- Keep unsupported shortfalls in review instead of classifying them by guesswork.
Common mistakes
- Reviewing gross charges without grouping them back to a payout ID.
- Ignoring non-charge transaction types inside the same payout cycle.
- Using payment date alone and treating settlement timing gaps as proof of an error.
How Reconcile Locally helps
- Keeps Stripe payout rows, component rows, and bank rows in one local review flow.
- Separates matched payouts from unknown bank payments and open amount differences.
- Preserves conservative wording when the export only proves a deduction, not its final business cause.
What still needs manual review
- Exact naming and export filters can change, so reviewers should confirm their Stripe export layout first.
- Some reserve, dispute, and grouped-settlement cases still require manual confirmation.
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
Which Stripe balance-transaction columns matter most?
Start with payout ID, type, amount, fee, net amount, and timing fields. Those columns usually explain why the bank deposit differs from gross payments.
Should I match customer charges directly to the bank deposit?
Usually no. Start from the payout ID and the payout-level net amount, then work backward into the charge and balance-transaction rows.