AI readiness

Which accounting tasks to automate first: five signs, three warnings

Deciding which accounting tasks to automate first? Five signs a task is ready for an AI agent, and three signs it needs more work before anyone hands it over.

Beaks · · 5 min read
Fountain pen resting on old lined paper beside white flower petals

Most finance teams that try AI pick the wrong first task. They pick the one that annoys them most, or the one a vendor demo happened to show, and then spend three months finding out why it was harder than it looked. Deciding which accounting tasks to automate first is not a technology question. You can answer most of it by watching the work for a week. This post gives five signs that a task is ready for an agent, and three signs that it is not ready yet, all of which you can check without buying anything.

If you want a fuller method, we scored one task step by step in can you automate the VAT return?. The signs below are the shortcut: things you can see from the outside before you sit down to score anything.

Five signs a task is ready for an agent

1. Two people describe it the same way

Ask the two people who do a task to explain it, separately. If their steps match, in the same order, with the same checks, the task has a method rather than a habit. That method can be written down, and anything written down clearly can be followed by a colleague or an agent. If the descriptions differ, the first job is agreeing on the method.

2. Checking the result is quicker than producing it

A bank reconciliation might take an hour to prepare and ten minutes to review. A supplier statement match might take forty minutes to do and five to check. When checking is much faster than doing, an agent can draft and a person can approve, and the time saved is real even before the agent is trusted to work alone.

When checking takes as long as doing, the saving disappears into review. Those tasks come later.

3. The inputs arrive in the same place and the same shape

Bank feeds, a monthly payroll export, invoices in one shared inbox, a trial balance from the same report every month. Predictable inputs are the strongest single sign of a task an agent can start on.

Watch for the opposite: "the client sends it somehow, usually by email, sometimes on WhatsApp". That task needs a better intake before it needs an agent.

4. Someone has written down what done looks like

Not the steps, the finish line. "Reconciled, with every unmatched item over a set amount explained, and the explanation filed against the transaction." A task with a clear definition of done can be reviewed against it, by a manager or by the person who used to do it. A task whose finish line is "when it looks right" cannot.

5. Mistakes are caught before they leave the building

Ask what happens if this task goes wrong. If the answer is "the review catches it", or "the variance shows up in the management pack and someone asks", the blast radius is small. Start there. Tasks whose mistakes go straight to a client, a bank or a tax authority wait until the quieter tasks have built a track record.

Three signs a task is not ready yet

None of these mean "never". They mean "fix this first", and the fix is usually useful whether or not an agent is ever involved.

1. The answer to every question is "it depends"

Sit with the person who does the task and count how often they say "it depends" or "you'll know when you see it". Each one is a judgement call that lives in their head. A few are fine, and they can stay with a person. If the whole task is made of them, the hours are in the exceptions, which is usually where the cost sits too.

The fix is to write down each "it depends" as a rule, or as a named exception that a person keeps. Over a few months, most turn out to be rules nobody had written.

2. Only one person has ever done it

If one person runs a task and nobody else has done it in the last year, nobody can write instructions for it except that person. That is a continuity problem first, which we covered in the bus factor of a 40 person accounting firm, and an automation problem second. A task that cannot move to a colleague cannot move to an agent either.

The fix is a backup, trained by the owner, who writes the manual as they learn. By the time the backup can do the task, it is documented.

3. The task is about to change

A move to new accounting software, a new client portal, a restructure of who does what. Automating a task that will look different in six months means doing the work twice. Run the new version for a couple of cycles, then look again.

A hypothetical first pass

Take a hypothetical bookkeeping firm with around 30 recurring tasks on its list. Run the eight questions above against each task and a rough pattern tends to appear.

  • A handful pass all five signs and hit none of the warnings. Usually things like coding bank transactions against known rules, preparing reconciliation drafts, chasing missing receipts, or assembling a standard monthly report from the same sources. These are where an agent starts, drafting while a person approves.
  • A larger group passes most signs but fails on documentation or definition of done. These are a writing job, not an AI project.
  • A few hit the warnings. Year end judgement calls, unusual tax treatments, the client only one partner really understands. They stay with people, and the first step is getting the know-how out of a single head.

Your numbers will differ. The shape is what matters.

Do it with the people who do the work

Run this exercise with the team, not about them. The people who do these tasks know which ones they would happily never touch again, and they know where the "it depends" sits. Tell them plainly what the list is for: finding the boring half of the work to hand over first, so that more of their week goes to the judgement calls and client work that need them. A list built in the open is also an honest list, and an honest list is the only kind worth automating from.

Collecting these signs for every recurring task, from the work people already do, is what we are designing Beaks to do. For a first pass, a spreadsheet with your task list down the side and eight columns across the top is enough.

One thing to do this week

Pick five recurring tasks your team runs every month. For each one, answer the eight questions above with a yes or no, in front of the person who does the task. Circle any task with five yeses on the signs and no warnings. That is your first candidate. For everything else, write down which question failed: that is your to-do list, and most of it is writing.

← All posts

Know what your team actually does.

Beaks holds every recurring task, writes the manual as people work, and shows which work is ready for AI.

Request early access

Keep reading