Naming exported files from a batch run should follow one fixed pattern: client, account's last four digits, statement period and the target books, in that order. A name built this way tells whoever imports the file exactly which company and which bank account it belongs to, so the import lands in the right ledger without anyone opening it first.
What belongs in the name of a batch export file?
A batch export file name needs four facts: the client, the account, the period and the destination. The first three say what the file contains. The fourth says where it goes. Leave out any of them and someone has to open the file, or guess, before importing it.
Each part has a job:
- Client. A short, stable name, written the same way in every file. It should match the name of the company file in the accounting system, so the person importing can find it at a glance.
- Account. The last four digits of the bank or card account. Two accounts at one bank otherwise produce identical names.
- Period. The statement month, year first, such as 2026-09. Year-first dates sort in order in any file list.
- Destination. The target system, such as qbo for QuickBooks Online or xero for Xero, and the entity if the client has more than one.
The order matters as much as the parts. Client first groups each client's files together. Account before period keeps each account's months in a run. Destination last makes it the final thing a reader sees before importing.
Export names follow the same logic as the names you give incoming statement PDFs, but they answer a different question. An incoming name says what arrived. An export name says where it is going.
Export file names from one example batch run
The table below shows export names from one example batch. The clients, accounts and periods are made up for illustration. Each row is one file, for one account, for one month, bound for one set of books.
| Export file name | Client books | Account in those books |
|---|---|---|
| example-bakery_4417_2026-09_qbo.csv | Example Bakery LLC, QuickBooks Online | Checking 4417 |
| example-bakery_8820_2026-09_qbo.csv | Example Bakery LLC, QuickBooks Online | Card 8820 |
| harbor-dental_1130_2026-09_xero.csv | Example Harbor Dental, Xero | Checking 1130 |
| harbor-holdings_2205_2026-09_xero.csv | Example Harbor Holdings, Xero | Checking 2205 |
| pine-landscaping_7702_2026-09_qbo.csv | Example Pine Landscaping, QuickBooks Online | Checking 7702 |
| tile-works_5519_2026-08_qbo_v2.csv | Example Tile Works, QuickBooks Online | Checking 5519, re-export |
Two rows deserve a note. Harbor Dental and Harbor Holdings are separate entities that share a name and a bank. Spelling out the entity in the client part keeps their files apart. The Tile Works row is a second export for August, after a fix, which the next section covers. The file extension in these examples is only an illustration; use whatever file type your export produces.
Some statements carry check images on their pages, which can add lines or change how a statement converts. If a batch includes them, see handling bank statements with check images in a batch before exporting, so the exported lines match the statement.
Should a re-exported file get a new name?
A re-exported file should get a new name, with a version tag such as v2 at the end. The tag shows that an earlier export exists and that this one replaces it. Without it, two files with the same name sit in different folders, and nobody can tell which one went into the books.
Re-exports happen for ordinary reasons. A failed statement was fixed and reconverted. A category was corrected after review. A client sent a missing page. Each one changes the file, so the name should change too.
Three rules keep versions under control:
- Never overwrite an export that has been imported. Keep it, so you can see what went into the books.
- Record which version was imported. A tracker row per client and month with the file name answers this in seconds. A statement conversion tracker gives a layout you can reuse.
- Import the new version only after removing or adjusting the old lines. Otherwise the books hold both, and every transaction appears twice.
The version tag is the simplest audit trail a practice can keep, and it costs nothing to add.
Export names that send an import to the wrong ledger
Most wrong-ledger imports trace back to a vague file name. A file called "export.csv" or "September.csv" carries no client, so the person importing picks a company from memory. With many clients open in one day, memory fails. A name that states the client and destination removes the guess entirely.
Naming habits that cause trouble:
- Batch-level names. "batch_2026-09.csv" for a file that holds one client's data looks like a combined file and invites the wrong import.
- Client names that drift. "Bakery", "Example Bakery" and "example-bakery-llc" for the same client make search unreliable.
- No entity. A client with two companies and one name produces two files that look the same.
- No account digits. Checking and savings at the same bank export with identical names.
Clear export names also matter when a practice changes hands. A buyer reviewing past work needs to see which file went into which books without asking the seller. Buying a bookkeeping practice lists the records worth checking, and a clean export history is one of them.
AutoBankConvert exports QuickBooks or Xero files per client or for the whole batch, and a consistent naming pattern makes each per-client file easy to place. What a bank statement converter for bookkeepers should do covers the rest of the export step. To try it on next month's batch, request a spot.