Supply Chain & InventoryFree checklistPDF, Excel, Word export

Purchase Order Acknowledgement Review Checklist

An order acknowledgement is the supplier's written reply to your PO, and it is where price, date and terms drift away from what you ordered. This checklist helps you accept only what you actually agreed.

0%

0 of 34 items complete

10 critical items still open - these are the highest-risk gaps.

Download checklist:

Identification and quantity

Price and commercial terms

Delivery

Quality and compliance flow-downs

Recording and follow-up

Every critical item must pass before you accept the acknowledgement. Any open critical item should go back to the supplier in writing with a due date.

Acknowledgement exception report

Optional: we can outline an exception report that compares acknowledgements to POs in your ERP.

Optional. The tool and every export work without this. No spam.

How to use the checklist

Open the acknowledgement next to the PO and work through each group. Tick an item when the two documents match. Anything that does not match should be marked as an exception, then either accepted by the buyer with approval or sent back for correction. Export the completed list to PDF for the PO file when a PO is high value, regulated or part of a long-term agreement. For repeat orders you can check only the critical items.

  • Compare the acknowledgement and PO side by side
  • Treat each mismatch as an exception to resolve
  • Pay most attention to the items marked critical
  • Export the result for high value POs

Why acknowledgements matter

Under common contract law, a seller's acknowledgement that adds or changes terms can be read as a counter-offer, and silent acceptance of it can create disputes about which terms apply. Practical problems follow, such as a price increase billed months later or a lead time that nobody noticed. A short review at acknowledgement stage costs far less than correcting these at invoice or receiving. Ask your legal advisor how your jurisdiction treats conflicting terms.

Handling exceptions

Record each exception with the line, the difference, the impact and the decision. Small differences such as a one-day date change may be accepted by a buyer within a set limit. Price increases, new surcharges, quality clause changes and different Incoterms should go to a manager. Reply in writing and update the ERP, not only the email thread, so that receiving, planning and accounts payable all see the same data.

Common mistakes

Common errors are filing acknowledgements without reading them, accepting a revised date without telling planning, allowing the supplier's standard terms to replace yours, and never chasing missing acknowledgements. Another problem is not tracking who accepted what. A simple exception log with names and dates prevents blame later and shows which suppliers regularly change terms.

  • Do not file without checking
  • Tell planning about every date change
  • Reject conflicting terms in writing
  • Chase missing acknowledgements

Frequently Asked Questions

Is an order acknowledgement legally binding?

It can be. A seller's acknowledgement may count as acceptance or as a counter-offer, depending on the jurisdiction and the terms. If it changes your terms and you do not object, disputes about which terms apply can follow. Confirm your position with legal counsel.

How soon should a supplier acknowledge a PO?

Many buyers ask for acknowledgement within one to three business days. Put the time limit in the PO terms or supplier agreement, and chase after it passes. For long lead items, request line level promise dates, not only an order level date.

What is an EDI 855?

The X12 855 is the purchase order acknowledgement transaction. It lets the supplier accept, change or reject lines of an EDI 850 purchase order. Your ERP can compare the 855 with the PO automatically and flag price or date differences.

Should every acknowledgement be reviewed?

Review all acknowledgements for high value, regulated or new supplier orders. For stable repeat items you can sample, or let the ERP flag only the differences. The aim is to catch changes, not to read identical documents repeatedly.

If acknowledgements arrive as PDFs or EDI 855 messages, we can build a read-only agent that compares them with the PO in your ERP and lists the differences for the buyer to approve.