Reference build · Accounting firms · WhatsApp and email

A document-chasing agent for a 400-client CA firm

An agent that sends each client the right checklist, reads what comes back, files it against the right client and year, asks only for what is still missing, and keeps one live board of who is complete.

Reference build — a working agent and a worked example, not a client deployment

01 · The problem

Busy season is not hard because the accounting is hard. It is hard because of the chasing.

Fifteen days before a due date, a firm with 400 individual and small-business clients still has something missing from most of them: a bank statement, Form 16, a capital gains statement, a sales register. An article assistant messages each one from a personal WhatsApp, several times. Files come back as photos of single pages and get saved into folders named after the client, mostly. Nobody can answer "who is complete?" without opening 400 folders.

Three touches per client at about five minutes each is roughly a hundred hours a season on chasing alone, done by people who should be learning accounting. And the missing capital gains statement is still found by the partner at review, two days before the deadline.

Constraints that shaped the design

  • The agent prepares. Nothing is filed, posted or sent to a department by it.
  • Client messages are templates the firm approved; frequency and timing are the firm’s.
  • Documents stay in the firm’s storage and the agent reads the document it is classifying, not the archive.
  • Escalation to a phone call is a person’s decision, prompted by the board.
02 · Agent design

A per-client checklist, a document reader, and a board that is always true.

  1. 1The season opens. For each client the agent loads the profile (salaried, business, capital gains, rental, GST-registered, audit applicable) and builds the checklist from the firm’s templates.
  2. 2It sends the checklist on the client’s channel, WhatsApp or email, as an approved message, and opens a tracking row per document.
  3. 3A file arrives. The agent reads it: what it is (a bank statement, Form 16, a broker’s capital gains report), whose, which period, whether it is complete. It files it against the client and year and ticks the row.
  4. 4If the file is partial or for the wrong period, it replies asking for exactly that, once, on the firm’s schedule. It never asks for something it already has.
  5. 5The board updates: complete, in progress, stuck, needs a call. Clients whose documents contradict last year’s (a new rental income, a missing broker) are flagged for a person.
  6. 6When a client is complete the agent tells the assigned article, and the file moves to preparation.

Why an agent, and not a chatbot or a Zap: A reminder sequence sends the same message to everyone on a timer and cannot tell that the photo a client sent is page two of a three-page statement. The agent reads what came back, decides what is still missing for this client, and asks for only that. That decision, made 400 times a day, is the whole job.

03 · Tools

The 6 tools it may call, and nothing else

The tool list is the permission list. If a capability is not here, the agent does not have it, however it is asked.

ToolWhat it doesWhat it may touch
get_client_profileLoads the client type and last year’s document setReads the client master
send_checklistSends the approved checklist message for this clientWrites to WhatsApp or email via the firm’s templates
classify_documentIdentifies a received file, its owner, period and completenessReads the uploaded file only
check_completenessCompares what has arrived against the checklistReads the tracking rows
request_missingAsks for exactly the missing items, within the frequency capWrites an approved message
update_boardUpdates the completion board and flags contradictionsWrites to the board and the staff queue

Model and orchestration

  • Claude (Anthropic API) with tool use
  • Supabase Edge Functions (Deno) for the agent loop
  • Postgres for memory, logs and the approval queue

Channels

  • WhatsApp Business API
  • Email (Gmail or Microsoft 365 via API)

Storage and books

  • Google Drive or SharePoint for files
  • A sheet or table for the board
  • Tally, Zoho Books, QuickBooks or Xero downstream, untouched by this agent
04 · Guardrails

What keeps it safe to run on real data

Guardrails

  • The agent has no tool that posts to books, files a return or contacts a department.
  • Messages are templates; the agent fills in the client’s missing items, nothing else.
  • A frequency cap per client, set by the firm, that the agent cannot exceed.
  • Documents are read for classification and filed; the model does not retain them, and the firm’s storage is the only copy.
  • Every classification is logged with its confidence; low-confidence files are queued for a person rather than filed.
05 · Result

What the reference build does, and the worked example for one season.

What the build does

  • Builds a per-client checklist from the firm’s templates and the client’s profile
  • Classifies received PDFs and images by type, owner, period and completeness
  • Asks only for what is missing, inside the frequency cap, and stops when complete
  • Maintains a live board the manager uses to decide who gets a call
  • Flags clients whose documents contradict the prior year
Hours chasing and filing documents, per season~100 → ~15Worked example
Knowing who is complete400 folders → one boardWorked example
Classification accuracy on common document typesMeasured on the firm’s own files in week one of a pilotTarget
Missing items found at partner reviewTracked per season as the pilot’s headlineTarget

Assumptions

  • 400 clients, about three chasing touches each at five minutes, including filing what arrives
  • Around 15 hours of a person’s time remain for the calls that need one

What a pilot measures that this page cannot

  • Completion rate at seven, three and one day before the deadline, against last season
  • Classification accuracy by document type, and the review queue size
  • Client messages per completed file
  • Late filings and notices attributable to missing documents

Want this agent for your accounting firm?

A pilot runs it on your data in two to three weeks for a fixed fee, measured against your own baseline. Thirty minutes to scope it, free.

Other case studies