1Reason
A missing PO number, found
An invoice arrives with no PO number. The clerk finds the vendor’s open PO in your ERP whose items, quantities and prices fit, adds the number and matches it line by line.
Clerked vs DocuPhase
DocuPhase, now onPhase, reads invoices in any format, handwriting included, and matches them to POs and receipts at line level.
When a line doesn’t match or a PO number is missing, Clerked’s AI clerks get the answer and update the invoice.
Finance teams running AP on Clerked
What Clerked’s AI clerks do
once an exception is caught.
2Reason
Vendor emails from live ERP data
A unit price comes in above the PO. The clerk drafts the email asking the vendor for a corrected invoice, quoting the PO and receipt from your ERP, for your team to send.
3Reason
Each exception to its owner
Freight nobody approved goes to the person who raised the PO, who answers by replying, with no login. The clerk codes the freight and moves the invoice on.
4Reason
Memories your team can edit
Before go-live, the clerks read your invoice history and keep memories in plain English, like which account one carrier’s freight codes to at each plant. Your team can read, edit or delete every one.
Where the two overlap,
and where they differ.
Reads any invoice format
DocuPhase: YesClerked: YesLine-level three-way matching
DocuPhase: YesClerked: YesApproval workflows
DocuPhase: YesClerked: YesDuplicate invoice checks
DocuPhase: YesClerked: YesWrites invoices to your ERP
DocuPhase: YesClerked: YesResolves exceptions itself
DocuPhase: NoClerked: YesEmails vendors for missing info
DocuPhase: NoClerked: YesRoutes each exception by type
DocuPhase: NoClerked: YesReadable, editable memories
DocuPhase: NoClerked: YesScheduled custom agents
DocuPhase: NoClerked: YesRun AP without logging in
DocuPhase: NoClerked: Yes
