Bookkeeping for multiple bank accounts works when every account is listed in one map, every statement goes through conversion in the same batch, and the accounts close in a fixed order, with transfers matched on both sides. The client's month is done only when each bank account on the map is marked closed, not when the busiest one is.
Why does bookkeeping for multiple bank accounts go wrong?
Errors with several accounts rarely come from the transactions themselves. They come from the joins: a statement that never arrived for the quiet savings account, a transfer recorded on one side only, or a card payment posted as an expense. Each account looks fine alone. The problems show up only when the accounts are read together.
A client with one checking account gives the bookkeeper one statement, one reconciliation and one place for every dollar. Add a savings account, a payroll account, two cards and a line of credit, and the same month now has six statements arriving on different days, money moving between them, and six balances that must all agree with the bank. The work does not grow evenly. The number of possible transfers between accounts grows faster than the number of accounts.
The usual failures are predictable:
- A missing account. An account the client opened during the year is never added, so its activity is absent from the books.
- A silent statement. A low-activity account produces a statement that nobody requests, and its month goes unreconciled.
- Half a transfer. Money leaves checking for savings, and only the checking side is posted.
- Mixed ownership. A personal account appears in the batch and its lines are coded as business.
The IRS, in Publication 583 on starting a business and keeping records, says a business account should be kept separate from personal checking. That advice is the reason the map below has an owner column: a multi-account client is where personal and business money most often meet.
Building an account map for a multi-account client
An account map is one table listing every account the client holds, with what it is for, where its statement comes from and when its cycle ends. Build it at onboarding, check it every quarter, and treat it as the master list. If an account is not on the map, it is not in the close.
Here is an example map for a fictional catering business. The account numbers and dates are made up.
| Account | Type | Purpose | Owner | Statement source | Cycle ends |
|---|---|---|---|---|---|
| Checking 4417 | Bank | Operating, all sales deposits | Business | Bank portal PDF | Last day of month |
| Savings 8821 | Bank | Tax reserve | Business | Bank portal PDF | Last day of month |
| Payroll 3090 | Bank | Funded from checking for payroll | Business | Emailed PDF | 20th |
| Card 9032 | Credit card | Supplies and fuel | Business | Card portal PDF | 12th |
| Line of credit 5508 | Loan | Seasonal working capital | Business | Lender statement | Last day of month |
Five columns carry most of the value. The purpose column tells you how to read the transactions. The owner column catches personal accounts before they enter the books. The source column tells you where to go when a statement is late. The cycle column tells you which accounts need a mid-month cutoff. The type column decides whether the balance is an asset or a liability.
Keeping the map current
Accounts change more often than clients mention. Add a standing question to the monthly message: has the business opened or closed any account this month? A short, repeatable request works better than a long checklist; email templates for bookkeepers has wording for the monthly statement request.
Converting every account's statement in one batch
Converting all of a client's statements at once, rather than as each one arrives, keeps the month's data together and makes gaps visible. If the batch has four statements and the map lists five accounts, you know before any posting starts that one is missing. Converting piecemeal hides that until the final reconciliation.
Wait for the last statement on the map, or set a fixed day after which you convert what you have and chase the rest. The fixed day suits accounts with mid-month cycles: a card closing on the 12th will not be available on the 1st, so either convert it on its own day each month or hold the whole batch until it lands. Choose one approach per client and keep it. How often a client's books are worked at all also shapes this choice; how often to do bookkeeping compares weekly and monthly rhythms.
In AutoBankConvert, each client has its own workspace with its own accounts, rules and history, and a folder of statements across banks and months can go through conversion in one upload. Each statement must pass its balance check, opening balance plus transactions equal to closing balance, before it is marked done. A batch of five statements with one failure tells you exactly which account to look at first.
Card statements in the batch
Credit cards behave differently from bank accounts: purchases raise the balance, payments lower it, and the cycle usually ends mid-month. They belong in the same batch but need their own posting rules. The guide to credit card statement bookkeeping covers the sign conventions and cycle dates.
In what order should a client's bank accounts close?
Close the account that receives the most money first, usually the operating checking account, then the accounts it funds, then the cards and loans it pays. Following the money downstream means each transfer is already posted on the sending side when you reach the receiving account. You match transfers instead of guessing at them.
For the example client, the order would be:
- Checking 4417. All sales arrive here, and it funds every other account.
- Savings 8821. Receives the tax reserve transfers from checking.
- Payroll 3090. Receives the payroll funding from checking.
- Card 9032. Paid from checking each month.
- Line of credit 5508. Draws go into checking, payments come out of it.
The order matters most when a reviewer checks the work. A fixed order means every close looks the same, so a difference stands out. It also means a new team member can pick up a half-finished client and know exactly where the last person stopped.
Transfers between a client's own bank accounts
A transfer between two of the client's own accounts is neither income nor expense; it is money changing pockets. Record it once, as a transfer from one account to the other, and confirm the same amount appears on both statements. A transfer posted on one side only leaves one account overstated and the other understated.
A clearing account makes the check mechanical. Post every transfer out to the clearing account from the sending side, and every transfer in from the clearing account on the receiving side. At month end, the clearing account should be zero. Anything left is a transfer with one side missing, and the amount tells you which one to look for.
Timing breaks the zero sometimes, and that is fine as long as you can name the item. A transfer sent on the 31st and received on the 1st sits in clearing over the month end. Note it, and confirm it clears in the next month.
When transfers were coded wrongly for months
If a categorization rule has been sending transfers to an income or expense account for months, fix the rule first and then move the old lines in one pass. Reclassifying transactions in bulk covers how to find the full scope and check the reports afterward.
Tracking which bank accounts are closed each month
A close tracker shows, per client, each account on the map and its status for the month: statement received, converted and balanced, reconciled, reviewed. The client is done when every row reads reviewed. Without the tracker, a busy month ends when the big account balances, and the quiet ones slip.
An example tracker for the same client, mid-close, with made-up statuses:
| Account | Statement in | Balanced | Reconciled | Reviewed |
|---|---|---|---|---|
| Checking 4417 | Yes | Yes | Yes | Yes |
| Savings 8821 | Yes | Yes | Yes | No |
| Payroll 3090 | Yes | Yes | No | No |
| Card 9032 | No, due 12th | |||
| Line of credit 5508 | Yes | Yes | Yes | Yes |
Read the tracker from left to right. The first blank in a row is the next task for that account. Read it from top to bottom for the client: the month is not done until the last column is full.
When a client has more bank accounts than the business needs
Some clients open accounts out of habit, one per project or an old one kept alive with a few dollars in it. Each one costs a statement request, a conversion, a reconciliation and a line on the tracker every month. When an account has no clear purpose on the map, ask the client whether it should stay open.
Suggest consolidation, not closure, as the first step. A tax reserve, a payroll account and an operating account each have a clear job. A second operating account at another bank, used twice a year, often does not. If the client agrees to close one, the remaining balance moves by transfer, and the account comes off the map once its final statement shows zero.
Leave the decision with the client, and write it on the map either way, so the next bookkeeper does not ask the same question. Some extra accounts exist for good reasons the bookkeeper cannot see, such as a lender's requirement or a partner agreement. The bookkeeper's part is to show the monthly cost in work and to keep each remaining account on the map and in the close.