Use case #4 · CPA
Controller automates tax prep end-to-end with Claude Code and the tax software's REST API
- Tax prep
- Advanced
- Claude Code (Enterprise plan), Thomson Reuters tax software REST API
- Source checked · practitioner blog
The short version
What they did
Transform trial balances, transaction detail and investor allocations into tax-ready data with code, then push data entry, return creation and e-file status through the API.
Result (as claimed)
“This is the first year the work looked fundamentally different.” “Almost anything you can do as a human inside the software can also be replicated and done by a machine through the API.”
Prompt
I’m a controller using Claude Code to turn trial balance data into a draft return file. I’ll provide [tax software API documentation], [trial balance export], [reviewed account-to-return-line mapping] and [return type and tax year].
1. Read the documentation and confirm which fields the draft return requires. Ask about missing mappings before coding.
2. Write a script that reads the export, applies only my mapping and produces the data file required by the API.
3. Include a log showing each source account, amount and destination line, plus checks that totals agree with the trial balance.Explain how to run and test it using [a past return with known answers]. List unmapped accounts and missing fields separately. Don’t invent tax classifications, send data to the API, create a live return or e-file anything. The first output is a local draft for review.
Do it yourself
These steps are my suggested way in, not Tofique Elder’s setup.
Level: Advanced for pushing data through a tax software API. Mapping a trial balance in a chat is Beginner.
What you need
- A chat assistant that reads spreadsheets.
- A past year’s trial balance and your account-to-return-line mapping.
- For the full version: Claude Code or another coding agent, and API access to your tax software.
Start simple
- Take last year’s trial balance for a return you already filed.
- Ask the assistant to map each account to a return line and explain each choice in a column.
- Compare its mapping with the filed return line by line.
- Fix the mapping table and keep it as the starting point.
Take it further
- Have a coding agent turn the mapping into a script that outputs the import file your software accepts.
- If your software has an API, use the Prompt and start with read-only calls before any data entry.
- Keep a log of every mapping decision so a reviewer can trace it.
Check your work
- Tie the script’s totals to the trial balance before anything goes into the return.
- Run it on a filed return first and compare every line.
- Never let a script e-file. A preparer and reviewer still sign every return.
Before you rely on it
- This is general information about how accountants use AI, not professional guidance for your engagements.
- You stay responsible for the work under your professional standards, including review and sign-off. An AI tool’s output is a draft, not evidence.
- Before you send client data to an AI tool, read the tool’s data and training terms, and get any client consent you need. For tax return information, that includes IRC section 7216.
Source checked. The link, author, date and quote were confirmed against the source. The result itself has not been reproduced. Prompt adapted for this library, inspired by the case. Business size: In-house tax team (Masterworks). Results are quoted as the source claimed them and never improved. Spot an error or a broken link? Email charlie@cbarmorecpa.com.