1Reason
A missing PO number, filled in
The clerk narrows the vendor’s open POs in your ERP to the likely one and asks whoever raised it to confirm. Then it adds the number and sends the invoice to approval.
Clerked vs Quadient AP
Quadient AP, formerly Beanworks, reads invoices, matches line items to POs and receipts and routes approvals through the steps you set up.
When an invoice has no PO number or carries freight nobody approved, Clerked’s AI clerks get the answer and update the invoice.
Finance teams running AP on Clerked
What the clerks do when
an invoice doesn’t add up.
2Reason
Vendor emails from live ERP data
A supplier bills 100 units against a receipt for 80. The clerk drafts the email asking for a corrected invoice, with the PO and receipt lines from your ERP, for your team to send.
3Reason
Each exception to its owner
Freight nobody approved goes to the buyer on the PO, and a possible duplicate comes back to AP with both invoices side by side. They answer by email, Slack or Teams, with no login.
4Reason
Memories from your own history
Before go-live, the clerks read your invoice history and keep memories like: this vendor bills by the case and you stock by the each. Your team can read, edit or delete every one.
What both do, and what
the clerks do after that.
Reads any invoice format
Quadient AP: YesClerked: YesLine-level three-way matching
Quadient AP: YesClerked: YesApproval workflows
Quadient AP: YesClerked: YesDuplicate invoice checks
Quadient AP: YesClerked: YesWrites invoices to your ERP
Quadient AP: YesClerked: YesResolves exceptions itself
Quadient AP: NoClerked: YesEmails vendors for missing info
Quadient AP: NoClerked: YesRoutes each exception by type
Quadient AP: NoClerked: YesReadable, editable memories
Quadient AP: NoClerked: YesScheduled custom agents
Quadient AP: NoClerked: YesRun AP without logging in
Quadient AP: NoClerked: Yes
