1Reason
Freight never on the PO
An invoice adds freight the PO never included. The agent asks the buyer who placed the order, and if they agreed it, writes the answer onto the invoice and moves it to approval.
Clerked vs Rillion
Rillion is strong at multi-entity AP, matching each invoice line to the PO and receipt and posting approved invoices to your ERP.
Where Rillion routes an exception to a person, Clerked’s AI clerks get the answer and update the invoice themselves.
Finance teams running AP on Clerked
What the agents do when
an invoice doesn’t line up.
2Reason
An invoice with no PO number
The agent looks for a matching open PO in your ERP. When none lines up, it drafts an email asking the vendor for the number, and you read it and send it.
3Reason
Each exception to its owner
A regular vendor sends a bill far larger than usual, so the agent sends it to the budget owner with past bills attached. They answer from email, Slack, Teams or their phone, with no login.
4Reason
Memories you can read and edit
Before go-live, the agents read your invoice history and keep memories in plain English, like “this vendor bills by the case.” Your team can read, edit and delete every one.
Where the two overlap,
and where the agents act.
Reads any invoice format
Rillion: YesClerked: YesLine-level three-way matching
Rillion: YesClerked: YesApproval workflows
Rillion: YesClerked: YesDuplicate invoice checks
Rillion: YesClerked: YesWrites invoices to your ERP
Rillion: YesClerked: YesResolves exceptions itself
Rillion: NoClerked: YesEmails vendors for missing info
Rillion: NoClerked: YesRoutes each exception by type
Rillion: NoClerked: YesReadable, editable memories
Rillion: NoClerked: YesScheduled custom agents
Rillion: NoClerked: YesRun AP without logging in
Rillion: NoClerked: Yes
