AI bookkeeping: What an agent should never do alone

AI bookkeeping works best when an agent prepares financial records and a person retains authority over decisions that affect the business. It can match receipts to transactions, organise invoices, draft journal entries and flag discrepancies. It should not independently move money, issue refunds or close an accounting period. These actions have consequences that a neat spreadsheet cannot undo.

The approval line belongs between preparation and commitment. A proposed entry can be checked before it changes the books. A payment sent to the wrong supplier has already left the account. Good AI bookkeeping starts with this distinction, then defines exactly what the agent may do, what it must leave for review and when it has to stop.

Give the agent the paperwork first

Much of bookkeeping involves collecting information and comparing documents against established rules. These tasks suit an agent because the work can be checked against invoices, receipts and transaction records.

Suppose a supplier sends an invoice for office equipment. The agent can extract the supplier name, date, amount, tax and payment terms. It can compare the invoice with a purchase order, look for a matching bank transaction and draft an entry using the company's accounting rules. If two invoices appear to cover the same purchase, it can flag the possible duplicate for review.

Receipt matching follows the same pattern. The agent compares the merchant, date and amount on a receipt with a card transaction, then attaches the supporting document to its proposed match. If the receipt total differs from the transaction, it should explain the discrepancy and leave the item unresolved. A bookkeeper can focus on exceptions instead of checking every straightforward match by hand.

The important word is proposed. A useful draft shows the source document, selected account category and reason for the choice. It also states where information is missing or uncertain. That gives the reviewer something specific to check rather than a finished-looking entry with no explanation.

The bookkeeper template offers a starting point for defining this delegation. Its brief should identify the records to inspect, the rules to follow, the work the agent may prepare and the exceptions that require a person.

Keep proposed entries separate from changes to the books

Correctly reading an invoice does not always mean correctly classifying it. An annual software subscription, for example, might need to be treated as a prepaid expense rather than charged entirely to the current month. The right treatment depends on the company's accounting policy and the transaction's circumstances.

An agent that copies last month's category without checking the details may produce a plausible but incorrect entry. Similar problems arise with tax codes, foreign currency transactions, reimbursements and unfamiliar supplier charges. The agent should suggest a treatment when the written rules cover it, explain the evidence and ask for review when they do not.

A business may choose to let an agent post certain routine entries, but that permission needs a defined scope. Specify which transaction types qualify, which records it can change and what conditions trigger a review. The ability to read a ledger should not automatically grant permission to rewrite it.

Existing records deserve particular care. Correcting a record the agent created may fall within its assignment, but deleting or overwriting a record it did not create requires human approval. An apparent duplicate might be a genuine duplicate, or it might represent a separate payment with similar details. The agent should present the evidence before anyone removes the record.

Keep the proposed entry, supporting document, account selection and approval together in the activity history. If someone questions the classification three months later, the team should be able to see what the agent proposed and why, along with any changes made by the reviewer.

Payments and refunds are approval decisions

A prepared payment is not an authorised payment. An invoice may match a purchase order while still containing a changed bank account, an unapproved charge or a duplicate request. The agent can assemble the payment details and supporting documents, but a person should verify the destination, amount and business reason before the money moves.

Refunds need the same boundary. Imagine a customer asks for their money back, but the order history shows that a replacement item has already been sent. The agent can collect the relevant records and draft a recommendation. It should not issue the refund simply because the request matches a familiar pattern. Someone must decide whether the refund is due and whether another remedy has already been provided.

An approval request should describe the action clearly enough for a person to judge it. Show the payee, amount, relevant invoice or order, and the reason for the proposed payment or refund. A reviewer should be able to approve, change or reject the proposal rather than accept an entire batch without seeing its individual consequences.

In Delagents, actions with effects outside the workspace wait in an approvals inbox. Each card shows the exact action, the cost so far and a deadline. A person can approve it, change it or reject it. The agent can complete the preparation, but it cannot treat a correct match as permission to move money.

Leave period close to the person responsible

Closing the books is a decision about whether the period's records are ready to be relied on. Completing a checklist does not prove that every material issue has been resolved, and a status marked complete cannot replace the judgement of the person responsible for the accounts.

An agent can do much of the preparation. It can reconcile bank transactions, identify missing invoices, list old unreconciled items, compare account balances with the previous month and draft proposed accruals. It can also prepare a close checklist that separates completed work from open questions.

Consider a bank reconciliation with an unexplained difference. It might be a timing issue, a missing transaction or a bookkeeping error. A sharp movement in an expense account might be legitimate, or it might point to a duplicate entry. The agent can gather evidence and suggest possible explanations. The finance lead or accountant must decide whether the explanation is sufficient to close the period.

Reopening a closed period and posting a late adjustment require similar care. Management may already have used the figures in a report or decision. Any proposed change should identify the affected period, the supporting evidence and the reason for the adjustment. The person with authority over those accounts should approve the change.

If the deadline arrives with unresolved discrepancies, the agent should report what remains open. It should not hide uncertainty behind a completed status or invent an explanation to get past the checklist. A useful report tells the reviewer what is known, what is missing and which decision is still needed.

Put the approval rules in the brief

Instructions such as "use judgement on routine bookkeeping" leave too much room for interpretation. The brief should define routine work in terms the agent can apply to an actual invoice or transaction. It should also name the conditions that require a stop.

• Allow the agent to read authorised invoices, receipts and transaction records, match documents and draft entries within the written accounting rules.
• Require review when amounts do not match, a duplicate is suspected, a tax treatment is unclear or a transaction falls outside the permitted categories.
• Keep payments, refunds and period close behind explicit human approval, with the exact action and supporting evidence available to the reviewer.
• Define which records the agent may edit, and require approval before it deletes or overwrites records it did not create.
• Set a hard budget cap for the delegation and retain an append-only activity log of tool calls, approvals and policy changes.

The budget cap and the approval rules solve different problems. A bookkeeping task may consume resources while processing documents or checking records, even when it never makes a payment. A hard cap limits the cost of the delegation. It does not authorise financial transactions or override an approval checkpoint.

The activity log gives the team a record of what happened. If a reviewer rejects an entry, the history should preserve the proposal and the decision. An append-only log also records changes to permissions, so the team can establish which rules applied when an action was taken.

Before using an agent on live accounts, test its instructions against awkward cases. Give it an invoice whose amount differs slightly from the purchase order, a receipt that may be duplicated or a refund request with conflicting order records. Check whether it explains the discrepancy, shows its evidence and stops where required. The test should measure whether it respects the approval line, not simply whether it finishes the task.

Start with one account and a batch of receipts

Choose a narrow assignment from the next bookkeeping run, such as matching receipts to card transactions for one account. Give the agent access only to the records it needs. Define what counts as a match, instruct it to leave discrepancies unresolved and have a bookkeeper compare the proposed matches with the source documents before anything is posted.

Review the first batch for incorrect matches, missing evidence and cases where the agent should have stopped. Adjust the brief before adding another task, such as drafting expense entries. Keep payments, refunds and period close outside its independent authority. Write that first brief around a real batch of receipts, and decide in advance which discrepancies must return to a person.