1Reason
A short shipment, answered
A vendor bills the full order, but your ERP shows part of it received. The clerk asks the person who raised the PO, who answers from email, Slack or Teams, with no login.
Clerked vs MineralTree
MineralTree reads emailed invoices, matches their lines to the PO, routes approvals by email and pays vendors by check, ACH or virtual card.
Clerked’s AI clerks resolve the exceptions along the way, getting the answer from whoever owns it and updating the invoice.
Finance teams running AP on Clerked
Exceptions get an answer,
and the invoice moves on.
2Reason
A missing PO number, requested
An invoice arrives with no PO number. The clerk drafts the email asking the vendor for it, written from the order and receipt in your ERP, and your team sends it.
3Reason
Memories your team can edit
Before go-live, the clerks read your invoice history and keep memories in plain English, such as where a vendor’s fuel surcharge is coded. Your team can read, edit or delete every one.
4Reason
Agents that run on a schedule
Build an agent for a check someone does by hand, like receipts that post after the invoice. It runs in the background on your schedule and tells you what it found.
Where the two overlap,
and where they differ.
Reads any invoice format
MineralTree: YesClerked: YesLine-level three-way matching
MineralTree: YesClerked: YesApproval workflows
MineralTree: YesClerked: YesDuplicate invoice checks
MineralTree: YesClerked: YesWrites invoices to your ERP
MineralTree: YesClerked: YesResolves exceptions itself
MineralTree: NoClerked: YesEmails vendors for missing info
MineralTree: NoClerked: YesRoutes each exception by type
MineralTree: NoClerked: YesReadable, editable memories
MineralTree: NoClerked: YesScheduled custom agents
MineralTree: NoClerked: YesRun AP without logging in
MineralTree: NoClerked: Yes
