Can AI automate tax preparation?

AI can assist with the process around tax preparation, including document collection, status updates, and deadline monitoring. A qualified professional should keep control of tax positions, substantive review, client advice, and filing approval.

When should a firm implement tax-season automation?

Start early enough to map the workflow, test representative historical cases, train staff, and run a supervised pilot before peak volume. The required lead time depends on integrations, data quality, scope, and exception rates.

What is a sensible first tax-season workflow?

Client document collection is often a practical starting point because requests, reminders, receipts, and exceptions are visible. Measure current chase time and completion time before building so the firm can judge the result.

Tax season automation: What AI should and should not do

A practical plan for automating tax-season collection, status, and deadline work while qualified professionals keep tax judgment.

Tax-season automation should remove collection, routing, and status work without handing professional judgment to software. Start with client document collection or deadline monitoring. Keep tax positions, advice, review, and filing approval with qualified people.

The workload is large. The IRS expected about 164 million individual returns for tax year 2025 to be filed before the April 15, 2026 federal deadline. That national figure does not measure a firm’s workload, but it shows why tax processes need clear controls at peak volume.

Draw the boundary before choosing a tool

Step	Good automation role	Human responsibility
Build request lists	Pull required items from approved templates	Approve unusual or client-specific requests
Send reminders	Schedule approved messages based on missing items	Handle disputes, sensitivity, or relationship risk
Classify received files	Suggest document type and match it to a request	Resolve low-confidence or conflicting items
Monitor deadlines	Read status, flag risk, and prepare an escalation	Decide extensions, priorities, and client commitments
Answer status questions	Report approved workflow status	Answer tax questions and explain professional decisions
Prepare or file a return	Assemble evidence or route tasks	Make tax judgments, review the return, and authorize filing

The IRS Office of Professional Responsibility explains that Circular 230 sets standards of competence and diligence for practice before the IRS. A system can help prepare information, but the practitioner remains responsible for work covered by those standards.

Automate the chase

A Document Chaser can compare the approved request list with received files, send reminders from approved templates, and route genuine questions to staff. It should not invent a new document request or answer a tax question.

Measure the manual process before launch:

staff minutes spent chasing documents per engagement
days from first request to a complete package
number of reminders sent by staff
items misclassified or attached to the wrong engagement
exceptions that require professional judgment

These measures create a baseline. After launch, use the same definitions and the same type of engagements. A claim that the workflow is “faster” is not useful if the firm changed the population or stopped counting exception work.

Keep deadline monitoring read-only

A Deadline Sentinel can read the due date, current status, missing items, and assigned owner. It can then group routine items and escalate defined risks. It should not decide whether a return is complete or whether an extension is appropriate.

Read-only monitoring limits the consequence of an incorrect signal. Staff can correct a status or dismiss a false alert without undoing a filing or posting. The NIST AI RMF Core recommends defining the exact task, assigning oversight roles, and selecting risk measures before use. Those steps are especially important when tax-season volume rises.

A worked pilot plan

This example is a planning template, not a client result or a universal timeline.

Suppose a firm wants to pilot document collection on 40 similar individual-return engagements. It first measures last season’s chase time and completion time for a comparable group. The firm then tests the system on historical cases, including late documents, duplicates, illegible files, and client questions.

For the live pilot, the firm might require:

Control	Example acceptance rule
Scope	Only approved request types and message templates
Identity	Every document must match one client and engagement
Confidence	Low-confidence classifications go to a person
Communication	Tax questions receive no automated substantive answer
Audit trail	Every reminder, classification, override, and escalation is logged
Rollback	Staff can pause messages and resume the manual process

The thresholds should come from the firm’s risk tolerance and historical data. A small, supervised pilot is meant to reveal exception types before peak volume, not prove that the system can run without oversight.

Start before the rush

There is no reliable universal build duration. Timing depends on the firm’s systems, data quality, workflow scope, security review, and number of exceptions. Begin early enough to map the process, collect representative cases, test integrations, train reviewers, and observe a supervised production period before peak filing volume.

The Profitable Line Audit measures the current workflow and defines the control points. It gives the firm a baseline for deciding whether a tax-season build is worth doing.

Sources and methodology

The national filing figure and professional-responsibility boundary come from the IRS. The workflow controls apply NIST’s task, oversight, measurement, and monitoring principles. The pilot size and acceptance rules are illustrative and should be replaced with the firm’s own volume, historical cases, policies, and professional advice.