email59

Security

The direct deposit change email: how payroll diversion works, and the check that keeps a paycheck where it belongs

It arrives in human resources or accounting on Tuesday morning: a polite email from a genuine employee asking to update their direct deposit information before Friday's payroll. There is a voided check attached, a quick apology for the short notice, and an explanation that their old bank account was closed. When the bookkeeper updates the routing number in the payroll software, Friday's salary does not go to the employee. It lands in an online mule account and vanishes within minutes.

This attack is called payroll diversion, and it is one of the most reliable cash-out mechanisms in modern Business Email Compromise (BEC). Unlike executive impersonation scams asking for fifty-thousand-dollar vendor wires or urgent retail gift cards, payroll diversion targets ordinary operational habits. For small business employers, dental clinics, schools, and distributed teams, processing a bank detail update feels like standard administrative support. But when that change is processed on the strength of an email alone, the financial loss falls squarely on the employer.

The anatomy of a payroll diversion attack: why fraudsters strike on Tuesday

Payroll diversion attacks follow a predictable rhythm designed around banking cutoff windows. In the United States, direct deposit files processed via the Automated Clearing House (ACH) network require employers to submit payroll records 1 to 2 banking days before disbursement. Attackers understand this timeline thoroughly, which is why the vast majority of payroll diversion attempts land on Monday morning or Tuesday afternoon.

Attackers leverage three primary infiltration methods to deliver the fraudulent request to HR or payroll:

  • Display-name spoofing on free webmail: The attacker sets up an account on Gmail or Outlook with the display name matching the employee (e.g. Sarah Miller <sarah.miller.personal2026@gmail.com>). The body opens with a casual pretext: "My company laptop is in the shop and I can't access my work email, so I'm writing from my personal address. Can you please update my direct deposit for this week's check?" Busy administrators reviewing emails on phones see the familiar name and skip inspecting the header.
  • Compromised employee webmail (Account Takeover): The attacker harvests corporate Microsoft 365 or Google Workspace credentials through credential phishing or session hijacking. They sign in, install a silent forwarding rule (sending messages containing "payroll" or "deposit" to an external address and auto-deleting them from the inbox), and email HR from the employee's genuine corporate address. When HR replies, the filter hides the response from the real employee.
  • Lookalike typosquatted domains: The criminal registers a domain almost identical to the employer's domain (e.g. @acme-corp.co instead of @acme-corp.com, or @cornpany.com replacing 'm' with 'rn').

Here is what a typical payroll diversion email looks like when it reaches an HR desk:

From: Sarah Miller <sarah.miller.personal26@gmail.com>
To: HR & Payroll <payroll@company.com>
Date: Tuesday, 9:14 AM
Subject: Urgent: Direct deposit bank update for Friday's payroll

Hi Team,

I recently switched to a new banking institution and closed my old account. Could you please update my direct deposit details for this upcoming Friday's payroll?

I want to make sure my paycheck doesn't bounce back or get delayed. Here are my updated banking details:

  • Bank Name: Green Dot Bank (GO2bank)
  • Routing Number: 084302636
  • Account Number: 492019385012
  • Account Type: Checking

I have attached my direct deposit authorization slip and a voided check PDF for your records. Please let me know once this is confirmed in the system.

Thank you so much,
Sarah Miller

Every element of this email is calibrated to exploit administrative courtesy: an urgent impending cutoff, an attached document that looks official, and a plausible reason why the employee needs immediate assistance.

The numbers: 8% to 11% of BEC cash-outs and the mule bank ecosystem

In quarterly threat reports published by Fortra and the Anti-Phishing Working Group (APWG) across 2024 and 2025, payroll diversion consistently ranks as one of the top cash-out methods in Business Email Compromise. While gift card scams lead in volume due to low technical overhead and wire fraud leads in gross dollar value, payroll diversion occupies a dangerous middle ground: high success rates, moderate individual values ($1,800 to $6,500 per incident), and near-zero recovery rates once disbursed.

BEC Cash-Out MethodShare of Observed BEC (APWG 2025)Primary Target Within OrgAverage Loss Per EventRecovery Likelihood
Gift Card Scams45% to 55%General Staff / Assistants$500 – $2,5000% (Redeemed in minutes)
Payroll Diversion8% to 11%HR & Payroll Specialists$1,800 – $6,500< 2% (Drained on payday)
Vendor Invoice Fraud7% to 12%Accounts Payable (AP)$45,000 – $250,000+15% – 30% (If frozen < 24h)
Direct Wire Fraud5% to 9%Finance Directors / Controllers$80,000 – $500,000+20% – 40% (Kill Chain response)

The FBI Internet Crime Complaint Center (IC3) reported that total Business Email Compromise losses surpassed $2.77 billion in 2024 and expanded to $3.05 billion across 24,768 complaints in 2025. During targeted surges, dollar losses tied strictly to payroll diversion climbed by over 800% as organized cybercrime groups turned their attention toward decentralized workplaces.

Where does the money go? The mule banking network

Threat actors rarely route stolen paychecks to traditional national commercial banks. Brick-and-mortar financial institutions enforce strict identity verification at branch opening and place holds on sudden large ACH transfers. Instead, payroll diversion relies heavily on fintech neobanks and prepaid card providers:

  • Green Dot Bank / GO2bank (~31% of tracked diversion mules): Green Dot's mobile banking platform and retail prepaid cards allow digital account setup and instant debit card provisioning. In threat intelligence reports by Fortra, Green Dot routing numbers consistently account for nearly a third of all identified payroll diversion drop accounts.
  • SoFi Bank (~14%): Fast online onboarding and smooth ACH integration make compromised or synthetic SoFi accounts a frequent secondary target.
  • Sutton Bank / Cash App (~12%): Routing numbers mapped to prepaid digital wallets permit immediate conversion of ACH credit into debit card point-of-sale purchases or instant Bitcoin purchases.
  • Chime / The Bancorp Bank (~10%): Popular for early direct deposit features, allowing fraudsters to access diverted funds up to two days before traditional payroll settlement dates.

Why processing bank changes by email alone guarantees a loss

When an accounting team realizes on Friday morning that an employee did not receive their wages, the instinctive response is to contact their business bank and request an ACH recall. In practice, ACH reversals almost never work in payroll diversion cases.

Under Nacha Operating Rules, an Originating Depository Financial Institution (ODFI) can issue an ACH Return or reversal within 5 banking days under specific exception codes. However, an ACH reversal is not a credit card chargeback. The receiving bank (RDFI) will only return the funds if the money remains in the receiver's account. Because fraudsters schedule automated transfers or ATM cash withdrawals the moment the ACH credit posts at 6:00 AM, the account balance is typically zero by 7:00 AM. The receiving bank answers with code <code>R01</code> (Insufficient Funds) or <code>R16</code> (Account Frozen). The money is gone.

Worse, the legal burden rests entirely on the employer. Under the federal Fair Labor Standards Act (FLSA) and state wage protection laws (such as California Labor Code § 204 or New York Labor Law § 191), an employer cannot tell an employee: 'We sent your paycheck to a fraudster who emailed us, so you will have to wait until we recover the money.' An employer remains strictly liable for paying earned wages on time. The business must immediately issue a second, full paycheck out of its own reserves, absorbing a 100% loss on the diverted funds.

The 4-step verification check that keeps a paycheck where it belongs

Stopping payroll diversion does not require expensive enterprise threat defense appliances. It requires one non-negotiable rule: never execute a direct deposit or bank account change based solely on an email request. Every small employer and bookkeeper should adopt this four-step verification check:

1. Out-of-Band Call

Never reply to the email. Call the employee using the phone number already stored in their personnel file or speak to them face-to-face. Never use a phone number listed in the email body or signature.

2. The 1-Cycle Hold Rule

Any bank change submitted within 72 hours of a payroll cutoff does not take effect for that pay run. Either deposit to the existing verified account or issue a physical paper check handed directly to the employee.

3. Dual-Channel Notice

When a change is confirmed, an automated security notice is sent to both the employee's work email and their registered personal mobile phone/email detailing the last 4 digits of old and new accounts.

4. Self-Service Portal MFA

Require employees to edit their own payment methods inside Gusto, ADP, or Rippling using Multi-Factor Authentication. Forbid manual admin entry from email attachments.

How do major payroll platforms handle these security safeguards out of the box? Here is a comparison of direct deposit protections across four leading small-business payroll providers:

Payroll PlatformEmployee Self-Service MFAMandatory Change AlertsAdmin Dual-ApprovalPre-Note Verification Support
GustoYes (SMS or Authenticator App)Yes (Automatic email & SMS)Optional (Custom admin permissions)Yes (Zero-dollar prenote / micro-deposits)
ADP Workforce NowYes (ADP Mobile / Push / SMS)Yes (Security alert notification)Yes (Configurable workflow approvals)Yes (Pre-notification cycle support)
RipplingYes (TOTP / Biometric RPass)Yes (Real-time employee push alert)Yes (Custom approval policies)Yes (Instant bank login via Plaid)
QuickBooks PayrollYes (Intuit Account 2FA)Yes (Email confirmation)No (Single admin sign-off)Yes (Test transaction verification)

The security confirmation email: what to send when bank details change

Whenever an employee's direct deposit routing is altered, your system or HR department must immediately dispatch a standardized security notice. This notification should be sent to both the employee's corporate email and the personal phone or email stored during initial hiring onboarding. Like a <a href="/articles/was-this-you-new-device-and-password-changed-emails.html">new-device or password-changed-emails.html">new-device or password-changed alert</a>, it gives the real employee an immediate opportunity to intervene before payday.

Subject: Security Alert: Your direct deposit details have been updated

Hi [Employee Name],

This is an automated notification confirming that your direct deposit banking information for [Company Name] payroll was recently updated on [Date, Time, Time Zone].

Summary of Changes:

  • Previous Account: [Previous Bank Name] ending in [****1234]
  • New Account: [New Bank Name] ending in [****5678]
  • Effective Payroll Date: [Upcoming Payroll Date]

Did you authorize this change?

If you requested this update, no further action is required.

If you did NOT request this change, your account may be compromised. Contact HR and Payroll immediately at [HR Phone Number] or email [Official Security Email] so we can freeze this disbursement and secure your paycheck.

Sincerely,
Payroll & People Operations
[Company Name]

Automating bank change alerts with email59

If you build internal HR tools, employee portals, or bookkeeping scripts, you should never let bank detail mutations pass silently. Using a light email API like email59, you can trigger an instant out-of-band security notice to an employee the exact moment a direct deposit record is updated:

import os
import requests

EMAIL59_API_KEY = os.environ.get("EMAIL59_KEY")

def notify_direct_deposit_update(employee_email: str, employee_name: str, old_last4: str, new_last4: str, new_bank: str):
    """Dispatches an immediate security notice via email59 when bank details mutate."""
    payload = {
        "to": employee_email,
        "subject": "Security Alert: Direct deposit details updated",
        "template": "notice",
        "heading": "Direct Deposit Updated",
        "body": (
            f"Hi {employee_name},\n\n"
            f"Your payroll direct deposit account was changed to {new_bank} ending in ****{new_last4} "
            f"(previously ****{old_last4}).\n\n"
            f"If you authorized this change, you can safely ignore this email. "
            f"If you did NOT authorize this change, please call Payroll immediately at 555-0199 to freeze payment."
        ),
        "button_text": "Review Payroll Settings",
        "button_url": "https://portal.yourcompany.com/payroll/security",
        "brand": {"name": "People Operations", "color": "#2f5bd3"}
    }
    headers = {
        "Authorization": f"Bearer {EMAIL59_API_KEY}",
        "Content-Type": "application/json"
    }
    resp = requests.post("https://email59.com/v1/send", json=payload, headers=headers, timeout=10)
    resp.raise_for_status()
    return resp.json()

Keeping paychecks where they belong

Payroll diversion works because it exploits empathy and operational hurry. An administrative team wants to be responsive to an employee who says their bank account closed and they need help before payday. But genuine payroll security is built on friction.

By enforcing an out-of-band phone call on the number already recorded in your files, requiring employees to update details through self-service portals with multi-factor authentication, and holding late changes for a physical paper check, your organization removes itself from the 8% to 11% of BEC statistics. For related guides on handling critical customer communications and billing notices, read our articles on <a href="/articles/statement-of-account-email-five-open-invoices-ageing-buckets.html">monthly statements of account</a> and <a href="/articles/receipt-email-what-a-payment-receipt-has-to-carry.html">payment receipts</a>.

Send your first email More articles