Supplier Bank Account Change Verification Checklist
A supplier sends a familiar-looking email:
“Please note that our bank account has changed. Use the new account for the balance payment.”
The change may be legitimate.
Bank-change rule: stop the normal payment path, preserve the existing approved banking record, independently verify the change through a previously trusted channel, verify the beneficiary relationship and evidence, obtain approval, then update the vendor record and return to pre-payment verification.
Suppliers can change banking instructions because of:
- a new banking relationship;
- a new currency account;
- company restructuring;
- group treasury arrangements;
- factoring;
- account closure;
- collection through another approved entity.
But a changed bank account should never move directly from:
Email Received
to:
Vendor Record Updated
to:
Payment Sent
The safer workflow is:
Bank Change Request Received
↓
Hold the Payment
↓
Preserve Existing Bank Details
↓
Compare Old vs New
↓
Verify Through a Previously Trusted Channel
↓
Verify the Person and Reason
↓
Verify the New Beneficiary
↓
Review Red Flags
↓
Document Evidence
↓
Approve the Change
↓
Update Supplier Record
↓
Return to Pre-Payment Verification
The core rule is:
A supplier bank-account change is not proof of fraud, but it should stop the normal payment workflow until the change has been independently verified.
Why Bank Account Changes Need a Separate Verification Process
A supplier may already have passed:
The payment structure itself should already have been defined through Payment Terms for New Overseas Suppliers so this page handles only the bank-change exception, not the commercial term design.
- company verification;
- restricted-party screening;
- commercial qualification;
- contract approval;
- production inspection.
That does not mean a new banking instruction should automatically be trusted.
Changing a supplier's approved bank details affects not only one invoice.
Once the vendor record is changed, future payments may also follow the new instructions.
That makes the bank-account change itself a controlled procurement exception.
The correct principle is:
Verify first. Update the supplier record second. Pay third.
Step 1: Hold the Payment and Preserve the Existing Record
When new banking instructions arrive, do not overwrite the existing details immediately.
For a new supplier, this exception control should sit after broader Supplier Due Diligence rather than replacing normal qualification.
First place the affected payment on:
HOLD
Preserve the currently approved information:
- Existing Beneficiary Name
- Existing Bank Name
- Existing Account Number / IBAN
- Existing SWIFT / BIC
- Existing Bank Country
- Payment Currency
- Previous Successful Payment Details
- Date the Existing Details Were Approved
Also record the new request:
- Request Date
- Requesting Contact
- Invoice / PO Affected
- Requested Effective Date
- Reason Given for the Change
Key Rule
Never delete or overwrite the existing approved bank record before verification is complete.
You need both versions to understand what actually changed.
Step 2: Compare the Old and New Bank Details
Build a side-by-side comparison.
| Field | Existing Approved Details | Proposed New Details | Changed? |
|---|---|---|---|
| Supplier Legal Entity | |||
| Beneficiary Name | |||
| Bank Name | |||
| Account / IBAN | |||
| SWIFT / BIC | |||
| Bank Country | |||
| Currency | |||
| Payment Instructions |
The first task is not to decide whether the request is fraudulent.
It is to answer:
Exactly what changed?
Different changes create different levels of concern.
Only the Account Number Changed
Still requires verification.
Bank Changed
Requires independent confirmation.
Beneficiary Changed
Requires stronger verification of the relationship.
Bank Country Changed
Requires additional review.
Beneficiary, Bank and Country All Changed
This should receive significantly higher scrutiny.
None of these automatically proves fraud.
But none should pass without explanation.
Step 3: Verify Through a Previously Trusted Channel
This is the most important step.
Suppose the bank-change request arrives by email.
Do not rely only on:
Replying to that email and asking, “Please confirm.”
If the communication channel itself has been compromised, the same person controlling the request can also confirm it.
Instead, use a contact route that existed before the bank-change request.
Possible channels include:
- previously verified supplier phone number;
- existing finance contact in supplier records;
- known director or account manager;
- established procurement messaging channel;
- independently obtained official company contact.
Avoid using the new request itself as the only source for:
- new telephone number;
- new WhatsApp contact;
- new finance contact;
- new verification instructions.
Key Principle
Do not verify a bank-account change using only the same communication channel that requested the change.
A useful rule is:
Known channel > newly supplied channel.
Why Replying to the Same Email Is Not Enough
Consider this exchange.
Supplier email:
“Our bank details have changed.”
Buyer:
“Please confirm that this is correct.”
Reply:
“Yes, confirmed.”
That does not create independent verification.
Both messages may have passed through the same compromised channel.
The better approach is to contact the supplier using information that procurement already trusted before the bank-change request existed.
The request and the verification should not depend entirely on the same path.
Step 4: Verify the Person Requesting the Change
Do not verify only the account.
Verify the authority behind the request.
Record:
- Full Name
- Job Title
- Existing Relationship With Supplier
- Known Contact Status
- Authority to Request Payment Changes
- Reason for Change
- Effective Date
- Which Orders / Invoices Are Affected
Useful questions include:
- Who authorized this bank change?
- Why was the account changed?
- When did the new account become effective?
- Does the new account permanently replace the old one?
- Does it apply to all currencies?
- Does it apply to every supplier entity in the group?
A bank-change request from a known employee is useful information.
But a familiar name or email alone should not complete the verification.
Verify both the banking information and the authority of the person requesting the change.
Step 5: Verify the New Beneficiary
Now compare:
Use the Supplier Legal Company Registration Check to confirm the contracting entity baseline before accepting a new beneficiary relationship.
Contracting Supplier
with:
Proposed Beneficiary
This is one of the most important exception checks.
Beneficiary Matches the Supplier Legal Entity
This is simpler.
But the new bank details still need to be independently verified.
Beneficiary Does Not Match the Supplier
Example:
Supplier:
ABC Building Materials Co., Ltd.
New Beneficiary:
XYZ Global Trading Ltd.
Do not immediately conclude:
Fraud.
But do not process the payment either.
Possible legitimate explanations may include:
- parent company;
- subsidiary;
- group treasury company;
- factoring provider;
- authorized collection entity.
Procurement should verify:
- What is the relationship?
- Why is the supplier directing payment there?
- Is the relationship documented?
- Has the supplier independently confirmed it?
- Has the exception been internally approved?
Key Rule
“It is our finance company” is not enough by itself.
Beneficiary Relationship Verification Table
| Question | Result |
|---|---|
| Beneficiary matches supplier legal entity? | Yes / No |
| If no, relationship explained? | Yes / No |
| Relationship documented? | Yes / No |
| Supplier independently confirmed the arrangement? | Yes / No |
| Required compliance review completed? | Yes / No |
| Internal approval obtained? | Yes / No |
If the answers remain incomplete:
HOLD / ESCALATE
Step 6: Review Bank-Change Red Flags
Use a structured risk review rather than relying on instinct.
If the new payee or transaction structure creates a fresh trade-compliance question, revisit Restricted Party Screening for International Suppliers before the payment exception is approved.
| Change or Signal | Suggested Response |
|---|---|
| Same beneficiary, new account at same bank | Verify |
| Same beneficiary, different bank | Independent verification |
| Beneficiary changed | Enhanced verification |
| Bank country changed | Enhanced verification |
| Third-party beneficiary | Document + escalate |
| Change immediately before large balance | Higher scrutiny |
| “Pay today” urgency | Hold + verify |
| New email domain | Hold + verify |
| Supplier refuses independent confirmation | Do not release |
| Invoice and bank details both changed | Enhanced review |
| Beneficiary + bank + country changed together | High-risk hold |
A red flag does not prove fraud.
It means:
More verification is required before approval.
Step 7: Collect Supporting Evidence
The amount and quality of evidence should reflect the risk of the change.
Possible evidence may include:
- supplier bank-change letter;
- official company letter;
- updated beneficiary information;
- bank confirmation where appropriate;
- company registration data;
- evidence of group-company relationship;
- factoring documentation;
- collection agreement;
- independent call record;
- internal verification notes.
Do not make one document universally mandatory.
A simple account-number update by the same supplier may require less evidence than:
new beneficiary + new bank + new country + large balance payment.
Key Principle
Evidence should explain both what changed and why the new beneficiary is entitled to receive the payment.
Step 8: Approve Before Updating Supplier Master Data
The correct sequence is:
Bank Change Requested
↓
Payment Held
↓
Old Details Preserved
↓
Independent Verification
↓
Beneficiary Relationship Verified
↓
Evidence Collected
↓
Approval Completed
↓
UPDATE VENDOR RECORD
↓
Return to Payment Verification
Do not use:
Request
↓
Vendor Record Changed
↓
Verification Later
The supplier record should be the output of the verification process.
Not the starting point.
Supplier Bank Account Change Verification Checklist
Use the following checklist for each material change.
Change Request
- Supplier Legal Name
- Request Date
- Person Requesting Change
- Position
- Reason for Change
- Effective Date
- Invoice / PO Affected
Existing Approved Details
- Beneficiary
- Bank
- Account / IBAN
- SWIFT / BIC
- Bank Country
- Currency
Proposed New Details
- Beneficiary
- Bank
- Account / IBAN
- SWIFT / BIC
- Bank Country
- Currency
Independent Verification
- Existing Trusted Contact Used
- Contact Source
- Person Confirming
- Position
- Verification Date
- Reason Confirmed
Beneficiary Verification
- Beneficiary Matches Supplier?
- Relationship Identified if Different?
- Supporting Documents Received?
- Relationship Independently Confirmed?
Risk Review
- Bank Country Changed?
- Beneficiary Changed?
- Third-Party Beneficiary?
- Unexpected Urgency?
- Email / Domain Changed?
- Large Payment Pending?
- Other Material Red Flags?
Decision
- Verified
- Hold
- Rejected
- Escalated
Approval
- Reviewer
- Approver
- Approval Date
Bank Account Change Decision Gate
Use this workflow.
New Bank Details Received
↓
Is a Payment Pending?
YES
→ HOLD PAYMENT
↓
Preserve Existing Bank Record
↓
Compare Old vs New Details
↓
Verify Through Previously Trusted Contact
↓
Supplier Confirms the Change?
NO
→ STOP / ESCALATE
YES
↓
Does the New Beneficiary Match the Supplier?
YES
→ Continue.
NO
→ Verify legal / commercial relationship.
↓
Relationship Verified?
NO
→ HOLD / ESCALATE
YES
↓
Material Red Flags Still Unresolved?
YES
→ HOLD / ENHANCED REVIEW
NO
↓
Supporting Evidence Complete?
NO
→ HOLD
YES
↓
Required Approval Complete?
NO
→ HOLD
YES
↓
UPDATE APPROVED BANK RECORD
↓
Return to:
Pre-Payment Verification
↓
RELEASE PAYMENT
Example: Bank Change Before a Large Balance Payment
Assume procurement has ordered:
$80,000 customized shower enclosure package
Payment terms:
- 30% deposit
- 70% after passed inspection before shipment
Already paid:
$24,000
Balance due:
$56,000
The inspection has passed.
The balance is otherwise ready for payment.
Then an email arrives:
“Please remit the USD 56,000 balance to our new bank account.”
The email appears inside the normal supplier email thread.
Existing details:
| Field | Existing |
|---|---|
| Beneficiary | ABC Building Materials Ltd. |
| Bank Country | Hong Kong |
| Bank | Bank A |
| Account | Existing Account |
| Field | Proposed |
|---|---|
| Beneficiary | XYZ Trading Pte. Ltd. |
| Bank Country | Singapore |
| Bank | Bank B |
| Account | New Account |
New instructions:
| FieldProposed | |
|---|---|
| Beneficiary | XYZ Trading Pte. Ltd. |
| Bank Country | Singapore |
| Bank | Bank B |
| Account | New Account |
Several material elements changed:
- beneficiary;
- bank;
- bank country;
- account.
Correct outcome:
HOLD
Not:
“This must be fraud.”
And not:
“It came from the normal email, so pay.”
Procurement should:
- Contact ABC using a previously verified contact.
- Confirm whether the change is genuine.
- Ask why XYZ is receiving the money.
- Verify the relationship between ABC and XYZ.
- Obtain supporting documentation.
- Record the verification.
- Obtain approval.
- Update the approved bank record only after verification.
- Return the transaction to normal pre-payment review.
Only then should the payment proceed.
What If the Supplier Says the Shipment Will Be Delayed Unless You Pay Today?
This is where procurement controls often break down.
The supplier may say:
“Cargo cannot be released unless payment arrives today.”
The project team may also be under pressure because:
- the site needs the material;
- the vessel cutoff is approaching;
- installation is scheduled;
- a delay will affect the project.
That pressure does not change the verification requirement.
Shipment urgency does not replace bank-change verification.
The correct response is to:
- accelerate internal verification;
- call the supplier immediately;
- collect evidence quickly;
- escalate internally where needed.
But do not:
- skip independent confirmation;
- ignore a new beneficiary;
- update the supplier record first;
- pay simply to protect the shipment date.
Key Principle
Increase verification speed when urgent—not reduce verification quality.
What If Only One Bank Field Changed?
Not every change has the same risk level.
Account Number Changed
Verify why the account changed and confirm through a trusted contact.
SWIFT Changed but Bank Appears the Same
Verify the reason.
Bank Branch Changed
Confirm that the new branch and account belong to the supplier.
Currency Account Changed
Confirm which currency and invoices the account applies to.
A single-field change may be lower risk than several simultaneous changes.
But:
Any material payment-instruction change should be reviewed before use.
What If the Bank Account Is in Another Country?
Do not automatically reject it.
International suppliers may legitimately use banking arrangements outside their registration country.
But a bank-country change should trigger additional questions.
Ask:
- Why did the banking jurisdiction change?
- Is the beneficiary still the same legal entity?
- If not, what is the relationship?
- Is the arrangement consistent with the contract?
- Does it affect compliance requirements?
- Has the supplier independently confirmed the change?
Outcome:
Different bank country = enhanced review, not automatic fraud.
What If the Supplier Uses a Third-Party Beneficiary?
A request such as:
“Please pay our partner company instead.”
should not be handled as a routine supplier payment.
Possible legitimate arrangements exist.
But procurement should require:
- explanation;
- relationship documentation;
- supplier confirmation;
- internal approval;
- compliance review where appropriate.
The further the beneficiary moves away from the contracting supplier, the more important the verification becomes.
Third-party beneficiary = exception requiring documented approval.
Preserve an Audit Trail
Keep a record of how the change was handled.
Bank Change Verification Record
| Field | Record |
|---|---|
| Supplier | |
| Change Request Date | |
| Existing Beneficiary | |
| Existing Bank | |
| New Beneficiary | |
| New Bank | |
| New Bank Country | |
| Requesting Contact | |
| Trusted Contact Used for Verification | |
| Confirmation Date | |
| Reason for Change | |
| Beneficiary Relationship | |
| Supporting Documents | |
| Red Flags | |
| Reviewer | |
| Approver | |
| Final Decision | |
| Vendor Record Updated Date |
This makes it possible to reconstruct:
- what changed;
- who requested it;
- how it was verified;
- what evidence existed;
- who approved it;
- when the supplier record changed.
When Should the Change Be Rejected or Escalated?
Do not update the bank record when material uncertainty remains.
Examples include:
- supplier denies requesting the change;
- beneficiary relationship cannot be explained;
- supplier refuses independent verification;
- supporting documents conflict with supplier identity;
- several unexplained changes occur together;
- compliance concerns arise;
- verification remains ambiguous.
Outcome:
DO NOT UPDATE / DO NOT PAY
Escalate through the buyer's appropriate legal, compliance, management or fraud-response process.
Procurement does not need to prove that a crime occurred.
It only needs to recognize:
The payment instruction has not been verified sufficiently to release funds.
What Procurement Should Never Do
Update the Vendor Record Immediately
Preserve the old record and verify first.
Confirm Only by Replying to the Same Email
Use a previously trusted communication channel.
Use Only the New Phone Number in the Change Request
Use existing or independently verified contact details.
Assume the Normal Email Thread Is Automatically Safe
Treat the email as one source of information, not final verification.
Pay an Unrelated Beneficiary Without Documentation
Verify the relationship and obtain approval.
Let Shipment Urgency Override the Control
Move faster, but keep the verification standard.
Delete the Previous Bank Details
Preserve the audit trail.
Where Bank Change Verification Fits in the Supplier Payment Workflow
The broader process is:
Keep the exception inside the broader International Supplier Contract & Payment Risk Workflow so legal entity, contract, invoice, beneficiary and bank controls remain connected.
This exception module should always return to the Pre-Payment Verification Checklist before money is released.
Supplier Verification
↓
Restricted Party Screening
↓
Agree Payment Terms
↓
Contract / PO
↓
Production / Inspection
↓
Pre-Payment Verification
↓
Bank Details Changed?
NO
→ Continue Payment Approval
YES
↓
Bank Account Change Verification
↓
Verified?
YES
→ Update Approved Supplier Record
→ Return to Pre-Payment Verification
→ Release Payment
NO / UNRESOLVED
→ HOLD / ESCALATE
Bank-account change verification is therefore not a separate administrative task.
It is an exception-control module inside the supplier-payment workflow.
Tools and Resources for Bank Change Verification
Procurement teams may use:
- supplier verification resources;
- company registration databases;
- corporate ownership databases;
- restricted-party screening tools;
- vendor onboarding templates;
- payment-control checklists;
- supplier master records;
- fraud-prevention references;
- contract documentation.
Build Procurement Hub organizes these resources around actual procurement tasks and exceptions.
The purpose is not merely to tell buyers:
“Be careful of fraud.”
It is to help them answer:
What changed, how should we verify it, what evidence should we save, and when is it safe to update the supplier record?
The central principle is:
A supplier bank-account change is not proof of fraud, but it should stop the normal payment workflow. Preserve the old details, verify the change through a previously trusted channel, confirm the new beneficiary relationship, document the evidence, and approve the change before updating the supplier record or releasing funds.
Verify the Bank Change Before You Update the Vendor Record or Release Funds
Hold the payment, preserve the existing approved details, compare old and new instructions, confirm the change through a previously trusted channel, verify the requesting person and beneficiary relationship, review red flags, save the evidence, obtain approval, then update the supplier record and return to pre-payment verification.