1Reason
It gets the answer itself
An invoice arrives with no PO number. The clerk emails the person who buys from that vendor, gets the number back and matches every line to the PO and receipt.
Clerked vs Medius
Medius moves each invoice through a well-built workflow, from reading and matching to approval and posting to your ERP.
When an invoice is missing a PO number or bills freight nobody approved, Clerked’s AI clerks get the answer and update the invoice.
Finance teams running AP on Clerked
What Clerked’s agents do
when an invoice doesn’t line up.
2Reason
Vendor emails from live ERP data
Freight shows up that the PO never allowed for. The clerk drafts the vendor email quoting the PO line and what receiving recorded, and you read it and send it.
3Reason
Memories you can read and edit
Before go-live, the clerks read your invoice history and keep memories like: this vendor bills by the case and we stock by the each. Your team can edit or delete any of them.
4Reason
Custom agents on a schedule
Build an agent for a check someone does by hand, like POs that are over-consumed or a vendor whose prices are creeping. It runs on your schedule and tells you what it found.
The basics both products cover,
and what Clerked’s agents do next.
Reads any invoice format
Medius: YesClerked: YesLine-level three-way matching
Medius: YesClerked: YesApproval workflows
Medius: YesClerked: YesDuplicate invoice checks
Medius: YesClerked: YesWrites invoices to your ERP
Medius: YesClerked: YesResolves exceptions itself
Medius: NoClerked: YesEmails vendors for missing info
Medius: NoClerked: YesRoutes each exception by type
Medius: NoClerked: YesReadable, editable memories
Medius: NoClerked: YesScheduled custom agents
Medius: NoClerked: YesRun AP without logging in
Medius: NoClerked: Yes
