# Bookkeeping for Multiple Clients Without Mixing Books

- Author: AutoBankConvert (https://www.autobankconvert.com)
- Published: 2025-01-10
- Updated: 2025-01-10
- Category: Client work
- Canonical: https://www.autobankconvert.com/blog/bookkeeping-for-multiple-clients

> Bookkeeping for multiple clients without mixing their books: separate workspaces, client-specific rules and a weekly rhythm that keeps every client current.
Bookkeeping for multiple clients works when each client has its own workspace, its own rules and its own file trail, and when your week is organized around statement close dates instead of whoever emailed last. Separation prevents mixed books. A fixed weekly rhythm keeps every client current.

## How do you keep multiple clients' books separate?

You keep multiple clients' books separate by giving each client one home for everything: one accounting file, one folder of source documents, one set of coding rules and one history of decisions. Anything that is shared between clients, such as a template, holds no client data.

Mixing happens in small, ordinary ways. A statement is saved to the wrong folder. A rule built for one client is applied to another. A bank login is shared across tabs. Each is easy to make on a busy day, and most are hard to see afterward because the numbers still look plausible.

Build separation into four places:

- **Accounting files.** One file or company per client, never a shared file with a class or tag per client. Keep a note of who owns each login.
- **Source documents.** One folder per client, with a fixed layout inside it, for example a folder per year and a folder per account. The same layout for every client means you stop thinking about where things go.
- **Rules and templates.** Coding rules live with the client. Shared templates hold structure only: account names and numbers, never a client's payees.
- **Software workspaces.** If your tools support separate client workspaces, use them. In AutoBankConvert, each client keeps their own accounts, rules and history, so a rule approved for one client does not change another's.

### A short separation test

Once a quarter, run three checks on a few clients picked at random:

1. Open the client's folder and confirm every file belongs to that client, by account holder name on the statement.
2. Open the client's rules and confirm every payee in them belongs to that client's real activity.
3. Compare each bank account's closing balance in the books with the last statement.

A failed check on any of these tells you where a leak is, and the fix is usually small if you catch it early.

## A weekly rhythm for a multiple client bookkeeping load

A weekly rhythm for a multiple client bookkeeping load is a fixed schedule that assigns each client to a day based on when their statements close. It replaces deciding every morning who to work on, and it makes the last days of the month predictable.

Statements close on different dates. Many business checking accounts close at calendar month end, while credit cards close on a date set by the issuer. Grouping clients by close date lets you request and process each group when its documents exist, instead of waiting for the end of the month.

### Example: twelve clients across a week

The table below is an example of a weekly calendar for twelve clients. The groupings and days are illustrative.

| Client group | Statement close | Request sent | Process | Review and export |
| --- | --- | --- | --- | --- |
| Clients 1 to 3 (mid-month card cycle) | 15th | Monday after the 15th | Tuesday | Wednesday |
| Clients 4 to 6 (month-end, small volume) | Last day | First Monday | Tuesday | Wednesday |
| Clients 7 to 9 (month-end, high volume) | Last day | First Monday | Wednesday | Thursday |
| Clients 10 and 11 (quarterly catch-up) | Quarter end | First Monday of quarter | Thursday | Friday |
| Client 12 (new client, onboarding) | Varies | Per onboarding plan | Friday | Following Monday |

Read the table by rows. Each group has one day for asking, one for processing and one for review. Keep review a day apart from processing, because errors are easier to see after a night away from the numbers.

Two habits make the rhythm hold. First, send all requests for a group in one sitting, using the same template. The wording that gets replies is in [how to collect bank statements from clients](/blog/how-to-collect-bank-statements-from-clients). Second, keep one slot a week for exceptions: late statements, a question from a client, a rule that needs repair. Without that slot, exceptions eat the days meant for routine work.

### When the calendar slips

Calendars slip, and the rhythm should survive it. When a group's statements arrive two days late, move that group's processing day, not the whole week. Note the reason in the client record, so a pattern of late files is visible after a few months. A client who is late three months running needs a different collection method, or a conversation about the due date. Do not absorb the delay silently by working an evening; that hides the problem from you and from them.

## Client specific rules that must not cross books

Client specific rules are coding rules that are correct only for one client's books. They must not cross books because the same payee name can mean different things for different clients, and a rule that fits one client will quietly mis-code the others.

Take three clients who all pay "Home Depot". A contractor buys materials that belong in cost of goods sold. A landlord buys repairs for a rental. A software consultant buys a shelf for the office, which is office supplies. One shared rule is wrong for at least two of them.

Which rules may be shared and which must stay with one client is set out in [shared rules versus per client rules](/blog/accounting-automation-for-bookkeepers#shared-rules-versus-per-client-rules-in-a-practice). In short, keep retailers, payments to individuals, transfers, owner draws and any payee agreed with the tax preparer per client, and share only payees whose meaning cannot vary, such as the bank's own fees.

### When a rule has crossed books

A crossed rule shows up as a payee in one client's rules that never appears on that client's statements, or as corrections that cluster on one vendor. Fix it in three steps: delete the rule from the wrong client, find every line it coded there since it was created, and recode those lines before the next export. Then note the date in the client record, so a reviewer knows which periods were touched.

### Keeping a rule's reason

A rule without a reason is hard to trust a year later. Add a short note when you create one: who decided, and why. "Contractor, approved by client in March" is enough. When a rule starts producing corrections, the note tells you whether the rule or the client's situation changed.

When a client's vendor list grows, uncertain lines should wait for a person rather than guess. AutoBankConvert sends those to a review queue with a suggested category, and approving a suggestion teaches that client's rules only.

## Multiple clients at the same bank and the mix up risk

Multiple clients at the same bank create a mix up risk because their statements look nearly identical: same logo, same layout, same column order. The only difference is the account holder name and the masked account number, and both are easy to overlook when you work through a batch.

The risk is highest at month end, when you download or receive many files at once. A file named "statement.pdf" from the bank can belong to anyone. A client with two businesses at the same bank, or a married couple with a joint and an individual account, adds more look-alikes.

Defenses that work:

1. **Check the header, not the filename.** Before a statement enters a client's folder, confirm the account holder and the last four digits of the account number.
2. **Name files by a fixed pattern.** Client, account, year and month in the name make a misplaced file obvious. The patterns are in [naming pattern examples for client statement files](/blog/bank-statement-file-naming-convention#naming-pattern-examples-for-client-statement-files).
3. **Record each client's account list.** Keep the bank, account type and last four digits for every account in the client record. A statement for an account not on the list is a prompt to stop and ask.
4. **Check the opening balance.** An opening balance that does not match last month's closing balance is the quickest sign of a wrong file.

Some tools match files to clients automatically. AutoBankConvert matches each uploaded or forwarded file to its client, and checks that the opening balance plus transactions equal the closing balance. Neither step removes your own check of the header on a new account, but both reduce the chance a misplaced file goes through unseen.

## Which client gets attention first each week?

The client who gets attention first each week is the one with the nearest deadline that you cannot move: a tax payment date, a payroll filing, a lender report or a client meeting. After deadlines, work on clients with the largest backlog, since small backlogs grow into large ones.

A simple order for deciding:

1. **External deadlines this week.** Anything a third party will penalize or a client has promised to someone.
2. **Clients whose documents arrived.** Work you can finish now should be finished now.
3. **Clients falling behind.** If a client is more than one month behind, schedule catch-up time before it becomes three months.
4. **New clients in onboarding.** Early weeks set the pattern for the relationship; see the [bookkeeping client onboarding checklist](/blog/bookkeeping-client-onboarding-checklist).
5. **Everyone else, by close date.**

Hold the line on the order, even when a client asks for urgency. A client who is loud is not always a client who is late. Tell them when their turn comes, and keep that date.

Capacity matters as well. If the order never reaches step five, the workload is too heavy for the hours, and the fix is process or help, not longer days. When you have moved most routine steps off your plate, [AutoBankConvert](/) can take the monthly conversion and coding steps for the clients you assign it.