Can Claude Do My Bookkeeping? Give It the Books First

The question sounds like a request to get rid of a chore. There is a folder of receipts, a bank account full of unexplained payments, and an evening you would rather have back. Claude can read the files. It can explain the transactions. Surely it can finish the job.

Sometimes it can do a surprising amount. The difficulty is knowing what “finished” means.

A beautifully categorised spreadsheet can still count a transfer as income. A persuasive summary can describe a profitable business whose biggest customer has not paid. A bank account can agree to the penny while the payroll entries are missing altogether. Bookkeeping has several ways of looking complete before it is.

Can Claude do my bookkeeping? Yes, it can carry out useful parts of the work when connected to accounting software: inspect the ledger, answer questions, prepare changes and help code transactions. A conversation built around an uploaded statement is a much narrower thing. You still need a continuing set of books, supporting records and someone to review what goes into them.

We build IQ Books and the ReconcileIQ connector, so we have an interest here. We also have an embarrassing example. The Claude session behind our earlier ChatGPT article found unfinished bookkeeping in our own demo company. This article draws on that same documented session; it is not a second experiment or a comparison of the two assistants.

The bank statement tells half the story

Imagine a small installation business. There is £12,000 coming in from a customer, £3,000 arriving from another account, and a £900 card payment to a builders’ merchant. Give Claude those three lines and it can offer a reasonable account of them.

But the £12,000 might settle an invoice already recorded as a sale. Record another sale and you have counted the income twice. The £3,000 might be money moved from the business savings account. The builders’ merchant payment might cover materials for two different jobs, with a personal purchase on the same receipt.

Those are illustrative transactions, not results from our test. The point is that the description on the statement cannot settle any of them. The missing information lives in the sales ledger, the other bank account, the receipt and what the owner knows about the purchase.

You can supply that context in a long conversation. You can upload more files, explain your accounting policy and keep correcting the answer. That may be useful for a small, contained exercise. It also leaves you responsible for keeping the conversation and the actual records in step.

Next month, the invoice is still paid. The transfer is still a transfer. The receipt still needs to support the posting. A bookkeeping system has to preserve those facts after you close the chat.

Give Claude access to the ledger and the question changes

A connector lets Claude ask accounting software for records and use the operations that software makes available. Anthropic’s Model Context Protocol provides a standard for those connections. You do not need to learn the protocol to use one.

For bookkeeping, the practical difference is straightforward. Claude can retrieve an invoice before deciding what a receipt relates to. It can ask for an aged debtors report instead of inferring who owes you money from deposits. It can retrieve the profit and loss for a defined period, with figures calculated by the ledger.

The interpretation still deserves scrutiny. Claude can misunderstand a question or explain a correct figure badly. But you now have something concrete to check: a report, a transaction, a customer balance. You can open the app and follow the answer back to its source.

Our ReconcileIQ connector gives Claude that access to IQ Books. What follows describes our connector’s behaviour. Other connectors have their own permissions, operations and limits.

Our demo company had a rather good accountant’s question

Brackenfield Outdoor Ltd is an invented garden and tool supplier we use for testing. Its records are seeded, not a real customer’s accounts: two years of activity, a trade counter, online sales, installation work, seven bank accounts and the less glamorous machinery behind them.

In the published session, Claude could retrieve the year’s turnover and profit from the ledger. Useful, certainly. The more revealing moment came when it inspected whether the books were in a fit state.

It flagged £243,735.92 sitting in Opening Balance Equity. It also identified payroll control balances on the wrong side and a fixed asset register that did not cover all the assets in the ledger.

There is something uncomfortable about asking an assistant to demonstrate your accounting software and getting a list of accounting work you have not finished. There is also something encouraging about it. A clean-looking dashboard had not made those questions go away.

The opening balance finding is a good example. A system can balance while still containing an unresolved setup balance. “The debits equal the credits” is an essential check. It does not establish that the accounts tell the right story.

Finding the balance was useful. Clearing it would require evidence about what belonged there. We should not turn a successful diagnosis into a claim that Claude completed the treatment.

The best first request is an inspection

It is tempting to connect an assistant and immediately ask it to tidy everything up. I would start with a quieter request:

That is a suggested starting prompt, not a quotation from our test. It asks for an output you can use: a work list with evidence.

Then narrow the questions. Which bank transactions are still drafts? Which invoices are overdue? Is there anything in suspense? Which entries explain the difference between the customer balances and the debtors control account?

You want to learn whether Claude can distinguish a missing entry from an unusual but legitimate one. A large payment is not automatically an error. An old customer balance is not automatically a bad debt. Asking for the underlying records makes those distinctions easier to review.

Read-only access is enough for this first pass. You can decide whether to authorise changes after seeing the quality of the inspection.

“Looks right” is a poor approval process

In the same published session, we asked Claude to raise and issue a £1,500 deposit invoice for an installation job. Through the connector it prepared a plan showing the existing customer, the sales account, £300 VAT and the resulting £1,800 receivable.

We declined it. Nothing was posted.

That is a modest test, but an important one. Preparing an entry and posting an entry are separate events. With ReconcileIQ, bookkeeping changes are previewed first and the approved plan is then carried out once. You can inspect what will happen before it becomes part of the books.

Approval still takes attention. Is that the right customer? Is £1,500 the amount before VAT or the amount the customer agreed to pay in total? Does the invoice date belong in this period? An assistant can prepare exactly what you asked for while you have asked for the wrong thing.

A useful review is specific enough to catch that. “Yes, looks fine” after glancing at the final total is a thin defence against an entry on the wrong customer account.

What about the bank transactions?

Questions about profit are the pleasant end of bookkeeping. The repetitive end is working through the bank: recognising suppliers, finding invoice payments, identifying transfers and deciding what needs a person’s attention.

Through the connector, Claude can run CodeIQ against bank transactions. CodeIQ uses an eight-phase logical pipeline covering transfer detection, invoice matching, historical pattern learning, universal pattern matching, MCC category matching, semantic AI, user learning override and VAT classification.

The assistant starts and discusses that work; the coding comes from CodeIQ. You review the proposed result, including uncertain lines, before approved transactions are posted back to IQ Books, Xero, QuickBooks, Sage or Pandle.

This distinction matters when choosing a connection. Reading and changing IQ Books directly is one capability. Coding a statement for a connected Xero company is another. The latter does not mean Claude has unrestricted access to every part of that company’s Xero account.

Automatic coding uses four credits per transaction. Every ReconcileIQ account starts with 1,000 non-refreshing free credits. The connector guide explains the permissions and which operations use credits.

Some questions still belong to the owner

A payment to a director is an obvious example. The bank can establish that money left the company. It cannot establish, on its own, whether the payment settled an expense claim, repaid a loan or represented something else. A confident label does not supply the missing facts.

Claude can help assemble the evidence and explain the alternatives. You or your accountant still need to establish the treatment. The same goes for a repair that might be an improvement, an expense with mixed business and personal use, or a receipt that nobody can find.

Our connector also leaves certain actions out altogether. It does not submit returns to HMRC, pay anyone, produce bank payment files, close the financial year or manage organisation membership. You carry out those actions in the app where available, with the appropriate review.

Those are limits of the ReconcileIQ connector, rather than a claim about every possible Claude integration. They make the division of responsibility explicit: Claude can prepare useful work without being handed every power the account owner has.

Connecting is still sharing data

A connector saves you from repeatedly pasting statements into a conversation. It does not make the assistant blind to your financial information. When Claude asks for a report or a record, the information returned is sent to Claude.

Choose the organisations and permissions you actually need. Consider what customer, supplier and employee information the requested records may contain, and check the data terms and settings for the Claude account you are using. Our connected-assistant privacy explanation describes our side of that exchange.

You should not have to paste a bank password into chat. ReconcileIQ authorisation takes place on our sign-in page, where you choose the connection’s access. You can revoke it from Connected apps.

How to try Claude with your own books

Start with a free IQ Books account. One organisation gets the whole ledger, including customers, invoices, suppliers, bills, stock, projects and VAT. Invoice emailing and reminders from our domain, plus CIS300 and Companies House filing, are the paid exceptions.

Then open ReconcileIQ in Claude’s connectors directory, connect your account and select the organisation and permissions. Enable the connector in your conversation. If your workspace requires a custom connection or an administrator’s involvement, follow our Claude setup guide and Anthropic’s connector instructions.

Connecting, reading the ledger and making bookkeeping changes carry no ReconcileIQ charge. CodeIQ coding and reconciliation use credits. Claude’s own plan limits and charges apply separately.

For the first conversation, pick a period you know. Ask about a customer whose balance you can check, or a month whose profit and loss you have already reviewed. Follow the answer back into the app. A familiar set of records makes a better first test than a year of unexplained transactions.

Then ask what is unfinished. That was where Claude became most useful to us. The turnover figure was reassuring. The awkward questions about the books were worth more.