All guides/Bookkeepers and accountants

What to trust an AI assistant with, and what to keep manual

Retrieval, comparison and first drafts are safe to delegate. Judgment calls are not. Plus the verification habit that makes the line hold.

Updated

Trust an assistant with retrieval, comparison and first drafts. Keep the judgment calls, and anything you would not check afterwards. That line is simple to state and it holds up in practice, because it is not about how good the model is. It is about whether a wrong answer is visible to you before it leaves your desk.

What it is genuinely good at

Retrieval. Pulling a report for a period, finding a transaction someone described vaguely, reconstructing the activity on an account. You verify these in seconds against QuickBooks, which is exactly why they are safe to delegate. Caribooks covers 35 reports, so most of what you would otherwise navigate to by hand is one sentence.

Cross-file comparison. Asking the same question of several client files in one sitting: who is carrying receivables past 60 days, which files have a bank balance that moved more than expected, which ones have not been touched since last month. Doing this by hand means the same clicks repeated once per file.

"What changed since." A running answer to what moved in a file since a date you name. This is the request people underrate, and it is the one the QuickBooks interface makes most tedious to assemble.

Anomaly spotting. Duplicate transactions, a vendor entered under two spellings, an expense account that jumps in one month. Treat the output as a list of things to look at, never as findings. The value is that it reads the whole file, not that it is right.

Drafting. An invoice from a source document, a first pass at categorizing a batch of expenses, a note explaining a variance to a client. Drafting is where a review step already exists in your workflow, so nothing new has to be invented.

What to keep manual

Final classification with tax consequences. Capital or expense, the treatment of a benefit, which tax code applies to a purchase. An assistant can propose and can show you what similar transactions were coded to. The decision is yours, and this guide is not the place to look for the rule. That is your professional call and, where it matters, your client's tax adviser's.

Period-end judgment. Accruals, cut-off, allowances, anything where the right answer depends on what you know about the business rather than what is in the ledger.

Anything where you have no prior expectation. If you cannot say roughly what the answer should be before you ask, a wrong answer looks exactly like a right one. Get your expectation first, then ask.

Anything you would not check. This is the real line, and it is worth being blunt about. If you are delegating a task specifically so you never have to look at it, you are not saving time, you are transferring risk onto a system that cannot carry it.

One habit that does most of the work

Start every session, on every file, with a question you already know the answer to.

Ask for a bank balance at a date you have already reconciled. Ask for revenue in a period you have already filed. Compare the answer to what you know, then ask the real question.

This costs a few seconds and catches the two failures that actually happen. The first is being connected to the wrong company, which is easy when a practice holds many files and two clients have similar names. The second is a connector that has lost its session and is answering from stale numbers, which looks completely normal until you read the figures closely.

When a number matters, there is a second half to the habit: ask for it two ways. A total from a report and the same total from a transaction list should agree. When they do not, you have learned something either about the file or about the question you asked.

Who is responsible for the file

You are. That does not change because the answer arrived in a conversation instead of a report window.

An assistant's output is an input to your working papers, not a sign-off. Nobody at Intuit, at the assistant vendor, or at Caribooks reviews a number before it reaches you. Caribooks relays between QuickBooks and the assistant and stores no accounting data. There is no second pair of eyes in the chain, and it would be a mistake to behave as though there were.

Two structural controls help you hold that line. Every connection starts read-only, so until you decide otherwise the worst outcome is a wrong answer rather than a wrong entry. And sending a document, voiding, and deleting each require an explicit confirmation in the conversation, every time. The guides index covers how to set the access level across a practice.

Where this is the wrong tool

If the work you want to hand over is judgment, the assistant adds a review step and removes nothing. You will spend the time you saved checking, and you should.

If your clients are on QuickBooks Desktop, this does not apply at all. Desktop does not expose the API this depends on, so it is not supported and cannot be.

And if you only need a profit and loss and the ability to send an invoice, Intuit's own connector inside Claude is free with a QuickBooks subscription, though it does not cover the balance sheet, the general ledger, journal entries, vendors or bills, and it is not available to Canadian QuickBooks companies. The comparison sets out the differences.

Try Caribooks for 14 days

$39 per company per month, no card required.

What to trust an AI assistant with · Caribooks