One queue, described so it can be measured.
Everyone can read an invoice. Nobody has time to be responsible for one.
Supplier invoices arrive in the AP mailbox in whatever format the supplier chose. The AP team opens each one, finds the order it belongs to, checks the goods or service was received, and works out why the numbers disagree when they do.
Most of them match. The month is spent on the ones that do not, and on chasing the budget holders who can explain them. By the time anyone asks why a particular invoice was paid, the reasoning sits in an email thread nobody can find.
What it usually looks like
You are not short of people who can read an invoice. You are short of people who can take responsibility for one.
One AI employee, hired on a job description the controller writes.
Nothing new is installed for the team. The AI employee is connected to the mailbox and the folders finance already uses, and only to those.
On day one it only reads and files. Every proposal waits for a person. Before anything runs, the controller sets two things, and both are recorded as decisions with their name on them.
Above it a person decides, at every trust level, in every configuration, including level five.
Anything the record has not seen before sits above the line by default, whatever the amount.
The books stay in the finance system. Xalios prepares work with the evidence attached. It does not move money.
“Match supplier invoices against purchase orders and receipts in the AP mailbox. Query anything that does not add up with the supplier or the budget holder. Report to the accounts lead.”
Four steps. One of them a person’s, and it takes a minute.
One supplier invoice, from the moment it arrives to the moment it is filed. Nobody spends time on it until there is something to decide, and what reaches the accounts lead is a decision, not a pile of paperwork.
Invoice INV-4471 from a freight supplier lands in the AP mailbox overnight.
Finds order PO-2210 and the signed-off delivery. Line items and total checked. Spots a $180 freight charge above the agreed rate. That is more than it is allowed to settle, so it stops.
Writes up what it found, attaches the invoice, the order and the rate card, and sends it to the accounts lead with a recommendation: query the supplier before approval.
The accounts lead reads the recommendation, agrees and approves. The query goes to the supplier and everything is filed where finance expects to find it.
What lands with the accounts lead is the exception and the reason. Not the invoice and a question.
What the auditor would read, and what the controller reads on a Tuesday.
The same record, with no separate reporting layer. Both can be replayed. Six months later the order, the receipt and the rate card open as they were when the decision was made, not as they are today.
For the finance team, twelve weeks in.
Not fewer people. Paperwork stops getting in the way of judgement. The exceptions, the supplier relationships and the difficult calls stay with the people who are good at them, and the queue stops eating their week.
Every invoice needs a person, including the majority that match cleanly.
Only exceptions reach a person, and each one arrives with the evidence and a recommendation.
The reasoning behind a disputed approval sits in an email thread nobody can find.
Every decision can be replayed as it stood at the time, with the sources attached.
Trust in automation is all or nothing, so it stays at nothing.
Authority is earned for each kind of work, raised by the controller and withdrawn automatically when quality slips.
A month-end crunch, and a headcount request that keeps being turned down.
Capacity added by filling a role. The AP team spends its week on disputes and supplier relationships.
Audit preparation is a fortnight of asking colleagues for screenshots.
The audit pack is a by-product of the work, and the question about a disputed approval has an answer on the day.
What stays with the finance team
The payment limit and the trust level
Both set and changed by the controller. Every change is itself a record with a name on it.
Judgement on the exceptions
Disputes, credit notes, early-payment decisions and anything involving a supplier relationship stay with the people who own the relationship.
The books
The finance system stays the system of record. Xalios hands it prepared work with the evidence attached, and never moves money.
Open a decision from week three and get week three.
Most audit questions about invoices are questions about evidence: why was this approved, on what basis, and what did the approver know. A useful test at week twelve is simple. Pick ten decisions at random and ask for the reasoning.
The answer to “why was this paid” becomes a click, not an investigation.
One AI employee becomes an operating model.
The memory built on invoices, which suppliers, which price lists, which buyers own which orders, is the foundation the next role starts from. Each addition is faster than the last, and each one starts again at level 1 for its own kind of work.
Invoice matching
The pilot. Level 3 as the target, with preparing the payment run as the next step you can choose.
Supplier queries
Drafts replies to suppliers from what the record already holds. Anything leaving the organisation waits for a person.
Statement reconciliation
Checks supplier statements against the ledger each month and lists the differences, with the invoice or credit note attached.
