What an AI assistant should not do in your books

Ask most finance teams what they want from AI and the answer is not "do my accounting". It is "tell me where I stand without me building another report". That distinction is the whole design brief.

Reading is genuinely useful

Most questions a business owner asks about their books are lookups across several places at once. How much is outstanding, and how much of it is late. What output VAT has been charged this quarter, and which invoices are excluded because they are still drafts. What the cash position is across the operating and reserve accounts. Each of those is a query, not a judgement — and answering it in a sentence, with the figures, saves a genuine half hour.

Filing is not

Posting a journal, issuing an invoice, closing a period or submitting a return are all acts with legal consequences and a named responsible person. An assistant that performs them removes the moment where a human looks at the number and agrees with it. So Ledger AI reads your workspace data and drafts; it does not file anything on its own, and every answer says to check the figures before you file.

• It reads: balances, VAT position, customer history, cash across accounts.
• It drafts: an invoice with your usual lines, the right terms, the customer's TRN pulled from their record.
• It stops there: issuing, posting, approving and filing stay with a person who has the permission to do them.

The right test for AI in finance is not what it can do. It is what you would still be comfortable signing.