An agent built 14 payment runs. A human still pressed send.

The person who builds the weekly payment run just met their replacement. It ran fourteen batches in five weeks.

Coupa published the numbers on August 20, 2026. Its Payment Batch Creation Agent ran 14 payment batches on its own.

That covered 2,395 separate payments worth $20.1 million. All of it in the agent's first five weeks in production.

Coupa says more than 450 customers now run its agents in production. The batch agent is the one that touches money.

One line in the release matters most. The agent does everything up to release.

A human still approves the money leaving. Or a separate system does.

A corporate payment run has six steps. Most people outside finance think it has one.

Step one is capture. The invoice arrives as a PDF, an email, or a data file, and the system reads it in.

Step two is the match. The invoice gets checked against the purchase order and the receiving record.

That is the three-way match. It is the control that stops a company paying for goods it never got.

Step three is approval. A budget owner signs off, and the invoice becomes payable.

Step four is the batch. Someone decides which approved invoices go out in this run, and which ones wait.

This is the step Coupa automated. It looks clerical and it is not.

Step four is a judgment call with money attached. Cash on hand, due dates, and early payment discounts all argue with each other.

Step five is release. The batch gets approved and the payment file goes to the bank.

Step six is settlement and matching. The bank pays, the statement comes back, and the ledger gets squared.

The agent owns step four. It reads the approved queue and assembles the run.

Nobody sorted invoices by hand for those 14 batches. The output arrived ready for a signature.

The legacy setup is a clerk plus a rules engine. Rules handle the easy cases, and a person handles what the rules cannot express.

That person carries context no system holds. Which vendor called angry last week, and which one is about to miss payroll.

The trade is throughput for memory. A clerk is slow, and a clerk remembers.

The machine setup wins on volume and consistency. It applies the same logic to every invoice at 2 a.m. on a Saturday.

Where machines fail is specific.

Duplicate invoices are the first failure. The same bill arriving through two channels looks like two valid payables.

Vendor bank detail changes are the second. It is a common corporate payment fraud, and it looks exactly like routine vendor maintenance.

Discount math is the third. A 2% early payment discount is worth taking until the cash costs more elsewhere.

That last one is why the human release step is not theater. Somebody has to own the funding decision.

There is a control reason too. Separation of duties is an audit requirement, not a preference.

If one system prepares and approves, the control collapses. Auditors will not sign that.

Four pools move here.

The first is accounts payable headcount. Shared service centers are staffed for invoice volume, and step four is where that volume lives.

The second is outsourcing. Finance outsourcing contracts are priced per invoice processed.

That pricing dies when the invoice needs no processing. The vendor sold effort, and the effort left.

The third is bank float. Payment timing gets optimized, and optimized timing means less idle cash in an operating account.

The fourth is supply chain finance. Banks earn on early payment programs because companies cannot chase discounts at scale.

An agent that chases them changes the pitch. The bank was selling a service the buyer can now perform.

Now look at the other end of the same pipe. Agents also pay each other directly, with no invoice at all.

Coinbase's x402 protocol has handled more than 165 million payments worth about $50 million. Lincoln Murr, its head of AI product, estimates 99% settle in USDC.

Do the division. That is roughly 30 cents per payment.

Coupa's average is about $8,400. Same technology, two completely different economies.

One has a human on the release button and thousands of dollars at stake. The other has neither.

Step four fell. Step five held.

The judgment of which approved bills to pay this week is now machine work. The authority to move the money is not.

That limit is an audit rule, not a capability gap. Rules change faster than capabilities do.

Watch for the moment a controller accepts a second system as the approver. Step five falls the day that becomes normal.

Territory: +machines on payment preparation, +incumbents on the release.

Accounts payable labor and per-invoice outsourcing fees compress, while the release control stays human by audit rule.