# A Bank Statement File Naming Convention for Clients

- Author: AutoBankConvert (https://www.autobankconvert.com)
- Published: 2026-07-18
- Updated: 2026-07-18
- Category: Batch conversion
- Canonical: https://www.autobankconvert.com/blog/bank-statement-file-naming-convention

> A bank statement file naming convention for client folders: client, bank, last four digits and period in one pattern, with examples and rename steps.
A bank statement file naming convention is a fixed pattern that puts the client, the bank, the last four digits of the account and the statement period into every file name. Use one pattern for all clients, write dates year first, and never include a full account number. Then files sort themselves and no client's statements get mixed up.

## What should a statement file name include?

A statement file name should carry four facts: who the client is, which bank issued it, which account it covers and which period it reports. With those four, anyone can tell what a file is without opening it, and a missing month shows up as a gap in the list.

Here is why each part earns its place.

### Client

The client goes first, because most work happens one client at a time and you want a client's files grouped. Use a short, stable name, such as "example-bakery". Pick it once and write it the same way every time. "Example Bakery", "Example Bakery LLC" and "ExampleBakery" are three different names to a sort order and to a search.

### Bank and account

The bank tells you which layout to expect. The last four digits of the account tell you which account, which matters as soon as a client has two accounts at one bank. Without them, two checking accounts at the same bank produce files that look identical. Banks usually print account numbers masked, ending in four digits, so those digits are already on the statement and are enough to tell accounts apart.

### Period

The period is the statement month. Write it as year, then month: 2026-03. A file name that starts a date with the month, such as 03-2026, sorts all Marchs together across years. Year first sorts chronologically in any file list, with no extra work.

For statements whose period does not match a calendar month, say a cycle that runs from the 15th to the 14th, name the file for the month in which the period ends, and use that rule for every client. The rule matters more than which rule you choose. If a bank changes its cycle, the files still follow your convention.

### Smaller choices

- **Separators:** pick hyphens or underscores and use them everywhere. Spaces work on most systems but break in some URLs and scripts.
- **Case:** lower case avoids two names that differ only by capitals.
- **Characters:** skip slashes and colons, which file systems treat as path characters, and ampersands, which scripts and URLs can misread.
- **Extension:** keep .pdf, because the name should describe the content, not the format.

## Naming pattern examples for client statement files

A workable pattern is client, bank, last four digits, then period, joined by underscores, with hyphens inside each part: client_bank_last4_yyyy-mm.pdf. The table below shows example names against weaker ones. All names and numbers are made up for illustration.

| Good name | Bad name | Why the bad one fails |
| --- | --- | --- |
| example-bakery_first-national_4417_2026-03.pdf | statement.pdf | Says nothing about client, bank, account or month; downloads from a bank often arrive like this |
| example-bakery_first-national_9082_2026-03.pdf | Example Bakery savings March.pdf | No year, no account digits, spaces and capitals, so it sorts away from its neighbours |
| harbor-plumbing_city-credit-union_1130_2026-02.pdf | Feb statement (2).pdf | A copy suffix from a duplicate download; no client |
| harbor-plumbing_city-credit-union_1130_2025-12.pdf | 12-2025 harbor.pdf | Month first, so December sorts above March from a later year |
| example-bakery_first-national_4417_2026-01_2026-12.pdf | all of last year final.pdf | A twelve-month download that needs [splitting by month](/blog/split-bank-statement-pdf-by-month) before it can be named for one period |
| example-bakery_first-national_4417_2026-03.pdf | 000123454417_March.pdf | Embeds the full account number |

The fifth row shows a convention for files that cover a range: put the start and end period at the end. It is a holding name. Split the file and rename each piece, so every final file covers one account and one month.

Some practices add a final tag for the file's status, such as "_converted" or "_review". It can work, but it also changes the name each time the status changes, and the original file then has two names. A simpler route is to keep names fixed and track status somewhere else, such as a checklist or the converter's own run list.

## Which folder structure suits named statement files?

A suitable folder structure puts the client at the top, then the year, then optionally the account, with the file name repeating the key facts so a file stays identifiable if it is moved out of its folder. Folders organize browsing. File names keep each file identifiable after it leaves its folder.

A structure that holds up for a practice:

```
clients/
  example-bakery/
    statements/
      2026/
        example-bakery_first-national_4417_2026-01.pdf
        example-bakery_first-national_4417_2026-02.pdf
        example-bakery_first-national_9082_2026-01.pdf
```

Three decisions matter here.

1. **Client first.** Everything for a client lives in one place, which also makes it simple to archive a client who leaves. For how to keep each client's records fully apart, see [keeping the books of multiple clients separate](/blog/bookkeeping-for-multiple-clients#how-do-you-keep-multiple-clients-books-separate).
2. **Year as a folder.** Twelve months per account per year already produces many files. A year folder keeps each directory short enough to scan.
3. **No account folder unless the client has many.** With two or three accounts, the last four digits in the name are enough, and sorting groups each account's months together when the digits come before the date. With six or more accounts, an account folder is easier to read.

Add an "incoming" folder per client for files exactly as they arrive. You rename and move them into the year folder. That way a mistake in renaming never destroys the original.

This structure also suits conversion. When you upload a folder of statements to a converter, names that carry the client and account let you confirm each file landed in the right place. [What a bank statement converter for bookkeepers should do with a batch](/blog/bank-statement-converter-for-bookkeepers) lists the checks to expect. In AutoBankConvert, files are matched to the client when you upload or forward them, and a clear name makes it easy to see for yourself that the match is right.

## Renaming a backlog of badly named statement files

Renaming a backlog works best as a one-time pass in a fixed order: sort out which client each file belongs to, read the account digits and period from the first page of each file, then apply the pattern. Doing it client by client avoids moving a file into the wrong folder.

A step list that keeps the work short:

1. **Copy everything into an "incoming" folder.** Leave the originals alone until the end.
2. **Group by client.** Open files you cannot identify from the name. The account holder is on the first page.
3. **Read three facts from the first page of each file:** bank, last four digits, and the statement period. Do not trust the name the client or the bank gave the file, and do not trust the file's modified date, which often shows when it was downloaded.
4. **Record the facts in a sheet** with the old name, bank, last four, period and the new name. A spreadsheet formula can build the new name from the other columns, which removes typing mistakes.
5. **Rename in one pass** and sort the folder. The list should show an unbroken run of months for every account.
6. **Look for gaps and duplicates.** A missing month is a statement to ask the client for. Two files with the same new name are either a duplicate download or two different statements that need a closer look.
7. **Move the files into the year folders** and archive the incoming copies.

A file that holds several months, or several accounts, should not be renamed until it is split. See [how to split a bank statement PDF by month](/blog/split-bank-statement-pdf-by-month) before you give it a final name.

The gap check in step 6 is the useful part of the exercise. A renamed backlog turns "I think we have everything" into a list you can read against the twelve months of the year.

## File names that leak full account numbers

A file name that holds a full account number exposes that number everywhere the name appears: shared folders, email subject lines, upload logs, backup listings and browser history. Last four digits are enough to tell accounts apart, so a file name never needs more.

The problem can start with the bank's own download, if the bank puts the full account number in the file name. Check what a bank's export gives you the first time you pull one for a client. Rename those files as part of the intake step, before they are shared or uploaded.

Check three places for leaks:

- **File names** that came straight from a bank download.
- **Folder names**, where people sometimes put the account number to find the right folder.
- **Your tracking sheet**, if it stores full numbers in the same columns as names. Store last four digits only.

If full numbers already appear in a backlog, a bulk rename from your tracking sheet fixes the names in one pass. Fixing the name does not remove the number from the statement itself, which still contains whatever the bank printed, so store the files wherever your practice keeps client records.

Ask clients who send files by email to use the bank's download rather than a photo, then rename on receipt. A short request template saves you the same fix every month. The same rule keeps working when the file count grows, which is what a convention is for. If you want to see how a monthly batch moves from named files to categorized, export-ready output, [AutoBankConvert](/) shows the whole path.