Operations

Retaining senior accountants starts with the work beneath them

Retaining senior accountants is rarely about pay alone. Look at how much of their week is recurring, rule bound work, and give that away first.

Beaks · · 5 min read

Ask a managing partner what worries them most and many will name the same thing: losing a senior accountant. The person who knows the awkward clients, reviews the tricky files and holds the close together. Retaining senior accountants is usually discussed in terms of pay, flexibility and progression. Those matter. But there is a quieter question that rarely gets asked: how much of your best person's week is work that is beneath their skill level, and has been for years?

The argument of this post is simple. In most firms, a large share of a senior person's week is recurring, rule bound work that nobody ever took off them. Finding that work and giving it away first is one of the few retention moves that also makes the firm more resilient.

How a senior week fills up

Nobody designs a senior accountant's week. It accumulates. A task lands with someone because they were the one who set it up, or because a client trusts them, or because it went wrong once and they fixed it. Years later they are still doing it, long after the work stopped needing their judgement.

Take a hypothetical senior at a 30 person bookkeeping firm. Their week, written out honestly, might include:

  • Reviewing management accounts for six clients, and talking two of them through the numbers.
  • Answering junior questions on unusual transactions.
  • Running the same three bank reconciliations they have done since they joined, because the clients are "theirs".
  • Preparing the monthly payroll check pack for a large client, which follows the same steps every month.
  • Chasing missing supplier statements for the purchase ledger.
  • Rebuilding a client report in a spreadsheet because the template breaks when a new cost centre appears.

The first two items are the reason the firm hired a senior. The rest are recurring tasks with clear rules. They are not unimportant, and some of them carry real risk if done badly. But none of them need ten years of experience every single time.

Count it, do not guess it

If you want to know how much of the week falls into the second group, you have to look. Guessing tends to go wrong in both directions: partners assume seniors spend most of their time on judgement work, and seniors, when asked, often underestimate how much routine work they carry because it has become invisible to them.

An illustrative way to do it: take one senior, list every recurring task they own, and for each one note how often it runs, roughly how long it takes, and whether the steps are the same each time. Say the list comes to 14 tasks and about 18 hours a month on the rule bound ones. That is an illustrative figure, not a benchmark, but if your own count lands anywhere near it, you have found more than two working days a month of capacity sitting at senior rates.

We described a fuller version of this exercise in how to build a recurring task list in a week. For this purpose, one person and one afternoon is enough to start.

Why the work beneath them matters for retention

There is no need to invent statistics to see the mechanism. Talk to anyone who left a firm at senior level and you will often hear some version of the same story: the interesting work kept getting squeezed by the work that had to be done regardless. Month end arrives, the routine tasks take priority because they have deadlines, and the review, advice and training work gets done in the evening or not at all.

Recurring work has a particular quality that makes this worse. It never finishes. A one-off piece of dull work ends. A monthly reconciliation that has been yours for six years will be yours for the next six, unless someone deliberately moves it. People notice that.

So the retention question is not only "are we paying them enough?" It is also "are we using them for the work they are good at, and can they see a way out of the rest?"

Giving the boring half away first

Moving routine work off a senior's desk is straightforward to describe and easy to get wrong. A few principles help.

Document before you move

A task can only go to someone else, person or agent, if the know-how comes with it. The senior is usually the only one who knows why the payroll pack checks that particular variance, or which client's bank feed arrives late. Capture that while they still do the work, not in a handover rush. Recording the task once as it is done is often quicker than writing a manual from scratch.

Do not strip the training ladder

Some recurring work is how juniors learn. Reconciliations and ledger runs teach a trainee how a client's business actually behaves. Moving those tasks to a junior, with a documented method and a senior review, can be a promotion for both people. The senior moves up to review and advice. The junior gets real work with a safety net. Be careful not to hand every learning task straight to an agent and leave juniors with nothing to grow on.

Start agents on drafts

Where a task is rule bound and well documented, an AI agent can take on the preparation while a person approves the output. That is the approach set out in drafts first, trust later: the agent earns more freedom task by task from its own track record. For the senior, the change is that they review a prepared draft instead of building it from nothing.

Say it out loud

Tell the senior what you are doing and why. The goal is to give them back time for the work they were hired for, and to make sure no one person is the only route to a client's month end. If the move is framed as taking the dull half of the job away, people tend to welcome it. If it happens quietly, people assume the worst, and they would be right to ask.

The resilience bonus

There is a second reason to do this. The routine work held by your most experienced people is often the work held by only one person. That is key person risk in its purest form: if they leave, the know-how leaves with them, and nobody can step in, human or agent. Documenting and moving those tasks is a retention move and a continuity move at the same time. The work Beaks is built around, an inventory of recurring tasks with owners and manuals attached, is meant to make exactly this visible.

One thing to do this week

Sit down with one senior person for an hour. List every recurring task they own, and mark each one either "needs your judgement" or "follows the same steps every time". Pick the most frequent task in the second group and agree, together, who it should move to and what needs writing down first. Then put a date on it.

← 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