1Reason
Partial shipments, matched as they land
The invoice bills the whole order, but receiving has logged part of it. The clerk matches what arrived, holds the rest and sends the invoice to approval once the receipts post.
Clerked vs Esker
Esker is built for large finance teams on several ERPs, matching invoices from email, EDI, mail and portals to POs and goods receipts.
When freight shows up that nobody approved, Clerked’s AI clerks ask the buyer, get the answer and update the invoice.
Finance teams running AP on Clerked
What the clerks do when
an invoice needs an answer.
2Reason
A missing PO number, requested
The clerk looks up the vendor’s open orders in your ERP and drafts an email asking which one the invoice belongs to. Someone on your team reviews and sends it.
3Reason
Freight nobody approved, to the buyer
A vendor adds freight that isn’t on the PO, so the clerk sends it to the person who raised the order. They answer from email, Slack or Teams, with no login.
4Reason
A year of invoices, read first
Before go-live, the clerks read your invoice history and keep memories in plain English, like which account a vendor’s fuel surcharge goes to. Your team can read, edit or delete any of them.
The basics both cover,
and what the clerks do next.
Reads any invoice format
Esker: YesClerked: YesLine-level three-way matching
Esker: YesClerked: YesApproval workflows
Esker: YesClerked: YesDuplicate invoice checks
Esker: YesClerked: YesWrites invoices to your ERP
Esker: YesClerked: YesResolves exceptions itself
Esker: NoClerked: YesEmails vendors for missing info
Esker: NoClerked: YesRoutes each exception by type
Esker: NoClerked: YesReadable, editable memories
Esker: NoClerked: YesScheduled custom agents
Esker: NoClerked: YesRun AP without logging in
Esker: NoClerked: Yes
