AI Agents in Accounting: Build a Graph, Not a Swarm

Accounting looks bespoke from the outside and turns out, on inspection, to be remarkably mechanical. Underneath the judgment and the client relationships, the day-to-day is heavy manual work: reading documents, holding an ever-changing body of tax law in your head, computing against it, hunting for optimizations, and filling in forms. That combination — high recall, strict rules, repetitive computation — is close to a perfect use case for AI.

Strip an accountant's core loop down to its mechanics and it's almost unfair. You read content, you compute it against a set of tax rules and predefined calculations, and you fill in forms. That's work AI does faster and more consistently than even the most Red Bull-enhanced accounting graduate at 2 a.m. in the back half of March.

And the filing is the floor, not the ceiling. Once the mechanical work does itself, the directors, principals, and partners get their most valuable hours back — for business development, for clients, for judgment. The agents can run dozens of scenarios per client and surface the optimal one for that client's specific situation, something no human has the time to do by hand across an entire book of business.

First, the boring prerequisite: machine-readable data

None of this works on a shoebox of receipts. Before you can talk about agents, the data has to be in a machine-readable format. Yes, folks — someone still has to get it into a system. That's far less painful than it used to be, since most of it now arrives digitally already. But readable isn't enough. A dumb machine has to be able to find the right number at the right moment, which means the data also has to be organized and structured. Get this wrong and every clever thing downstream inherits the mess.

Architect it like a brilliant, stupid team

Here's the mental model I keep coming back to: an AI agent team should be designed like a team of human employees with unlimited knowledge and almost no common sense. Each one knows an enormous amount and will still walk confidently off a cliff if you let it. You manage that the way you'd manage capable-but-literal people — narrow jobs, clear ownership, and a chain of command — not by throwing them all in a room and hoping.

Concretely, here is how I'd staff it:

• Tax-law agents, one per section of the code. Personal, corporate, trusts, and the other structures each get their own specialist. There's simply too much law for one agent to hold well, and splitting it means they can consult each other across boundaries instead of one generalist guessing.
• Accounting-data agents. Specialists that comprehend the financial data itself — and, again, more than one: personal income and expense, corporate, trust. Each reads its own kind of books fluently.
• A deductions expert. A sibling to the tax-law agents, but pointed at savings. Its whole job is to look for the legitimate optimizations the others would skip past.
• A compiler. The agent that assembles the actual tax report and filings out of everyone else's work.
• A critical thinker. An agent whose only role is to question every other agent — to push back, poke holes, and refuse to take an answer at face value.
• An auditor. A check on the whole output, looking at it the way an auditor would before it ever reaches a human.
• An orchestrator. The one that runs the show, routes the work, and decides who is asked what, and when.

A graph, not a swarm

I'd wire these together as an agent graph, not a swarm. The distinction matters. In a swarm, every agent can talk to every other agent and they all churn together until some output falls out. It's seductive and occasionally brilliant, but it's also opaque, hard to reproduce, and nearly impossible to explain after the fact.

A graph imposes a hierarchy: agents talk along defined edges, escalate through the orchestrator, and pass work in a structure you can actually trace. In a regulated, high-consequence domain like tax, that constraint isn't a limitation — it's the point. You want to be able to say exactly which agent concluded what, on whose input, and why. A graph gives you that lineage. A swarm gives you a confident answer and a shrug.

Wrap it in APIs and an app

All of this sits behind a custom set of APIs and a web application, so accountants can actually run the work — kick off an engagement, watch it progress, review the output. The application also gives the agents a channel they badly need: a way to ask the user a question. When the data is ambiguous, or a judgment call is genuinely a human's to make, the system should stop and ask — not guess.

Keep the human at the end

Accounting is regulated, so a human stays at the end of the process — always. But the human's job changes. Instead of re-reading every document and re-deriving every number, they review a summary of the agents' decision-making: what was concluded, on what basis, and where the judgment calls were made. The human reviews reasoning, not raw data. The machine does the recall and the arithmetic; the professional owns the judgment and the signature.

This is the shape of AI that changes a business rather than decorating it. Not a chatbot bolted onto the side of the practice, but a structured team of narrow specialists doing the mechanical heart of the work — under a hierarchy you can audit, behind an interface your accountants control, with a human accountable at the end. Faster filings, fewer errors, optimization at a scale no firm could ever staff for, and partners freed to do the work only people can.