This question usually arrives in one of two moods. Either you are hoping the answer is yes, because the line item is annoying and the work looks mechanical. Or you employ someone you like and you are wondering whether you are about to have an uncomfortable conversation.
The honest answer is that the job is being hollowed out from the middle, not eliminated from the outside. Which half gets hollowed matters more to you than the headline.
Separate the job from the typing
Most people picture bookkeeping as data entry, and data entry is exactly the part that automates. If that is genuinely all your bookkeeper does, then yes, that work is going to shrink and keep shrinking.
But sit with a competent one for a month and the typing is not where the time goes. The time goes into the questions nobody else is asking:
- This invoice says consulting. Consulting on what, for which project, in which period?
- The owner paid for this personally. Is it a business cost, a reimbursement, or a draw?
- This vendor was paid twice. Is it a duplicate, a deposit and a balance, or two different jobs?
- Revenue is up and the bank balance is not. Which of those two numbers is wrong?
Every one of those is a question about the business, answered by someone who has context the ledger does not hold. Software can flag the anomaly. It cannot phone the project manager.
What the role becomes
The direction is away from recording and toward reviewing. The work that remains looks less like entry and more like control: setting the rules, checking that the automation applied them correctly, and handling the cases it could not.
| Shrinking | Growing |
|---|---|
| Keying transactions | Deciding the treatment for new ones |
| Matching line by line | Investigating what did not match |
| Chasing paperwork | Chasing the answer behind the paperwork |
| Producing the report | Explaining what moved and why |
That is a harder job than the one it replaces, and it needs someone who understands why the rules exist. A person who was only ever taught the clicks will struggle with it. A person who understood the accounting will be more useful than they were before, because the tedious part stops consuming their week.
If you employ someone today
Two failure modes are worth avoiding, and they pull in opposite directions.
The first is keeping the role exactly as it is while quietly adding tools around it. You end up paying for the software and the manual process at once, and nothing speeds up, because nobody was given permission to stop doing the old steps.
The second is cutting the role on the assumption that the software covers it, then discovering across the following months that the exceptions were the job. The errors do not announce themselves. They accumulate quietly until something forces a look, and the cleanup costs more than the salary saved.
The middle path is unexciting and usually right. Automate the recording, rewrite the role around review and exceptions, and be explicit about who now owns the parts the software does not. Written down, so it is a decision rather than an assumption.
The risk is not that software does the job badly. It is that nobody notices the job changed, and the review step quietly belongs to no one.
If you are hiring
The skills worth paying for have shifted. Speed and accuracy at entry are becoming less valuable, because the machine is faster and does not get tired. What is worth more:
- Judgment on treatment. Can they explain why a cost belongs in one period rather than another, without reaching for a rule they half remember?
- Willingness to ask. The worst outcome is someone who codes an unclear transaction confidently rather than raising it.
- Comfort with the tooling. Not enthusiasm for it. Comfort, plus the instinct to check what it produced.
- Clear writing. If they cannot explain a variance in two sentences, the reports will not help you decide anything.
The short version
AI is replacing a task, and the task was never the whole job. What it cannot replace is somebody being responsible for the numbers being right, and able to tell you what they mean.
If your current arrangement is mostly typing, expect it to change and plan for that. If it is mostly judgment, the tooling makes that person more productive rather than less necessary. Either way the thing to protect is the review step, because that is where the expensive errors get caught and it is the first thing to fall off when everyone assumes the software has it covered.