Stripe

Stripe Balance Transactions Export Sample Dataset

Stripe's Balance Transactions export from the Dashboard Reports panel is delivered as a UTF-8 CSV with exact production columns: id, created, currency, amount, fee, net, type, description, source, and reporting_category. This dataset contains 7,500 synthetic balance transaction records spanning charges, refunds, disputes, payouts, and adjustments — mirroring a high-volume SaaS billing environment. The critical Stripe accounting quirk is that all created timestamps are forced to UTC regardless of your dashboard timezone setting, and the amount and fee columns store values in the smallest currency unit (cents for USD). More dangerously, the sign convention inverts depending on type: for charge rows, amount is positive and fee is negative, but for refund and dispute rows, amount becomes negative while fee becomes positive (the fee is returned). Naive SUM aggregation across all transaction types double-counts fee reversals as additional charges. The structural dirty data inventory includes: 1,840 description fields containing unescaped commas that break delimiter-based parsers, 420 rows with embedded CRLF line breaks in multiline dispute descriptions, and missing UTF-8 BOM causing € and £ symbols to render as mojibake. Expected Output: Yields exactly 7,500 valid transactions with accurate net revenue figures. Ideal for: ETL testing, DuckDB demos, Power BI, Excel Power Query, CI pipelines. Load this file into the stripe-formatter tool to correctly net the fee reversals before building your P&L.

This dummy dataset simulates a standard export from Stripe, containing realistic yet fully anonymized records that mirror the structure and common data quality issues found in real production environments. The CSV file includes typical problems such as inconsistent formatting, missing values, duplicate entries, and non-standardized categorical fields.

It is designed to be used as a safe sandbox for testing data cleaning workflows directly in your browser — no uploads, no server round-trips, no third-party data exposure. Whether you are validating a transformation pipeline, benchmarking a cleaning tool, or simply exploring common data quality patterns, this sample provides a representative starting point without risking any sensitive business data.

Data Schema

Column NameData TypeDescription
idstringUnique record identifier
created_attimestampRecord creation date and time
statusstringCurrent status of the record

Recommended Tools

Related Workflows

How to Convert Stripe Payout Reports into QuickBooks Import Format

Stripe's payout CSV has 15+ columns that don't map to QuickBooks' expected schema. This guide shows how to separate gross revenue from processing fees, reformat dates to MM/DD/YYYY, and produce a clean CSV that QuickBooks accepts without manual reconciliation.

Isolate True Net Processing Fees from Stripe Balance Transactions

Stripe's Payouts export only shows the lump-sum deposit hitting your bank account — it tells you nothing about the per-transaction fee composition. To calculate your real effective processing rate, you need the Balance_Transactions.csv file, but this export dumps charges, refunds, adjustments, dispute reversals, and Stripe billing fees into a single flat table with no hierarchy. The Fee column contains negative values for processing fees, but refund-related fee reversals and dispute charges are interspersed without clear grouping, making a simple SUM() wildly inaccurate. This workflow filters the Type column to isolate charge, payment, refund, and dispute rows separately, recalculates the net fee per original transaction by grouping on Source ID, and produces a clean summary showing your true blended rate.

Convert Stripe UTC Export Timestamps to Local Tax Period

Stripe hardcodes all CSV export timestamps to UTC with no option to select your local timezone. For a business operating in US Pacific Time (UTC-8), a customer purchase completed at 5:30 PM PST on March 31st appears as 2024-04-01 01:30:00 in the Created (UTC) column of your Stripe export. This single timestamp shift pushes that revenue into Q2 for tax purposes, creating a discrepancy between your Stripe revenue total and your QuickBooks sales ledger. This SOP detects all timestamp columns (Created (UTC), Available On (UTC)), applies a configurable timezone offset, and rewrites the date in YYYY-MM-DD format aligned to your state's tax jurisdiction.

Sample Datasets