Before updating a purchase order from a supplier confirmation, check that the response covers the correct revision, every relevant line, and the actual quantities, prices, specifications, and dates agreed. Record any difference as a proposed change until the authorized owner accepts it.
The downloadable PO confirmation checklist (Excel) is designed for reviewing a reply that has already arrived. If the response is missing, start with the PO chasing playbook.
Gather the comparison set
Open the current approved PO, the supplier acknowledgement, the applicable quote or agreement, and approved amendments. Include relevant attachments and line notes. Record the confirmation reference and receipt time so another buyer can reconstruct the review.
Check whether the acknowledgement responds to an earlier PO revision. A supplier may correctly confirm revision two while the current order is revision three. Ask for confirmation of the changed lines rather than treating an older document as approval of the latest request.
Use three results for each check: match, difference, or unknown. A blank field is unknown unless an explicit reference unambiguously incorporates the agreed value. This avoids giving incomplete acknowledgements the appearance of a clean review.
Check order identity and coverage
- Supplier legal entity and ordering site match the intended counterparty.
- PO number and revision identify the current request.
- Supplier order number is captured.
- Every relevant PO line is accounted for.
- Rejected, omitted, substituted, and split lines are visible.
- Ship-to site and delivery address are correct.
Review coverage before totals. A confirmation can have a plausible total while excluding a critical line. If the supplier acknowledges only part of the order, keep the remainder open with a precise follow-up question.
Microsoft’s vendor-collaboration workflow supports line changes, rejections, substitutions, and split deliveries. Those are distinct responses to review, not interchangeable meanings of “confirmed.” Other systems may represent them differently. Microsoft documentation.
Identify the level at which the supplier made the promise. A header saying “all items confirmed” may incorporate every unchanged line, while a line note can override the header for one item. Record which evidence supports the accepted value rather than flattening all notes into one order status.
When one acknowledgement covers multiple POs, split the review by PO, line, and revision. When multiple acknowledgements cover one PO, check whether the later document replaces the earlier one or adds a delivery schedule. Ask the supplier if this is unclear; adding both quantities can double the apparent commitment.
Check the material and quantity
- Internal item and supplier part number map to the same requested material.
- Manufacturer part number, drawing, grade, or specification revision matches where required.
- Quantity and unit of measure match, including pack conversions.
- Split deliveries sum to the intended total.
- Minimum order quantities or order multiples have not silently increased the purchase.
- Required certificates, inspection documents, packaging, and traceability requirements are acknowledged where applicable.
Do not infer interchangeability from a similar description. If a supplier offers an alternative grade or part, capture the proposed difference and route it for technical and purchasing review. A note saying “equivalent” is a claim to check.
For units, retain the original expression alongside any conversion. “Ten boxes of 50” and “500 each” may reconcile cleanly; “ten boxes” with no pack quantity does not. Ask the supplier to state the missing basis.
Check price and commercial details
- Currency, unit price, and price basis are explicit.
- Extended line amount reconciles with quantity and unit price.
- Discounts, surcharges, tooling, packaging, and freight follow the applicable agreement.
- Payment and delivery terms have not changed without review.
- Any new condition in the acknowledgement is identified for the appropriate commercial owner.
Do not resolve conflicting documents by choosing the newest timestamp alone. Establish which agreement or approved change governs the field. Preserve the supplier’s proposal and the buyer’s decision so a later invoice review has evidence of what was accepted.
This checklist records operational differences; it does not determine the legal effect of competing terms. Send a disputed term through your established commercial review process.
Apply tolerances only where authority is explicit
Your team may have approved rules for rounding, price differences, delivery windows, or over- and under-delivery. Record the rule, units, scope, and owner before using it. A configured tolerance is not evidence that an item substitution, specification change, or new surcharge is commercially acceptable.
For a pack conversion, verify both quantity and value. If a PO requests 240 each at $3.25 and the supplier confirms 20 packs of 12 at $39, the quantities and $780 total reconcile. If the supplier confirms 20 packs at $3.25 without identifying the price basis, ask whether the price is per pack or per item. A plausible total elsewhere does not fix the ambiguous field.
Where rounding is permitted, retain the unrounded calculation and the permitted rounding rule. Where approval is needed, give the owner the original value, proposed value, absolute difference, and consequence. Do not quietly round an exception away to make the order pass review.
Check dates at the right level
For each line or split schedule, distinguish requested dates from confirmed dates and dispatch from receipt. Capture the destination and any condition attached to the promise, such as receipt of an advance payment or release of a drawing.
Confirm that a week number or date range is usable for planning. Ask for clarification when a critical need falls inside that range. Include receiving and inspection time when assessing whether the date meets the production requirement.
Microsoft separately defines requested and confirmed ship and receipt dates. That distinction is useful when reviewing a supplier’s free-text acknowledgement, even if your own system uses different field names. Microsoft date definitions.
Worked example: a confirmation that looks complete
In this illustrative example, PO line 20 requests 500 seals, revision C, at $2.40 each, received October 12. The confirmation states ten boxes at $120 per box, revision C, “delivery October 12.”
The supplier confirms each box contains 50 seals, so the quantity and $1,200 total reconcile. But “delivery” means dispatch from its warehouse. The buyer asks for the receipt date, and the supplier confirms October 14.
The review therefore records matching material, quantity, and price, with a date difference requiring planning’s decision. The buyer retains October 12 as the requirement and records October 14 as the proposal until approval. If planning cannot accept it, the line moves into a recovery plan.
Suppose the same PO has line 30 for 200 washers at $0.80 each. The acknowledgement omits it entirely. The order’s expected total is $1,360, but the supplier document shows only $1,200. The buyer does not mark the PO confirmed because line 20 reconciles financially. Line 30 remains unknown, with a request for 200 washers and a receipt commitment.
The completed review has two actions: planning decides the seal receipt proposal, and the supplier answers the missing washer line. If planning accepts October 14 and the supplier confirms the washers unchanged, the authorized updater records both dispositions. The review retains the original October 12 requirement, the approved change, and the supplier evidence supporting the current schedule.
This example contains no quality release. Matching revision C on the acknowledgement establishes the stated commitment; it does not establish that the delivered seals meet revision C. Inspection and acceptance remain a later responsibility for the appropriate quality owner.
Route differences to the person who can decide them
Procurement owns assembling the comparison and obtaining missing facts. Planning evaluates effects on need dates and quantities. Engineering or quality reviews specifications, approved substitutions, and acceptance requirements. The authorized commercial owner approves price and term changes. Finance retains its own invoice and payment responsibilities.
Use a single review record with separate actions when a line has several differences. For example, a substitute part offered at a higher price with an earlier date needs both technical and commercial decisions. Approval of the price does not approve the part. Record which decisions must precede others.
If an approver is absent, route through the established delegation process and record the alternate owner. Do not treat a forwarded email or an unanswered approval request as acceptance. The buyer handover guide gives a working format for transferring open decisions.
Deal with revisions arriving during review
Before applying an update, check that the PO revision and supplier response are still current. If the buyer changes quantity while a review is open, preserve the completed checks for unchanged fields and recheck affected lines. Record the point at which the old review was superseded.
A supplier may send a corrected PDF without changing its reference number. Retain the receipt timestamp and file version so the evidence is distinguishable. Ask whether it replaces the full acknowledgement or only a named section.
After an approved update, read back the current record. Verify units, schedule totals, dates, and linked approval. If the update fails, leave an explicit record-update action open; do not send a success message based on an attempted save.
Check review quality as well as completion
Define review completeness as reviewed lines with every applicable field classified and every difference disposed of, divided by all lines in the selected acknowledgement cohort. Keep unknown fields visible in the denominator. A checklist tick is insufficient if the supporting source cannot be found.
Track rework separately: lines reopened because a material confirmation difference was missed, divided by previously completed reviewed lines in the same cohort. State the observation period and review sample. Later changes by the supplier are a different cause from an original review error.
For a weekly sample of 40 completed lines, two missed pack conversions produce a 5% observed rework rate for that sample, not a claim about every order. Read the two failures to determine whether the form, mapping data, or reviewer guidance needs correction.
Record the disposition and finish the review
For each difference, name the decision owner, next action, and due time. Once approved, update the authoritative record through the normal change process and retain the evidence. Check that any derived dates or downstream requirements still make sense after the update.
The confirmation review closes when all relevant lines have a documented disposition and the accepted commitments are reflected in the record. Delivery and invoice work continue under their own completion criteria.
Use this checklist to define what good purchase order management looks like in your team: a dependable commitment and a traceable decision, ready for the next person who touches the order.
