# A Pre-Batch Checklist for Bank Statements

- Author: AutoBankConvert (https://www.autobankconvert.com)
- Published: 2026-05-20
- Updated: 2026-05-20
- Category: Batch conversion
- Canonical: https://www.autobankconvert.com/blog/pre-batch-checklist-for-bank-statements

> A pre-batch checklist for bank statements: complete months, readable pages, no locks, names that map to clients and accounts, before any conversion runs.
A pre-batch checklist for bank statements confirms four things before a conversion runs: every account has every month it should, each page is readable, no file is locked or in the wrong format, and each file name maps to one client and one account. Ten minutes on the folder saves an afternoon of reruns.

## What belongs on a pre-batch checklist for bank statements?

A pre-batch checklist covers completeness, readability, file condition and naming, checked in that order. Completeness comes first because a missing month is the problem that costs the most later. Readability and file condition decide whether the run fails, and naming decides how fast you can find a file when something does fail.

The table below is the checklist itself. The failure column gives examples of what each problem looks like in a real folder.

| Check | How to do it | What a failure looks like |
| --- | --- | --- |
| Every account present | Compare the folder with the client's account list | Savings account statement never sent |
| Every month present | List periods per account; look for gaps | February and April, no March |
| Full periods | Opening date of each statement follows the previous closing date | A mid-month download covering the 1st to the 19th |
| All pages present | Page count printed on the statement ("page 4 of 4") matches the file | A 6-page statement saved as 5 pages |
| Readable pages | Open scans and photos at full size | Blurred amounts, cut-off columns, steep angle |
| No locks | Every PDF opens without a password prompt | Bank's emailed statement still protected |
| Right file types | Only statement PDFs in the folder | A spreadsheet, a cover letter, a screenshot |
| No duplicates | Same account and period appears once | "statement.pdf" and "statement (1).pdf" with identical content |
| Names map to clients | Each name carries client, account digits and period | "March.pdf" in a folder shared by three clients |
| Special cases flagged | Note foreign-currency, combined and image-heavy files | A euro account mixed in with US dollar checking |

The last row matters because some statements need different handling in the run. A client with a foreign-currency account, for instance, needs each currency balanced on its own, which the post on [multi currency bank statements in a batch](/blog/multi-currency-bank-statements-in-a-batch) explains.

### Who runs the checklist

The person who gathered the statements should run it, because they know what was asked for and what came back. If statements arrive from several people, appoint one owner per client for the month.

## Are the statement months complete before the batch?

Statement months are complete when every account on the client's list has a statement for every period in the run, and each statement's opening balance equals the previous one's closing balance. Checking dates alone is not enough. A balance chain that breaks between two statements shows a missing month even when the file names look continuous.

Start from the account list, not the folder. A folder only shows what arrived. The account list shows what should have. If a client opened a new account mid-year, add it to the list the month it appears.

### Partial and custom-range statements

Clients sometimes send a download from online banking instead of the bank's monthly statement. These often cover an odd range, such as the first of the month to the day they downloaded it. A partial period converts fine but leaves a gap at the end of the month, and the next statement may then overlap it.

For a new client who needs a long history, the bank's monthly statements are the cleaner source. The guide to [downloading multiple bank statements at once](/blog/download-multiple-bank-statements-at-once) covers getting a year of monthly files without ending up with stray date ranges.

### A quick balance-chain test

For each account, write the closing balance of one statement next to the opening balance of the next. Every pair should match. If January closes at 8,204.11 and the next file in the folder opens at 9,560.40, a statement is missing between them, or the file you think is February is really March.

## Readable pages: the pre-batch scan and photo check

A page is readable when a person can read every amount and date on it at normal zoom without guessing. If you have to squint, the converter will struggle too. Check every scan and photo before the run, and ask for a replacement now rather than after the batch fails.

Digital PDFs downloaded from a bank rarely have this problem. The text is already in the file. Scans and phone photos are where readability fails, and the failures come in a few shapes:

- **Blur.** Usually from a phone held by hand. Digits like 3, 5, 6 and 8 are the first to merge.
- **Angle.** A page photographed from the side squeezes columns together at the far edge.
- **Cropping.** The balance column, often at the right edge, is cut off.
- **Shadows and folds.** A crease through the amount column can hide a decimal point.
- **Low contrast.** Faded thermal or recycled paper scanned too light.

Open the first and last page of each scanned statement at full size. Those are where totals and balances sit, and they are the pages most likely to be photographed carelessly. If both are clear, the middle pages usually are too.

AutoBankConvert reads scanned and digital PDFs in the same run, and every page is read, including scanned ones. A clearer image still means fewer statements held back for review, so the check earns its time.

## Locks, odd file types and stray files before a batch

The batch folder should hold unlocked statement PDFs and nothing else. Password-protected statements, spreadsheets, images, cover letters and email signatures saved as files all cause failures or noise. Remove or fix each one before the run, so every failure in the results points at a real statement problem.

Work through the folder by type:

- **Locked PDFs.** Try opening each file. Any password prompt means the file needs unlocking with the client's password before it goes in.
- **Spreadsheets and CSV files.** Clients sometimes export transactions from online banking as well as sending the PDF. Keep the PDF for the run. A spreadsheet is a separate source with its own date range, and putting both in invites duplicates.
- **Image files.** A phone photo saved as an image rather than a PDF. Combine a statement's photos into one PDF in page order, or ask for the bank's file.
- **Non-statement PDFs.** Notices of fee changes, privacy notices and tax forms that came in the same email. Move them to the client's document folder.
- **Zero-byte or broken files.** A failed download shows as a tiny file that will not open. Download it again.

If the folder must also feed a spreadsheet of all clients' transactions, keep that as a separate step after conversion. The method in [extracting data from multiple PDF files to Excel](/blog/extract-data-from-multiple-pdf-files-to-excel) works from the same cleaned folder.

## Pre-batch file names that map to clients and accounts

A pre-batch file name maps to a client and account when it carries the client's short name, the last four digits of the account and the statement period. A good converter reads the statement itself to sort files, but names let a person find, rerun or replace one file without opening a dozen others.

An example pattern, with invented values:

```
harlow-optometry_checking_5528_2026-06.pdf
harlow-optometry_savings_0913_2026-06.pdf
pinecrest-kennels_card_7740_2026-06.pdf
```

Rename at the moment a file enters the folder, not at the end. A folder of "Statement.pdf", "Statement (2).pdf" and "Statement (3).pdf" is quick to create and slow to untangle, and duplicates hide inside it because their names differ only by a copy number.

Names never need a full account number. The last four digits are enough to tell accounts apart, and leaving the rest out means a file name pasted into an email or a ticket reveals nothing useful.

### Where the folder lives

Keep the batch folder somewhere access is limited to people who work on that client. For a sole practitioner working from a spare room, that also means a locked computer and no family logins on the same account; [running a home based bookkeeping business](/blog/home-based-bookkeeping-business) covers keeping client data separate at home.

## When the pre-batch checklist costs more than it saves

The pre-batch checklist costs more than it saves for a small, familiar run: a client with one or two accounts, digital PDFs downloaded straight from the bank, and a balance chain that has never broken. For that client, the conversion's own balance check catches the rare problem faster than a manual pass would.

Shorten the list in steps rather than dropping it:

1. **Always keep** the account-and-month completeness check. No balance check can tell you a statement was never sent.
2. **Keep** the lock check for any bank known to send protected files.
3. **Drop** the readability check for clients who only send digital PDFs.
4. **Drop** the renaming step if the converter sorts by what is printed on the statement and you never handle the files by hand.

Run the full list for new clients, catch-up work and any month when a client changes banks. Those are the runs where a missing or unreadable file is most likely, and where it costs the most to find later.

When a cleaned folder is ready, the run itself is one upload. [AutoBankConvert](/) takes a folder across banks and months and matches each file to its client.