If you handle expense data for about 20 clients, the goal is not a single shared login. It is one consistent system you sign in to once, where each client has a clearly separated space, the same folder layout and the same monthly routine. Separation protects the clients; consistency protects your time.
The numbers here are in US dollars and are made up to show the method. Nothing in this piece is tax or legal guidance.
What does one-login-for-everything cost you today?
Count the hidden time. Suppose each client has four places you must visit every month: a bank portal, a card portal, a receipt inbox and a payroll or invoicing tool. That is 20 times 4, so 80 separate sign-ins. At two minutes each, including finding the right sign-in details and waiting for a code, that is 160 minutes, or 2 hours 40 minutes, before you have recorded a single transaction. Cut the places per client to one and you save most of it.
Give every client the same skeleton
- One folder per client, named with a short client code and the legal name, for example C014 Alder Roofing
- Inside it, subfolders for Statements, Receipts, Payroll, Correspondence and Year-end
- One working file per client, built from the same template, with identical column order
- A one-page client profile listing accounts, year-end, who approves what, and the client's preferred contact
Identical layouts mean you can open any client at 8 pm after a long day and still know where the bank statements go.
How should clients send you their records?
Ask for exports, not access. A monthly statement file from each account, uploaded to the client's folder, is safer for both sides than you holding live bank credentials. Never ask a client to email or message their banking sign-in details; if a provider offers a read-only invitation for accountants, use that route and keep it in the client's name so it can be switched off later.
Set one upload deadline for everyone, such as the 7th. Send a reminder on the 5th listing exactly what is missing, for example the March statement for the business credit card and receipts over $75.
A monthly rhythm that fits 20 clients
| Week | Task | Time budget |
|---|---|---|
| Week 1 | Collect files, chase missing statements | 3 hours |
| Week 2 | Categorise and reconcile five clients per day | 10 hours |
| Week 3 | Review exceptions and unusual items | 4 hours |
| Week 4 | Send one-page summaries and questions | 3 hours |
That is 20 hours for the month, a bit over an hour per client. Your own times will differ; the point is to put a budget on each client so one messy file cannot swallow a week.
How do you keep clients' data separate?
Treat each client as a separate workspace, never a tab in a giant combined workbook. Mixing clients in one file makes a mistaken export or a shared screen a confidentiality problem. Use a tool or folder structure where a person can belong to several client spaces but each space is sealed from the others. SpendixAI lets you keep records in your own personal workspace for personal use, but it is not designed as a multi-client accounting console, so check any tool you consider against your client load.
Which quick checks catch errors?
- Opening balance for the month equals the closing balance from last month
- Total of imported transactions equals the statement total, to the cent
- No duplicates: the same amount, same merchant within two days gets a second look
- Everything over a threshold you set, say $250, has a receipt
- Uncategorised items are zero before you send the summary
Run these in the same order for every client. After a quarter, they become automatic.
Next step
Pick your three messiest clients and move them onto the skeleton first. Once the template proves itself, migrate the rest in batches of five.
Useful ideas start with a clearer picture of your own spending.
Explore your reports


