An unsupported bank statement is a file a converter cannot read with enough confidence to trust the numbers, so it flags the file instead of exporting a guess. Common causes are password locks, image-only pages, odd layouts and damaged files. Most are fixed by downloading a fresh copy from the bank.
What makes a bank statement unsupported?
A statement becomes unsupported when the converter cannot read its transactions reliably, or cannot prove the result is right. The file may be locked, blurry, cut off or laid out in a way the reader cannot follow. Unsupported means the tool stopped, not that the statement is wrong.
Two kinds of failure
Flags fall into two groups:
- The file cannot be read at all. It is locked, damaged or empty of readable content. Nothing comes out.
- The file is read, but the result fails a check. Lines come out, but the opening balance plus the transactions does not equal the closing balance, so the result cannot be trusted.
AutoBankConvert's FAQ describes the second kind: if a statement fails its balance check, it is flagged instead of exported. The homepage says it supports most US business and personal checking, savings and credit card statements and that it reads layouts rather than relying on a list of banks. A flag, then, usually points to the file, not to the bank.
The troubleshooting table
The table covers six common reasons a statement is flagged. Find the symptom, then use the fix.
| Cause | What you see | Fix |
|---|---|---|
| Password-locked PDF | The file will not open without a password | Download an unlocked copy, or remove the lock with the password |
| Image-only pages | The text cannot be selected; the page looks like a photo | Download the PDF from the bank's site instead of scanning |
| Phone photo or screenshot | Tilted, cropped or blurry image | Ask the client for the bank's PDF; rescan flat if none exists |
| Missing or cut-off pages | Balances do not connect from page to page | Download the full statement again; check the page count |
| Failed balance check | Lines read, but the totals disagree | Compare against the statement; look for a missed line or a misread digit |
| Damaged or partial file | The file opens with errors or stops partway | Download it again and compare the file size |
What to do first
Open the file yourself. If you can open it, scroll all pages, and select text on one line, you have a good sense of which row of the table applies. If the page looks like a photo, it is image-only. If it asks for a password, it is locked. This takes under a minute and tells you which fix to try.
Password locked statement PDFs
A password locked statement PDF asks for a password before it opens, so a converter cannot read its contents. Some banks lock statements with a password the customer set up, or one built from details such as a date of birth. The fix is to unlock the copy, or download an unlocked one.
Why banks lock statements
Banks send some statements as protected PDFs because email is not a private channel. A locked file stops a stranger who intercepts the message from reading it. This is good practice, and it is the reason you should not ask clients to remove a lock and then email the open file.
Fixing a locked file safely
- Ask the client for the password rule, not for the password in the same message as the file.
- Open the file with the password, then save or print a copy without protection to the client's folder. Most PDF viewers can do this.
- Delete the unlocked copy once the work is done, or keep it only in the client folder under your retention rules.
- Better, ask the client to download an unlocked PDF from their online banking, where the lock is often not applied.
Do not run a locked statement through a random "unlock PDF" website. The file would go to a stranger's server, which defeats the purpose of the lock. See how to upload client statements securely for what to check before any file goes online.
A password you do not have
If the client does not know the password, the bank can usually reissue the statement or tell them how the password is formed. This is the client's task, since the bank will not discuss the account with you.
Image only statement pages and phone photos
An image-only statement page is a picture of text, not text. Scans of paper statements, screenshots and phone photos are all images. Reading them depends on how clear the picture is, so they are the files most likely to be flagged or to fail a balance check.
Why a picture is harder
A PDF that a bank generates holds the exact characters it printed. A picture holds only pixels, and every character has to be recognized from them. A blurred 3 can look like an 8, a faint decimal point can vanish, and a shadow can hide a column. Some converters read scanned pages anyway: AutoBankConvert's homepage says scanned and digital PDFs both work. But a clear scan still beats a poor one, and a failed balance check is the protection against a misread digit.
Phone photos and screenshots
A phone photo adds problems of its own: a tilted page, cropped edges, glare, and the curve of paper held in one hand. A screenshot of online banking usually shows only part of a statement, and it can miss the opening or closing balance. If you must work from a photo, take it flat, in good light, with all four corners visible, one page per image.
The best fix: get the real file
Ask the client to download the PDF from their online banking. Most banks offer this under a statements or documents menu. The download is cleaner than any scan, and it takes the client two minutes. The post on how to collect bank statements from clients covers the request wording, but a short note works: "Please download the PDF statement from your bank's site, not a photo."
If the client has only paper, scan it flat at a reasonable resolution, in black and white or grayscale, and check every page appears. Then check the balance after conversion.
Why flag an unsupported statement instead of guessing?
A converter flags an unsupported statement because a wrong guess is worse than no answer. A guessed number goes into the client's books looking correct, and nobody checks it. A flag tells you which statement needs a person, before a mistake reaches a report.
The cost of a quiet error
Suppose a tool misreads a 1,000.00 deposit as 100.00. The books are now short by 900.00, and the bank reconciliation will not tie. If the tool says nothing, you find out at month end, or worse, at year end, and you hunt through twelve statements for one digit. If the tool flags the file, you find the page the same day.
The balance check is the proof
The balance check is why a flag is trustworthy. Opening balance plus every credit, minus every debit, must equal the closing balance. When it does, the lines add up. When it does not, something was missed or misread. The related post on converter results that fail a balance check shows how to trace the gap.
A flag is a to-do, not a failure
Treat a flag as a work item. It says which client, which month and which file need attention, and it keeps clean statements moving. In an example batch of forty, thirty-eight pass and two wait. That is a better outcome than forty exported files with an unknown error in two of them.
If your tool lets you review flagged files in a queue, clear it before month end, not on the last day.
Unsupported statements a fresh download fixes
Many unsupported statements are fixed by downloading the statement again from the bank. A fresh PDF replaces a damaged file, a scan, a locked copy or a page set with missing pages. Check these first, because they take minutes.
When a fresh download is the answer
- The file is a photo or scan and the bank offers a PDF.
- The file is locked and the bank offers an unlocked version.
- Pages are missing. The bank's full statement has more pages than the file you have.
- The file is damaged. It opens with errors, or a copy sent by email arrived truncated.
- The statement is a combined PDF with several accounts. Download each account separately, or split the file.
How to ask the client
A request that works: "Please log in to your bank, open Statements, and download the PDF for each month from January to March. Send it to our secure link, not by email." Name the months, so nothing is skipped.
When a fresh download does not help
If a fresh, unlocked, text-based PDF still fails, the cause is likely the layout or the content: an unusual format, a statement with pages from several accounts, or a balance that does not reconcile because the bank's own totals include something not listed. Open the PDF, compare the printed totals with the lines, and send the file for review rather than forcing it through.
A few banks also offer a CSV or other data download in addition to the PDF. If the client's bank does, it can be a useful fallback, though a PDF is the document of record.
For the rest, the quickest route is a person looking at the one page that failed. To see how a flagged statement is handled in a monthly batch, look at AutoBankConvert, and keep your own copy of the final files according to your retention periods. Once the statement converts, check the balance, export, and move on to the next client.