2026-06-10 / 4 min read / proforma invoice / version control / payment review

How to Handle a Supplier That Changes the Proforma Invoice

By Trado Asia editorial desk · Published 2026-06-10 · Updated 2026-07-18

PI changes should be tracked by version, reason, and impact before deposit or balance payment.

What to check in the order file

Suppliers revise proforma invoices for ordinary reasons: corrected quantity, updated freight, changed packaging, new delivery date, or bank detail correction. The buyer should track revisions instead of treating every new PDF as final.

Save each version with date and sender. Compare seller name, product description, quantity, price, currency, payment term, beneficiary, shipping term, and delivery schedule. Small edits can change risk.

Ask for the reason when a revision affects legal identity or payment. A changed beneficiary, invoice issuer, or bank country needs more review than a corrected carton count.

Do not pay from an old PI after a new one appears. Confirm which version controls the order and ask the supplier to cancel or supersede prior versions in writing.

Create a short revision log. One line is enough: version, date received, changed fields, reason, buyer decision, and approved by. This helps when the team has several PDFs in email and nobody remembers which one matched the final payment.

Separate commercial changes from risk changes. A corrected delivery date or carton estimate may be routine. A new seller name, new beneficiary, bank country change, or sudden split payment request should trigger a harder review. The question is not whether the supplier can edit the PI; the question is whether the edit changes who is responsible, who gets paid, or what is being shipped.

When the buyer accepts a revision, update related records. The PO, shipment document pack, payment approval, and landed-cost worksheet may all depend on PI fields. If only the PI changes, the file can become internally inconsistent even when the supplier's explanation is reasonable.

Make the decision before the next handoff

Keep the approved PI with the payment proof. Accountants, managers, and dispute reviewers need to see exactly which version supported the transfer.

PI changes should be tracked by version, reason, and impact before deposit or balance payment. Another member of the team should be able to verify the answer from the file before the next transfer of funds. Name this point in the how handle invoice closeout rather than leaving it in chat.

Open the approved PI, beneficiary details, bank confirmation, payment receipt, and PO version together. Mark the first changed field and retain the earlier version beside the document the buyer plans to use. The comparison should show who supplied the revision, when it arrived, and which order step depends on it. The version control file should show how this point was resolved.

Familiar commercial explanations can hide a real mismatch. Ask which company, record, quantity, model, payment, or shipment the answer covers, and record when the answer applies only to this order. Use the payment review record to show who accepted the result and on what date.

Assign the file to finance and the purchasing team who approved the commercial terms. The owner does not need every chat message, but does need the final document, vendor answer, purchasing team decision, and next checkpoint. Link the answer to the proforma invoice checkpoint for this order.

The unresolved risk is that money may move against a different company, amount, currency, or document version. State whether the exception covers one shipment, one payment, one model, or the wider vendor relationship. A one-order decision should not silently become standing sign-off. Make this result visible in the how handle invoice decision record.

Close the record for the next order

Use the checklist as a closing test: save every pi version, compare identity and payment fields, ask reasons for major changes, and confirm the controlling version. Record who completed each step and save the evidence beside the document it supports instead of leaving a general note that the vendor was checked. Attach the evidence to the payment review version that now controls the order.

Give the exception an end point, such as receipt of a corrected document, payment confirmation, inspection, broker acceptance, warehouse receipt, or claim settlement. Link the answer to the proforma invoice checkpoint for this order.

Public guidance can frame the proforma invoice check, but it cannot establish the facts of this order. The importer's PO, invoice, beneficiary record, packing list, product evidence, broker reply, and shipment file remain the deciding records. Record the outcome with the version control evidence before handoff.

If the issue returns, begin with the prior note. It should show which record to request first and which assumption caused the earlier delay. The how handle invoice file should show how this point was resolved.

Retain the revision path visible. The folder should show which version was rejected, which version controls, and whether anyone outside sourcing still holds an obsolete copy. State the remaining limit in the proforma invoice note before the file is closed.

Record one of three outcomes: approve, approve with a stated condition, or hold. Name the evidence supporting that outcome and the event that would force the importer to reconsider it. The next reviewer should find the answer under version control without reopening the whole case.