Will AI replace accountants?
No, and the reason is the one that makes this a profession rather than a service. The longer answer is about who it does replace.
No. What AI compresses is preparation — data entry, document chasing, first-draft workpapers, reconciliations — not the part where somebody signs. Circular 230 section 10.22 places a due diligence obligation on the practitioner that no vendor can hold, and the preparer penalties under IRC sections 6694 and 6695 attach to a person. The accountants who lose ground will lose it to accountants using these tools, not to the tools.
Where the technology actually falls.
Not by job title. By whether a task produces material or carries responsibility for it.
Preparation
- Data entry, document collection and chasing what never arrived
- First-draft workpapers and the reconciliations behind them
- Extracting figures from statements, K-1s and brokerage packets
- Prior-year comparison and the what-is-missing list
- First drafts of client correspondence and notice responses
Signing
- Taking a return position and standing behind it
- Exercising due diligence under Circular 230 section 10.22
- Judging whether an answer that looks right actually is
- Carrying the preparer penalty when it was not
- Telling a client something they do not want to hear
Software cannot hold the obligation.
Most answers to this reach for the client relationship, which is true and is a claim about preference. The durable reason is that the obligation is personal by construction.
Circular 230 section 10.22 requires due diligence as to the accuracy of returns and documents, and it is owed by the practitioner. IRC section 6694 penalises an understatement due to an unreasonable position; section 6695 covers the procedural failures. None of them has an exception for where the draft came from. The IRS Office of Professional Responsibility said as much when it addressed generative AI in OPR Alert 2026-19: the output is a starting point, not a finished product.
That is not an argument against using these tools. It is the reason a person stays in the loop, which is a different thing from the reason vendors usually give.
The honest part of the answer.
Partners and signers are not the ones at risk. The exposure sits in roles whose work is mostly preparation and data handling, which is exactly what these tools are good at — and in the profession those roles are also the training ground.
Anyone telling firms this is purely additive is skipping that. Saying it plainly is more useful, because the firms that plan for it handle it better than the firms it surprises.
If AI does the prep, how does anyone learn to sign?
Preparing returns badly for a couple of years, and being corrected line by line, is how a preparer learned what mattered. The review-note cycle was not overhead on the training; it was the training. Automate the first draft and the instruction goes with it.
A firm can find itself several seasons in with faster throughput and nobody coming up who can tell whether the throughput is right. That is a staffing decision being made by default, and it lands harder here than in most professions because the licence assumes somebody can do the underlying work.
The firms handling it are inverting the junior role on purpose:
- New staff review and correct AI output rather than producing it. Finding the error teaches more than avoiding it did.
- The correction is explicit and said out loud, which is what used to happen in the margin of a draft.
- A slice of returns stays manual, not because the tool cannot do them but because someone has to learn to.
- Whoever signs can still do the work unaided. A reviewer who cannot produce the thing cannot judge it either.
The practical version.
Automate the assembly and be deliberate about the instruction you are removing. Settle what may reach a vendor before any of it starts — the section 7216 consent is the gate, and it is criminal rather than advisory.
Then write down who reviews what. That sentence is the supervision record and the training plan at the same time.
Get the next one.
Field notes from real deployments, written the way this one was. No schedule promised and nothing sold to you. Unsubscribe whenever.
Sources and standing.
Circular 230 section 10.22 is the due diligence obligation. IRC sections 6694 and 6695 are the preparer penalties. IRS OPR Alert 2026-19, issued June 2026, is the Office of Professional Responsibility's treatment of generative AI under Circular 230. Clinco v. Commissioner, T.C. Memo. 2026-16, is the Tax Court on fabricated citations. Last reviewed at source: September 2026.
No adoption or job-loss statistics appear on this page. The figures circulating on this topic recur word for word across unrelated sites and none of them trace back to a primary source, so none are repeated here. This is not legal advice. If something here is wrong, tell me and it gets corrected.
Keep reading
Build with us in Milwaukee.
Thirty minutes, one real constraint, and a written description of what could be built. No pitch decks, no small talk.