Purchase Order Change Stamps for Procurement Control

A vendor change can alter quantity, price, delivery, specification, tax treatment, payment terms, or the person authorized to receive goods. If staff write “approved change” on the original purchase order, receiving and accounts payable may still act on different versions.

A procurement stamp system should preserve the baseline order, identify the proposed variance, and show when the revised commitment becomes effective. It does not replace the purchasing system, contract terms, budget control, or delegated authority.

The routing cover should identify:

• purchase order and revision;
• supplier;
• requisition or contract reference;
• original amount or controlled financial reference;
• delivery location;
• buyer;
• issue date;
• current authorized version.

Never alter the original order and reuse its version. The receiving team needs to know which terms applied when goods arrived.

The covers initial sourcing and approval; this workflow starts when the issued commitment changes.

A change request should state what is changing and why.

Use PROPOSED CHANGE until the required reviews and supplier communication are complete.

One request may need several decisions:

• scope owner;
• technical reviewer;
• budget owner;
• procurement;
• legal or contract owner;
• tax or finance;
• receiving site;
• information security or privacy, when relevant.

Each state must name its scope. BUDGET AVAILABLE does not mean the commercial change is authorized, and supplier acceptance does not prove internal approval.

A supplier proposes delivering half the order this month and half next month with an added freight charge. The buyer should not write the new total on PO v1.

The change cover can show:

CR-07 · SPLIT DELIVERY + FREIGHT IMPACT · SUPPLIER QUOTE Q-92 · BUDGET / BUYER APPROVAL PENDING

After approval and supplier confirmation:

CR-07 AUTHORIZED · PO v2 ISSUED · SUPPLIER ACCEPTED 6 SEP · RECEIVING NOTIFIED

The original PO, request, approvals, and revised PO remain linked.

A purchase-order change can move through:

1. REQUEST LOGGED.
2. IMPACT EVIDENCE COMPLETE.
3. REQUIRED REVIEWS COMPLETE.
4. AUTHORIZED WITHIN DELEGATION.
5. REVISED PO GENERATED.
6. REVISED PO SENT.
7. SUPPLIER ACCEPTANCE RECORDED.
8. DOWNSTREAM SYSTEMS UPDATED.

Only after the revised order is issued should receiving and invoice matching treat it as the active instruction.

Send the revision to the delivery location with changed lines clearly identified. A receiving cover may state ACTIVE PO v2, SUPERSEDES v1, QUANTITY CHANGE LINES 3–4, and DELIVERY WINDOW REVISED.

If goods arrive under the old terms, mark the variance and route it. Do not force the receipt to match the revised order without evidence of supplier acceptance.

Accounts payable should match the invoice to the purchase order revision, receipt, change reference, and any authorized exception. A higher invoice is not proof that a change was approved.

The provides a related state model for duplicate, exception, approval, and payment queues.

If a change request is rejected, withdrawn, or replaced, preserve that outcome. Use REJECTED, WITHDRAWN, SUPERSEDED BY CR-08, or EXPIRED. Never leave an abandoned request looking pending.

Likewise, stamp obsolete printed orders SUPERSEDED — DO NOT RECEIVE without covering the original terms. Keep the audit copy according to policy.

Build the set through the . A helps distinguish request, approval, issue, and acceptance events when paired with the PO revision.

Use a fixed block with PO, revision, change request, state, owner, and date. Test the mark on purchase orders, quotes, receipt packets, and scanned invoices.

Choose price, quantity, delivery, specification, cancellation, and emergency changes. Confirm that each request has evidence, scoped approvals, an issued revision, supplier acknowledgment, receiving communication, and invoice alignment.

The control succeeds when no one has to ask which purchase order was active at the moment the organization committed, received, or paid.