Verifying supplier payments and bank-detail changes
Build payment checks that hold up against convincing emails and cloned voices, with known contacts, separate approval and a clear fraud response.

An invoice arrives in a familiar email thread with a new bank account. Later, a call sounding like the supplier’s usual contact asks you to pay before the end of the day. Those details can make the request convincing without making the payment safe.
The Canadian Anti-Fraud Centre’s spear-phishing guidance describes supplier impersonation and fraudulent payment-detail changes. A business needs a way to verify the change before it reaches the payment run.
Define which changes need verification
Write down the events that trigger a separate check: a new supplier, changed banking details, an unusual payment destination or a request to skip the normal approval process. Treat a staff member’s request to change their payroll deposit details the same way.
Apply the procedure even when the request comes from a senior person or a long-standing supplier. Give staff permission to pause the change while they verify it, and name someone who can resolve an urgent exception.
Record who can edit supplier details and who can release payments. In a small team, a second person with payment rights should check both the change evidence and the payment destination.
Call a contact you already know
Use a previously verified number from your supplier record or contract. Don’t use a number supplied in the change request, its attachment or a follow-up message. If your records are incomplete, establish the contact through a separate, documented onboarding process before paying.
Confirm the request and the affected supplier account. Record the date, the person reached and the outcome in the supplier record. Protect banking information from unnecessary copying into email or chat.
A reply within the original email thread doesn’t provide an independent check. The sender’s account may be compromised.
Don’t treat a familiar voice as approval
A joint Canadian cyber and fraud advisory warns about impersonation using AI-generated voices and spoofed communications. A familiar voice or displayed phone number can’t be the only check on a payment.
Calling back on a number you already hold helps, but follow the rest of your written procedure too. Confirm the business purpose, the supplier change and the destination. If the conversation pushes staff to bypass those checks, pause and escalate through another established contact.
Use a practice scenario with the finance team: an apparently urgent supplier change arrives while the person who normally signs off is away. Check that their backup knows where to find the verified contact and can refuse an unverified payment.
Protect the systems around the payment
Give finance staff individual accounts with only the permissions their role needs. Require MFA, keep devices updated and remove access when roles change. Review unexpected changes to supplier records and payment permissions.
Email authentication and filtering can help reduce some impersonation. They can’t tell you whether a message from a real supplier’s account is a real request or whether the bank details on the invoice are right. The email-authentication guide explains that boundary.
Keep the approved invoice and verification record together so a reviewer can see why the payment was released. Don’t sign off payments in quick chat messages that can’t be traced back to the transaction.
Act quickly if a payment may be fraudulent
Contact the financial institution that sent the payment immediately, using its established contact details. Ask about available recovery or recall steps. Recovery isn’t guaranteed.
The Canadian Anti-Fraud Centre’s victim guidance also directs victims to report fraud to police and the CAFC. Preserve transaction details, emails and the verification record for those reports.
Notify IT if an account may be compromised and contact the supplier through a known channel. Check pending payments for the same changed details before releasing anything else. Review the failed step afterwards and update the procedure with the people who use it.


