A business customer approves an ACH payment after receiving an email about a vendor’s new bank account. The login is legitimate. The payment amount looks familiar. The destination belongs to a fraudster.

This illustrative scenario explains why ACH fraud detection needs more than a check for stolen credentials. Fraud managers at banks and credit unions need to examine payment behavior, account activity, and the circumstances behind an instruction, then give staff a clear way to act.

What is ACH fraud detection?

ACH fraud detection is the process of identifying potentially fraudulent Automated Clearing House payments by reviewing transaction details, account behavior, and available customer information. It covers suspicious outgoing payments and incoming funds that may reach accounts controlled or used by criminals.

An originating depository financial institution (ODFI) handles payment origination. A receiving depository financial institution (RDFI) receives ACH entries. Each sees different evidence, which makes coordination important.

Which ACH fraud schemes should teams recognize?

Three patterns deserve a place in training and investigation procedures:

  • Account takeover: A criminal gains unauthorized access and initiates payments or changes payment instructions.
  • Unauthorized debits: Funds are pulled from an account without valid authorization, potentially using stolen account information.
  • Payment redirection: A fraudster impersonates a vendor, executive, or employee to change where a legitimate payment goes.

Payment redirection can involve business email compromise (BEC) or payroll impersonation. A customer may approve the transfer while misunderstanding who will receive it. The FBI recommends independently verifying payment requests and changes to account details. FBI guidance on BEC.

What should ACH monitoring look for?

Start with the account’s expected activity. A large payment may be normal for an established business and unusual for a consumer account with little history.

Useful review signals include:

  • A new recipient or changed payment destination, especially alongside unusual urgency.
  • Payment counts or values that differ sharply from prior activity.
  • Unexpected credits to a new or previously inactive account.
  • A Standard Entry Class (SEC) code inconsistent with the receiving account type.
  • Several incoming credits under different names, followed by movement of funds out of the account.

Nacha’s risk-management guidance discusses transaction patterns, account characteristics, and name comparisons during investigations. These signals support additional review; none proves fraud by itself. Nacha guidance on risk-based controls.

For example, a seasonal business may legitimately increase payroll. Investigators need access to that context before deciding whether an alert warrants escalation. Segment monitoring by account type and expected activity rather than applying one dollar threshold across the entire portfolio.

How do detection and prevention work together?

Detection identifies suspicious activity. Prevention controls can reduce the chance that a fraudulent instruction becomes a payment.

For business customers, consider separate approval for payment changes and verification through a previously established contact channel. Calling a number supplied in the suspicious email does not provide independent confirmation.

Authentication also matters. FFIEC guidance supports risk assessments and layered security, including multifactor authentication or equivalent-strength controls for high-risk activities. Those controls address access risk, but a legitimate user can still be deceived into approving a payment. Federal Reserve summary of FFIEC authentication guidance.

Connect payment alerts with relevant account changes and investigation history where available. Give customers and members a clear reporting route when something looks wrong.

What do Nacha’s 2026 rules require?

Nacha’s expanded fraud-monitoring requirements are now in effect. All ODFIs came into scope on March 20, 2026. Coverage expanded to all RDFIs by the Phase 2 practical effective date of June 22, 2026.

The requirements call for risk-based processes and procedures, with reviews at least annually. RDFI monitoring addresses incoming credits suspected of being unauthorized or authorized under false pretenses. The rules do not require pre-posting monitoring. Nacha’s fraud-monitoring rule details.

Nacha is also technology-neutral: it does not prescribe a particular monitoring product. Institutions should assess whether their existing controls, data, and workflows meet their responsibilities. Nacha’s credit-push fraud monitoring resources.

What happens after an alert?

An alert needs an owner and a response path. A practical workflow is to:

  • Review the payment, account history, and available authentication or change records.
  • Verify suspicious instructions through trusted contact details.
  • Engage ACH operations and the other institution promptly when recovery may be needed.
  • Assess available funds and permitted hold or return options with the appropriate teams.
  • Record the decision, supporting evidence, and follow-up actions.

Nacha publishes separate response checklists for ODFIs and RDFIs. Adapt them to your institution’s authority, obligations, and operating procedures. Recovery is not guaranteed.

Track confirmed fraud, false positives, time to review, losses, and recovered funds. Review missed cases as well as successful catches.

For your next control review, trace one suspicious ACH payment from alert to resolution. Identify who receives it, what information they can see, and whether they can reach the right person before funds move again.

Explore more fraud-prevention insights for community banks and credit unions from REDi.