Procure to pay: the process step by step, and where automation pays

Procure to pay is the chain of steps that turns a request to buy something into a recorded payment: a requisition, an approval, a purchase order, a receipt, a supplier invoice, a match between those documents, the payment, and the entry in the ledger. Very little of the effort in the procure to pay process goes into the buying. Ardent Partners, in its State of ePayables 2025 research, put the average cost of processing a single supplier invoice at $9.84 and the average time at 8.2 days, and found that 18.4 percent of invoices are exceptions, so roughly one invoice in five needs a person to work out why it disagrees with the order behind it. Ardent's own reading of its data is that exceptions are typically the biggest single reason those costs and cycle times are not lower. The numbers describe where the cost of the process sits, and they explain why automating it starts at the invoice rather than at the requisition.

The procure to pay process, step by step

The process has eight steps, and each one produces a record that the next one depends on.

1. A requisition: someone asks to buy something, through a procurement tool, an ERP screen, a form or an email.
2. An approval: a budget holder signs off, within the limits the company's delegation of authority sets.
3. A purchase order: purchasing commits to a supplier on quantity, price and terms.
4. A goods receipt: the warehouse or the requester confirms what arrived, or that the service was delivered.
5. An invoice: the supplier bills, by e-invoice, supplier portal or EDI, or as a PDF sent to an accounts payable inbox.
6. A match: the invoice is compared with the purchase order on price and with the receipt on quantity, within tolerances.
7. A payment: the approved invoice joins a payment run on its due date and goes out by ACH, check, card or wire.
8. A record: the payment posts to the ledger, receipts not yet invoiced are accrued at month end, and the bank statement is reconciled.

The purchase order is the document that holds the chain together. It is the company's commitment to a price and a quantity, and it is what the receipt and the invoice are later checked against. Two departments share the process, purchasing up to the order and accounts payable from the invoice onward, and in most mid-market companies they work in different systems, or in different corners of one system that were never set up to agree with each other. The hand-off between the two is where most of the problems below begin.

Procure to pay versus source to pay

Source to pay is the wider cycle. The Hackett Group defines source to pay as the whole procurement lifecycle, from strategic sourcing and supplier selection through purchasing, invoice processing and payment, so it adds the upstream work that happens before anyone raises a requisition: analyzing where the money goes, running sourcing events, choosing suppliers, negotiating contracts and setting suppliers up in the vendor master. That upstream half is often called source to contract, and procure to pay is the downstream half that begins once a supplier and its terms exist. Large companies buy separate software for each half and staff them with separate teams. A mid-market company usually has a controller, a purchasing manager and a small AP team covering both, so the distinction matters less as an org chart than as a sequence: spending that skips the upstream half arrives downstream without the contract and the order that would make it easy to pay.

Skipped upstream work is also where much of the risk enters. A supplier set up in a hurry, with bank details copied from an email, is an easy route for payment fraud. The Association for Financial Professionals found in its 2026 Payments Fraud and Control Survey that 76 percent of organizations experienced attempted or actual payments fraud in 2025. The controls that stop it sit inside the procure to pay process: a verified vendor master, a purchase order, a receipt, and a match before the money leaves.

Where the cost and the days sit

The clean invoice is cheap. When the price on the invoice agrees with the order and the quantity agrees with the receipt, the match clears in seconds whether a person or a system does it, and the invoice then waits only for its due date. The days and the cost pile up on the invoices that don't agree. The full report shows how wide the spread runs: best-in-class teams spent $2.65 and 2.9 days per invoice, against $12.42 and 13.5 days for everyone else, and carried an exception rate of 11.1 percent against 20.9 percent. The slow end of that distribution is working a larger queue of invoices that need someone to find a missing receipt, confirm a price the buyer renegotiated by phone, or ask the requester whether a freight charge was approved.

Each exception is a small investigation. The clerk opens the invoice, finds the order in one screen and the receipt in another, and reconstructs what happened between them: a partial shipment, a substitute item, a price change nobody wrote down. We walked through that reconstruction, and the redesign that removes most of it, in three-way match, rebuilt. The cost of the whole process is set by how many invoices need that investigation and how long each one takes, which is the arithmetic in the unit economics of the exception tail.

Invoices with no purchase order behind them

An invoice with no purchase order is an exception by construction. There is nothing to match it against, so someone has to find out what was bought, whether it arrived, who approved it and which account it belongs to, usually by email and usually after the fact. These invoices are common. In the same Ardent survey, 65.4 percent of invoices were linked to a purchase order on average, so roughly one in three arrived without one, while best-in-class teams linked 84 percent. Some spending never goes through an order for good reasons: rent, utilities, subscriptions and professional fees are billed against contracts or recurring terms. The rest is spending that should have had an order and didn't, and it is the part of the exception queue a company can shrink by changing how it buys rather than how it pays.

The format of the invoice adds a second layer of work. Ardent found that only 51.4 percent of invoices are submitted electronically, and an invoice that arrives outside a structured channel has to be read before it can be matched. Supplier invoices also differ in layout, in how they describe items, and in where they put the order number, when they include one at all. Reading that variety reliably is a problem of its own, which we treat in the long tail of document variability.

What procure to pay automation changes

For most of the last twenty years, procure to pay automation meant two things: optical character recognition that read invoice fields from fixed templates, and matching rules inside the ERP or an AP tool. Both work on the clean path, and what they leave to a person is the part that costs the money, so the newer work is aimed there.

An agent working the process reads each invoice in whatever form it arrives, extracts the lines, finds the order and the receipt, and applies the tolerances the finance team already uses. The invoices that clear go forward for payment. For the ones that don't, the agent does the investigation a clerk would do: it checks for a partial receipt, looks for a price change in the buyer's correspondence, asks the requester to confirm a receipt that was never entered, and presents the exception with the evidence attached and a proposed resolution. An invoice with no order goes back to the person who bought the goods, with a request to raise the order or approve the spend, and that routine is how purchase order compliance improves in practice. Before each payment run, the agent checks bank details against the verified vendor master and holds any change that arrived by email. After payment, it writes the entries back to the ledger.

People keep the decisions that carry judgment or authority: approving spend, settling a dispute with a supplier, changing a tolerance, adding a supplier to the vendor master. Nothing leaves without a person. The point of the agent is that when one of those decisions reaches a person, it arrives with everything needed to make it in a minute rather than an afternoon.

A reasonable counter, answered

A reasonable counter is that procure to pay suites exist for exactly this. Coupa, SAP Ariba and the procurement modules of the large ERPs digitize the requisition, enforce the purchase order, give suppliers a portal and run the match, and a company could buy one instead of automating around the systems it has. For a company with a procurement department and the purchasing discipline a suite assumes, that is often the right call. The mid-market company that buys through email and pays from QuickBooks or an older ERP is in a different position. A suite is an implementation project measured in months, and its value depends on suppliers and employees changing how they work, which the software encourages but can't do for them. Until they do, the invoices still arrive as PDFs, the spending without orders still happens, and the exceptions still land in a queue. An agent works on the documents and systems as they are today, as a layer on top of the existing systems, and a company that later adopts a suite can keep the agent on the exceptions the suite routes to people.