Workflows & security · Convert

How to Combine Multiple Bank Statements into One Spreadsheet

Normalize each statement independently, verify it, then append transactions with account and source keys.

Create a canonical transaction schema

Choose stable columns before combining anything: institution, account label, masked account ID, account type, currency, statement start, statement end, transaction date, posting date, raw description, debit, credit, normalized balance effect, running balance, source file, source page, and source row.

Map each statement into that structure without erasing source-specific evidence. A field absent from a statement should remain blank, not zero. Convert dates and amounts to real typed values, and document the sign convention for deposit assets and credit-card liabilities.

Verify before appending

Reconcile each statement independently to its opening and closing balances or printed totals. This localizes extraction errors. If twenty statements are combined first, one missing row becomes a portfolio-wide difference that is much harder to trace.

Check continuity between consecutive statements for the same account. The prior closing balance should normally agree with the next opening balance, and periods should not overlap unless the bank intentionally issued corrected statements. Keep corrected versions explicitly labeled instead of mixing both.

Append, deduplicate, and preserve account boundaries

Power Query can combine similarly structured files from a folder, but automated append is safe only after schemas and types match. Create a deterministic row key from source identity and position; do not deduplicate solely by date, description, and amount because legitimate repeated purchases exist.

A combined transaction ledger can be sorted across accounts for analysis. Running balances cannot. They belong to one account and its original order, so keep account-level sequences and never calculate a single running balance across checking, savings, and credit cards.

  • Validate each statement first.
  • Keep account and statement identifiers on every row.
  • Detect overlapping periods and corrected statements.
  • Deduplicate by source lineage, not transaction resemblance alone.
  • Reconcile account-level totals after the append.

Frequently asked questions

Can I use Power Query to combine monthly files?+

Yes. Power Query can append files from a folder when they share a stable schema. Validate types, signs, and source columns before making the refresh automatic.

How do I find duplicate bank transactions?+

Use source file, page, and row lineage first. Similar date, description, and amount combinations should be review candidates, not automatic deletions, because recurring and same-day purchases can be legitimate.

Sources and further reading

We prioritize regulators, public agencies, and first-party product documentation. Sources support the general guidance above; StatementMint’s workflow recommendations are our own.

  1. Import data from data sources with Power QueryMicrosoft Support

Educational information only—not financial, accounting, tax, or legal advice. Institution terms and your facts control.