Why Do Bank Statement PDFs Have Merged Cells in Excel? (And How to Fix It)

You converted your bank statement PDF to Excel and opened the file. Instead of clean rows of transactions, you got a mess of merged cells, split rows, and text scattered across random columns. This is not a problem with your file—it is a predictable failure mode of generic PDF-to-Excel conversion, and it has a specific cause.

Why Bank Statement PDFs Produce Merged Cells in Excel

A bank statement PDF is a visual document. The bank designed it to look good on paper or screen, not to be machine-readable. Inside the PDF, the transaction table is stored as a grid of positioned text boxes—each number and word has an exact X and Y coordinate on the page. There is no concept of "rows" or "columns" in the PDF format itself.

When a generic PDF converter reads this file and tries to put it into Excel, it does one of two things. It either copies the visual layout—converting each positioned text box into an Excel cell at roughly the corresponding position on the grid, which produces merged cells and misaligned columns—or it extracts all text in reading order and pastes it into column A, which produces a wall of text that requires manual parsing.

Neither approach understands that the goal is to get one transaction per row with date, description, and amount in separate columns. The converter does not know it is looking at a financial document.

The Three Specific Causes of Merged Cells in Bank Statement Conversions

1. Layout-Based Conversion

Most generic PDF converters use layout analysis: they detect the position of each text element and assign it to an Excel cell at the corresponding grid position. When the bank uses a table with thin borders, the converter may interpret adjacent cells as merged. When text in one column is vertically centered across what should be two rows, the converter creates a merged cell spanning both rows.

2. Multi-Line Transaction Descriptions

Many bank statements have transaction descriptions that wrap to a second line when the merchant name is long. Chase statements frequently have this issue. A generic converter sees two lines of text in the description column and creates two rows in Excel—one with the date and first line of the description, and a second row with just the continuation of the description and no date or amount. The transaction is split across two rows, which breaks every formula that totals by date or category.

3. Scanned Statement OCR Errors

If your bank statement is a scanned image rather than a native PDF, the converter must use OCR to read the text. Generic OCR does not understand table structure—it reads text in reading order and may miss column boundaries entirely, causing multiple columns of data to land in a single Excel column as concatenated text.

How to Fix Merged Cells in a Bank Statement Excel File

If you already have a converted file with merged cells, the fix depends on how severe the problem is.

• For a small number of merged cells: Select all cells, go to Home > Merge & Center dropdown > Unmerge Cells. This unmerges everything but leaves blank cells where the merge used to be. You will need to fill in the blank cells manually.
• For split transaction rows: Identify rows where the description is split. Copy the second line of the description into the first row's description cell, then delete the extra row. For large statements, this is impractical to do manually.
• For wholesale conversion failures: Re-convert using a bank-statement-specific tool. If the generic converter produced unusable output, no amount of manual cleanup is more efficient than starting over with the right tool.

How to Avoid Merged Cells Entirely

The only reliable way to avoid merged cells when converting a bank statement is to use a converter that understands financial document structure. A bank statement converter does not treat the PDF as a generic document to be laid out in a grid. It understands that a bank statement contains a header section with account information, a transaction table where each row is one transaction, and a summary section with totals and balances.

It identifies multi-line descriptions and merges them back into a single row. It handles separate debit and credit columns by combining them into a signed amount. It correctly reads date formats even when the year is missing. The output is one row per transaction, every time.

Bank-Specific Merged Cell Issues

• Chase: Multi-line descriptions are the main cause of split rows. Deposits listed in a separate section from withdrawals also confuses layout-based converters.
• Wells Fargo: Running balance column is sometimes interpreted as an amount column, creating an extra column or merged cell in the amount area.
• Bank of America: Section headers (Deposits and Other Credits, Withdrawals and Other Debits) are sometimes imported as data rows.
• Barclays: Transaction codes (BGC, FPO, TFR, DD) at the start of descriptions are sometimes treated as separate columns by layout converters.
• Citibank: Category groupings (Purchases, Payments, Credits) create sub-header rows that generic converters import as transactions.

Frequently Asked Questions

Why does Excel show #REF! errors after I unmerge cells?

Formulas that reference merged cells may break when you unmerge them. The cell reference no longer points to a single cell. Fix by selecting the formula cell and updating the reference to point to the correct unmerged cell.

Can I automatically unmerge all cells and fill in values?

Yes, with a macro. Select the merged range, run: Selection.UnMerge, then use Ctrl+G > Special > Blanks to select blank cells, type = and the up arrow to reference the cell above, and press Ctrl+Enter to fill all blank cells. This works for simple merged cells but does not fix split transaction rows.

Does converting bank statements to CSV avoid the merged cell problem?

Yes. CSV is plain text and cannot contain merged cells. If you export to CSV from a bank statement converter, the output is always one value per field. The underlying data quality issue (split rows, wrong column mapping) still applies, but merged cells specifically are a display artifact that only appears in Excel format.