You uploaded the file. You clicked convert. And now you are staring at one of the following: a completely blank output, a CSV where every transaction has landed in a single column, rows that are missing or duplicated, amounts that look like they were put through a blender, or an error message that tells you nothing useful.
Bank statement conversion fails in predictable ways. The causes are almost always one of a handful of specific problems, each with a specific fix. This guide walks through every common failure mode, explains why it happens, and tells you exactly what to do about it.
Problem 1: The Output Is Blank or Nearly Empty
You convert a ten-page statement and get back a CSV with zero rows, or just the header row and nothing else.
Why it happens: The most common cause is that the PDF is an image scan rather than a text-based document. The converter parsed the file successfully but found no extractable text — because there is no text, only pixels arranged to look like text.
How to diagnose it: Open the original PDF and try to click and drag to highlight a single word in the transaction table. If the text highlights and you can select individual characters, the file is text-based. If nothing highlights — or the entire page selects as a single block — the file is a scanned image.
The fix: Use a converter with built-in OCR capability. OCR — optical character recognition — reads the image and converts the visual representation of text into actual extractable characters. Not all converters include OCR as a standard feature. Some require a separate add-on or a higher-tier plan. BankConvert includes OCR as part of its standard processing pipeline — scanned statements are detected automatically and routed through OCR without any additional steps on your end.
If the file is genuinely text-based and you are still getting blank output, the issue may be with the PDF's internal structure — see Problem 6 below.
Problem 2: All Transactions Are in One Column
The CSV opens in Excel and every transaction row is crammed into a single cell in column A, with all the data — date, description, amount — running together as one unbroken string.
Why it happens: The converter failed to identify the column boundaries in the original PDF. This typically happens with PDFs where the transaction table uses unusual spacing, overlapping text elements, or non-standard column separators that confuse the parser.
It also happens when a general-purpose PDF extractor is used instead of a financial-statement-specific converter. General tools extract text linearly — reading across the page without understanding that different segments belong in different columns.
How to diagnose it: Open the original PDF and look at the transaction table. Are the columns clearly defined with visible lines or consistent spacing? Or is the layout unusual — very narrow columns, merged cells, or descriptions that wrap across what looks like a single wide column?
The fix: Switch to a converter purpose-built for bank statement formats. A financial-specific converter understands that a date belongs in a date column, an amount belongs in an amount column, and a description occupies the space between them — even when the visual boundaries are not perfectly regular. If you are already using a financial converter and still seeing this problem, the statement format may be one the tool has not been trained on. Contact support with a sample page to confirm.
Problem 3: Rows Are Missing From the Output
You convert a statement that you know contains 200 transactions, but the output CSV has only 160 rows. Some transactions have simply disappeared.
Why it happens: Missing rows typically have one of three causes. First, multi-line transaction descriptions — where a single transaction spans two or three lines in the PDF — can be parsed as multiple separate rows or, more commonly, as a single row where subsequent lines are dropped. Second, page breaks can cause the first or last row on a page to be lost if the converter does not handle cross-page transactions correctly. Third, transactions in a section of the PDF that uses a different layout — such as a fee summary section at the end of the statement — may be excluded if the converter only processes the main transaction table.
How to diagnose it: Count the rows in the original PDF manually for one page and compare against the converted output for the same page. If a specific page is losing rows, the problem is isolated and easier to address. If rows are missing evenly throughout, the multi-line description issue is more likely.
The fix: For multi-line descriptions, look for a converter setting that controls how line breaks within a single transaction are handled. The correct behavior is to join continuation lines into a single description field rather than treating each line as a separate transaction. For page break issues, ensure your converter is designed to handle multi-page documents as a single continuous stream rather than processing each page independently. For missing fee sections, check whether the converter has an option to include all table types from the statement, not just the primary transaction table.
Problem 4: The File Is Password Protected and Won't Open
The converter returns an error immediately upon upload, or the conversion completes but produces empty output, and the original PDF requires a password to open.
Why it happens: Banks apply password protection to statements as a security measure, particularly for business accounts and for statements delivered via secure messaging systems. If you have not entered the password before uploading, or if the converter does not support password-protected files, the tool cannot access the content.
How to diagnose it: Try opening the PDF in any PDF viewer. If you are prompted for a password before the document opens, the file is encrypted. If the document opens without a password prompt, the issue is something else.
The fix: Find the password. For bank-delivered statements, the password is typically your account number, date of birth, or a combination of personal details — check the email that delivered the statement or contact your bank. Once you have the password, use a converter that accepts it as part of the upload process. BankConvert prompts for the document password when a protected file is detected and processes the content without storing the password after the session ends. You can find more detail on handling this scenario in the guide on how to convert password protected bank statements.
Problem 5: Amounts Are Wrong, Garbled, or Formatted as Text
The conversion completes and the rows look correct, but the amount column contains values like "1.234,56" instead of "1234.56", or entries like "$1,200.00" that Excel treats as text rather than numbers, or — most dangerously — amounts that are numerically wrong due to misread digits.
Why it happens: Currency and locale formatting issues are among the most common sources of subtle errors in bank statement conversion. European bank statements frequently use a period as a thousand separator and a comma as a decimal marker — the opposite of US convention. A converter that does not handle locale-aware number parsing will produce numerically incorrect amounts without any visible error.
Currency symbols and thousand separators in the amount column cause Excel and accounting software to interpret values as text rather than numbers, which means they are excluded from calculations and summations without any obvious warning.
OCR misreads are a separate cause — on scanned statements, the digit 1 can be read as 7, a 0 as a 6, or a decimal point missed entirely. These errors are rare with high-quality OCR but not impossible.
How to diagnose it: Sort the amount column in Excel. Text values will sort differently from numeric values and will cluster at the top or bottom of the sort. For locale errors, look for amounts where the comma and period positions seem inverted relative to what you would expect.
The fix: For currency symbols and separators, clean the amount column before importing. In Excel, use Find and Replace to remove $ signs and commas used as thousand separators, then reformat the column as Number. For locale issues, use a converter that allows you to specify the source locale — or one that detects it automatically from the bank format. For OCR errors, spot-check five to ten amounts against the original statement before using the data downstream.
Problem 6: The PDF Is Corrupted or Partially Damaged
The conversion fails with an error, or completes but produces output that is obviously wrong — missing entire sections, showing garbled characters, or containing data that does not correspond to any transaction in the original.
Why it happens: PDFs can become corrupted during download, email transmission, or file transfer. Partial downloads produce files that open visually but have incomplete internal structure. Some banks produce PDFs with non-standard internal formatting that certain parsers cannot handle.
How to diagnose it: Open the PDF in two different PDF viewers — Adobe Acrobat and your browser's built-in viewer, for example. If the document renders differently in the two viewers, or shows visual artifacts in one that are absent in the other, the file has structural issues. If the file opens normally in both viewers but still fails to convert, the issue is likely with the converter's parser rather than the file itself.
The fix: Re-download the statement from your bank's portal rather than using the copy that was emailed or transferred. Fresh downloads are less likely to be corrupted. If re-downloading is not possible, try printing the PDF to a new PDF using your operating system's print-to-PDF feature — this regenerates the file structure and often resolves non-standard formatting issues. The resulting file is technically a new PDF that may convert more cleanly than the original.
Problem 7: Multi-Page Statements Produce Inconsistent Column Headers
Each page of a multi-page statement converts correctly on its own, but when combined, the column headers repeat mid-file, columns shift position between pages, or the running balance resets unexpectedly.
Why it happens: Some bank statement formats repeat the column header row at the top of every page — a feature that looks helpful when reading but creates duplicate header rows in a combined CSV output. Others change their column layout slightly between the first page (which may include an account summary) and subsequent transaction pages.
The fix: Look for a converter setting that handles repeated headers — the correct behavior is to include the header row once and treat all subsequent identical rows as data to be excluded. For column shift issues, a converter trained on your specific bank's statement format will handle the variation automatically. If you are working with a converter that does not, the fix is to process each page individually and manually align the columns before combining — time-consuming but reliable.
Problem 8: Transactions From the Wrong Date Range Appear
The converted output includes transactions from outside the statement period, or the dates themselves are wrong — showing the current year when the statement is from two years ago.
Why it happens: Date parsing errors occur when the converter misreads the date format and applies the wrong year or swaps day and month. A statement dated 03/04/2023 could be parsed as March 4th or April 3rd depending on whether the converter assumes MM/DD or DD/MM convention — and both are valid interpretations without locale context.
The fix: After conversion, sort the output by date and check the first and last rows. If the date range does not match the statement period, the converter is applying the wrong date convention. Switch to a converter that detects the bank's locale and date format automatically, or specify the date format explicitly in the converter's settings. For BankConvert's accuracy and reliability approach to date parsing across international formats, the dedicated guide covers the technical detail.
A Quick Diagnostic Checklist
Before spending time troubleshooting, run through this checklist to identify the most likely cause quickly.
Can you select text in the PDF? If no, it is a scanned image — use OCR. Does the PDF require a password to open? If yes, locate the password before uploading. Does the amount column contain currency symbols or commas? If yes, clean before importing. Are row counts lower than expected? Check for multi-line description handling. Are dates outside the expected range? Check date format convention settings. Does the file open differently in two PDF viewers? Re-download or regenerate the file.
Most conversion problems are solved by one of these six checks. The tools to fix them exist — the key is knowing which problem you are actually dealing with before you start troubleshooting.
When to Switch Tools
If you are consistently running into conversion problems with your current tool — particularly around scanned statements, international formats, or password-protected files — the issue may not be your files. It may be the tool's limitations.
A converter that handles edge cases well does not require you to pre-process files, clean outputs manually, or work around format-specific bugs. It handles scanned PDFs through built-in OCR, accepts password-protected files gracefully, produces clean numeric amounts without symbols, and combines multi-page statements without repeating headers.
BankConvert is built to handle these cases as standard rather than as exceptions. If your current workflow involves regular manual cleanup after conversion, it is worth running your most problematic statement through a different tool and comparing the output.
A five-minute test on your hardest file tells you more than any feature list.