UsefulBox guide · reconstruct historical months from file exports
How to Reconcile Historical Stripe Transactions for Xero Review
Prepare historical Stripe exports for Xero review when direct feeds begin late, old payout months need reconstruction, or report columns have changed.
Freeze the historical scope first
Historical reconciliation is easiest to corrupt when exports use different date ranges or report versions. Record the exact period, currency, account, report type, and export timestamp before combining files.
Do not assume that created date, available date, payout date, and bank date belong to the same accounting period. Preserve each date when normalizing the ledger.
Normalize changing report columns
Use explicit field mapping rather than hard-coding one Stripe report layout. Map semantic fields such as created date, type, amount, fee, net, currency, transaction ID, payout ID, and available date to the actual columns in each export.
When a historical file lacks an optional field, keep that absence visible. For example, missing payout IDs should trigger date-and-currency grouping and a warning rather than a fabricated identifier.
Preserve an auditable reconstruction
Export the normalized ledger and warnings alongside the summary. The reviewer should be able to see which rows were invalid, duplicated, unmatched, or moved across periods, and which residuals remain unresolved.
This process prepares evidence for review; it does not select account codes, tax codes, exchange rates, or journals.
Build the review pack in your browser
Upload CSV or XLSX exports, confirm the field mappings, and export a normalized ledger, payout bridge, unmatched list, cross-period movements, and warnings.
Build a reconciliation pack