When should you use it?
- Your return includes a small business
- Revenue or expenses come from several sources
- You suspect double counting
Not for: Tax advice on positions; Complex entity returns without a professional
What do you need, and what do you get?
You need
- Bank statements
- Receipts
- Revenue reports
You get
- Reconciled spreadsheet
- List of duplicates and questions
How does it work, step by step?
- Gather recordsStatements, receipts and revenue reports for the year.
- Build one ledgerEach transaction once with its source document.
- Find duplicatesFlag items that appear in more than one source.
- Reconcile totalsMatch ledger totals to bank statement totals.
- ReviewTake questions to your preparer before filing.
The prompt
Our own prompt, inspired by u/stormy1one on r/ClaudeAI and written to work in Claude and ChatGPT. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
Here are transactions from {sources}.
Build one ledger with date, amount, counterparty, category and source document.
Flag likely duplicates across sources with reasons. Reconcile monthly totals to bank statements and list differences.
Do not give tax advice; list questions for a preparer.Inspired by u/stormy1one on r/ClaudeAI: Anyone else doing taxes with Claude?. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Do not rely on the assistant for tax positions.
- Check calculations in the spreadsheet, not in chat text.
Our take
The win in this post is catching double counting, the classic mistake when revenue flows through several systems. Keep the core rule: every figure ties to a statement you can open. Build one ledger, hunt duplicates, then reconcile totals before anything enters tax software. Judgment calls about tax treatment belong with a preparer, not with a chat model. Feed bank exports and receipts as files, not paraphrases from memory. Triple-check formulas in the spreadsheet. When attribution of clients looks wrong, fix the source data rather than papering over it in the return. Keep an audit folder with the final ledger, source statements and notes on every adjustment. Do not e-file until a human with tax literacy has reviewed elections and checkboxes. If the LLC has employees or multi-state issues, stop and get professional help sooner. Re-run the reconcile after any late 1099 arrives. Schedule a calendar reminder the week before filing to re-check late documents.
Where the time goes back: Duplicates and gaps are found before filing, not after.
FAQ
Can it file my taxes?
Is my data safe?
Source and credit
Inspired by u/stormy1one on r/ClaudeAI. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- Anyone else doing taxes with Claude?
- Creator
- u/stormy1one on r/ClaudeAI
- Published on
- Original date
- Mar 15, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Claude
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.