Contracts & Trade Risk

What to Check Before Paying a New Overseas Supplier

A supplier sends an invoice and says:

“Please arrange the balance payment today.”

The invoice looks familiar.

The email comes from a known contact.

The amount seems close to what procurement expected.

That still does not mean the payment should be released immediately.

Before money leaves the buyer, procurement should verify that:

• the correct supplier entity is being paid;
• the payment is actually due;
• the required contractual milestone has been completed;
• the invoice matches the PO or contract;
• the amount reconciles with previous payments;
• the beneficiary and bank details are correct;
• no unexplained payment exception exists;
• required internal approval is complete.

The core rule is:

Verify the payment against the approved transaction—not against the supplier email alone.

A practical pre-payment process should end with one of three outcomes:

RELEASE

HOLD / CLARIFY

ESCALATE

---

Build a Pre-Payment Release Gate

Before releasing an overseas supplier payment, use eight basic gates.

Gate 1

Are we paying the correct supplier entity?

Gate 2

Is this payment actually due?

Gate 3

Has the required milestone been verified?

Gate 4

Does the invoice match the PO or contract?

Gate 5

Do the bank details match the approved record?

Gate 6

Are there any material payment red flags?

Gate 7

Is the required compliance review still current?

Gate 8

Has the payment received the required approval?

Only after all applicable gates pass should payment be released.

---

Gate 1: Are You Paying the Correct Supplier Entity?

Start with the legal entities involved.

For a new supplier, the payment gate should sit after broader Supplier Due Diligence rather than replacing supplier qualification.

Confirm the legal identity baseline through How to Verify a Supplier's Legal Company Registration before accepting a beneficiary or invoice entity as the expected transaction party.

Compare:

• Supplier Legal Name
• PO Entity
• Contract Entity
• Invoice Entity
• Beneficiary Name

Example:

PO:

ABC Building Materials Co., Ltd.

Invoice:

ABC Building Materials Co., Ltd.

Beneficiary:

ABC Building Materials Co., Ltd.

Result:

MATCH

Now consider another request.

Contracting supplier:

ABC Building Materials Co., Ltd.

Beneficiary:

XYZ International Holdings Ltd.

This does not automatically mean fraud.

There may be a legitimate reason, such as:

• approved parent company;
• group treasury arrangement;
• factoring;
• authorized collection entity.

But procurement should not release payment automatically.

The correct status is:

ENTITY MISMATCH — VERIFICATION REQUIRED

Key Principle

A different entity is not automatically fraudulent, but it should leave the normal payment path until the relationship is independently verified and approved.

---

Gate 2: Is This Payment Actually Due?

A supplier requesting money does not automatically make the payment contractually due.

The release gate should follow the commercial structure already agreed in Payment Terms for New Overseas Suppliers rather than a supplier's ad-hoc payment request.

Check:

• Contract
• Purchase Order
• Approved Proforma Invoice
• Payment Schedule

Suppose the payment terms are:

30% deposit 70% after passed pre-shipment inspection

The supplier emails:

“Production is complete. Please pay the 70% balance.”

Production completion is not the agreed trigger.

The inspection still has to occur and pass.

Outcome:

HOLD — PAYMENT MILESTONE NOT REACHED

Key Rule

Supplier request date and contractual payment due date are not the same thing.

---

Gate 3: Has the Required Milestone Been Verified?

Payment terms should be connected to actual performance.

After PO release, use Construction Purchase Order Tracking to keep production and shipment milestones visible before the next payment trigger.

Possible milestones include:

• Sample Approved
• Materials Purchased
• Production Started
• Production Completed
• Pre-Shipment Inspection Passed
• Packing Completed
• Shipment Booked
• Shipping Documents Issued
• Goods Delivered

Now ask:

What evidence proves the milestone has been reached?

Possible evidence includes:

• inspection report;
• approved production milestone;
• packing list;
• production photos;
• shipping booking;
• bill of lading;
• delivery record.

The appropriate evidence depends on:

• payment size;
• supplier history;
• transaction risk;
• contract requirements.

For example:

Payment trigger:

40% after passed inspection

Evidence:

Approved inspection report

If procurement has only received:

“Everything is finished, please pay.”

the payment gate has not been passed.

Supplier statement ≠ verified payment milestone.

---

Gate 4: Does the Invoice Match the PO and Contract?

Do not review the invoice in isolation.

Compare it against procurement's approved records.

This can catch simple but expensive errors.

Example:

Contract Value:

$80,000

Deposit Already Paid:

$24,000

Expected Balance:

$80,000 − $24,000 = $56,000

Supplier invoice requests:

$60,000

Outcome:

HOLD — AMOUNT DOES NOT RECONCILE

Do not assume the supplier's arithmetic is correct.

---

Recalculate the Payment Before Release

Procurement should independently calculate what is due.

A practical formula is:

Current Payment Due = Approved Contract Value − Previous Payments − Approved Credits / Adjustments − Amount Not Yet Due

Possible adjustments include:

• deposit already paid;
• credit note;
• quantity reduction;
• approved variation;
• retention;
• partial delivery;
• contractual deduction where applicable.

The objective is simple:

The supplier invoice should agree with procurement's own payment record.

This also helps prevent:

• duplicate payment;
• overpayment;
• incorrect balance;
• missed credit notes.

---

Gate 5: Do the Bank Details Match the Approved Record?

Check:

• Beneficiary Name
• Bank Name
• Account Number / IBAN
• SWIFT / BIC
• Bank Country
• Payment Currency

Then compare them with:

• approved supplier master data;
• previously verified banking instructions;
• approved contract or onboarding record.

Bank Details Unchanged?

YES

→ Continue.

Bank Details Changed?

NO NORMAL PAYMENT RELEASE

→ Route to a separate bank-account-change verification process.

The payment should not continue merely because the new bank details arrived from the supplier's normal email account.

Key Rule

Any unexplained bank-detail change is a separate verification event.

This is especially important for large balance payments.

---

Gate 6: Review Payment Red Flags

A payment can look normal overall while still contain one important exception.

Common red flags include:

• unexpected urgency;
• “payment must be made today”;
• new bank account;
• new bank country;
• changed beneficiary;
• request to pay an unrelated third party;
• slightly changed email address;
• new email domain;
• revised invoice at the last minute;
• changed payment process;
• unusual secrecy request;
• supplier refuses independent confirmation;
• amount differs from contract;
• communication style suddenly changes.

One red flag does not automatically prove fraud.

The correct response is:

Material Red Flag = HOLD + VERIFY

Do not let urgency override the payment process.

---

A Familiar Email Thread Is Not Payment Verification

A fraudulent or incorrect payment request does not always arrive as an obvious scam.

It may appear:

• inside an existing supplier email thread;
• under a familiar display name;
• using the supplier's normal invoice format;
• with correct order details.

That is why payment verification should rely on approved transaction records rather than email familiarity alone.

Compare the request with:

• supplier master record;
• PO;
• contract;
• payment history;
• approved banking information;
• known contact information where independent confirmation is required.

The supplier email is evidence to review, not authority to release funds.

---

Gate 7: Is the Compliance Review Still Current?

Restricted-party screening and other compliance checks may already have been completed during supplier onboarding.

If a legal entity, payee or other transaction party changed, revisit Restricted Party Screening for International Suppliers where the transaction risk requires it.

But procurement should ask whether anything material has changed.

Examples:

• supplier legal entity changed;
• payee changed;
• parent company changed;
• destination changed;
• end user changed;
• transaction structure changed;
• relevant risk conditions changed.

If the transaction parties remain unchanged and the screening is still valid under company policy:

→ Continue.

If a new party has entered the transaction:

→ Review whether re-screening is required.

Key Principle

A changed transaction party may require a new compliance review even when the original supplier was already approved.

---

Gate 8: Has Internal Approval Been Completed?

Payment should leave an audit trail.

A minimum payment record may include:

• Payment Request
• Supplier
• PO
• Invoice
• Amount
• Supporting Evidence
• Verification Result
• Exceptions
• Approval
• Payment Date
• Transaction Reference

For larger teams, the process may use:

Maker

Prepares the payment.

Checker

Verifies the transaction.

Approver

Authorizes release.

A small company may not have three separate employees.

But the principle still applies:

Use a deliberate verification step before pressing Send.

Do not let the same supplier email serve as:

• payment request;
• verification;
• approval.

---

Pre-Payment Verification Checklist

Use this checklist before releasing money.

Supplier

• Legal Entity Confirmed
• Supplier Status Approved
• Restricted-Party Review Current Where Required

Commercial

• PO Confirmed
• Contract Confirmed
• Payment Terms Confirmed
• Payment Stage Confirmed
• Milestone Reached
• Required Evidence Received

Invoice

• Supplier Name Matches
• PO Number Matches
• Product / Scope Matches
• Currency Matches
• Contract Value Matches
• Previous Payments Deducted
• Current Amount Recalculated
• Remaining Balance Correct

Banking

• Beneficiary Matches Approved Record
• Bank Matches
• Account / IBAN Matches
• SWIFT / BIC Matches
• Bank Country Matches
• Bank Details Changed?

Approval

• Exceptions Resolved
• Verification Complete
• Approval Recorded

Final result:

RELEASE / HOLD / ESCALATE

---

Payment Release Decision Gate

Use this workflow.

Payment Request Received

↓

Correct Supplier Entity?

NO

→ HOLD / VERIFY

YES

↓

Payment Due Under Contract?

NO

→ HOLD

YES

↓

Required Milestone Verified?

NO

→ HOLD

YES

↓

Invoice Matches PO / Contract?

NO

→ CLARIFY

YES

↓

Amount Reconciles?

NO

→ HOLD

YES

↓

Bank Details Unchanged?

NO

→ Bank Account Change Verification

YES

↓

Material Red Flags?

YES

→ HOLD + VERIFY

NO

↓

Compliance Review Current?

NO

→ REVIEW

YES

↓

Approval Complete?

NO

→ HOLD

YES

↓

RELEASE PAYMENT

---

Example 1: Payment Ready for Release

Order:

$80,000 customized shower enclosure package

Payment Terms:

30% deposit 70% after passed inspection before shipment

Deposit Already Paid:

$24,000

Supplier Requests:

$56,000

Now procurement checks the payment.

Supplier Entity

Matches contract:

YES

Contract Value

$80,000:

YES

Deposit

$24,000 already paid:

YES

Remaining Balance

$56,000:

YES

Inspection Required

Completed:

YES

Inspection Result

Passed:

YES

Invoice

Matches PO and contract:

YES

Beneficiary

Same approved supplier:

YES

Bank Details

Unchanged:

YES

Compliance Status

Current:

YES

Approval

Complete:

YES

Outcome:

RELEASE

The decision is based on several independent checks, not simply the supplier's payment email.

---

Example 2: Correct Invoice, Changed Bank Account

Use the same order.

Everything appears correct:

• Contract: correct
• Amount: correct
• Inspection: passed
• Invoice: correct

Then the supplier sends:

“Our normal bank account is temporarily unavailable. Please send the balance to our new bank account in another country today.”

Now the verification becomes:

Amount

Correct ✓

Milestone

Correct ✓

Invoice

Correct ✓

Beneficiary / Bank Details

Changed ✗

Unexpected Urgency

Yes ✗

Outcome:

HOLD

The fact that every other gate passed does not override the failed banking gate.

The payment should enter a dedicated bank-account-change verification process before release.

---

An Entity Mismatch Is an Exception, Not an Automatic Fraud Conclusion

International transactions sometimes use legitimate structures where the beneficiary differs from the contracting supplier.

Possible examples include:

• group treasury entities;
• approved parent companies;
• factoring arrangements;
• authorized collection companies.

Therefore:

Beneficiary Mismatch

does not automatically equal:

Fraud

But it should mean:

STOP AUTOMATIC PAYMENT

Then verify:

• legal relationship;
• written authorization;
• contract treatment;
• internal approval.

Record why the exception was accepted.

The same logic applies to:

• bank-country changes;
• payment-currency changes;
• new payees.

---

Pre-Payment Record Template

Keep a record for each material payment.

This record can help procurement later reconstruct:

• why the payment was released;
• which information was verified;
• who approved it;
• what exceptions existed.

---

When Should Procurement Hold a Payment?

A payment should enter HOLD / VERIFY when a material exception remains unresolved.

Examples include:

• supplier entity mismatch;
• payment not yet contractually due;
• required milestone not verified;
• invoice amount does not reconcile;
• unknown beneficiary;
• changed bank details;
• unexpected new bank country;
• unexplained urgency;
• unresolved compliance issue;
• missing approval.

Holding payment does not mean accusing the supplier of fraud.

It simply means:

The payment has not yet passed the release gate.

---

Pre-Payment Verification Is Still Needed With Different Payment Methods

The exact process changes depending on the payment method.

But basic verification still matters whether the transaction uses:

• T/T;
• Letter of Credit;
• Documentary Collection;
• Open Account.

For example, procurement may still need to confirm:

• payment is due;
• amount is correct;
• supplier is correct;
• documents are correct;
• contractual milestone is satisfied;
• approval is complete.

A more structured payment method does not remove the need for transaction verification.

---

What Procurement Should Never Do

Pay Only Because the Supplier Says the Payment Is Urgent

Check the contractual due date.

Trust a Revised Invoice Without Reconciliation

Compare it with the PO, contract and payment history.

Assume an Existing Email Thread Is Automatically Safe

Verify against approved records.

Ignore a Beneficiary Mismatch

Treat it as an exception.

Ignore Changed Bank Details

Move the payment into separate verification.

Pay Before the Contractual Trigger Has Been Met

Check milestone evidence.

Keep No Record of the Verification

Document the release decision.

---

Common Pre-Payment Verification Mistakes

Common failures include:

• reviewing only the invoice;
• forgetting previous payments;
• paying before inspection or milestone completion;
• relying on supplier email instead of contract terms;
• failing to recalculate the balance;
• ignoring beneficiary differences;
• ignoring bank-detail changes;
• accepting urgency without verification;
• releasing payment while exceptions remain open.

Most of these problems are avoidable with a simple release checklist.

---

Where Pre-Payment Verification Fits in the Procurement Workflow

A controlled supplier-payment workflow looks like this:

Keep this final release check inside the broader International Supplier Contract & Payment Risk Workflow so contract, milestone, invoice and payment controls remain connected.

Supplier Verification

↓

Restricted Party Screening

↓

Agree Payment Terms

↓

Contract / PO

↓

Production

↓

Inspection / Milestone Verification

↓

Pre-Payment Verification

↓

Bank Details Changed?

YES

→ Bank Account Change Verification

NO

↓

Release Payment

↓

Record Transaction

This makes pre-payment verification the final procurement control point before funds leave the buyer.

---

Tools and Resources for Pre-Payment Verification

Procurement teams may use:

• supplier verification resources;
• restricted-party screening databases;
• company-registration databases;
• contract and PO templates;
• inspection services;
• payment-control templates;
• trade-finance references;
• beneficiary-verification procedures;
• currency tools.

Build Procurement Hub organizes these resources around the actual transaction workflow.

The objective is to help buyers move from:

Supplier Approval

to:

Payment Terms

to:

Milestone Verification

to:

Release / Hold Decision

rather than treating supplier payment as a simple invoice-processing task.

The central principle is:

Do not release a supplier payment because the invoice looks familiar or the supplier says it is due. Verify the entity, contractual milestone, amount, evidence, bank details and approval status—and hold any unexplained exception before funds are sent.

Release Payment Only After the Transaction Passes the Payment Gate

Verify the legal entity, contractual due date, milestone evidence, invoice, previous payments, beneficiary and bank details, compliance status, exceptions and internal approval. If any material exception remains unresolved, hold or escalate before funds leave the buyer.

Explore Contracts & Trade Risk Resources Explore Supplier Verification Tools