ID Validation
Checks for required id column with balance transaction IDs (txn_XXXXX).
Enter your email to receive a sign-in link
Check your Stripe balance transactions CSV export for missing columns and data format issues.
Free preview — then from $5. Save with bundles.You can preview Stripe Balance validation results for free — no signup needed. Full validation reports use credits based on row count.
Go to Balances > All Activity in your Stripe dashboard and click Export. Choose your timezone, date range, and select All columns for the complete itemized CSV.
Balance transactions are granular records of every financial event in your account. Payouts are specific transfers of your available balance to your bank account.
Balance → Transactions → Export CSV
Upload your Balance Transactions Export export file
Check your Stripe data for errors and warnings
Issues are flagged inline with clear fix suggestions — review and correct before you import.
Checks for required id column with balance transaction IDs (txn_XXXXX).
Validates transaction Type column (charge, refund, payout, dispute, etc.).
Validates Amount, Fee, and Net currency columns.
Checks Source ID format for linked objects (ch_, re_, po_).
Files processed locally. Your data never leaves your computer.
Get validation results in seconds, even for large files.
Fourteen balance transactions had Source IDs pointing to charge objects that didn't exist anywhere else in the export — orphaned references from test-mode charges that leaked into the live export. The validator's referential integrity check caught every one before I fed the file to our ERP.
I merged three months of balance exports and found that Amount plus Fee didn't equal Net on 83 rows. Turned out one export used cents (integer amounts) while the others used dollars with decimals. The precision mismatch would have thrown off our entire reconciliation if the validator hadn't flagged it.
A client's export had 'Charge', 'charge', and 'CHARGE' in the Type column — Stripe's API is case-sensitive, but the CSV had been hand-edited. The validator flagged all 29 non-standard type values so we could normalize them before importing. Inconsistent naming like that silently breaks category filters.
Your Stripe Balance files stay on your device. Processing happens client-side, nothing leaves your machine.
Your Stripe Balance files are never cached, logged, or stored anywhere. Every session is ephemeral.
Designed for data sovereignty. No third-party trackers or analytics touch your Stripe Balance files.
Issues you might encounter when importing Source data to Target - and how we solve them
The 'id' column (txn_xxx) is required but not found
File without 'id' column
txn_1A2B3C4D5E6F7G
Balance transaction ID is essential for reconciliation
Re-export from Stripe Dashboard → Balance → Export
The 'Type' value is not a recognized Stripe balance transaction type
sale or deposit
charge, refund, payout, adjustment, fee
Only Stripe's standard transaction types are valid
Check if data was modified after export
The 'Net' column showing net amount after fees is missing
(blank or missing Net column)
1425 (gross minus fees, in cents)
Net amount is crucial for accurate accounting
Re-export ensuring all balance columns included
Gross - Fee ≠ Net (amounts don't reconcile)
Gross: 1500, Fee: 75, Net: 1400 (incorrect)
Gross: 1500, Fee: 75, Net: 1425 (correct)
Balance transaction amounts should be mathematically consistent
Check for data corruption or manual modifications
Buy bundles and get up to 60% off. Perfect for recurring monthly conversions.
Once your Stripe export passes validation, convert it to your accounting format
Created (UTC) → JournalDate
Amount → Credits
Fee → Debits
Created (UTC) → Date
Amount (Gross) → Amount (Row 1)
Fee → Amount (Row 2)
Help us improve—what stopped you today?
Enter your email to claim your welcome bonus
SpreadsheetBroccoli