Review the Purchase-Order Acknowledgement Before Production Starts

You order 10 pieces of a part for a required date. The supplier acknowledges one pack of 12 and gives a later date. That acknowledgement is useful, but receiving it does not answer the two questions that matter: does your company accept the extra two pieces, and can the new date still support the job?

Resolve those questions before production or allocation starts. Put the supplier’s acknowledgement beside the purchase order that was actually released, compare every line and term, route each difference to someone with the authority to decide it, and preserve the final version agreed with the supplier. An acknowledgement can accept the PO as issued or propose amendments; the buyer still needs to identify and close those amendments rather than treating receipt of the document as automatic acceptance.

Place the acknowledgement beside the released PO

Start with document identity. Record the PO number, supplier, buyer entity, currency, acknowledgement reference and the revision or issue date on both documents. Then confirm that the PO beside the acknowledgement is the released version sent to that supplier. A draft, an earlier revision or a buyer’s working spreadsheet is not a reliable comparison baseline.

The acknowledgement should be treated as the supplier’s response to a particular order. Lapasar’s procurement glossary describes that response as either acceptance of the issued terms or a proposal to change them. Infor’s purchase-order acknowledgement results documentation likewise compares the acknowledgement with the PO and displays message lines when processing errors or differences occur.

If the references do not establish a single matching pair, stop the review at the document level. Ask the supplier which PO revision it acknowledged, or resend the current released PO and request a new acknowledgement. Do not copy confirmed values into an internal sheet and assume the scope problem is solved. Until the document pair is known, every apparent match or exception remains uncertain.

Review each changed line

Compare one PO line with one acknowledged line at a time. Use stable identifiers such as the PO line number and the ordered part number; descriptions alone can be too broad. For each line, place the original requirement beside the confirmed value for the part number or specification, quantity, unit of measure, unit price, currency, required or promised date, and any stated minimum order or pack rule.

A blank is not a match. It is an unknown that must be clarified when the field is necessary to release the line. The same applies when an acknowledgement summarizes an order at header level but does not state how an exception affects an individual line. The practical goal is not a green-looking spreadsheet. It is a list in which every line is either confirmed unchanged or has an identified difference with an owner and a recorded answer.

This line-level approach is consistent with the difference types in Invoice Data Extraction’s acknowledgement checking guide, which calls out price, quantity, dates, backorders, substitutions, minimum quantities and pack sizes. Its software claims are specific to that provider; the useful method here is the side-by-side comparison of ordered and acknowledged values.

Backorders and substitutions

A backorder changes more than the quantity shipping first. Record the quantity available now, the balance on backorder, the promised date for each portion and whether split delivery is acceptable. “10 ordered, 6 confirmed” is incomplete if the acknowledgement does not say whether four are cancelled, rejected or due later. Keep the unresolved balance open until the supplier supplies that answer and the person responsible for the requirement decides whether the resulting schedule works.

A substitution needs a separate decision. Capture the supplier’s proposed part number and the exact point of difference from the ordered item. Do not approve a substitute because the description says “equivalent,” and do not infer interchangeability from price or appearance. Send fit, interface, material, rating, revision and other specification questions to the person responsible for technical acceptance. If that person rejects the substitute, procurement can ask the supplier to restore the ordered part, propose another option or confirm the backorder. If it is accepted, retain the approval and make the accepted identifier visible in the final order record.

Keep quantity and substitution decisions separate even when they appear on the same line. A reviewer may approve six units now and four later while rejecting the proposed alternative part. One broad status such as “approved” can hide that split result.

Pack-size changes

Pack size, order unit and piece quantity must be read together. In the opening example, “1 pack” and “12 pieces per pack” mean 12 pieces, not the 10 pieces on the released PO. The register should preserve all three values: ordered quantity and unit, acknowledged pack quantity and pack size, and the resulting piece quantity. It should also show any corresponding change in extended line value and storage or usage impact.

Never silently round the internal PO quantity to the supplier’s pack size. The buyer or other commercial authority may accept the 12-piece pack, negotiate a different quantity, or decline the change. The supplier then needs to acknowledge the resulting choice. If the line also has a later date, close the quantity and date as separate exceptions. Acceptance of the pack does not prove acceptance of the delay.

The table below shows a compact exception register using hypothetical values. It is a working control, not a KTSU test record or a substitute for the underlying PO and acknowledgement.

The first row is traceable to a decision and a matched final document pair. The second is still open. The order should not be marked fully released merely because the quantity question has been resolved.

Resolve differences through the right approver

Assign the decision by what the changed field affects, using your company’s actual approval matrix. Procurement can normally own supplier communication and commercial negotiation, but that does not give one person authority over every consequence of a changed line.

• Send part-number, material, drawing, revision, fit or performance changes to the designated engineering, product or technical authority.
• Send unit price, currency, minimum quantity, pack-size and other commercial changes to procurement and any budget authority required by the resulting value.
• Send promised-date, split-shipment and backorder impacts to the planning, maintenance or operations owner who controls the need date.
• Send inspection, certification or quality-document changes to the quality authority named for the order.

Some exceptions need more than one answer. A 12-piece pack at the original unit price may need commercial approval for the extra quantity and operational confirmation that the surplus can be received. A substituted part may need technical acceptance before procurement can agree a revised price. The register should therefore allow one PO line to have multiple exception rows or clearly separated decisions.

Record the decision in a form the next person can verify: approver name or role, date, exact accepted or rejected value, conditions and the document or message that carries the supplier’s response. “Discussed,” “noted” or “OK” is too vague when several values changed. A decision such as “accept 12 pieces at CAD X.XX each; do not accept 29 Oct; supplier to reconfirm 15 Oct” separates the resolved term from the open one.

After the internal decision, send it back to the supplier and request a corrected acknowledgement or another clearly referenced written response. Changing only the buyer’s internal sheet creates two competing records: the buyer plans against the revised value while the supplier may still produce or ship against its earlier acknowledgement. Likewise, an automated import that updates confirmed quantities or dates does not show that the right person accepted the business impact.

Treat an unanswered exception as a hold for the affected line. Do not replace the missing answer with an assumption, a blank cell or the latest value seen. If production must start before every issue can be closed, the responsible authority should define and record the limited release scope. The register itself cannot grant that authority.

For broader supplier-selection considerations outside this acknowledgement task, see Undercarriage Parts Supplier: Reliable OEM Solutions for Construction – KTSU.

Save the final agreed order record

Close the review by preserving the chain from original requirement to final agreement. Keep the released PO, the first acknowledgement, the exception register, each internal decision, the supplier’s answers and the final PO/acknowledgement pair. Use revision identifiers and dates so a receiver, planner or accounts-payable reviewer can tell which version governs the operational handoff.

A final pass should answer five questions:

1. Does every acknowledgement line map to a line on the released PO, with the same units or an explicit conversion?
2. Is every change to part, quantity, price, pack or date recorded as its own resolved or open exception?
3. Did the person with authority for each affected field give a specific answer?
4. Did the supplier confirm the resulting values in a referenced final document or message?
5. Do the operational copy, supplier copy and exception register point to that same final version?

If any answer is unknown, keep the relevant line open. A register with no highlighted differences can still be incomplete if a required confirmed value is missing. Conversely, a changed line can be ready when the difference, authority, answer and supplier-confirmed final version are all traceable.

The hypothetical opening case therefore closes only when both decisions are complete: 12 pieces are accepted or rejected through the commercial route, and the later date is accepted or corrected through the planning route. The resulting PO and supplier acknowledgement must agree with those decisions. If you are preparing an undercarriage-parts order with KTSU, send the part and order details for review, including the PO reference, affected line, requested value, acknowledged value and unresolved question.