1Reason
A missing PO number, filled in
An invoice arrives with no PO number. The clerk asks the person who buys from that vendor, matches each line to the PO and receipt, and updates the invoice.
Clerked vs Airbase
Airbase runs cards, expenses and bill pay, and it reads, matches and routes supplier bills before syncing them to your ERP.
When a bill has no PO number or freight nobody approved, Clerked’s AI clerks get the answer and update the invoice.
Finance teams running AP on Clerked
What the AI clerks do
when an invoice needs an answer.
2Reason
Vendor emails from live ERP data
An invoice adds freight the PO never allowed for. The clerk drafts the vendor email quoting the PO line and receipt, and someone on your team sends it.
3Reason
Each question to its owner
A price above the PO goes to the buyer who agreed it, and an unusually large bill to the budget owner. They answer from email, Slack, Teams or their phone, with no login.
4Reason
Memories you can read and edit
Before go-live, the clerks read your invoice history and write what they learn in plain English, like where a vendor’s fuel surcharge is coded. Your team can read, edit or delete every memory.
What both products cover,
and what the AI clerks do next.
Reads any invoice format
Airbase: YesClerked: YesLine-level three-way matching
Airbase: YesClerked: YesApproval workflows
Airbase: YesClerked: YesDuplicate invoice checks
Airbase: YesClerked: YesWrites invoices to your ERP
Airbase: YesClerked: YesResolves exceptions itself
Airbase: NoClerked: YesEmails vendors for missing info
Airbase: NoClerked: YesRoutes each exception by type
Airbase: NoClerked: YesReadable, editable memories
Airbase: NoClerked: YesScheduled custom agents
Airbase: NoClerked: YesRun AP without logging in
Airbase: NoClerked: Yes
