2026-06-13 / bank detail change / payment safety / beneficiary review

A Bank Detail Change Protocol for Small Importers

Bank changes need a fixed protocol so urgency, chat messages, and familiar contacts do not override payment evidence.

A bank detail change can be ordinary. A supplier may move accounts, use an export company, receive payment through a group finance office, or correct an old bank instruction. The same event can also be the moment when a buyer sends money to the wrong account. Small importers are exposed because they often rely on familiar sales contacts, fast messaging apps, and a single finance person who wants to keep production moving.

The buyer should write a bank detail change protocol before the first scare. The protocol should say who can receive a change notice, who verifies it, who approves payment, and which documents must match before funds move. It should apply even when the supplier contact sounds familiar. Fraud and internal supplier mistakes both exploit the same weakness: the buyer treats a changed bank instruction as an administrative update instead of a payment-risk event.

Start with the beneficiary name. Compare the bank account holder with the invoice issuer, contract seller, proforma invoice, email domain, and prior payment records. If the beneficiary differs, ask for a written relationship explanation on company letterhead or in an email from a verified company domain. The explanation should name both companies and state who remains responsible for production, shipment, defects, and refunds. A message that says 'same boss' or 'our finance account' is not enough for a file.

Use a callback rule. The buyer should confirm the change through a channel already known before the change notice arrived. Do not reply only to the email that supplied the new account. Call a known number, use an existing verified contact, or ask a second supplier manager to confirm. Record the date, person, method, and exact account confirmed. If the supplier resists a callback because payment is urgent, treat that resistance as part of the risk review.

Lock the invoice sequence. A bank change should trigger a fresh proforma invoice or payment instruction that shows the order number, amount, currency, beneficiary, bank name, and reason for the account used. Do not wire against a loose bank slip pasted into a chat. The payment document should sit beside the PO, quotation, deposit condition, and supplier confirmation. If the buyer later needs to explain why funds went to a different beneficiary, the file should answer without relying on memory.

Separate deposit and balance rules. A deposit sent to a changed account creates production risk. A balance sent to a changed account creates leverage risk because the buyer may release money after goods are packed or loaded. For balance payments, the protocol should require a document pack review before approving the new beneficiary: final invoice, packing list, inspection evidence, shipment photos, and any bill of lading draft if available. A changed account should not bypass the pre-shipment file.

Small teams should also set a value threshold. Low-value orders may use a lighter review, but every bank change deserves at least beneficiary matching and callback confirmation. Higher-value orders should require manager approval and a short payment-route note. The note should say what changed, why the buyer accepted it, which documents support the route, and what remains unresolved. If the explanation feels thin, pause the payment.

Keep old bank records. Buyers sometimes overwrite supplier bank data in their accounting system and lose the prior route. Keep a payment history that shows beneficiary names, account endings, invoice numbers, and dates. That history helps detect a sudden switch, supports insurance or bank inquiries, and helps finance compare reorders. It also prevents a supplier from treating a one-time exceptional account as the new default without review.

The point of a protocol is not suspicion. It is consistency. A buyer who follows the same steps on every bank change can move faster because the team knows what evidence it needs. A supplier who uses a legitimate new account can provide the relationship note and confirmation. A risky change will struggle to pass simple checks. Payment safety improves when the buyer makes the route visible before money leaves.

Train the team to treat small changes the same way as large ones. A fraud attempt may start with a small sample fee, and a legitimate supplier may use the same changed account for a later balance payment. Record the first change carefully. Add the account to the supplier file only after review, and mark whether the approval applies to one order or future orders. If the buyer accepts a one-time route, the accounting system should not quietly make it the default beneficiary. That distinction prevents today's exception from becoming tomorrow's unreviewed habit.

The protocol should leave an audit trail that a bank, insurer, manager, or future buyer can read. Save the old instruction, new instruction, verification note, callback record, approval name, and wire confirmation together. If the payment later becomes disputed, the buyer can show that it did not act from a single message. The file may not recover funds by itself, but it gives the buyer a stronger position than a chat screenshot and a bank slip.