1Reason
Freight nobody approved
A supplier adds freight the PO never mentioned. The clerk asks the buyer who raised the PO, and on a yes, codes the freight and sends the invoice on for approval.
Clerked vs Ottimate
Ottimate is built for multi-location groups, reading invoices in any format, matching them line by line and checking for duplicates and fraud.
Clerked does that too, then its AI clerks ask whoever owns each exception, draft the vendor email and update the invoice.
Finance teams running AP on Clerked
What Clerked’s agents do
when an invoice doesn’t line up.
2Reason
An invoice with no PO number
The clerk drafts an email asking the vendor for the number, written from your ERP data. When the vendor replies, it matches the invoice line by line to the PO and receipt.
3Reason
A partial shipment, to its owner
The receipt in your ERP shows part of the order missing, so the clerk asks whoever received the delivery. 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 keep memories like: this vendor bills by the case and we stock by the each. Your team can edit or delete every one.
Where the two overlap,
and where they differ.
Reads any invoice format
Ottimate: YesClerked: YesLine-level three-way matching
Ottimate: YesClerked: YesApproval workflows
Ottimate: YesClerked: YesDuplicate invoice checks
Ottimate: YesClerked: YesWrites invoices to your ERP
Ottimate: YesClerked: YesResolves exceptions itself
Ottimate: NoClerked: YesEmails vendors for missing info
Ottimate: NoClerked: YesRoutes each exception by type
Ottimate: NoClerked: YesReadable, editable memories
Ottimate: NoClerked: YesScheduled custom agents
Ottimate: NoClerked: YesRun AP without logging in
Ottimate: NoClerked: Yes
