# How to Automate Bank Statement Downloads for Clients

- Author: AutoBankConvert (https://www.autobankconvert.com)
- Published: 2025-03-17
- Updated: 2025-03-17
- Category: Statement automation
- Canonical: https://www.autobankconvert.com/blog/automate-bank-statement-downloads

> How to automate bank statement downloads for each client: e-statement emails, shared folders and bank alerts, so statements reach conversion without chasing.
To automate bank statement downloads for a client, pick one route per account and set it up once: forward the bank's e-statement emails to your intake address with a filter, have the client save PDFs to a shared folder, or use the bank's statement-ready alert as a reminder. Each route then delivers the month's file without a request email.

## Which bank statement download routes can be automated?

Bank statement download routes fall into three groups that can run without a monthly request: email forwarding of e-statements, a shared folder the client saves into, and a bank alert that prompts a short manual step. A fourth route, direct bank or aggregator connections, gives transaction data rather than the statement PDF and suits a different workflow.

Each route trades setup effort against how much still depends on the client. The table below compares them. It describes typical behaviour; individual banks differ.

| Route | What arrives | Setup effort | Usual failure |
| --- | --- | --- | --- |
| E-statement email with PDF attached | The statement itself | One filter, once | Bank changes sender address or subject |
| E-statement notice without attachment | A message saying the statement is ready | Filter plus a manual download | Client ignores the notice |
| Shared folder | Whatever the client saves | Folder per client, naming rule | Client stops saving, or saves the wrong file |
| Bank alert as reminder | A prompt, no file | Alert set in online banking | Alert turned off after a password reset |
| Data connection | Transactions, not the PDF | Client consent and upkeep | Connection expires and needs reauthorising |

Whether a bank attaches the PDF or only sends a notice is the most important detail to learn for each client. You find out by asking the client to forward one example message.

## Routing e-statement emails into automated downloads

E-statement email routing turns the bank's monthly message into a file in your intake without anyone opening it. The client, or you if you hold a delegated mailbox, creates a mail filter that matches the bank's sender and subject and forwards those messages to your practice's intake address. Set up correctly, the statement arrives the day the bank releases it.

Most mail services support filtered forwarding. Google's help page on [automatically forwarding Gmail messages](https://support.google.com/mail/answer/10957) explains the pieces: you add a forwarding address, Gmail sends a verification message to that address, and the forwarding only starts once someone clicks the link in it. By default automatic forwarding sends all mail, so to forward only bank statements you search for those messages, create a filter from the search and choose forward as the action.

Points that decide whether email routing keeps working:

- **Match on sender, not just subject.** Subjects such as "Your statement is ready" are generic and may catch marketing mail.
- **Confirm the verification step.** Forwarding that was never verified looks set up and sends nothing.
- **One filter per bank.** A client with two banks needs two filters, each tested once.
- **Expect notices without attachments.** Some banks email a notice rather than the statement itself. In that case the email still has value as a trigger, but someone has to log in and download the PDF.

AutoBankConvert accepts statements forwarded to your firm's inbox and matches each file to its client, so a forwarded e-statement goes straight into that client's next conversion. Clients do not need an account of their own for this.

## Shared folders as a statement download drop point

A shared folder gives each client one place to save statements, and gives you one place to collect them. It suits clients whose bank sends notices rather than attachments, or who prefer downloading to setting up mail filters. The folder does not download anything itself. It makes the client's single monthly action short and predictable.

Make the folder hard to misuse:

- **One folder per client, one subfolder per account.** A client with checking, savings and a card gets three, so files never need sorting.
- **A naming rule.** Ask for account name and month, for example `Checking-6318-2026-03.pdf`. The rule matters less than its consistency.
- **Bank PDFs only.** Ask clients not to save screenshots or exported spreadsheets in the statement folder. A downloaded PDF reads more reliably than a photo.
- **Restricted sharing.** Only the client and your practice should have access. Avoid links that anyone with the URL can open.

A folder works best paired with a calendar reminder for the client on the day statements usually post. That replaces your chasing email with their own prompt.

### When the client saves the wrong file

The most frequent shared folder mistake is a file that looks like a statement but is not one: a transaction history export for a custom date range, a printed web page, or last month's PDF saved again under a new name. A transaction export usually lacks the opening and closing balances, so the totals cannot be checked against anything. When this happens, reply with a screenshot of where the statements page sits in that bank's online banking. One clear picture fixes it for good.

## Setting up automated statement downloads for one client, step by step

Setting up automated statement downloads for one client takes one session at onboarding and a check after the first month. The order below avoids the most common trap, which is building a route before you know what the bank actually sends. Repeat it for each account the client holds.

1. **List every account.** Checking, savings, credit cards and loans, with the bank and the last four digits of each.
2. **Ask for one recent statement message per bank.** Find out whether the PDF is attached or only announced.
3. **Choose a route per account.** Attached PDF means email forwarding. Notice only means a shared folder plus the notice as a reminder.
4. **Switch the account to e-statements.** Paper statements cannot be routed, and a scan adds reading risk.
5. **Build the route.** Create and verify the mail filter, or create the folder and share it.
6. **Send a test.** Forward last month's statement through the new route and confirm it lands in the right client's intake.
7. **Write it down.** Note the route, the bank's sender address and the expected arrival day in the client file.
8. **Check after the first real cycle.** When the next statement is due, confirm it arrived without anyone asking.

The worked example below shows the result for a fictional client with three accounts.

| Account | Bank sends | Route | Expected arrival |
| --- | --- | --- | --- |
| Checking ending 6318 | PDF attached | Gmail filter forwards to practice intake | 2nd of each month |
| Savings ending 4471 | Notice only | Client saves PDF to shared folder | 2nd, prompted by notice |
| Card ending 0907 | PDF attached | Second Gmail filter, card sender | 8th of each month |

Once statements arrive, conversion takes over. The walkthrough of [automated bank statement conversion, stage by stage](/blog/automated-bank-statement-conversion) follows a file from upload to export. If a client's books live in SAP Business One rather than QuickBooks or Xero, the import end differs, and the guide to [SAP Business One bank statement processing](/blog/sap-business-one-bank-statement-processing) covers what that system expects.

## Automated statement downloads that fail quietly

Automated statement downloads fail quietly because a broken route sends nothing, and nothing looks the same as a statement that is merely late. A changed sender address, an expired password, a filter deleted during a mailbox cleanup or a client who switched banks will all stop delivery without an error. You notice only when the month is due.

Ways to catch a quiet failure early:

- **Keep an expected arrival day per account.** If nothing has arrived three business days after it, check the route before emailing the client.
- **Watch for notices without files.** If a notice arrives but no PDF follows in the folder, the client's manual step is the gap.
- **Recheck after any bank change.** A merger, a new online banking platform or a renamed product often changes sender addresses.
- **Recheck after password resets.** Some clients turn off alerts or forwarding while securing an account and forget to restore them.
- **Compare against the account list.** Count the statements received against the accounts you expect. One missing account is easy to overlook in a month with ten files.

A monthly schedule helps here. AutoBankConvert lets you set a recurring run per client, and new statements are converted as soon as they arrive. Pair that with your expected arrival days, and an account that has not delivered by its usual day is easy to spot.

## When should a client keep downloading statements by hand?

A client should keep downloading statements by hand when automating the route would create more risk or work than it saves. That includes clients with very few accounts and irregular activity, banks that offer neither attachments nor alerts, and clients who will not maintain a filter or folder. A clear monthly request can be the better system.

Cases where manual download is the sensible choice:

- **Dormant or seasonal accounts.** An account with two transactions a year does not need a route.
- **Shared mailboxes with tight security policies.** Some organisations block automatic forwarding outside the domain.
- **Clients in transition.** A business about to change banks should wait until the new account is open.
- **Catch-up work.** A backlog of a year or more is a one-off pull rather than a recurring route. The guide to [software for catch-up bookkeeping projects](/blog/software-for-catch-up-bookkeeping) covers handling that volume.

Some clients are better served with less automation overall. The post on [when not to automate bookkeeping for a client](/blog/when-not-to-automate-bookkeeping) sets out how to make that call. For the clients where a route does make sense, [get started with AutoBankConvert](/get-started) and forward the first month's statements to see them convert on arrival.