# Export Converted Statements per Client After a Batch

- Author: AutoBankConvert (https://www.autobankconvert.com)
- Published: 2026-07-21
- Updated: 2026-07-21
- Category: Batch conversion
- Canonical: https://www.autobankconvert.com/blog/export-converted-statements-per-client

> How to export converted statements per client after a batch run: one file per client and account, named for the books it goes into and checked on arrival.
To export converted statements per client after a batch, produce one file for each client and account, in the format that client's books use, and name it for the company file it goes into. Check each export's period, line count and closing balance against the statement before you import it, then record which files went where.

## Why export converted statements per client and not as one batch file?

Converted statements should leave a batch as separate files per client because accounting software imports into one company at a time. A combined file that holds eight clients cannot go into any of them as it stands. Splitting it by hand afterwards brings back the copy-and-paste errors that conversion was supposed to remove.

The risk is not only wasted time. A mixed file invites a specific, expensive mistake: one client's transactions posted into another client's books. It happens when a filter is set wrong, or a few rows sit below the visible part of a spreadsheet. Nothing warns you at import. The error surfaces weeks later as a reconciliation that will not tie, or a client asking why a stranger's rent payment is in their ledger.

A combined batch file still has uses. It is handy for a quick look across every client in a run, for spotting odd amounts, or for keeping a month's output together in an archive. It just should not be the file you import.

AutoBankConvert keeps each client's accounts, rules and history in a separate workspace, and lets you download QuickBooks or Xero files per client or the whole batch at once. The per-client download is the one meant for posting.

## One export file per account inside a client

Inside a single client, give each bank or card account its own export file. Accounting systems usually import bank lines into one bank or card account at a time, so a file mixing checking and a credit card must be split first. One account per file also keeps each file's totals checkable against one statement.

This matters most for clients with several accounts at one bank, or for clients whose statements arrive bundled. A business may receive one PDF that shows checking and savings together, or send a folder where the card statement and the checking statement look nearly identical. When a batch holds both kinds, [checking and credit card statements in one batch](/blog/checking-and-credit-card-statements-in-one-batch) explains how to keep their signs and accounts apart before export.

Card accounts deserve a second look at this step. On a card statement, a purchase increases what the client owes, while on a checking statement a payment out reduces cash. When both sit in one file, it is easy to import card lines with the sign reversed. Separate files make the sign of each account's lines obvious when you open them.

The example below shows one batch broken into per-client, per-account export files. Every name and figure is made up for illustration.

| Client | Account | Period | Lines | Closing balance | Export file |
| --- | --- | --- | --- | --- | --- |
| Example Bakery LLC | Checking 4417 | 2026-09 | 212 | 18,402.11 | example-bakery_4417_2026-09_qbo |
| Example Bakery LLC | Card 8820 | 2026-09 | 64 | 3,118.70 owed | example-bakery_8820_2026-09_qbo |
| Example Harbor Dental | Checking 1130 | 2026-09 | 147 | 52,960.00 | harbor-dental_1130_2026-09_xero |
| Example Harbor Dental | Savings 1131 | 2026-09 | 3 | 120,004.55 | harbor-dental_1131_2026-09_xero |
| Example Pine Landscaping | Checking 7702 | 2026-09 | 98 | 6,240.38 | pine-landscaping_7702_2026-09_qbo |

Five files come from three clients. Each file has one job and one destination, and its totals can be checked against exactly one statement.

## Matching each client export to the books it goes into

Each client export should match the system and the company file that client actually uses. A practice that serves both QuickBooks and Xero clients needs the right format per client, chosen once and kept on record. The export name should then say where the file is going, so the person importing it does not have to guess.

Three facts decide each client's export:

1. **The accounting system.** QuickBooks or Xero, or something else you handle separately.
2. **The company file or organisation.** Some clients run more than one entity, and each entity has its own books.
3. **The target account in those books.** The checking account, the card, the savings account.

Record these three facts once per client and per account, in your client list or tracker. Then the export step becomes a lookup rather than a decision. When a new account appears, add it to the record before you export anything for it.

Clients with more than one entity need care here. A holding company and its operating company may bank at the same place, with similar account names. Their statements convert into separate workspaces only if you set them up that way. If they share a workspace, their exports will share a file, and the one-client-per-file rule breaks before it starts.

## What should you check in a client export before import?

Check four things in every client export before import: the period, the line count, the closing balance and the account it belongs to. Each should agree with the original statement. If all four agree, the file is safe to bring into the books. If one does not, stop and find out why before anything is posted.

How to run each check quickly:

- **Period.** The first and last dates in the file should fall inside the statement period. A line dated outside it suggests a year was read wrong or two statements were combined.
- **Line count.** Count the transaction lines on the statement, or use its printed count if it has one, and compare. A mismatch of one or two is the classic sign of a dropped or doubled line.
- **Closing balance.** Opening balance plus the file's credits, minus its debits, should equal the statement's closing balance.
- **Account.** The last four digits in the file name should match the statement header.

Overlaps between periods are worth a separate look. Some banks cut statements mid-month, some clients send a duplicate covering a few overlapping days, and a re-downloaded file may repeat lines from the prior month. If two exports for the same account share dates, the import will double those lines. [Overlapping statement periods in a batch](/blog/overlapping-statement-periods-in-a-batch) explains how to spot and trim the overlap before it reaches the books.

Bundled files cause a related problem. A client who downloads twelve months as one PDF produces one long export unless it is split. That file is hard to check against a single statement, and it may cover a period you have already posted. [Splitting a bank statement PDF by month](/blog/split-bank-statement-pdf-by-month) shows how to break it into monthly files first, so each export matches one statement again.

## Client exports that reach into a closed period

A client export can reach into a period that is already closed, for example when a late statement arrives or a catch-up batch starts too early. Importing it would change figures that have been reported, reconciled or filed. Trim the export to the open period, or hold it until someone decides how to handle the closed months.

There are three common causes:

- **A late statement for a past month.** The client finally sends July in October, after July was closed.
- **A date range that starts too early.** A batch built from a full-year download includes months that were posted from another source.
- **A rerun after a fix.** A statement that failed and was fixed later now exports with lines from a closed month.

Before importing, compare each export's earliest date with the client's closing date in their books. If the export starts before it, decide what to do with the earlier lines. Often the answer is to drop them because they are already posted. Sometimes they are genuinely missing and need posting through a dated adjustment that the client's accountant agrees to.

The stakes rise once a tax return has gone in. Changing a filed year's figures is not a bookkeeping shortcut. It may mean an amended return or an adjustment in the current year, and the decision belongs with the client's tax preparer. [What to do when books change after taxes were filed](/blog/books-changed-after-taxes-were-filed) walks through who decides and how to record it.

## The per-client export routine after a batch, step by step

A per-client export routine is a short, fixed sequence you run after every batch, in the same order for every client. Working one client at a time, from the export through the checks to the import, keeps files from crossing between books and leaves a record of what went where.

1. **Clear the batch first.** Every statement should be converted, or flagged and handled. Exporting around a failed statement leaves a hole in that client's month.
2. **Open the first client.** Confirm their statements for the period are all present, one per account.
3. **Export per account.** One file per bank or card account, in that client's format.
4. **Name each file.** Client, last four digits, period and target system, in a fixed order.
5. **Run the four checks.** Period, line count, closing balance and account, against the statement.
6. **Import into the right company file.** Open the company named in the file before importing.
7. **Record it.** Note the file name, the date imported and who did it in the client's tracker row.
8. **Move to the next client.** Repeat steps two to seven until the batch is done.

The record in step seven is easy to skip and expensive to lose. When a client asks in March whether September was posted, the tracker answers in seconds. Without it, someone has to open the books and compare dates by hand.

The routine is the same for three clients or thirty, so it scales without new decisions. To see how a batch moves from uploaded PDFs to per-client QuickBooks or Xero files, [look at how AutoBankConvert handles a month of statements](/).