# Business Email Compromise: The Payment Verification Habit That Stops Wire Fraud

> Amen Security Team · 2026-11-21T15:00:00.000Z · cybersecurity · bec · email-security · phishing · microsoft-365 · smb · canada

Business email compromise · SMB · Canada

In short. Business email compromise (BEC) tricks a trusted person into changing where money goes — vendor banking, payroll, or a wire “just this once.” The control that works is boring: verify every payment change on a channel you already trust, not the email thread. Then harden Microsoft 365 so a stolen mailbox cannot silently forward threads for weeks. Amen Security is a Winnipeg [cybersecurity](/en/services/cybersecurity) and [managed IT](/en/services/managed) shop; we operationalize this for Canadian and US SMBs on Microsoft 365 and hybrid stacks.

The one habit that stops most BEC losses: verify banking changes on a known phone number — never from the email itself.

  What attackers sellUrgency · authority · “don’t call the boss”

  Your habitDual-channel verify on every bank/routing change

  Tech backstopMFA · no external auto-forward · inbox-rule hunts

What people actually search. After a near-miss or a news spike, owners and bookkeepers look up business email compromise, BEC scam, and verify vendor payment change. Microsoft, law-enforcement advisories, and CISO blogs all repeat the same sentence: verify out-of-band. This page turns that sentence into a one-page policy your finance desk will follow — then lists the Microsoft 365 checks when a mailbox already looks wrong.

Business email compromise is a process attack, not a virus

BEC usually starts with a real inbox — yours, a vendor’s, or an executive’s — not a malicious attachment. Attackers read enough mail to mimic tone, timing, and thread history. They wait until someone asks about an invoice, then slip in new banking details or a “updated PDF.” Sometimes they spoof without a compromise; sometimes they live inside the mailbox for days and hide with inbox rules. Either way, the loss is a human clicking Send on a payment that felt routine.

  - Vendor change fraud — “Our bank changed — here is the new EFT info” inside a familiar AP thread.

  - Executive wire / gift card — fake CEO or owner voice, often mobile-friendly, sent when travel is plausible.

  - Payroll redirect — “Please update my deposit account before Friday.” HR panic clicks.

  - Lawyer / title scams — last-minute “closing wire” changes in construction and real-estate deals.

  - Lookalike domains — one swapped letter, forwarded PDF, or reply-to trick on a busy Tuesday.

If the message asks you to change where money goes, the message is not enough — even when the thread looks perfect and the signature is theirs.

Why BEC works on competent people

  
    Authority + deadline

    “Close the books tonight.” Helping feels professional; pausing to call feels like letting the team down. Attackers engineer that guilt on purpose.

  

  
    Familiar thread

    They reply inside a real vendor conversation — sometimes from a compromised mailbox you have emailed for years.

  

  
    One-person finance

    No second approver means no friction. Dual control is cheaper than arguing with a bank after a wire is gone.

  

Training videos about spelling mistakes do not fix this. The mail is often fluent. What fixes it is a written rule everyone hears from the owner: we verify payment changes by phone, using a number that was already on file before the email arrived.

The payment verification habit (write it once, train it louder than phishing quizzes)

  - Any bank, routing, SWIFT, or payroll change — call or text a number already in your ERP, contract, or CRM. Never use a phone number only in the suspect email or PDF.

  - Two people above a threshold — pick a dollar amount your owner will defend. Dual approval kills most BEC losses for SMBs.

  - Vendor master data discipline — only accounts payable updates banking details; sales does not “just help the client.”

  - Pause the thread — reply on a new outbound message after the call, not by continuing the possibly compromised chain.

  - Post the sentence on the wall — “We verify every banking change by phone.” Clients respect it; insurers recognize it.

After money moves. Call the bank immediately — recovery windows are short. Preserve headers and logs, but do not wait for perfect forensics to alert the institution. Document the dual-channel steps you attempted; that matters for insurance and law enforcement reports.

Microsoft 365 controls that shrink BEC blast radius

Humans first; then identity. Most BEC paths involve password reuse, legacy clients, or mailbox rules attackers add after sign-in. Pair people policy with the controls in our [Microsoft 365 MFA guide](/en/blog/microsoft-365-mfa-smb-security-defaults) and tenant hygiene in [M365 cleanup](/en/blog/microsoft-365-cleanup-licences-security-settings).

  - MFA on every user — especially finance, payroll, owners, and anyone who can approve wires.

  - Block legacy authentication — SMTP/IMAP/POP that bypasses MFA is still common on old scanners and line-of-business mail.

  - Disable external auto-forward — attackers love forwarding to Gmail they control.

  - External sender banners — tag mail from outside the org so “CEO from Gmail” stands out.

  - DMARC alignment — reduce spoof of your domain; does not stop compromised vendors, but helps your brand.

Fifteen minutes in Microsoft 365 after a scare

Run this when someone reports odd sends, a vendor says they never changed banking details, or MFA prompts they did not request.

  - Reset password + revoke sessions for the suspect account; check sign-in logs for impossible travel.

  - Inbox rules audit — delete silent forwards, “move to RSS/Notes,” and rules that mark mail read.

  - Mailbox forwarding — remove SMTP forwarding; confirm transport rules are not exfiltrating.

  - MFA registration — ensure Authenticator devices belong to the user, not the attacker.

  - Tell AP and payroll — freeze vendor file changes until dual-channel verify completes.

One-page BEC playbook (printable)

  - Dual-channel verify on every payment detail change — phone number from master data only.

  - Dual approval threshold named in dollars.

  - Who declares “payment freeze” and who talks to the bank.

  - IT steps above when a mailbox is suspect.

  - Evidence list for insurer — timestamps, headers, call notes, not screenshots alone. See [assessment deliverables checklist](/en/blog/cybersecurity-assessment-canada-evidence-deliverables-checklist).

Read it once at a staff meeting. A policy nobody rehearsed is wallpaper.

[Book a BEC and Microsoft 365 payment-controls review](/en/contact?tab=consult&utm_source=blog&utm_medium=site&utm_campaign=bec-payment-verify)

FAQ

Is BEC only wire fraud? No — EFT changes, payroll redirects, and fraudulent invoices count. Same verify habit.

Do we need a SOC? Most SMBs need MFA, forwarding controls, and a finance ritual — not 24/7 SOC theatre.

What if the vendor’s mailbox was real but hacked? That is classic BEC. Your verify call catches it when their IT has not.

Who is Amen? Winnipeg MSP — [email](/en/services/email), [managed IT](/en/services/managed), French when tickets are French. Remote across Canada and the US.

If you only do one thing

Post “We verify every banking change by phone” where AP and payroll see it daily, and kill external mailbox forwarding in Microsoft 365 this week. [Request the review](/en/contact?tab=consult&utm_source=blog&utm_medium=site&utm_campaign=bec-payment-verify)

## Topic: Cybersecurity & compliance
- [Main guide](https://amensecurity.ca/en/services/cybersecurity.md)
- [Managed IT vs Break-Fix: Side-by-Side Comparison](https://amensecurity.ca/en/guides/msp-vs-break-fix.md)

---
Source page: https://amensecurity.ca/en/blog/business-email-compromise-payment-verify-smb
Markdown version for AI agents · Amen Security
Email: info@amensecurity.ca
Phone: +1 (204) 514-3536
