Claude for Tax Preparation: What It Does for a Tax Practice

The common question is whether Claude can do tax prep. It's the wrong shape of question. A return is dozens of small jobs, and only some of them are reading and drafting.

The useful question is narrower. Which part of the work goes to which Claude product, and under which account. The Reviewer still signs at the end.

This piece sorts that out for a CPA or EA firm. It names each product in the vendor's own words and maps it to the prep tasks where a draft helps. Then it lists the guardrails to set before any client folder goes near it.

The Claude products a tax practice meets

There are several, and they get mixed up. Here is each one as Anthropic describes it, with nothing added.

Cowork. Anthropic's Cowork help page says: "Cowork is available to paid Claude plans (Pro, Max, Team, Enterprise) only." The same page says: "On desktop, Claude can read from and write to your local files without manual uploads or downloads." For a tax practice, that second line is the one that matters. Which folder you point it at is a decision someone at the firm makes on purpose.

Claude Code. Anthropic's overview page says: "Claude Code is an agentic coding tool that reads your codebase, edits files, runs commands, and integrates with your development tools." A firm might point it at the scripts around prep: renaming scanned files, building a checklist from a folder listing, reshaping an export. Treat that as tooling for the office. Return figures get decided elsewhere.

Computer use in Claude Code. Anthropic's computer use page says: "Computer use is a research preview on macOS that requires a Pro or Max plan. It is not available on Team or Enterprise plans." Read both sentences before anyone plans around it. The vendor labels it a research preview, and the plan line rules out Team and Enterprise.

The chat window. This piece quotes no vendor line about it. The rule is the same as for the others: check which account it runs under before anything from a client file goes in.

No ranking. Each one fits a different job, and some fit none of yours.

Where a draft helps in prep work

What follows is a method, not a vendor claim. Each task produces a draft. The Preparer checks it against the source before anything moves.

For the folder tasks, the quoted line that covers local files is the Cowork one. The office-script work above is where Claude Code's own description points.

Listing what's in the folder. Point the tool at a Doe practice folder and ask for an inventory: file name, document type, issuer, period, page count. Ask it to flag duplicates, drafts sitting beside finals, and anything outside the named client or period. Then the Preparer opens the folder and confirms the list matches. An inventory is only useful if every line is checked against a real file.

Pulling figures with page citations. Ask for every figure with its source row, including a "could not find it" status as an allowed answer. The full request and the check that follows it are in the guardrails below. Don't skip that check because the rows look tidy.

Drafting a missing-items request. Give the tool your organizer checklist and the confirmed inventory. Ask it to list what the checklist expects and the inventory doesn't show, then draft a plain request to the client. The Preparer edits it, removes anything already received, and decides what actually goes out. A missing-items list built from an unchecked inventory can repeat the inventory's mistakes.

Comparing to prior year. Give it last year's confirmed figures and this year's cited figures for Jane Doe. Ask for a side-by-side with each change marked and both sources cited. Ask it to list items that appeared last year and have no match this year. The Preparer reviews each flagged change and decides which ones need a question to the client. Treat the comparison as a pointer to places to look, not as an explanation of them.

In every one of these, the output is a starting draft. Write your prompts and your office procedure as checks a person runs, not as trust in what comes back.

What stays with the Preparer, the Reviewer, and the tax software

This part is about how the practice runs. No tool changes it.

The return is computed in the Firm's tax software. The Preparer keys it from checked figures. The Reviewer reviews it and signs off. Nothing in the drafting steps above signs anything. Nothing a chat or folder session produces counts as a workpaper until a person checks it and moves it there.

Treat a step as incomplete until its record names the person who checked it.

Account terms before client data

Before a single client file is opened, settle which account the work runs under.

Anthropic's page on model training says: "This article is about our commercial products such as Claude for Work and the Anthropic API." It then says: "We will not use your chats or coding sessions to train our models, unless you choose to participate in our Development Partner Program."

Two things to note. That line is scoped to commercial products, so don't read it as covering any other account type. And it is about training, not every question a firm has about how data is handled. Read the vendor's current terms for the account you actually use, and confirm whether anyone at the firm has opted into that program.

Where computer use comes up, recall the plan line quoted above: it names Pro or Max and excludes Team and Enterprise. Square that against the account your firm has approved for client work before anyone tries it.

Guardrails a firm sets first

These go in writing before the first live folder.

1. Name the account. One approved account type for client work, chosen after reading its terms. Check whether your account takes part in the Development Partner Program. Personal accounts stay out of client folders.
2. Name the folders. Point the tool at a copy of one client's folder for one period, not the original. Keep other clients' folders outside its reach, and check each cited file against the named client and period.
3. Practice on Doe files first. Run every new prompt on a Doe Holdings practice folder before it touches a real one. Revise the prompt on Doe files, then check the output again.
4. Require citation rows. No figure without a citation row. The request and the check are in the citation piece; apply them to every extraction.
5. Name who checks. The Preparer checks drafts. The Reviewer reviews the workpaper. Write down who checks each extracted figure against its cited source before use, and who reviews the resulting workpaper. What the Reviewer needs from the file is laid out at for reviewers.
6. Decide where the trail lives. Copy the prompt, the citation rows, and the checker's initials into the workpaper. A chat session isn't the file of record.

For the bookkeeping side of the same tools, see Claude for accounting. This piece stops at returns work.

Where TracePrep fits

In TracePrep's Reasonable Compensation Study, every figure traces to its source, occupation, geography, and period, at field level. A Reviewer signs off on each Study, and the audit log records who prepared it, who changed what, and who approved it. Finalized evidence stays with the Firm.

This is general information, not tax or legal advice. Your licensed professional and your Firm's Reviewer are responsible for every return and every conclusion. Keep client data inside the systems your Firm has approved. As general guidance only, not advice: if you use an AI tool with client data, firms generally look for a business or commercial plan whose terms cover how that data is handled; read the vendor's current terms before you do.

Join the waitlist