Start with the inbox: where an AI-prepared Xero bill stops
When an invoice lands in a shared finance inbox, someone still needs to know what it is, who supplied it and whether the business should approve it. The safe boundary is simple: AI prepares a proposed bill in Xero, while a named person remains responsible for the accounting decision and approval.
Suppliers send invoices as the original evidence of a purchase. Xero records incoming purchases as bills, so the original document should stay attached to, or linked from, the draft. An AI workflow can read the invoice, extract supplier, invoice number, dates, tax and totals, normalise formats, match the supplier record, flag possible duplicates and check that the arithmetic adds up. It should show confidence for each field, rather than presenting an uncertain guess as a fact. Xero’s guide to AI in accounting provides useful context for this kind of assistance.
Preparation stops at a reviewable draft. A named reviewer should receive items with low confidence in one or more fields, an unknown supplier, changed bank details or an unusual invoice. That person confirms the source document and decides any uncertain accounting treatment, including tax, account coding and whether the bill itself should be approved. Approval must be recorded by the authorised person, not inferred from an automated match.
Bill approval is also separate from payment authorisation. Even after a bill is approved in Xero, a person or an existing payment control must authorise when and how money leaves the bank. As a London AI and automation partner, Wise Solutions makes new technology approachable without programming, with the transparency teams need to build trust: a trail of what the AI prepared, what it could not establish and who made each decision.
The control flow for AI invoice processing in Xero
AI invoice processing should stop at decisions, not run straight from an inbox to payment. The following control flow fits a shared service team and can complement Xero’s bills and expenses tools (Xero bills and expenses).
1. Receive and retain the source. A monitored shared inbox accepts invoices and credit notes, including forwarded messages and attachments. Save the original email, attachment, received time, sender and any thread context in a traceable record. Reject password-protected or incomplete files to a review queue; do not silently replace an original with an OCR copy.
2. Extract, then show confidence. Read supplier, invoice number, dates, currency, line items, net, VAT and total, while preserving the page image or PDF. Present each field with confidence and highlight missing, conflicting or unreadable values. A person corrects or confirms the data before it can move on.
3. Verify the supplier and bank details. Match against the approved supplier record using more than a name alone. A new supplier, changed bank account or mismatch pauses processing for an independent check through a trusted contact route, never the contact details in the invoice. Record who verified it and when.
4. Investigate duplicates. Compare supplier, invoice number, amount, date, currency and document similarity, then show possible matches to a reviewer. Hold likely duplicates, but allow a documented release where a repeat invoice is legitimate, such as a recurring charge or separately delivered service.
5. Check arithmetic, VAT and notes. Recalculate line extensions, discounts, net, VAT and total. Flag a VAT mismatch, mixed VAT treatment, missing rate or uncertain tax code for human resolution, and hold it from posting until evidence supports the treatment. Link credit notes to the original bill or explain the allocation, checking that they are not applied twice.
6. Apply currency policy. For foreign-currency bills, retain the invoice, exchange-rate source and rate date required by the organisation’s policy. Stop when the evidence is missing or the rate is ambiguous, and route the exception to someone authorised to choose the treatment.
7. Route and record approval. Apply rules for amount, supplier risk and cost centre, with segregation where required. Capture the decision, approver, timestamp, coding, exceptions and supporting evidence before creating a draft in Xero. A draft is not approval and approval is not payment authority.
8. Sync visibly, then authorise payment separately. Send only the reviewed draft. Show failures, rejected fields and the last successful state to the operator. Retry with an idempotency key or equivalent invoice identity so a timeout cannot create a second bill; escalate after repeated failure. Once the bill is posted, a separate payment authoriser confirms due date, bank details and amount against the approved record. No automatic payment follows a successful sync.
Give every exception an owner and an evidence trail
An exception should be a work item, not a loose email. Record the invoice and supplier IDs, the reason it was held, the confidence of the rule or match, its age, named owner, next action, status and escalation route. Use consistent reasons such as bank-account change, possible legitimate duplicate, uncertain VAT treatment, credit-note mismatch, breach of currency policy or failed Xero sync. A queue sorted by age and escalation status makes overdue decisions visible. Set a due date for every owner and make escalation automatic when the due date passes, while preserving the original decision context.
Keep the evidence with the record. Retain the original invoice, extracted values, any corrections, validation checks, comments, approver and timestamps. Link related supplier-master changes, the Xero bill ID, each sync attempt and the resulting payment evidence. This lets a reviewer follow what was received, what was changed, who approved it and whether the transaction ultimately reached the ledger and bank.
For VAT, store the source and reasoning, not only the final code: jurisdiction, tax point, rate, exemption or reverse-charge assessment, and supporting correspondence where relevant. Evidence should be retrievable by invoice, supplier and period. HMRC’s record-keeping guidance sets out the records businesses must keep, so make retrieval part of the control rather than an end-of-year scramble.
Review the queue as a process, not a series of anecdotes. Track exception volume, age, reason, rework and false positives by supplier, rule and time period. Rising rework may point to poor extraction or an unclear policy; repeated false positives may justify a threshold change. Record the change, its approver and effective date, then monitor the next cohort. Owners close the loop by resolving, escalating or documenting why an exception remains open.
Measure Xero invoice automation before you expand
Before expanding AI invoice automation, an SME needs a baseline it can inspect. For a representative period, record invoice volume, staff touch time per invoice, exception rate, duplicate flags, approval turnaround, rework and sync failures. Define how each measure is counted, who owns the data and where evidence is kept. Any time-saving or exception-rate target is measured from that baseline, never promised.
Choose a bounded cohort, such as one entity, supplier group or cost centre, and agree stopping rules before processing starts. Pause for missing source documents, unexplained VAT or coding changes, supplier or bank-detail changes, repeated sync errors, duplicate uncertainty or any loss of approval evidence. Begin with human review around every proposed Xero bill. The reviewer can correct, reject or escalate while the team learns where the process needs clearer policy.
Run the pilot in phases. In observation, capture recommendations without writing to Xero. In draft creation, create proposed bills only after the source, supplier, calculations and coding have been reviewed. In controlled expansion, add cohorts gradually and compare results with the baseline at each checkpoint. Keep ownership with named people, retain approval evidence and supplier-change checks, and keep payment authority separate from bill preparation and synchronisation.
Set targets as questions to test: can touch time fall without more rework, and can the exception rate remain within an agreed tolerance? Report the actual result, sample size and unresolved cases. An accountant’s review of AI governance can help challenge the control design (ICAEW accountant review). Wise Solutions can audit your invoice process or run a Xero-connected pilot, tailoring automation without programming and keeping trust, transparency and human accountability visible as you expand.
