Procurement Automation

Purchase Order Acknowledgement: Does It Match What You Ordered?

The five differences between a purchase order and the supplier's acknowledgement that cost money, the rule that catches each, and what stays manual.

By
PhaseVane
Published
Reading time
7 min
On This Page

You issued the purchase order (PO) on Monday. The supplier's acknowledgement came back on Wednesday as a PDF, and it looks like the order. It has your PO number, the right item description and the right quantity on the first line. Further down, the unit price is AUD 1.70 higher "at time of dispatch", the delivery date is a week later than you asked for, the item code ends in PG instead of HDG, and 20 of the 120 lengths are on back order. Nobody reads that far until the invoice arrives.

An acknowledgement is the supplier telling you what it intends to deliver, at what price, and when. Checking it against the PO is the cheapest point to catch a difference, because nothing has been made or shipped yet. This guide sets out the five mismatches that cost money, the rule that catches each, and what you need from your ERP (the business system that holds your purchase orders) to automate the check.

In short

  • Five fields carry the money: price, quantity, date, item or specification, and terms.
  • Each needs its own tolerance. A later date is a block if it misses your need date; an earlier one is information.
  • Silence is a mismatch too. A PO with no acknowledgement after a set number of days goes on a chase list, and that needs only your PO data.
  • The obstacle is data access, not matching. You need a read-only PO export from your ERP. Without it, nothing can be checked automatically.
  • Accepting a change is a buyer decision. Software lists the differences and drafts the question; you decide whether to accept.

The annotated example

A contractor orders a top-up of ladder tray from a Sydney wholesaler for a site at Wetherill Park.

Field Purchase order PO-DEMO-2207 Supplier acknowledgement Mismatch
Item code LT300-3HDG LT300-3PG Item: PG reads as pre-galvanised; the PO specifies hot-dip galvanised to AS/NZS 4680
Quantity 120 lengths 100 now, 20 on back order Quantity: 20 lengths late, date not given
Unit price ex GST AUD 39.50 AUD 41.20 "price at time of dispatch" Price: 1.70 a length higher, and not fixed
Delivery charge AUD 220.00 AUD 260.00 Price: 40.00 higher
Delivery date 20 October 2026 (site need date) 27 October 2026 Date: 7 days after need date
Payment terms 30 days end of month 30 days end of month none
Terms Your PO terms "Supplier's standard terms apply" Terms: new clause

The money, computed:

  • Unit price: (41.20 − 39.50) × 120 = 1.70 × 120 = AUD 204.00
  • Delivery: 260.00 − 220.00 = AUD 40.00
  • PO value: 120 × 39.50 + 220.00 = 4,740.00 + 220.00 = AUD 4,960.00
  • Acknowledged value if all 120 ship at the new price: 120 × 41.20 + 260.00 = 4,944.00 + 260.00 = AUD 5,204.00
  • Difference: 5,204.00 − 4,960.00 = AUD 244.00 (4.9% of the PO), before any second delivery charge for the back order

Two of the five mismatches have no price on them and matter more than the 244.00. The pre-galvanised code is a specification change that may not meet the project requirement. The 7-day slip may hold up the installer.

The five mismatches

Mismatch How it costs money Rule Default severity
Price You pay the acknowledged price because the invoice matches it, not the PO Unit price or any charge differs from the PO; or wording makes the price variable ("at time of dispatch", "subject to surcharge") Block if higher; warn if variable; info if lower
Quantity Short or split deliveries; extra delivery charges; overage you must store or return Acknowledged quantity differs; back order or part shipment stated; rounding to a pack size Block if short against need; warn on split
Date Programme delay, idle labour, expediting cost Acknowledged date later than the PO date or the need date Block if after need date; warn if after PO date but before need; info if earlier
Item or specification Wrong product installed, rework, failed inspection Supplier code differs from the PO code; description adds or removes a specification term; "equivalent" or "alternative" appears Block
Terms A different payment term changes cash flow; a new terms clause may change your position Payment terms, Incoterms rule, delivery basis or a terms reference differs Warn; route anything about contract terms to whoever owns them

On terms: which set of terms governs when an acknowledgement refers to the supplier's own is a legal question that depends on your contract and your jurisdiction. This guide does not answer it. The check's job is to make sure the reference is seen by the right person. This is commercial guidance, not legal advice.

Tolerances: where to start

Every buyer sets their own. These are starting points that err towards showing too much rather than too little.

Field Starting tolerance Reason
Unit price Zero, unless a price variation clause or index adjustment is agreed in writing Any undisclosed increase is a decision, not noise
Charges (delivery, packing, surcharges) Zero; any new charge line is flagged New lines are where increases hide
Quantity Zero, except an agreed pack-size rounding Short delivery and overage both cost
Date Block after need date; warn after PO date The need date is what the site cares about
Item code Exact match, or an approved cross-reference list A code change is a specification question until proven otherwise
Currency Exact A currency change moves risk

What the check needs from your systems

From the ERP (read only): a daily export of open PO lines with PO number, line number, supplier, your item code and the supplier's item code, description, quantity, unit, unit price, currency, charges, PO date, need date, payment terms and Incoterms rule if used. A CSV export is enough. No write access is needed.

From the inbox: acknowledgements forwarded to a dedicated mailbox, or a rule that copies emails with "order confirmation" or "acknowledgement" in the subject. Acknowledgements that arrive by EDI (electronic data interchange) are already structured and can skip extraction.

Matching: by PO number first, then line number, then supplier item code. When the acknowledgement does not quote the PO number, the line is held for a person to match, never guessed.

This is the main reason PO acknowledgement checking is a harder first project than quote comparison: it needs a reliable ERP export and someone in IT to set it up. If your ERP cannot produce one, fix that first.

Who does what

You provide: the PO export, the acknowledgement mailbox, your tolerance settings, and an approved list of supplier code cross-references if you have one.

The system does: extracts each acknowledgement line with its source text, matches it to the PO line, applies the tolerances, produces a daily exceptions list, and drafts a question to the supplier for each exception. It also lists POs with no acknowledgement after the number of days you set.

The reviewer approves: each exception, either by accepting the change (with a reason) or by sending the drafted question. Every acceptance is logged.

What is exported: the exceptions list and the log, as Excel or CSV. Accepted changes are flagged for someone to update the PO in the ERP; the check never writes to the ERP itself.

What stays manual: deciding whether a later date or a substitute is acceptable, negotiating the price back, updating the PO, and anything to do with contract terms.

For the controls that keep extracted values traceable, see the controls that keep extraction honest. The same approach, applied to certificates and licences, is in supplier document tracking.

Where the PO Confirmation Checker fits

The PO Confirmation Checker is a PhaseVane workflow built to the rules above. It is in development and not on sale, and it is planned as a second workflow for teams that already have a clean PO export. PhaseVane is looking for design partners to test it on real POs and acknowledgements.

Book a 20-minute workflow call. Bring a PO export and five recent acknowledgements. You leave knowing whether your ERP export is enough to automate the check and which tolerances to set. Book a workflow call

If you would like to test it on your own documents, join the design-partner list.

Sources

No external data is used in this guide. The method and tolerances are PhaseVane practitioner judgement. Checked 9 October 2026.

Bring a PO export and five recent acknowledgements. You leave knowing whether your ERP export is enough to automate the check and which tolerances to set.

Book a 20-Minute Workflow Call

Or see Quote Desk.

Related Research

See all research notes

Topic: Procurement Automation

  1. Cost Driver Monitoring: Is This Supplier Price Increase Justified?

    Map each supplier cost element to a free public index, track it monthly, and test a price increase claim against the weighted move. Worked example.

    Procurement Automation
    Read More
  2. Freight Quote Comparison Automation: Can It Keep the Detail?

    How automated intake turns forwarder quotes from email, PDF and Excel into one comparison without dropping surcharges, TBA lines or validity.

    Procurement Automation
    Read More
  3. Human Review in Procurement Automation: What Stops a Misread Value?

    Ten controls that stop a wrong extracted value reaching a purchase order: source text checks, code-only maths, blocking flags and an approval log.

    Procurement Automation
    Read More