Almost every AP automation programme starts at the invoice, which is understandable, because the invoice is the document with the deadline attached. It's also the last document in the chain, which means most of what stops it was decided long before it arrived.

Two documents create the majority of those holds, and in most organisations neither one is automated at all.

The confirmation no one read

When a supplier acknowledges an order, they frequently change something — price, quantity, delivery date, etc. Peppol's ordering profile exists precisely because that response is a structured business document with meaning, and the BIS Ordering 3.3 specification covers the order response as a first-class message.

In practice, the confirmation arrives as a PDF in a buyer's mailbox, gets glanced at, and is never compared to the order. Three weeks later, invoice verification finds a price variance and stops the invoice, and an AP analyst spends forty minutes discovering that procurement agreed to the new price in an email no one in finance ever saw.

The delivery note that lives in a carrier portal

The second document has the same shape. A goods receipt posting in SAP updates the material stock and the purchase order history, which is what three-way matching depends on. Oracle turns the same dependency into a configuration choice through its match approval level options: two-way compares the order and the invoice only, three-way adds the receipt, four-way adds inspection. Worth knowing which of the three your services and expense lines run on, because two-way is common there and it means the receipt never enters the picture.

But in most groups the delivery note never reaches finance at all. It stops at a warehouse, in a carrier portal, or on a clipboard, and the only trace AP gets is a receipt posting that may lag the physical arrival by days. When it does, the invoice turns up before the evidence it needs and gets blocked for a reason that isn't a problem at all. It's a timing artefact, and your team works it like a genuine exception every single month.

What changes when both are read on arrival

Reading the confirmation on arrival converts a surprise into a decision. The price moved by an amount, against a limit somebody agreed, and either it sits inside the limit and a buyer updates the order, or it sits outside and a named person decides now instead of in three weeks. Be clear that the buyer step is a person: an inbound order response updates the delivery confirmation, the date and the quantity. It does not rewrite the price on the purchase order. If nobody changes the order, the variance you were warned about arrives on the invoice anyway.

Reading the delivery note does something similar at the other end. It gives AP a signal that goods arrived even before the receipt posts, so the invoice can be held for a known reason with a known clearing date instead of sitting in a general queue.

The four questions to ask about your own chain

Before buying anything, answer these for last quarter. Most teams have never had them written down:

• What proportion of held invoices trace back to a confirmation that changed something?
• How many blocks were lifted by the automatic release run once the goods receipt posted, with no buyer or supplier contact? And is that run actually scheduled?
• Where do order confirmations physically arrive, and who reads them?
• What's the median gap between physical delivery and receipt posting, by site?

That last number is usually the surprise. When it's four days at one plant and four hours at another, you've found a process difference that costs you a measurable amount of working capital every month.

What the after looks like on the 27th

The close week changes character. The exceptions that remain are disagreements about price, quantity or entitlement, and each arrives with the confirmation and the receipt already attached, so the person deciding has the evidence in one place.

What disappears is the category of hold that existed only because two documents were never compared.

What the Hypatos agents do with the two documents

Hypatos treats each use case as its own Workforce rather than as a feature of invoice processing. The order confirmation workforce reads the acknowledgement against the order and surfaces what changed, and the delivery notes workforce does the same at the receipt end.

Both follow the same rule as everything else in the workforce. The agents propose, a named person decides, and the record shows what was checked, so a price change that was accepted three weeks ago is visible on the invoice when it finally arrives.

Hypatos fits when your holds are being created upstream of AP, and when the documents that would have prevented them are arriving as PDFs to people who aren't measured on the close.

How many of your holds started at the dock

Take last month's held invoices and trace ten of them back to their origin — not the reason code, but the event.

If more than half started with a confirmation no one compared or a receipt that hadn't posted, your AP problem isn't in AP.

‍