
Invoice intake and exception triage
How Mercury Digital’s agents read, match and code invoices, sort exceptions by type, and route every payment decision to a named approver.
The short answer
The best way to use AI for accounts payable is to let an agent do the intake and matching and send only the exceptions to people.
With Mercury Digital, the agent reads each invoice, extracts and normalizes it, matches it to the PO and receipt, and codes it from written rules. Exceptions and payments go to a named approver.
What the agent does, and what it never does
Does: captures invoices from every inbound channel with their origin recorded, extracts and normalizes fields from PDFs and emails, runs the match, codes from written rules, files the record as work happens, and keeps a queue showing who has each open item.
Never does: approves a payment, changes vendor bank details, or guesses when a rule doesn't cover the case. Those go to a person.
Exception types and where each one goes
The value is in the exceptions. A clean three-way match doesn't need much intelligence; a mismatch does. Each exception arrives with the failed field named and the source documents attached.
| Exception | What the agent checks | What it sends to the person | Routed to |
|---|---|---|---|
| Possible duplicate | Same vendor, amount, invoice number or date pattern against paid and open invoices | Both invoices side by side with the matching fields highlighted | AP lead |
| PO mismatch (price or quantity) | Invoice lines vs PO lines | The line, the PO value, the invoice value and the difference | Buyer / PO owner |
| Missing receipt (no goods receipt) | Whether a receipt exists for the PO line | The PO, the invoice and who ordered | Requester or receiving |
| No PO / non-PO invoice | Whether a PO is required under your policy | Suggested coding from rules, plus the vendor's history | Budget owner |
| Unknown or changed vendor details | Vendor master vs invoice (name, tax ID, remit-to, bank details) | The differences, flagged as a possible fraud risk. Nothing is auto-updated | Controller (always) |
| Coding the rules don't cover | Whether a written rule applies | The draft coding left blank, with the question stated | AP lead (who then writes the rule) |
| Above approval threshold | Amount vs your approval matrix | The invoice plus the full match result | Named approver for that threshold |
How it works, step by step
Intake with origin
Extract and normalize
Match
Code from written rules
Triage exceptions
Hold the human gate
File as work happens
Works with your accounting system (e.g. QuickBooks, NetSuite)
Through its API
Writes only what you approve
Scopes agreed in the audit
Where this fits
Usually a Tier 1 engagement (Automate a Workflow). It runs in shadow mode next to your current AP process before any write access is granted.
What to measure. The auto-match rate (share of invoices matched without a person), exception turnaround (time from an exception being raised to its owner resolving it), exceptions by type, and invoices waiting at the payment gate. Mercury sets a baseline for these in week 1 and reports against it.
AP automation software vs a Mercury Digital agent
Tipalti, Stampli and the AP capabilities inside ERPs like NetSuite are licensed products with their own invoice capture, PO matching, approval and payment features. Tipalti describes a finance automation suite covering AP, global payments, procurement and expenses, with AI agents for invoice capture and PO matching (Tipalti). Stampli describes a procure-to-pay platform whose AI assistant, Billy, codes, matches and routes invoices (Stampli). NetSuite's AP describes invoice capture, matching bills to POs and receipts, approval workflows and payment automation inside the ERP (NetSuite Accounts Payable). Mercury Digital builds a governed custom agent around the process you already run, including the exception rules and the approvers you already have.
| Question | AP automation product | Mercury Digital agent build |
|---|---|---|
| What you get | A product your team adopts | An agent workflow built around your current AP process |
| Exceptions | Handled with the product's workflow | Typed, routed to your named owners, and logged with evidence |
| Payment control | The product's approval chain | A human gate on every payment and on every exception, closed by default |
| Fits best when | You're ready to standardize AP on a dedicated product or your ERP's AP module | Your rules are spread across inboxes, spreadsheets and an existing ERP |
Product descriptions checked against the vendors' own pages on Oct 27, 2026. Features and packaging change, so check each vendor's site for current details.
Related reading
- Related use cases: Document intake, extraction and filing · Automating month-end close · Purchase approval workflows that don't stall · Approval gates · The AR clerk as an AI employee · Readiness checklist
- Offer pages: Tier 1 / Automate a Workflow · Book your audit
