Xalios
Get a Demo
Solutions/Finance and AP

Invoices in.
Decisions you can defend.

An AI employee that reads the AP mailbox, matches to the order and the receipt, and hands you the exceptions with the reasoning already written down. Above the threshold you set, a person always decides.

Get a Demo→

The situation

Invoices arrive by email, in whatever format the supplier felt like. Someone opens each one, finds the order it belongs to, checks the goods were received, and works out why the numbers disagree when they do.

Most of them reconcile. The month is spent on the ones that don't, and on chasing the people who can explain them, and by the time anyone asks why a particular invoice was paid, the reasoning lives in a thread nobody can find.

What it needs to reach

The AP mailboxRead
Purchase ordersRead
Goods receiptsRead
The finance driveFile

Named mailbox, named folders. Not the tenant, and nothing your administrator has not granted in your own system.

Integrations →

What it does at each level

Most AP teams sit at level 3 for months and are glad they did. You move it up when the record has earned it, and you can move it back down the same afternoon.

LEVEL 1Read and fileOpens every invoice, extracts supplier, number, dates and totals, files it where finance already files things. Changes nothing.
LEVEL 2Match and flagMatches to the order and the receipt, marks the three-way match clean or broken, and says which of the three disagrees.
LEVEL 3Query and chaseDrafts the query to the supplier or the budget holder and waits for approval to send it. Tracks what came back.
LEVEL 4Prepare the runAssembles the payment run, clean matches below the threshold grouped and ready. A person releases it.
LEVEL 5Close the routine onesHandles clean, low-value, repeat-supplier invoices end to end, and reports what it did. Never the exceptions.
A floor, not a setting

The payment threshold

You set a value. Above it, a person decides, at every trust level, in every configuration, including level 5. There is no setting that turns this off, and an AI employee cannot raise its own threshold any more than it can raise its own trust level.

New suppliers, changed bank details and anything the record has not seen before sit above the line by default, whatever the amount. That is where payment fraud lives, so that is where a human stays.

How the floors work →
Below the threshold

Clean three-way match, known supplier, known bank details. Prepared, or closed at level 5.

Above the threshold

A named person approves, with the match, the sources and the exception history on the same screen.

Two records, side by side

This is what the auditor reads, and what your controller reads on a Tuesday. Same record, no separate reporting layer.

Invoice 41288 · matchedPrepared
DIDMatched to PO 9921 and goods receipt GR 4410. Totals agree to the penny.
BECAUSESupplier known for 3 years, bank details unchanged, value below the approval threshold.
SOURCESThe invoice PDF, the order, the receipt. Each one opens where it lives.
RELEASED BYA person, on the payment run, with one click.
Invoice 41304 · disputedEscalated
DID NOTDid not prepare for payment. Held it and raised the exception instead.
BECAUSEQuantity billed is 12; goods receipt shows 9. No credit note on file for the difference.
DRAFTEDA query to the supplier quoting both line items, waiting for approval to send.
WITHThe buyer who raised the order, named, with the receipt attached.

Both records replay. Six months later you can see the state of the drive, the order and the receipt at the moment the call was made, not today's version of them.

Decisions and replay →

What stays with the finance team

The threshold and the trust level

Both are set by the controller and changed by the controller. Neither can be self-granted, and every change is itself a record with a name on it.

Judgement on the exceptions

Disputes, credit notes, early-payment calls and anything involving a relationship stay with the people who own the relationship.

The books

We are not the ledger and do not move money. Your accounting system stays the system of record; we hand it prepared, evidenced work.

Pilot scope

One invoice run, two weeks

We take a real run, not a sample. At the end you have a set of decision records to read and a plain answer on whether this is worth doing at your volume.

Get a Demo→
SCOPEOne AP mailbox, one finance drive, one supplier segment.
LEVELStarts at 1. Level 3 by the second week if the record supports it.
YOU BRINGA controller for an hour a week, and the threshold you would defend.
WE BRINGThe job description, the connections, and a weekly review of what it got wrong.
Next functionRenewals that don't pass unnoticed.Notice periods, obligations and the clause a commitment came from, extracted with provenance.Legal and commercial →

Bring last month's run. We will show you the records it would have produced.

Get a Demo→