AI Insights Financial Services
When Your Firm’s Website Gives Tax Advice No One Will Sign
Talk to Fred
Ask Fred about Financial Services
This is the same Fred you would put on your own site. Ask about Financial Services, compliance, or how the guardrails work. Fred listens.
A prospect lands on your firm’s website in March and asks the question everyone asks in March: can they write off the home office, and how should they handle the 1099 from a side gig? The chatbot, eager to demonstrate value, walks them through it. No preparer looked at their return. No one confirmed the facts the answer depended on. The prospect acts on it, the position is wrong, and when the notice arrives, the advice they followed came from the firm’s own website. The firm gave tax guidance it never reviewed and cannot stand behind.
Accounting feels like a safe place for a helpful bot because the questions sound general. They are not. Tax answers depend entirely on specifics, and the moment a website starts giving them, it is offering professional advice the firm is accountable for, under a body of rules a general-purpose model has never heard of.
A Tax Answer Is Professional Advice, Not Trivia
"Can I deduct that" has no honest general answer. It depends on facts the website does not have and a judgment the website is not qualified to make. A chatbot answers anyway, because resolving the question is its job, and what comes out is a position the prospect will rely on. Preparing or advising on returns is regulated work. Practitioners who advise on federal tax matters operate under Treasury’s Circular 230 rules of practice, and state boards license who may call themselves a CPA and offer this work. A website handing out deduction strategies is doing the firm’s regulated job without the firm’s judgment, and the firm wears the result.
Client Data Has Its Own Statute
The friendly intake is its own trap. To answer anything useful, the bot draws out income, filing status, the messy details of someone’s finances, and tax return information carries a specific federal protection. The rules under Section 7216 of the tax code restrict how a preparer may use or disclose a client’s return information, with real penalties attached. A generic widget that funnels those details into a vendor’s system, outside the firm’s controls, can turn a convenience feature into a disclosure problem the partners did not sign up for.
"Helpful" and "Defensible" Are Not the Same Thing
Here is the gap that catches firms. A bot is built to give a confident, complete answer. A good preparer is built to ask three more questions before giving any answer at all. When a prospect pushes, "just ballpark it, can I deduct this or not," a chatbot steered by a prompt eventually obliges, because being helpful is its default. That is the difference between a tool told not to give tax advice and one built so it cannot. A disclaimer under the chat box does not stop the system from answering the version of the question it was not specifically warned about, and it does not make the answer defensible if a client relied on it.
Who Owns the Answer
A junior staffer who gave a client a deduction strategy without a partner’s review would be a training problem the firm fixes immediately. An unsupervised chatbot gives that strategy at scale, in writing, with no preparer in the loop and client data possibly sitting where it should not. The accountability does not transfer to the software vendor. It stays with the firm, which now has a transcript showing it advised on a tax matter no one signed off on, under rules that assume a credentialed person is responsible for the work.
The firms that get burned are not the ones that put a smart assistant on their site. They are the ones that let it answer "can I deduct this." The fix is an assistant that captures the engagement, answers logistics and scheduling, protects client information, and routes every substantive tax question to a preparer who can actually own the answer.
Frequently asked questions
Can an AI chatbot answer tax questions on my firm's website?
Not the substantive ones. Whether something is deductible or how to handle a specific form depends on facts the website does not have and judgment it is not qualified to make, and giving that advice is regulated work under Circular 230 and state CPA licensing. A bot that answers anyway is doing the firm’s professional job without review, and the firm owns the outcome. Use the assistant for scheduling and intake, and route real tax questions to a preparer.
What client-data rules apply to an accounting chatbot?
Tax return information is protected under Section 7216 of the tax code, which limits how a preparer may use or disclose it and attaches penalties for getting it wrong. A chatbot that collects income, filing status, and financial details and routes them into a generic vendor’s system can move that information outside the firm’s controls. Any client-facing chat has to be built to keep return information protected, not bolted on without regard for it.
Isn't a disclaimer enough to cover tax advice from a bot?
No. A disclaimer does not change what the system does when a prospect presses for a yes-or-no answer, and it does not make the advice defensible once a client has relied on it. The exposure is the substance of the answer and the data it collected, not the fine print beneath the chat. The reliable protection is an assistant built so it cannot give the advice in the first place, and that hands those questions to a person.
