What this decision should produce
Bank verification protects both commercial identity and the payment-change process.
Never approve a new or changed beneficiary from one email or chat message. Verify through a known contact and previously trusted channel, document the reason for any entity difference, and require a second internal review. If the explanation remains unclear, pause the transfer rather than relying on urgency.
Establish the expected beneficiary early
Ask for beneficiary details during supplier qualification, not minutes before the deposit. Record account name, bank, branch, country or region, account number or IBAN where applicable, SWIFT code, currency, intermediary information, and the legal relationship to the contracting supplier. Compare the beneficiary with the business license, quotation, proforma invoice, contract, and prior payments.
Some suppliers legitimately use an export company, group treasury company, or Hong Kong affiliate. Request a written explanation and supporting relationship documents appropriate to the transaction. Make sure the contract and invoice identify who receives payment and who remains responsible for product, delivery, quality, and refunds.
Treat every change as a separate security event
A message claiming that an account is frozen, under audit, unavailable, or replaced should trigger a controlled verification process. Do not reply only within the same email thread because a compromised mailbox can preserve the conversation history. Call a known telephone number or use another trusted channel and speak with a recognized contact.
Compare the new account country, beneficiary spelling, bank location, currency, and ownership with the established arrangement. Ask why the change is needed and when it takes effect. Pressure to pay immediately, secrecy, personal accounts, or a country unrelated to the transaction require escalation.
Use internal approval and payment controls
Separate the person who receives bank details from the person who approves changes and the person who releases funds where team size permits. Use a bank-change form, call-back record, supporting documents, and two-person approval. Store verified details in a controlled vendor master rather than copying them from the latest email each time.
Before transfer, confirm invoice number, order, currency, amount, beneficiary, bank, payment milestone, and evidence required by the contract. For a balance payment, verify inspection or shipment conditions as well as the account. Payment identity controls do not replace commercial release controls.
Respond carefully when something is wrong
If a suspicious change is detected before payment, stop the transfer and notify internal finance and supplier management through trusted channels. Preserve the messages and headers. If money has already been sent, contact the sending bank immediately and follow its fraud-response process; speed can matter. Obtain appropriate legal or law-enforcement advice for the jurisdictions involved.
After resolution, document the incident, correct vendor records, reset compromised communications, and review whether similar orders are exposed. Avoid publishing accusations before facts are confirmed. The operational lesson should focus on stronger verification, not on trusting one person less.
How the decision works in practice
Two days before a deposit, a buyer receives a reply in an existing email thread asking for payment to a personal account in another country. The signature and invoice look familiar. The buyer calls the supplier using the number stored from the factory visit; the supplier confirms its mailbox was compromised and the account is false. Finance blocks the change, saves the evidence, updates supplier contacts, and requires call-back plus two approvals for all future beneficiary changes.
What should be true before you continue
Never approve a new or changed beneficiary from one email or chat message. Verify through a known contact and previously trusted channel, document the reason for any entity difference, and require a second internal review. If the explanation remains unclear, pause the transfer rather than relying on urgency.
Turn the review into a decision record
Do not mark an item complete because it was discussed. Record the current source, revision, date, owner, and remaining uncertainty so another person can understand why the order moved forward.
| Confirm | Evidence to retain | Risk if unclear |
|---|---|---|
| Expected beneficiary collected during qualification | Record the source, date checked, responsible person, current file or observation, and any exception that still needs approval. | Verifying inside the same suspicious email thread |
| Account name matches or relationship is documented | Record the source, date checked, responsible person, current file or observation, and any exception that still needs approval. | Accepting urgency as proof |
| Bank country and currency are plausible | Record the source, date checked, responsible person, current file or observation, and any exception that still needs approval. | Paying a personal account without documented basis |
| Invoice and contract identify the payee | Record the source, date checked, responsible person, current file or observation, and any exception that still needs approval. | Copying details from an unverified invoice |
| Known-channel callback completed | Record the source, date checked, responsible person, current file or observation, and any exception that still needs approval. | Letting one person request and approve a change |
| Change reason and effective date recorded | Record the source, date checked, responsible person, current file or observation, and any exception that still needs approval. | Checking the bank but not the payment milestone |
| Second-person approval | Record the source, date checked, responsible person, current file or observation, and any exception that still needs approval. | Verifying inside the same suspicious email thread |
| Payment milestone evidence checked | Record the source, date checked, responsible person, current file or observation, and any exception that still needs approval. | Accepting urgency as proof |
| Vendor master updated securely | Record the source, date checked, responsible person, current file or observation, and any exception that still needs approval. | Paying a personal account without documented basis |
| Incident escalation contacts available | Record the source, date checked, responsible person, current file or observation, and any exception that still needs approval. | Copying details from an unverified invoice |
Ask for the information in one controlled message
Replace the bracketed details, remove any item that does not apply, and ask the supplier or project owner to identify deviations instead of replying with a general confirmation.
Subject: How to Verify a Supplier Bank Account Before Payment - evidence request for [product / order]
Hello [supplier or project owner],
We are reviewing this decision for [product, model, quantity, destination, and target date]. Please provide or confirm the following points using the current document revision and identify anything that differs from our request:
- Expected beneficiary collected during qualification
- Account name matches or relationship is documented
- Bank country and currency are plausible
- Invoice and contract identify the payee
- Known-channel callback completed
- Change reason and effective date recorded
- Second-person approval
- Payment milestone evidence checked
- Vendor master updated securely
- Incident escalation contacts available
For each answer, please name the supporting file, record, photo, sample, person, or date. Mark open items clearly and propose a completion date. We will use the confirmed information with the current specification, quotation, purchase order, quality plan, or shipment file as applicable.
Thank you,
[Buyer name / company]
What to confirm before moving forward
- Expected beneficiary collected during qualification
- Account name matches or relationship is documented
- Bank country and currency are plausible
- Invoice and contract identify the payee
- Known-channel callback completed
- Change reason and effective date recorded
- Second-person approval
- Payment milestone evidence checked
- Vendor master updated securely
- Incident escalation contacts available
Problems that make this decision harder
- Verifying inside the same suspicious email thread
- Accepting urgency as proof
- Paying a personal account without documented basis
- Copying details from an unverified invoice
- Letting one person request and approve a change
- Checking the bank but not the payment milestone
Frequently asked questions
Is a beneficiary different from the factory always fraud?
No. Export and group arrangements can be legitimate, but the relationship and responsibilities should be documented and independently verified.
Can a small test payment confirm the account is safe?
It can confirm routing, but not ownership or legitimacy. A fraudster can also receive a test payment, so identity controls remain necessary.
What if the supplier refuses a callback?
Pause the payment and escalate. A legitimate urgent change should still tolerate reasonable verification designed to protect both parties.
Turn the open question into a useful message
Use the checklist and related tool first. If the decision is still unclear, send the facts that change the answer so the conversation can begin with the actual product, order, supplier, and deadline.
- Product or project and the exact decision you need to make
- Target quantity, destination market, and required date
- Current quotation, supplier status, and the evidence already checked
- The remaining risk, mismatch, or question that is blocking progress
This guide supports planning and supplier communication. Product compliance, customs classification, taxes, contracts, and market-specific requirements should be confirmed with qualified professionals.