BreathingRoom
By function

AI Agents in Purchase Order Management: Where It Breaks

Requisition to PO is a person copying fields between systems.

The loop, as it actually runs

  1. Requisition raised
  2. approved
  3. PO issued
  4. acknowledged by vendor
  5. goods received
  6. matched to invoice

Where it breaks

Not in the steps. In the joins between them:

  • Approval routing lives in someone's inbox
  • Vendor acknowledgements are not tracked
  • Receipts are recorded late
  • Match exceptions are found at payment, not receipt

What that actually costs

The expensive failure in purchase order management is finding the mismatch at payment rather than at receipt. By the time the invoice is in front of you, the goods have been accepted, the vendor relationship is engaged, and your leverage is gone — so the wrong price gets paid and someone makes a note to raise it next quarter. The gap between those two moments is the entire cost, and it is a function of how quickly receipts are recorded. Late receipting is not an administrative tidiness problem. It is where the money goes.

What we would build first

Vendor acknowledgement tracking goes first, and it is usually the least obvious candidate. Nobody tracks acknowledgements because each individual one seems unimportant, but an unacknowledged PO is the earliest possible signal that a delivery will be late — earlier than the delivery date, which is when everyone else finds out. An agent that chases acknowledgements and escalates silence gives you a week of warning on the problems that would otherwise become expediting calls.

It runs inside Bill.com, NetSuite, Airtable, Gmail, Slack — the tools already in use.

How this one goes wrong

An agent that raises purchase orders from approved requisitions will, eventually, raise one from a requisition approved for a different quarter, a cancelled project, or a budget that has since been cut. Approval is a moment in time and the agent treats it as permanent. The guard is a freshness window: an approval older than a defined period is re-confirmed rather than acted on, and any requisition tied to a project or cost centre that has changed state is held. It is a small check that prevents the class of error where the process worked exactly as designed and the outcome was still wrong.

The individual jobs inside this loop — what starts each one and where it has to hand back to a person — are covered under finance & bookkeeping.

Where it lands hardest: construction & trades, freight brokerage & 3PL and wholesale distribution. Each of those pages carries the sector’s own economics — the three roles that absorb the work, and the season that decides when a build can start.

In most companies this work sits with procurement clerks, production planners and purchasing agents. Each of those pages carries the wage arithmetic for that role, and says plainly where the numbers do not justify the spend.