Claude is a good junior bookkeeper and a poor ledger. Give it a bank export and your chart of accounts and it will code transactions, explain each choice, find the items that do not tie and draft the month-end checklist. It should not be the system of record, it should not do arithmetic across hundreds of rows in its head, and it does not give tax advice. Use it for the judgement-and-writing half of the job, keep QuickBooks, Xero or a spreadsheet as the source of truth, and check every total against the bank.
What should you give Claude, and what should you never paste?
Bookkeeping prompts fail for one reason more than any other: Claude has to guess your categories. Give it these four things and most of the guessing goes away:
- Your chart of accounts. Account numbers and names, exported from your accounting software. Without it, Claude invents sensible-sounding accounts that do not exist in your books.
- Your coding rules. The ten vendors that make up most of your volume and where each goes. "Amazon = Office Supplies unless over $500, then ask me" is worth more than any instruction about accuracy.
- The period and the basis. Which month, cash or accrual, and the opening balance per the bank statement.
- The export itself as CSV. Date, description, amount, running balance. A CSV keeps the columns intact; a pasted PDF often does not.
What to strip first: full account and card numbers, routing numbers, tax IDs, and employee pay details you do not need for the task. Replace them with the last four digits. Claude does not need them to categorize anything, and a chat window is not where they belong.
Works from your bank and card exports and your QuickBooks or Xero ledger, codes each transaction to your chart of accounts, flags what it is unsure about instead of guessing, and hands you a close-ready trial balance.
Get the AI Bookkeeper →How do you get transactions coded the way your books expect?
Ask for a table, not prose, and make Claude separate what it knows from what it is guessing. The confidence column is the part that saves you time: you review the low ones and skim the rest.
Two lines in that prompt do most of the work. "Use only these" stops invented accounts. "Do not total anything" moves the arithmetic to a tool that cannot hallucinate a sum. If you need totals inside Claude, turn on code execution and ask it to compute them with code from the CSV, then compare the result with the closing balance on the statement.
How do you reconcile the bank against the ledger?
Reconciliation is matching, and matching is something Claude does well as long as you hand it both sides and tell it what counts as a match. Export the ledger register for the same account and period, then:
The last sentence matters. Asked to "reconcile", a model will sometimes produce a tidy zero difference by quietly treating an unexplained item as a timing difference. Telling it not to force the balance, and to lead with any gap, keeps the work honest.
A senior bookkeeper persona for small businesses: categorization with the reasoning shown, bank and card reconciliation, AP and AR entries, month-end close checklists and contractor tracking. She says plainly when a question needs a CPA.
Get Selma →How do you run a month-end close with Claude?
The close is where the hours go, and most of them are not arithmetic: they are remembering what to check, chasing documents and explaining movements. Claude is useful for all three.
Clearing accounts are the step people skip. Stripe and PayPal payouts arrive net of fees, so a clearing account that does not net to zero at month end usually means fees or refunds were never booked. Ask Claude to explain the leftover balance line by line rather than to fix it.
Where does Claude get bookkeeping wrong?
- Long columns of numbers. Without code execution it adds by predicting, not calculating. Any total it gives you in prose is a guess until a spreadsheet agrees.
- Invented accounts and rules. If your chart of accounts is not in the prompt, it will create plausible ones. Always paste it, every session.
- Tax treatment. Whether a meal is deductible, how a vehicle is depreciated, what a sales tax nexus is in your state: these depend on jurisdiction and change. Treat any tax statement as a question to take to your accountant, not an answer.
- Confident misreads of descriptions. "SQ *JOES" might be a coffee shop or a contractor paid through Square. The confidence column and your vendor rules exist for exactly this.
- Memory between sessions. It does not remember last month's decisions. Keep your rules in a document and paste them each time, or load them as a skill so they are always there.
Our longer piece on what AI bookkeeping automation replaces and what it does not covers the software side: bank feeds, receipt capture and where a model fits between them.
Buying a file is the right call if you need one specialist once. If you also need a controller, a cash-flow forecaster or a tax-prep checklist next month, the KissMySkills Library is cheaper: one connector puts all 2,500+ skills, prompt packs and agents inside Claude, ChatGPT, Claude Code or Cursor, and the skill loads when you ask for it by name. Library is $9 a month or $59 a year, starts with a free trial, no card needed, and you can cancel anytime.
Start your free trial Why a subscription beats buying files · See plansHow do you load a skill into Claude?
Two ways. With a one-time file, add it in the Claude app under Customize → Skills (code execution has to be on, under Settings → Capabilities), or paste its contents into a Claude Project's instructions, a ChatGPT custom GPT or a Gemini Gem. Our step-by-step install guide covers each app. With Library, you connect KissMySkills to Claude, ChatGPT or Cursor once, then ask for the specialist by name in the chat you already use.
For controllers, FP&A and reconciliation specialists, our Claude for accountants page lists the skills by task.
In summary:
Code transactions against your own chart of accounts with a confidence column, reconcile by handing Claude both sides and forbidding it to force a zero, and use it to write the close checklist and the email to your accountant. Keep totals in a spreadsheet and tax questions with a professional. For the full workflow in one agent: AI Bookkeeper ($39). For a bookkeeper persona across the whole cycle: Selma ($19). Both are also in Library at $9 a month.
AI Bookkeeper
Your bank export in, coded transactions and a reconciliation that shows its work out. Built for owners who do their own books and bookkeepers with several clients.
Or get it with every other skill in Library, $9 a month. Free trial, no card needed.
KissMySkills is a marketplace of 2,500+ AI skills, agents, prompt packs & free tools for Claude, ChatGPT & any AI chat.
Frequently asked questions
Can Claude do my bookkeeping?
It can do much of the work around bookkeeping: coding transactions to your chart of accounts, matching bank lines to ledger entries, building a close checklist and drafting notes for your accountant. It should not be your system of record, and its totals should always be checked in a spreadsheet or your accounting software.
Is it safe to paste bank statements into Claude?
Strip full account and card numbers, routing numbers and tax IDs first and keep only the last four digits. Claude needs dates, descriptions and amounts to categorize, not identifiers. Check your own plan settings and your firm policy on client data before pasting anything.
Does Claude work with QuickBooks or Xero?
Not as a direct integration in a normal chat. Export a CSV of the bank feed or register from QuickBooks or Xero, work on it in Claude, and import or enter the result back. The AI Bookkeeper agent is built around exactly that export-and-return loop.
Can Claude give me tax advice for my business?
No. It can list questions to ask and organize documents, but deductibility, depreciation and sales tax rules depend on your jurisdiction and change. Take any tax point to a qualified accountant before you act on it.
Why do Claude totals sometimes not match my bank?
Without code execution, a language model predicts numbers rather than calculating them, so long sums drift. Ask it not to total in prose, turn on code execution for any arithmetic, and always compare its result with the closing balance on the statement.
