The email came from the vendor you've paid every month for two years. Same logo, same signature, same tone. The only difference: a short note saying they'd changed banks, with new account details attached. Your ops lead updated the record and paid the invoice.
Three weeks later, the real vendor called asking why you hadn't paid.
If you're a technical founder, it's tempting to think this is a finance problem. It isn't. It's a systems problem, and engineers are unusually well equipped to fix it. This post covers the 2026 data and a practical set of controls a small team can implement quickly.
What the AFP 2026 survey found
The Association for Financial Professionals' 2026 Payments Fraud and Control Survey shows how widespread this has become.
- 76% of organizations experienced attempted or actual payments fraud.
- 74% were affected by business email compromise (BEC), a significant increase from the two prior years.
- 48% of organizations under $1 billion in revenue reported actual financial losses.
- Only 17% use AI tools to help mitigate payments fraud.
And while the scams are increasingly digital, the payment methods hit are surprisingly old-fashioned.
- Checks were the most targeted payment method at 58%, ahead of ACH debits (30%) and wires (25%).
Why startups and small businesses are especially exposed
Large companies have treasury teams, segregation of duties and multi-step approval workflows. Small teams have... Slack.
Few people, many hats. The person who receives the invoice often also approves and sends the payment.
Trust-based culture. Startups run on speed and trust. "The founder said to pay it" is often enough.
Lots of SaaS and contractor payments. Many small recurring payments to many vendors create a large surface area.
Public information. Your team page, LinkedIn posts and press releases tell attackers exactly who to impersonate and who to target.
AI-generated pretexts. Attackers now use AI to write convincing, typo-free emails and even mimic voices. The old advice to "look for spelling mistakes" no longer works.
The playbook: controls you can ship this week
Think of payments as a production system. You wouldn't let one person push to prod without review. Apply the same thinking to money.
1. Out-of-band verification for any bank detail change
This is the single most important control. Any request to change vendor bank details must be verified by calling the vendor at a phone number already on file, never one from the email. Write it down as policy. Make no exceptions, including for the CEO.
2. Two-person rule for payments over a threshold
Require a second approver for payments above a set amount, say $2,500, and for any first payment to a new account. Most banks and accounting tools support dual approval natively.
3. Lock down email
- Enforce MFA on every email account, preferably phishing-resistant methods like passkeys or hardware keys.
- Configure SPF, DKIM and DMARC for your domain, and move DMARC to
p=quarantineorp=rejectonce monitored. - Flag external email clearly and alert on lookalike domains.
- Alert on new mailbox forwarding rules, a classic sign of a compromised account.
4. Positive pay and payment controls at the bank
If you still write checks, enable positive pay, which matches issued checks against those presented. Also enable ACH debit blocks or filters so only authorized companies can debit your account.
5. Vendor master hygiene
Keep a single source of truth for vendor details. Log every change with who, when and how it was verified. Review the list quarterly and remove vendors you no longer pay.
6. Make "pause and verify" a cultural norm
Attackers rely on urgency: "This must be paid today or the contract is cancelled." Train your team that urgency is a red flag, and that nobody will ever be criticized for pausing to verify, especially when the request appears to come from the founder.
7. Plan the first hour
Write a one-page incident plan: who calls the bank, who preserves the emails, who contacts the vendor, who files a report. If money goes out fraudulently, the first hours matter for any chance of recovery.
A minimal policy you can paste into your handbook
Payments security policy
- Bank detail changes are verified by phone using contact details already on file.
- Payments over $2,500 and all first-time payments require two approvers.
- All staff use MFA on email and finance tools.
- Urgent payment requests are verified before payment, regardless of sender.
- Suspected fraud is reported immediately to [name] and the bank.
It's short on purpose. A policy people actually follow beats a 30-page document nobody reads.
Automating the boring parts (for engineers)
Because you're technical, you can go further than most small businesses. A few practical automations:
- Vendor change alerts. If your accounting tool has an API or webhooks, trigger a Slack alert and a ticket whenever vendor bank details change. The ticket can't be closed until someone records how it was verified.
- Lookalike domain monitoring. Watch for newly registered domains that resemble yours or your key vendors', and add them to your mail filter.
- Mailbox rule auditing. Run a weekly script against your email provider's admin API to list forwarding and auto-delete rules, and flag new ones.
- Payment anomaly checks. Flag payments to new accounts, unusual amounts, unusual times or vendors who haven't been paid in months.
- DMARC reporting. Route aggregate DMARC reports into a dashboard so you can see who's sending email as your domain.
None of these are complex projects. Together, they turn fraud prevention from "hope someone notices" into a monitored system.
Training that actually works
Annual security slide decks don't change behavior. Short, specific and frequent training does. Every quarter, spend fifteen minutes in a team meeting walking through one real example: a fake invoice, a vendor bank change request, an urgent message from "the CEO." Ask the team what they'd do. Then celebrate anyone who reported a suspicious message in the past quarter, even if it turned out to be legitimate. You want reporting to feel normal and rewarded, never embarrassing.
What to do if money has already gone out
Speed matters. Call your bank's fraud line immediately and ask them to attempt a recall. Preserve every email and message without deleting anything. Contact the real vendor through known channels. Report the incident to the relevant authorities; in the US that includes the FBI's Internet Crime Complaint Center (IC3). Then review how the request got through and close that gap before you do anything else.
Why this is a founder issue
It's easy to delegate security to whoever "does IT." But payments fraud sits at the intersection of finance, operations, culture and technology. Only the founder can make some of the calls: who has authority to pay, what the approval thresholds are and whether the company will slow down a little to be safe.
These are also the decisions founders put off, because nothing has gone wrong yet. Until it does.
Where The Lonely Entrepreneur helps
The Lonely Entrepreneur helps founders build the operating systems that keep a growing company safe:
- Spot your weak areas. The free Dermer Diagnosis scores five areas of your business and ranks your biggest exposures, with a 30-day action plan.
- Build controls with peers. The Learning Community includes 5,000+ learning modules, tools and templates, unlimited group coaching and weekly live sessions with Michael Dermer.
- Use AI where it actually helps. Only 17% of organizations use AI for fraud mitigation. The AI Sidekick helps companies apply AI where it matters.
- Get a CEO-level partner. For $5M to $50M companies, Sidekick provides a senior partner for operating and risk decisions.
The bottom line
The invoice will look real. The email will sound right. The voice on the phone might even sound like your CEO. Your defense isn't spotting the fake; it's having a process that doesn't depend on spotting it. Out-of-band verification, dual approval, locked-down email and a culture that rewards pausing will stop most attacks before money moves.
Ship one control today: write the bank-detail-change rule into your handbook and tell the team.
Frequently asked questions
How common is payments fraud for US organizations?
76% experienced attempted or actual payments fraud in 2025, according to the AFP 2026 Payments Fraud and Control Survey.
What is business email compromise (BEC)?
A scam where attackers impersonate a trusted person or vendor by email to trick staff into sending money or changing payment details. 74% of organizations were affected in 2025.
Which payment methods are most targeted?
Checks, at 58%, followed by ACH debits at 30% and wires at 25%.
What's the single most effective control against BEC?
Verifying any bank detail change by phone using contact details already on file, never ones in the request.
Where can founders get help building operating controls?
The Lonely Entrepreneur's Dermer Diagnosis identifies exposures, and its Learning Community, AI Sidekick and Sidekick programs help founders build stronger systems.



