How to Combine Multiple Bank Statements into One Spreadsheet

Combine transaction rows, not PDF pages

To combine bank statements into one spreadsheet, obtain an Excel or CSV export for each statement, check its rows, add account and source columns, and append the tables. Review overlapping periods before excluding duplicates. Keep the original exports unchanged so you can trace a correction back to its source.

Use a bank-native transaction export if it covers the account and period you need. For PDF sources, StatementMint produces Date, Description, and signed Amount columns. Convert each statement and confirm that the processed pages cover the whole statement you intend to combine. An allowance-limited preview is not a complete monthly export.

The combining and overlap-review steps below happen in your spreadsheet. Do not assume that downloading several StatementMint exports also merges them, adds account metadata, or removes duplicates for you.

Add a small set of source columns

Create a working copy with the columns below. Assign a unique account alias; the last four digits alone may collide across banks. Use an opaque alias such as Operating-A rather than putting a full account number into the combined file.

Assign a source ID to each export version and a fixed row number before sorting. Paste generated row numbers as values so sorting cannot change them. These are your bookkeeping columns, not fields that StatementMint adds to its standard export. Record the corresponding filename and statement period in a separate source register.

Review each file and map its coverage

Before appending, record each file's account, statement dates, row count, positive total, and negative total. Compare dates, descriptions, and amounts with the source PDF. Check the transaction sections and page boundaries as well as the net total: an omitted deposit and withdrawal of equal value would leave the net unchanged.

In the source register, compare date coverage for the same account. A monthly statement plus an activity download can overlap even if the filenames differ. A corrected statement may replace an earlier version. Establish which document is authoritative for that period and retain a record of the superseded version instead of adding both sets of rows.

Use a consistent date basis. A transaction date in one export and a posting date in another can describe the same event on different days. Resolve that difference against the source before treating a failed key match as evidence of a new transaction.

Append the reviewed tables in Excel

For a few files, copy the data rows into one master table with one header row. Match columns before pasting, exclude subtotals and repeated headers, and compare the resulting row count with the sum of the inputs.

For a repeatable workflow, load the reviewed tables into Power Query. In the editor, choose Home > Append Queries > Append Queries as New, select the tables, and confirm. Microsoft documents that append stacks rows and matches column names rather than their positions. A mismatched header can create an extra column with null values, so inspect the resulting schema.

In Power Query terminology, Append stacks transaction rows; Merge joins tables using matching columns. Use Append for this task. Keep source IDs and fixed row positions in the input tables, and check date and numeric types before loading the result into Excel. Availability and menu details depend on your Excel version.

Use two keys, with different jobs

For the working columns above, enter =E2&"|"&F2 in G2 and fill down. This source key identifies one row in one export version. A repeated source key can reveal that you appended the same input twice. If you renamed or regenerated a file, compare the source register too; a new source ID does not prove a new transaction.

For a two-decimal account, enter =A2&"|"&TEXT(B2,"yyyy-mm-dd")&"|"&C2&"|"&TEXT(D2,"0.00") in H2 and fill down. Use real Excel dates and numeric amounts first. Treat equal review keys as candidates for inspection, not permission to delete. Do not combine different currencies in a single comparison group or net total.

Sort by the review key to place equal candidates together. Keep the original description intact: stripping merchant numbers or reference text may collapse distinct purchases. A differing description can also hide real overlap, so inspect the overlapping date window even when keys differ. The delimiter can occur in source text; this readable helper key is not a guaranteed unique identifier.

Resolve overlap without deleting legitimate repeats

This synthetic example shows two real $45 purchases and one copied representation of the first purchase. All three share the same date, description, and amount. Assume you checked the printed references and source positions and confirmed that B-activity row 3 repeats A-Aug row 17.

Keep both purchases from A-Aug and exclude only the confirmed overlapping copy from the combined output. Retain that excluded row in a review sheet with the matching source key and your reason. Without evidence that distinguishes the purchases, leave the candidate unresolved instead of selecting a row at random.

Microsoft warns that Remove Duplicates deletes data and recommends checking or copying the original range first. For statement data, use a reviewed include/exclude column in your working file so you can explain each exclusion and reverse it if needed.

Check the output and save the merge checklist

For the example, three input rows minus one confirmed overlap gives two output rows. The signed input total is -135.00; subtracting the excluded signed amount of -45.00 gives -90.00. Compare positive and negative totals as separate controls, then investigate unexplained count or amount changes.

Perform those checks per account and currency. A transfer can appear once in each of two accounts; keep both account records even if a combined cash-flow report later treats the transfer differently. Avoid a single running balance across checking accounts and credit cards. Sort the whole output table so dates remain attached to their descriptions and amounts.

Download the plain-text checklist for your next monthly merge. It includes a source register, overlap decision log, and count and signed-total controls. To prepare your inputs, convert each complete statement to Excel or CSV, review it against the PDF, and then follow this workflow. Check the current plan allowance before processing a multi-statement backlog.

Download the bank statement merge checklist

Frequently asked questions