The Invoice That Changed Banks Overnight: A Payment-Diversion Playbook for Small Teams
Photo by Photo by Vitaly Gariev on Unsplash on Unsplash
It is 4:40 on a Friday afternoon. Your accounts-payable clerk sees a reply in an email thread she has used with the same vendor for two years. The logo is right. The signature is right. The invoice PDF looks like every other invoice from that supplier, except for one line near the bottom: the remittance account has changed. The amount is $25,000, the due date is Monday, and the vendor says the old account is closed. She pays it. On Tuesday, the real vendor calls about the overdue invoice.
That is business email compromise in its most ordinary form. Nobody broke into your network. Nobody guessed a password. Someone studied a real email thread, inserted themselves into the conversation, and counted on deadline pressure to do the rest. Small businesses are attractive targets precisely because a $25,000 payment can hurt, but the approval chain is often one person and a quick reply.
The thread was real. The payment instructions were not.
Payment-diversion scams rarely arrive as obvious junk. They arrive as a reply. The subject line already exists. The previous messages give the request context. The sender name looks familiar. The PDF may even be a real invoice with altered banking details, or a clean lookalike built from a template.
Under deadline pressure, people miss small signals: a reply-to address that is slightly off, a display name that matches but the domain does not, a sudden sense of urgency, or a request that arrives just before a weekend or a holiday. The biggest red flag is also the simplest: the email is asking to change where money goes.
That should stop the process. Not slow it down. Stop it.
The call-back rule that stops most of these losses
Make one rule non-negotiable: any request to change bank details, payment instructions, remittance accounts, or wire information must be verified by a live voice call to a known contact. Not a reply email. Not a text. Not a phone number printed in the request. Call the number your team already has in the vendor file, the signed contract, or the accounting system.
Then confirm the change out loud. Ask the vendor contact to state the bank name, the last four digits of the account, the invoice number, and the amount. Document who called, when, and what was confirmed. If you cannot reach a known contact, the payment waits. That includes requests from owners, executives, and long-time vendors. Especially those.
A second person should approve the payment after the call-back. This is not about distrust. It is about separating the person who receives the request from the person who releases the money.
A one-page internal policy you can adapt today
Purpose: Protect company funds from fraudulent payment-change requests.
Scope: All employees, contractors, and vendors involved in invoices, wires, ACH payments, and remittance changes.
Rule: No bank-detail or payment-instruction change is processed from email alone. Every change requires live voice verification with a known contact and a second approver.
Verification steps:
- Do not use contact information from the request.
- Call the vendor using the number in the approved vendor file or contract.
- Confirm bank name, account last four digits, invoice number, and amount.
- Record the name of the person who confirmed the change, the date, the time, and the number called.
- Obtain approval from a second authorized person before releasing payment.
Exceptions: None for payment changes. If urgent, escalate to the owner or finance lead, but the call-back still happens.
Reporting: Forward suspicious messages to IT or the designated security contact. Do not delete them.
Review: Revisit this policy quarterly and after any near miss.
A short accounts-payable checklist
Before releasing any payment, the AP owner should be able to answer these questions:
- Is this a new vendor, a new bank account, or a change to existing bank details?
- Did the request arrive by email, and does it ask us to ignore a previous process?
- Have I called a known contact using a number outside the email?
- Did the vendor verbally confirm the bank name, account last four, invoice number, and amount?
- Has a second authorized person approved the change?
- Is the confirmation documented in the vendor file or accounting system?
- Does the email domain match previous legitimate messages exactly?
- Is there any urgency, secrecy, or unusual executive involvement?
If any answer is unclear, hold the payment. A late payment is a conversation. A fraudulent payment is a loss.
Low-cost email safeguards that do not need a security team
You do not need an enterprise stack to make this harder. Start with the basics in 2026: turn on multi-factor authentication for every email account, especially finance. Make sure your domain has SPF, DKIM, and DMARC configured, even at a basic monitoring level. Use the external-sender banner most business email platforms offer so staff can see when a message comes from outside the company.
Audit mailbox rules. Scammers often create forwarding or deletion rules so replies disappear. Check for rules that forward finance email to an outside address or move messages into obscure folders. Review admin permissions and remove old accounts.
In Microsoft 365 or Google Workspace, look at built-in alerting or transport rules for messages that mention bank-change language, wire instructions, or remittance updates. You do not need perfect detection. You need one more speed bump before money moves.
Train the team in short, specific sessions. Fifteen minutes on payment-change scams is more useful than a generic annual security video. Practice the call-back rule during a normal week so it feels routine, not adversarial.
If a payment has already gone out
Call your bank immediately. Ask whether the transfer can be recalled or stopped. Report the fraud to the FBI Internet Crime Complaint Center. Preserve the emails and attachments. Notify the real vendor through a known number. Reset affected passwords, review mailbox rules, and check whether other messages were accessed. If you have cyber insurance, contact the carrier early and follow its instructions.
Most small businesses cannot undo a fraudulent transfer with a help-desk ticket. They can, however, make the next request pass through a human voice and a second set of eyes. The call-back rule is not glamorous. It is the cheapest control you can put between a convincing email and your bank account.