1Reason
Unapproved freight, resolved before you pay
A bill adds freight that wasn’t on the PO. The agent asks the buyer who placed the order, and on a yes, codes the freight and moves the invoice on.
Clerked vs Vic.ai
Vic.ai built its own AI for AP, reading invoices in any format, matching each line to the PO and receipt and catching duplicates.
Where Vic.ai flags a mismatch for your team, Clerked’s AI clerks resolve it and update the invoice.
Finance teams running AP on Clerked
What Clerked’s agents do
once an invoice is flagged.
2Reason
A missing PO number, requested
The agent drafts the email asking the vendor for the PO number, written from your live ERP data with the invoice details already in it. Your team reads it and sends it.
3Reason
Each exception to its owner
A price that doesn’t match goes to the buyer who agreed it, and a partial shipment to receiving. They answer by replying to the email, or in Slack or Teams, with no login.
4Reason
Memories you can read and edit
Tell the agents once that a freight vendor puts ticket numbers on its invoices, never a PO number, and they match on the ticket from then on. Your team can edit or delete every memory.
Where the two overlap,
and where Clerked’s agents act.
Reads any invoice format
Vic.ai: YesClerked: YesLine-level three-way matching
Vic.ai: YesClerked: YesApproval workflows
Vic.ai: YesClerked: YesDuplicate invoice checks
Vic.ai: YesClerked: YesWrites invoices to your ERP
Vic.ai: YesClerked: YesResolves exceptions itself
Vic.ai: NoClerked: YesEmails vendors for missing info
Vic.ai: NoClerked: YesRoutes each exception by type
Vic.ai: NoClerked: YesReadable, editable memories
Vic.ai: NoClerked: YesScheduled custom agents
Vic.ai: NoClerked: YesRun AP without logging in
Vic.ai: NoClerked: Yes
