One queue, described so it can be measured.
Everyone can answer a supplier. Nobody has time to look everything up first.
Supplier questions land in the AP mailbox between the invoices. Where is my payment. Did you receive invoice 4471. Why was this short-paid. Someone opens each one, looks up the invoice, checks the payment run and the remittance, and writes a reply.
Most answers are already in the system. The week is spent finding them, and the questions that wait longest come from the suppliers who chase the hardest. By the time a supplier puts deliveries on hold, three people have half-answered the same email.
What it usually looks like
You are not short of people who can answer a supplier. You are short of time to look up the answer before the supplier asks again.
One AI employee, hired on a job description the accounts lead writes.
Nothing new is installed for the team. The AI employee is connected to the AP mailbox and the invoice, payment and remittance records finance already uses, and only to those.
On day one it only reads and drafts. Every reply waits for a person. Before anything runs, the accounts lead sets two things, and both are recorded as decisions with their name on them.
Payment status, invoice receipt, remittance detail and payment dates, from the record. Nothing it cannot source.
Disputes, bank detail changes and anything with a legal angle are handled by a named person, and every reply leaving the organisation is sent by one, at every trust level.
The finance system stays the system of record. Xalios reads it and drafts from it. It does not change a payment or a supplier record.
“Read supplier questions arriving in the AP mailbox. Answer questions about payment status, invoice receipt and remittances from the record, with the source attached, and draft the reply for a person to send. Pass disputes and bank detail changes to the accounts lead. Report to the accounts lead.”
Four steps. One of them a person’s, and it takes a minute.
One supplier question, from the moment it arrives to the moment the reply is sent. Nobody spends time on it until there is something to decide, and what reaches the accounts lead is a reply to send, not a question to research.
A supplier asks why invoice 41288 has not been paid, six weeks after it was sent.
Finds the invoice, sees it was approved on the 3rd and is on the payment run for the 28th, and drafts a reply that says so, with the remittance date. Holds it for a person to send.
Attaches the invoice, the approval and the payment run entry, and puts the reply in the accounts lead’s queue with the source shown.
The accounts lead reads the reply, sees the source, and sends it. The supplier has a payment date before ten, and the reply is on the record with the invoice attached.
What lands with the accounts lead is a reply and its source. Not a question and a search.
What the auditor would read, and what the accounts lead reads on a Tuesday.
The same record, with no separate reporting layer. Both can be replayed. Six months later the question, the invoice and the payment run open as they were when the reply was sent, not as they are today.
For the finance team, twelve weeks in.
Not fewer people. Looking things up stops getting in the way of answering. Disputes, bank detail changes and the suppliers who need a call stay with the people who are good at them, and the inbox stops filling with the same question.
Every supplier question is looked up by hand.
Every question arrives with the answer found and the source attached.
Suppliers wait days for a payment date that is already in the system.
Routine status replies go out the same morning, sent by a person with one click.
Replies differ depending on who wrote them.
Replies come from the record, in one voice, and cite the source every time.
Nobody can say which supplier has been waiting longest.
Every question carries its own record: what was asked, what was found, who replied and when.
Trust in automation is all or nothing, so it stays at nothing.
Authority is earned for each kind of question, raised by the accounts lead and withdrawn automatically when quality slips.
What stays with the finance team
What it may answer and the trust level
Both set and changed by the accounts lead. Every change is itself a record with a name on it.
Judgement on the difficult ones
Disputes, bank detail changes, early-payment requests and any supplier who needs a call stay with the people who own the relationship.
The finance system
It stays the system of record. Xalios reads it and drafts from it, and does not change a payment or a supplier record.
Open a reply from week three and get week three.
Most questions about supplier correspondence are questions about accuracy: what was the supplier told, on what basis, and by whom. A useful test at week twelve is simple. Pick ten replies at random and ask for the source.
The answer to “what did we tell them” becomes a click, not a search through sent items.
One AI employee becomes an operating model.
The memory built on supplier questions, which suppliers ask what, which invoices get chased, which answers hold, 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.
Supplier query desk
The pilot. Level 3 as the target, with batching the routine replies as the next step you can choose.
Statement desk
Checks supplier statements against the ledger each month and lists the differences, with the evidence attached.
Payment runs
Puts together the weekly payment run, holds anything unapproved and explains why it was held.
