1Reason
A missing PO number, filled in
The clerk finds the likely open PO in your ERP and emails the buyer who raised it to confirm. On a yes, it adds the number and matches every line to the PO and receipt.
Clerked vs Zip
Zip runs the purchase from request to approved PO, and syncs approved transactions to your ERP.
When an invoice arrives with no PO number or bills freight nobody approved, Clerked’s AI clerks get the answer and update the invoice.
Finance teams running AP on Clerked
After the PO is approved,
the clerks act on the invoice.
2Reason
Vendor emails from live ERP data
An invoice adds freight the buyer confirms nobody agreed to. The clerk drafts the vendor email quoting the PO line and what receiving recorded, and you read it and send it.
3Reason
Each exception to its owner
A short shipment goes to whoever received the goods, and a price above the PO to the buyer who agreed it. They answer by email, Slack or Teams, without logging in.
4Reason
Memories you can read and edit
Before go-live, the clerks read your invoice history and keep memories like “freight from this vendor codes to the plant that received it.” Your team can edit or delete any of them.
Where Zip and Clerked overlap,
and what the clerks do next.
Reads any invoice format
Zip: YesClerked: YesLine-level three-way matching
Zip: NoClerked: YesApproval workflows
Zip: YesClerked: YesDuplicate invoice checks
Zip: YesClerked: YesWrites invoices to your ERP
Zip: YesClerked: YesResolves exceptions itself
Zip: NoClerked: YesEmails vendors for missing info
Zip: NoClerked: YesRoutes each exception by type
Zip: NoClerked: YesReadable, editable memories
Zip: NoClerked: YesScheduled custom agents
Zip: NoClerked: YesRun AP without logging in
Zip: NoClerked: Yes
