Accounting Flow
Two ways to put work on the board
Some jobs are identical every quarter. Some need a judgement call. AccountingFlow now has a way to automate each, and neither needs a developer.
AI agents
Put the repetitive half of practice work on autopilot
Point an AI agent at a list of clients or jobs, tell it what to look for, and let it work through them on a schedule. It drafts, proposes and reports — a person always approves.
Work through clients, or through jobs
An agent can run against a saved client filter, a saved task filter, or the clients that have a job matching a task filter. That choice decides what one unit of work is — and so what the agent can sensibly say.
"Review every VAT return still in preparation" is a question about jobs. "Write to every client who has one" is a question about clients: one email, not one per return.
Draw it, don't script it
Wire steps together on a canvas, where every connection says when it is taken — always, on what the step found, or on what it didn't. Save a step to your firm's library and reuse it in any agent.
A flow is stored on the agent, so its schedule, its filter, its safety limit per run and its notifications all come along unchanged.
What an agent can do
- Read the client fileEvery email and letter, the job history, the time booked — in context, before it answers.
- Chase before a deadlineWorks out who hasn't sent records, drafts the chase, and briefs the preparer for the ones who have.
- Keep records currentSpots a changed address or VAT number in a client's own email and proposes the update for approval.
- Tick off the workMarks a job's subtasks done once it has established the work is finished — and reports what it would not tick, and why.
- Raise the billGathers unbilled time and raises one draft invoice per client, grouped by service. Nothing is sent.
- Write the emailDrafts from one of your templates, or writes one for the work it just did when none of them fits.
Why it is safe to leave running
Unattended software writing to the practice record deserves scrutiny, so the constraints are worth being specific about.
- Off by default. Writing is enabled per agent; a deploy never turns an existing agent into a writer.
- It can only tick. No untick, no create, no delete. The worst a wrong call does is mark something done early — visible, attributed and undoable.
- It obeys the screen's rules. Admin-only subtasks, ones the workflow resolves itself, and enforced ordering are all refused.
- The client is never an argument. The run's client is fixed by your saved filter before the model is involved, so nothing in one client's data can point the work at another.
Read more
Client details that keep themselves up to date
Clients tell you things in passing: a new address, a new VAT number. An agent now reads their emails and post, spots what changed, and proposes the update — with nothing saved until someone approves it.
Agents that act, not just report
An agent that finds out the return was filed used to tell a person, whose next act was to tick the box saying exactly that. Agents can now tick it themselves, raise a draft invoice and write the email — inside fences worth understanding.
Point an agent at a job, not just a client
"Review every VAT return still in preparation" and "write to every client who has one" are different questions, and they need different answers. Agents can now be targeted three ways.
Saved steps: an agent library your firm can reuse
The instruction that took three attempts to get right should not live inside whichever agent happens to have it. Save a step once, drop it into any flow — and it copies rather than links, on purpose.
Questions
What is an AI agent in AccountingFlow?
An agent is a job you describe once and point at a list of clients or jobs. It works through them on a schedule, decides case by case, and reports what it found. You build it from an example in the app — no developer, no integration project.
Can an agent change client records or send emails on its own?
No. Agents draft and propose; a person approves. Emails and invoices are created as drafts, and a proposed change to a client record shows what the record says now, what it would say and why, and saves nothing until someone at the firm approves it.
What can an agent actually do?
Read a client’s emails, post and job history; chase records before a deadline; spot details that have changed on a client record; tick off a job’s subtasks once the work is done; raise a draft invoice from unbilled time; and write the covering email, including when none of your templates fits.
How do I control what an agent is allowed to do?
Writing is off by default and set per agent. An agent can only tick subtasks, never untick, create or delete them, and it obeys the same rules the screen does — admin-only subtasks and enforced ordering are refused. Every row it touches is labelled "Accounting Flow AI" with a timestamp.
When do agents run?
On the same repeat logic as workflow tasks: daily, chosen weekdays, a day of the month, the last working day of the month (stepping back off a weekend), or the nth weekday such as the second Tuesday. Narrow any of those to chosen months for quarterly or annual runs.
See what your firm could save
Two minutes, and it uses your own numbers.
Open the ROI calculator