Accounting Technology

BEC Losses Hit $3.05 Billion: Why Payment Controls Are Cybersecurity

BEC losses of $3.05 billion across 24,768 FBI complaints make payment verification an accounting control problem. Practitioners get a concrete checklist for approvals, access reviews and tested recovery.

How Would Your Controls Hold Up Under Pressure?
Exhibit · How Would Your Controls Hold Up Under Pressure? — Tumisu / pixabay

Adjustments

  1. FBI's 2025 Internet Crime Report logged 24,768 BEC complaints with roughly $3.05 billion in reported losses.
  2. Verizon's 2026 DBIR: vulnerability exploitation drove 31% of initial access; ransomware appeared in 48% of breaches.
  3. NIST recommends multifactor authentication, phishing-resistant options for sensitive apps, and access removal on role change or departure.
  4. FBI guidance: verify payment and account-change requests via previously verified numbers; report suspected BEC to IC3 immediately.

Business email compromise generated 24,768 complaints and roughly $3.05 billion in reported losses, according to the FBI's 2025 Internet Crime Report — figures reported to the Internet Crime Complaint Center, not a nationwide estimate of every loss. Donny Shimamoto, writing for the Center for Accounting Transformation, draws a blunt conclusion for practitioners: that threat lands squarely in accounting's territory, and traditional accounting internal controls, not cybersecurity tooling, are what stop it.

A supplier sends new payment instructions. An executive requests an urgent wire. A payroll administrator gets a password-reset message. Each looks like routine business, Shimamoto writes, but each demands a control that holds even when the request appears legitimate — because urgency is precisely the attacker's strategy.

What should payment controls require?

The FBI recommends independent verification of payment requests and of any change to account numbers or payment procedures. Shimamoto's practical checklist for firms:

  • Call a known contact on a previously verified number, never one supplied in the request itself.
  • Require a second approval for sensitive changes and document the verification before releasing funds.
  • Examine the exceptions: can someone override the process because an executive is traveling or a vendor demands immediate payment? Does the same person both change banking details and authorize the transfer?

Leaders, he argues, should explicitly back employees who pause a transaction to verify it — including requests that appear to come from leadership. A control that vanishes under pressure offers little protection.

What do the breach statistics actually mean?

Verizon's 2026 Data Breach Investigations Report finds vulnerability exploitation accounted for 31% of initial access in its breach dataset, with ransomware appearing in 48% of breaches. Shimamoto cautions these figures describe investigated breaches, not the probability any particular organization will be attacked.

For accountants, the response is better questions about the protections underpinning critical work. Who owns software updates, and how are urgent security fixes prioritized? Which devices and applications sit outside normal monitoring? If a system is too old to secure adequately, who formally accepts the risk of continuing to use it?

Access deserves equal scrutiny. NIST (the U.S. National Institute of Standards and Technology) recommends enabling multifactor authentication wherever offered, considering phishing-resistant options for sensitive applications, limiting access to what people need, and removing it when needs change or staff leave. An internal transfer should trigger an access review just as a departure does — convenience, Shimamoto warns, should not quietly become permanent authority. He suggests reviewing access to banking, payroll, financial reporting and document-sharing systems jointly with the technology team.

How do you make recovery measurable?

A backup report marked "successful" tells leadership nothing about how quickly payroll can resume or whether the accounting team can complete the close. Shimamoto advises working with technology and operational leaders to identify the processes that must continue during an outage, estimate the cost of interruption — delayed collections, missed payments, overtime, record reconstruction — and set how long each process can reasonably remain unavailable.

Then test recovery against those needs: a restoration exercise demonstrating usable data and an achievable recovery time, run with the people who will actually perform the work after systems return.

Outsourcing shifts, but does not remove, this responsibility. For a payroll provider, cloud accounting platform or managed technology service, establish in writing who handles access, backups, incident notification and recovery — and what your team does if the provider goes dark. Record those answers before an incident forces negotiation under pressure.

What does a practiced response look like?

Employees need a way to report a concern quickly, without fearing an honest mistake becomes a public reprimand. Shimamoto recommends short exercises using realistic scenarios — a payment has gone to a fraudulent account, or staff cannot access payroll on processing day — that identify who contacts the bank, who coordinates with technology specialists and who authorizes operational decisions, with essential contact information accessible even if email is down.

For suspected business email compromise, the FBI advises contacting the financial institution immediately and reporting the incident to IC3; both steps belong in the response plan.

His closing assignment: choose one critical workflow and follow it from request through authorization, execution and recovery. Identify a weakness, assign an owner, set a date to verify the fix. Cybersecurity becomes useful to leadership, he writes, when accountants can explain what is protected, what could interrupt operations and which action reduces that exposure.

via improvetheworld.net (Original)

Share this article:

More from Priya Raman

Priya Raman

Show full bio

Senior reporter covering technology and product news in CPA News is a professional daily at CPA News.

7 articles

Linked entries

  1. PCAOB Creates Five Audit-Misconduct Units as Budget Falls 9.4%
  2. PCAOB creates five specialist enforcement units for misconduct probes
  3. SEC SOX proposal could exempt 1,596 companies from 404(b) attestation
  4. 74% of AI-Using Clients Would Fact-Check Their Accountant's Work
  5. Sri Lanka Bars Two EY Partners From Bank Audits After $41 Million NDB Fraud

▲ Previous article