Last updated: May 30, 2026
A client emails you on a Tuesday night. Attached is a list of “8 problems” ChatGPT found with the partnership return you just filed. You read the first one and see the bot insists the EIN on the K-1 is wrong because it should “match” the recipient’s EIN. It shouldn’t. None of the eight are real. But now you have to write back, explain why a computer sounded so sure and got it all wrong, and do it without making your client feel foolish for asking.
That’s a real scenario a CPA described on tax Twitter this month, and the replies filled up with peers saying same here, every week. The “my client brought me a wrong AI answer” headache has quietly become one of the most common in the profession — and it’s landing right as Q2 estimated taxes come due on June 16, 2026, the busiest client-question stretch of late spring.
What actually changed
Clients didn’t suddenly get bolder. They got a tool that sounds like an expert. Around 76% of accountants and bookkeepers say more of their clients are now running tax and financial questions through ChatGPT and similar tools. Roughly 70% have had a client use an AI-generated answer to question or challenge their professional advice. And the errors aren’t rare — in one survey of 500 firms, half were aware of businesses that took a direct financial hit (overpayments, penalties, missed allowances) from wrong AI advice.
Here’s the part that stings: only about 5% of tax pros have brought AI into their own workflow. So in a lot of firms, the client is the more aggressive AI user — just without the training to spot when the output is nonsense.
Why is a general chatbot so confident and so wrong about tax? Because tax isn’t trivia. It’s multi-step, context-heavy reasoning, and the model is usually working from training data that’s months out of date, with no idea what state your client lives in or how their entity is structured. When you look at hundreds of these “the AI told me…” moments, the mistakes fall into the same six buckets:
- Outdated tax-year rules — last year’s brackets, an expired provision, a phased-out limit.
- Hallucinated code citations — an invented Internal Revenue Code section, or a real one that doesn’t say what it claims.
- Federal vs. state conflation — blending federal rules with state law, or applying one state’s treatment to a client elsewhere.
- Wrong filing status or deductions — recommending a deduction the client doesn’t qualify for.
- Entity-structure mix-ups — fumbling S-corp, partnership, or sole-prop rules (K-1 logic, reasonable comp, basis).
- Missing the multi-year picture — a clean single-year answer that ignores carryforwards, recapture, or an election that bites later.
That K-1 “EIN mismatch” your client flagged? Bucket five. The bot pattern-matched two ID numbers and decided they should be equal. A first-year staff accountant knows better. The model doesn’t.
The 4-step way to handle it (without losing the client)
The instinct is to fire back a one-line “that’s wrong, trust me.” Don’t. A defensive reply makes the client trust the bot more — now it’s your word against a tool that gave them three confident paragraphs. The pros who handle this well treat it as a small advisory engagement, not an insult.
Step 2 is the one you can’t skip: pull the actual IRC section, IRS publication, or form instruction and confirm the real rule yourself before you reply. Step 3 is where most of the time goes — and it’s exactly the kind of clear, polite, sourced writing AI is genuinely good at, once you’ve nailed the answer.
That last point is the move almost nobody in the profession is making yet. The online consensus among CPAs is “review it by hand and bill for the aggravation.” Fair — and you should bill for it. But you can cut the writing time in half by letting AI draft the explanation after you’ve done the thinking, then checking it before it goes out. Here’s a prompt to keep on a sticky note:
You are helping a CPA write a short, friendly reply to a client.
The client used an AI tool and got this answer:
"""
[PASTE THE CLIENT'S AI ANSWER — remove any names, SSNs, or EINs first]
"""
The correct rule, which I have verified against primary authority, is:
"""
[PASTE THE ACTUAL RULE + the IRS publication or IRC section you confirmed]
"""
Write a 150-word reply that:
- Thanks the client for checking
- Explains, in plain English, the ONE main place the AI went wrong
- States the correct treatment and cites the source I gave you
- Stays warm and non-defensive, and offers to walk through it on a call
Add no tax advice beyond the verified rule above.
That last line matters. You’re using AI as a writer, not a tax authority. The facts come from you; the model just shapes them into something kind and readable.
The one rule you cannot skip
Before you paste anything into a chatbot, look at what you’re pasting. Under Circular 230, you’re responsible for every position you take, whether a human or a machine drafted it — “the AI said so” is not a defense. And under IRC §7216 plus the AICPA Code of Professional Conduct, client tax information is confidential. You can’t drop a client’s real return data into a public AI tool that trains on its inputs.
The simple version: ask AI about the rule, never about the client. To use AI on actual client data, move to a business or enterprise tier with a data-protection agreement that keeps your inputs out of training.
What this means for you
If you’re a solo practitioner: This is your moment to look more responsive, not less. A same-day, sourced reply that gently corrects the bot is a trust-builder a big firm can’t match. Keep the prompt ready and you’ll turn a 30-minute annoyance into a 10-minute billable touchpoint.
If you run a small firm with staff: Write a one-paragraph internal policy now — what staff can paste, what they can’t, and the “verify against primary authority first” rule. The risk isn’t your seniors; it’s a junior pasting a client’s K-1 into a free chatbot to save time.
If you’re a bookkeeper, not a licensed preparer: Your best line is a referral. When a client’s AI answer wanders into tax-position territory, the move is “let’s get your CPA to confirm this one” — and AI can help you write that handoff cleanly.
If you’re heads-down in deadline season: With Q2 estimates due June 16, the AI-question volume is about to spike. Batch them. A saved prompt and a folder of your most-cited IRS pubs will save you hours.
What this won’t fix
- It won’t make you compliance-proof. Circular 230 puts the position on you. Verify every fact before it leaves your office.
- It won’t change a client who wants the wrong answer. Some people are AI-shopping for permission. Document your correct advice clearly; don’t try to win the argument.
- It can’t replace checking primary authority. Skip step 2 and you’re just laundering a guess through nicer prose.
- It won’t protect data on the free tier. Anonymize, or use a protected plan. There’s no shortcut around confidentiality.
- It won’t repair trust if you’re dismissive. The tone in step 1 does more work than the citation in step 3.
The bottom line
Clients bringing you confident, wrong AI answers isn’t a fad that fades after this season — it’s the new normal, and the firms that handle it gracefully will quietly win the relationships. The skill isn’t “knowing more than the bot.” You already do. It’s responding fast, sourcing your answer, and explaining it like a human who’s on the client’s side. AI can help you do the last part faster, as long as you stay the one who decides what’s true.
If you want to go from defending against AI to actually using it — safely, on the right tasks — our AI for Accountants & Finance course walks through it without the jargon or the coding.
Sources
- CFOtech — ChatGPT tax advice already costing firms, say accountants
- Dext — Businesses losing money to ChatGPT-style tax advice (survey of 500 firms)
- Journal of Accountancy — How will accountants learn new skills when AI does the work
- CNBC — I asked ChatGPT for tax help; experts say I fell into a classic trap
- IRS — Circular 230, Regulations Governing Practice before the IRS
- IRS — Second quarter estimated tax (due June 16, 2026)