Can an AI agent process supplier invoices?

Yes, from inbox to ledger. An AI agent can read supplier invoices as they arrive, extract the details, check the supplier, match to orders, code the lines and route each invoice for approval. It processes at depth 3 within rules. It does not approve invoices for payment, and it ignores any bank details printed on an invoice.

What does processing cover?

Accounts payable teams spend most of their time on the steps before approval: opening emails, saving attachments, keying invoice details, finding the right order, chasing receipts, coding lines and sending the invoice to the right approver. Each step is small. Together they fill the week.

An agent can do all of them. It reads the invoice, whatever its layout. It identifies the supplier and checks the supplier exists on the master file. It finds the order and goods receipt, codes the lines using the supplier's history and the coding rules, and routes the invoice to the approver set by the budget and authority matrix. The full sequence is set out in how to process supplier invoices from inbox to ledger.

Why does the inbox matter?

Supplier invoices arrive by email, which makes every one of them external. That has two consequences.

First, an invoice cannot introduce anything new to the master file. If the invoice shows a different bank account, address or company name from the master file, the agent uses the master file and flags the difference. Changed bank details on an invoice are a classic fraud pattern, and the supplier bank detail change verification checklist applies before anything changes.

Second, an invoice from a sender the agent cannot link to a known supplier is not processed. It goes to a person, because unknown senders are where fictitious invoices come from.

What does the agent do, and what stays with people?

The agent, at depth 3 within rules: - captures each invoice and its attachments; - extracts supplier, number, date, lines, tax and totals; - checks the supplier against the master file; - runs a duplicate check, as described in how to detect duplicate supplier invoices; - matches to order and receipt within tolerance; - codes lines from supplier history and rules; - posts the invoice to the ledger as unapproved and routes it to the approver.

People: - the budget holder approves the invoice for payment, within their authority; - AP resolves exceptions: no order, mismatches, unknown suppliers; - master data changes go through their own process; - payment is released by two people, as covered in whether an AI agent can pay supplier invoices.

Separation of duties rests on three different hands: the agent processes, a budget holder approves, two people release payment. The agent never approves an invoice it processed, and the approver never releases the payment for it.

An illustrative example

Take a regional hotel group whose AP inbox receives about 3,000 invoices a month. On a typical Monday, 160 arrive.

The agent processes 141 fully: matched, coded and routed. It holds 19. Eight have no order number, so it asks the requesting manager to raise one. Five are partial deliveries, held until the remaining receipts arrive. Three are from a laundry supplier whose invoice shows a new bank account; the agent processes the invoice against the master file details and flags the change to the AP lead. Two are from senders it cannot link to any supplier. One is a duplicate of an invoice paid last month.

By lunchtime the AP team has 19 exceptions to work through rather than 160 invoices to key.

What controls make it safe?

• Master file over invoice. Supplier and bank details always come from the master file.
• Unknown senders held. No invoice is processed for a supplier the agent cannot identify.
• Posted as unapproved. The agent's posting cannot be paid until a person approves.
• Coding confidence thresholds. Low-confidence coding goes to review.
• Every invoice filed with its trail. Extraction, checks, match, coding and routing on record.

Where Pryme fits

In Pryme, every invoice reaches the agent marked external, and an external claim cannot authorise a payment or change a supplier's bank details. Processing is certified on your own past invoices, including the duplicates and lookalike senders, and approval stays outside the agent's role scope.

Customer-side billing runs on similar rules, covered in whether an AI agent can issue customer invoices. The wider controls are in AI agents for finance: books you can audit.