Accounting tools for managing multiple client accounts.
No single product does this. Here is the stack layer by layer, what each layer actually fixes, and the one layer most firms never fill.
Five layers, and the third one is usually missing.
There is no single tool that manages multiple client accounts efficiently, and any list that names one is selling you the layer it happens to own. A firm running more than about ten QuickBooks Online clients needs five layers: practice management to say who does what by when, document intake to get source material in without chasing it, ledger access to actually reach the books, review and close to catch what went wrong, and client reporting to send something the client will read. Layers one, four and five are crowded markets with genuinely good products in them. Layer three is the one most firms never fill, and it is the layer that decides whether the other four compound or just accumulate as subscriptions.
Numbers Game is a layer-three tool. It is a QuickBooks Online connector that holds authenticated connections to every client file a firm manages and lets an accountant run work across all of them from one Claude or ChatGPT account, with a person approving every write. This article explains the whole stack, including the parts we do not build, because choosing layer three badly is how firms end up with five tools and the same week.
This guide uses QuickBooks Online examples because it compares QBO-specific tools and workflow details. Numbers Game also supports Xero; the multi-client connection model is the same, while the platform-specific tooling differs.
“Efficiently” is doing the hard work in that sentence.
Take a firm with forty QuickBooks Online clients and a weekly categorization pass. Say the actual thinking, looking at a merchant, deciding what it is, checking whether this client treats it differently, takes twelve minutes per client per pass. That is the professional work and it is worth what you charge for it.
The navigation around that thinking is rarely under six minutes. Choosing the client, waiting for the file, re-orienting to that client’s chart of accounts, remembering that this one puts contractor payments in a class and that one does not, then closing it and starting again. Six minutes, forty clients, four passes a month, is sixteen hours. A full working week per quarter, spent on the act of moving between books. It never appears on a timesheet as its own line because it is smeared across every other line.
This is why tool comparisons that rank products by feature count mislead firms. In a multi-client practice the question is almost never can this tool do the task. It is does this tool do the task once, or once per client. Efficiency at forty clients is a property of the connection model, not the feature list.
A useful test before any purchase: write down the task you do most often, then ask the vendor how it behaves when you have forty clients instead of one. If the honest answer is “you do it forty times, but each time is nicer”, you are buying a better-feeling version of the same week.
Practice management: who does what, by when.
Products to look at: Karbon, Financial Cents, Canopy, Jetpack Workflow, TaxDome. They differ in whether they lean toward tax practices, bookkeeping practices, or both, and in how much client-facing portal they bundle. All of them solve the same core problem.
What it fixes. Work becomes visible. Recurring jobs generate themselves, deadlines exist somewhere other than a partner’s memory, a staff member leaving does not take the client’s close checklist with them, and you can finally answer “where is the Halcyon close” without asking three people.
What it does not fix. None of these tools touch a ledger. A task card reading “categorize January for Halcyon Robotics” is a card. Somebody still opens Halcyon Robotics and does the work. Practice management makes the queue legible, which is valuable and is not the same as making the queue shorter. Firms that buy practice management expecting throughput are consistently disappointed, and then blame the tool for a problem it never claimed to solve.
Document and query intake: getting the inputs without chasing them.
Products to look at: Dext, Hubdoc and AutoEntry for receipts, bills and statements; Uncat for pushing the uncategorized queue back to the client in language they will actually answer.
What it fixes. A large share of close delay is not your firm being slow. It is waiting on a receipt, a statement, or an answer to “what was this $1,240 charge”. Intake tools convert that from an email thread you are managing into a queue the client can clear.
What it does not fix. The coding decision. Optical character recognition reads a receipt well and has no opinion about whether that receipt is a capitalizable asset under this client’s threshold. That judgment is the part of bookkeeping worth paying for, and it stays with you.
Ledger access: the layer most firms have never bought.
Ask a firm what it uses to reach client books and the answer is usually the name of a habit rather than a product: the client switcher in QuickBooks Online Accountant. That is not a tool choice. It is the absence of one, and it is the single largest constraint on a multi-client practice, because everything else in the stack eventually has to pass through it.
A ledger access layer is something that holds authenticated connections to many client files at once, and can run the same operation across all of them with per-client scoping that you control. There are three real options in 2026.
The QuickBooks Online Accountant client switcher
Free, universal, and one file at a time by design. It is the right answer for a firm with six clients and the wrong answer for a firm with sixty, because the cost it imposes scales linearly with your book and never gets cheaper.
Build against the QuickBooks Online API yourself
A real option if you have a developer. Intuit publishes an official QuickBooks Online MCP server, which runs as a local process on one machine and authenticates to one company realm at a time. That is a good fit for a developer wiring up a single company to an AI client. A forty-client firm going this route is registering and maintaining its own Intuit app, holding refresh tokens, and building the per-client authorization it needs before any of it is safe to hand to staff.
A hosted multi-tenant connector
One connection that already understands that a firm is a tenant, a client file is a scoped resource, and a staff member is a role. This is the category Numbers Game is in, and the category is young enough that most firms do not know it exists.
The reason this layer matters more than its profile suggests: it is the only layer that changes the arithmetic above. Practice management makes sixteen hours of navigation visible. Intake shaves the waiting. Only ledger access removes the per-client repetition itself, because it lets one request reach many books.
Here is what to demand of anything in this category, ours included. Connections should be OAuth only, so the tool never receives a QuickBooks credential. Each authorized AI client or integration should be restricted to the specific companies you name, and that restriction should be checked on every call rather than at setup. There should be a genuine read-only role that a client-side toggle cannot escalate. Revocation should take effect in seconds, not at the end of a token lifetime. Every call should land in an audit log that you can read yourself. And nothing should write to a client’s books without a named person approving it. Those are the six properties Numbers Game is built around, and they are also a fair checklist to hold us to. Our security page states the boundaries, including the ones that are not flattering.
Review and close: catching what the first pass got wrong.
Products to look at: Keeper and Xenett for bookkeeping-firm close review; inside QuickBooks itself, the Reclassify Transactions tool in QuickBooks Online Accountant and QuickBooks Online Advanced, which changes the account, class, and customer on a set of transactions at once.
What it fixes. Review discipline that would otherwise live in a partner’s head. A structured pass over uncategorized balances, negative asset accounts, unreconciled differences, aged items that should have cleared, and the specific mistakes your firm keeps making.
What it does not fix. Review layers are per-client by construction, and reclassification inside QuickBooks is a cleanup pass, which means it runs after the books were coded wrong. Both are worth having. Neither reduces the number of times somebody opens a file.
Client reporting: the part clients actually see.
Products to look at: Fathom, LiveFlow, Reach Reporting and Syft Analytics, which pull QuickBooks data into managed reporting, dashboards, and in LiveFlow’s case live spreadsheet models.
What it fixes. A client does not read a QuickBooks profit and loss export. They read a document with your name on it that tells them what happened. Reporting tools make that document repeatable instead of a monthly act of will.
What it does not fix. The commentary. Every tool in this category produces excellent charts and no opinion. The sentence “gross margin fell four points because you took the Halcyon job at a bad rate” is the billable part, and it is still yours to write. Which is the argument for making the retrieval cheap: the hours you save assembling numbers are the hours available to say what they mean.
What each layer fixes, and what it leaves for you.
| Layer | Examples | What it fixes | What it leaves alone |
|---|---|---|---|
| 1. Practice management | Karbon, Financial Cents, Canopy, Jetpack Workflow, TaxDome | Visibility, recurring jobs, deadlines, handover | The work itself. Never touches a ledger. |
| 2. Document intake | Dext, Hubdoc, AutoEntry, Uncat | Chasing receipts, bills, and client answers | The coding decision. |
| 3. Ledger access | QBO Accountant switcher, a self-built API integration, Numbers Game | The per-client repetition itself | Judgment, approval, and what you charge for it. |
| 4. Review and close | Keeper, Xenett, QBO Accountant Reclassify | Errors from the first pass, review discipline | Runs per client, and runs after the mistake. |
| 5. Client reporting | Fathom, LiveFlow, Reach Reporting, Syft | A document the client will actually read | The commentary, which is the billable part. |
What to buy first, by the size of your book.
Under 15 clients
Practice management is premature and will feel like homework. Buy intake first, because chasing documents is most of your delay at this size, and solve ledger access second. A spreadsheet is still a legitimate work tracker at fifteen clients.
15 to 50 clients
This is where practice management stops being optional, because the failure mode changes from slow to forgotten. Ledger access pays for itself fastest in this band: the per-client tax is large enough to hurt and the book is small enough that one person notices the whole of it.
50 clients and up
Add review and reporting layers, and start treating your firm's coding standards as a written artifact rather than a shared habit. At this size the constraint is no longer time, it is consistency between the people doing the work.
One warning about sequencing. Buying reporting before ledger access is the most common expensive mistake we see, because a reporting tool makes the last mile beautiful while the first mile still takes a week. The output improves and the calendar does not.
Three questions that separate the categories.
- Does it scope per client, and where is that enforced? Any tool touching several clients’ books needs to answer this precisely. “You pick the client in the interface” is a user-interface answer to a security question. What you want to hear is that the restriction lives in the credential and is checked on every call, so that no prompt, toggle, or mistake reaches a client you did not name.
- Does it write, and who approves? Reading is a low-stakes question. Writing is not. If a tool posts to the ledger, ask what a person sees before it posts, whether the approval is recorded with a name against it, and whether there is a single-step way to reverse a batch that went in wrong.
- What can it structurally not do? A vendor who can list what their product is incapable of has thought about the blast radius. Numbers Game cannot permanently delete QuickBooks records, cannot change Intuit account settings, cannot move money or initiate ACH, and does not touch payroll filings. Those are tool-level exclusions, not policy promises, which is the difference between a limit and an intention.
What this stack looks like at 200 clients.
Numbers Game was built inside AG Accounting, a firm running more than 200 QuickBooks Online clients, and every capability runs on those clients before it reaches anyone else. That is the reason the roadmap is unromantic. It is full of things like credit memos that actually apply to open invoices, and voiding rather than deleting where a third party already holds a copy of the document.
Nicole Jordan-Dahdal, who runs the fractional CFO and M&A practice PrismEdge, put the effect of collapsing the ledger-access layer this way: “A recent opex audit across three entities would normally have taken me a few days. With Numbers Game it was done in under two hours.” The detail worth noticing is which time was saved. She did not automate her judgment. She automated retrieval, and the hours that used to go into assembling numbers now go into reading them. The full write-up is here.
If you want to see the texture rather than the summary, we publish the prompts in our Prompt Library, organized by close, reconciliation, journal entries, vendor analysis and client communication.
Multi-client tooling, answered.
The rest of this series.
Accelerating transaction creation, seven ways
Bank rules, templates, batch entry, imports, receipt capture, API sync and AI drafting: what each speeds up and where each breaks.
AI tools for bookkeeper workflows and client reporting
Four categories of AI accounting tool, eight questions that separate them, and a recommendation by situation.
The best QuickBooks Online integration is the one for your job
Seven integration categories, how QBO OAuth and rate limits work, and eight checks before you connect a client’s books.
Bring one real client file.
A 30-minute walkthrough against your own books. Leave with a branded close report you can keep, whether or not you buy anything.