# Set Up Automatic Bank Statement Processing Each Month

- Author: AutoBankConvert (https://www.autobankconvert.com)
- Published: 2026-10-09
- Updated: 2026-10-09
- Category: Statement automation
- Canonical: https://www.autobankconvert.com/blog/automatic-bank-statement-processing

> Set up automatic bank statement processing for each client: monthly schedules, forwarded statements and review steps, so new statements convert on arrival.
Automatic bank statement processing means a new client statement is converted, checked and categorized without you starting the job. To set it up, link each client to a monthly schedule, give statements a way in (upload or forwarding) and decide who reviews what the run flags. Then a run finishes, and you only handle the exceptions.

## What triggers automatic processing of a new statement?

Automatic processing starts when a statement arrives, not when you remember to run something. The trigger is the file landing in the system, by upload or by forward, matched to a client whose monthly schedule is set. Nothing else has to happen for conversion to begin.

Three things have to be true for a statement to be picked up by itself:

1. **The statement is matched to a client.** Every later step uses that client's accounts, rules and history, so the match comes first.
2. **The client has a recurring run.** AutoBankConvert's recurring runs let you set a monthly schedule per client, and new statements are converted as soon as they arrive.
3. **The file is readable.** A statement that cannot be read, or that fails its balance check, is flagged instead of exported. That is the trigger for human attention, not for an error buried in a log.

### What "automatic" does not mean

It does not mean the client's books close themselves. A run converts and categorizes. Lines the rules are unsure about land in a review queue, and someone still approves them. Treat automatic processing as automatic up to the point where judgment is needed.

### Before you turn it on

Run the first month by hand with the same client. Confirm the balance checks pass, the categories look right and the export opens in the client's books. A schedule built on a bad first run only repeats the problem every month. The wider case for this approach is in the [overview of what a practice can hand off](/blog/bank-statement-automation-for-bookkeepers), which marks each step as automated, assisted or manual.

## Monthly processing schedules per client

A monthly processing schedule ties each client to the day their statements usually become available, so runs line up with when files actually arrive. Clients with different statement closing dates get different schedules, which spreads your work across the month instead of piling it into the last days.

Banks close statements on different days, and a client with two accounts at two banks may have two closing days. A schedule that runs on the first of every month for every client will find some statements not yet there. One schedule per client avoids this.

### Setting up a recurring run for one client

Follow these steps for each client. The steps describe the decisions you make, in the order that works best.

1. **Create or open the client's workspace.** Each client keeps their own accounts, rules and history, so nothing crosses between books.
2. **Record the accounts to expect.** Write down each bank account and card the client uses, so you know what a complete month looks like.
3. **Find the closing day for each account.** Look at last month's statement for the period end date. Statements usually become available a few days after it.
4. **Choose the run day.** Pick a day after the latest statement is normally available. A few days of buffer costs little.
5. **Turn on the recurring run.** In AutoBankConvert this is a monthly schedule per client, and new statements are converted as soon as they arrive, so the run day is the day you check that the month came in and processed.
6. **Decide how statements arrive.** Choose between the client uploading, you uploading, or forwarding to your firm's inbox.
7. **Name who reviews.** Decide who clears the review queue for this client, and by what day.
8. **Test with one real month.** Watch the run finish, check the balance results and open the export.

### A calendar for three clients

The dates below are an example. Your clients will close on their own days.

| Client | Accounts | Statement closes | Statements usually available | Run day | Review due |
| --- | --- | --- | --- | --- | --- |
| Example Bakery LLC | 1 checking | 28th | 1st to 2nd | 3rd | 5th |
| Example Landscaping Co. | 1 checking, 1 credit card | 15th and 20th | 17th to 22nd | 23rd | 26th |
| Example Dental Group | 2 checking | End of month | 2nd to 4th | 5th | 8th |

Notice the spread. The three clients produce work on the 3rd, the 23rd and the 5th, so no single day carries the whole load. The landscaping client has two closing days, and the run day waits for the later one so both accounts are in before processing.

### Plan limits

A schedule is only as large as your plan. The Practice plan on the homepage includes recurring monthly runs, 2,000 pages a month and up to 50 clients. Check the page allowance against the real number of pages your clients send before you schedule every client, because a busy month with many multi-page statements can use more than you expect.

## Forwarding client statements into automatic processing

Forwarding sends a client's statement email to your firm's inbox so the file enters processing without anyone downloading and re-uploading it. It suits clients who already receive statements by email and will not log into anything. Each forwarded file is matched to its client.

AutoBankConvert accepts statements by upload or by forward, and clients never log in unless you invite them. For many practices that is the difference between a workable process and none: clients do something they already do, and you do not need them to learn a new tool.

### Make forwarding work reliably

- **Ask for the bank's PDF, not a screenshot.** A downloaded PDF holds exact text. A photograph of a screen is a scan, and scans carry more risk of misreads.
- **One statement per email where possible.** It keeps each file easy to match and easy to trace if something goes wrong.
- **Keep a short list of expected statements per client.** Compare it with what arrived. If a file is missing, you notice.
- **Name files consistently.** A predictable name makes a mismatch obvious.

If your clients forward statements at all, ask them to set up a rule in their own mail so the bank's monthly statement email goes straight to your firm's address. That is the client's one-time action and everything after it can run by itself.

Getting clients to send statements at all is its own problem, with its own tactics. A well-worded request is covered in [a statement request email clients actually answer](/blog/how-to-collect-bank-statements-from-clients#a-statement-request-email-clients-actually-answer).

## How do you know automatic processing finished?

You know processing finished when each statement shows a balance check result and each client's review queue shows its count of lines waiting. A finished run has no statement in an unknown state: every one is exported, flagged for a failed check or waiting in review.

Do not assume a quiet system is a successful one. Silence can also mean nothing arrived. Check these outcomes for each client after a run:

| Outcome | What it means | What you do |
| --- | --- | --- |
| Balance check passed, no review lines | The statement is done | Spot check, then export |
| Balance check passed, lines in review | Conversion is right, some categories are unsure | Clear the queue; approvals teach the client's rules |
| Balance check failed | Something was missed or misread | Compare page and rows near the gap |
| Nothing for an expected account | The statement has not arrived | Contact the client |

### A short completion check

At the end of the run day, ask four questions per client. Did every expected account produce a statement? Did every statement pass its balance check? Is the review queue empty or assigned? Has the export been produced? If all four are yes, the client is done for the month.

Over time, the review queue should shrink. Approving a suggestion teaches the client's rules, so the same vendor is categorized automatically next month. A queue that does not shrink after two or three months usually means the rules are too narrow, or the client's spending is unusually varied.

### When a run produces odd results

If a client's statements start failing balance checks after months of passing, the bank may have changed its layout. [Keeping automation running through bank statement layout changes](/blog/bank-statement-layout-changes) explains the spot check to run, and the full set of fields to look at is in [what comes back from bank statement data extraction](/blog/bank-statement-data-extraction).

## Late or missing statements in an automatic processing schedule

A late or missing statement leaves a hole in a schedule: the run for that account has nothing to process. Handle it by recording which statements you expect, noticing the gap on run day and following up with the client, then processing the late file when it arrives.

A schedule cannot invent a statement. Late files are common: a client on holiday, a bank that posts statements late, an email that landed in spam. A good process makes the gap visible quickly.

### What to do, in order

1. **Compare arrivals with the expected list.** On the run day, list which accounts have a statement and which do not.
2. **Contact the client the same day.** Name the account and period you need. A specific request is answered faster than a general one.
3. **Offer a fallback.** If the client cannot find the email, they can usually download the PDF from their bank's online banking.
4. **Process the late file when it arrives.** It converts like any other statement, and it should pass the same balance check.
5. **Close the month only when every account is in.** A missing account makes the totals incomplete, even if every other number is right.

### A statement for the wrong period

Sometimes the file that arrives is the wrong month, a duplicate or a statement for a different account. The balance check helps here, because the opening balance should match the previous month's closing balance. If it does not, a statement is missing or the file is from another period.

### Treat late files as a pattern

If one client is late every month, move the run day later for that client, or ask for statements earlier with a recurring reminder. A schedule that fits the real arrival date beats a perfect schedule that is always waiting. When you are ready to put a few clients on a schedule, [request a spot via get started](/get-started).