Nacha’s Fraud Monitoring Rule Is Now Fully in Effect: Is Your ACH Program Compliant?

Both phases of Nacha’s 2026 risk management amendments have now taken effect. Here’s what originators are required to have in place — and how most organizations are actually measuring up.
If your organization originates ACH payments — whether that’s payroll, vendor disbursements, refunds, or any other credit or debit entry — you are an “Originator” in Nacha’s terminology, and as of this summer, you are squarely on the hook for fraud monitoring obligations. This isn’t a proposal or a best-practice recommendation. It’s a binding operating rule, enforceable under Nacha’s National System of Fines, and the rollout phase is now behind us.
This article is a deliberate pause-and-check. We’ll walk through exactly what the rule requires, when it took effect, what “compliant” looks like in practice, and — importantly — how well the market is doing at meeting the bar. If you haven’t formally revisited your ACH fraud controls, this is the moment to do it.
Two-Phase Rollout Is Now Both Behind Us
Nacha rolled out its fraud monitoring amendments in two phases, tied to origination volume rather than company size or industry:
- Phase 1 — effective March 20, 2026: Applied to all ODFIs (originating banks), plus non-consumer Originators, Third-Party Senders, and Third-Party Service Providers whose 2023 ACH origination or transmission volume was 6 million entries or more.
- Phase 2 — effective June 19, 2026 (observed June 22, 2026, since June 19 fell on the Juneteenth federal holiday): Eliminated the volume threshold entirely. Every remaining non-consumer Originator, Third-Party Sender and Third-Party Service Provider — regardless of size or volume — is now covered.
That second phase is the one most AP and finance teams underestimated. A great many organizations assumed the new rule was aimed at banks and high-volume processors. It isn’t. A fifteen-person nonprofit running twenty vendor payments a month is now held to the same fundamental standard as a Fortune 500 treasury operation: a documented, risk-based process for spotting fraudulent entries before they go out the door.
What the Rule Actually Requires
Nacha’s amendment requires covered Originators, Third-Party Senders and Third-Party Service Providers to “establish and implement risk-based processes and procedures reasonably intended to identify entries initiated due to fraud.” That phrasing is intentionally broad, and it’s worth unpacking, because the rule does not hand you a specific tool or checklist to buy. It’s both risk-based and technology-neutral:
- Risk-based means your scrutiny should scale with exposure. A $75 reimbursement doesn’t need the same treatment as a $250,000 vendor payment. Nacha doesn’t set dollar thresholds — you’re expected to set them yourself, based on your own risk profile.
- Technology-neutral means Nacha isn’t mandating a specific detection method. Velocity checks, anomaly detection, behavioral tolerances and manual review procedures can all satisfy the rule, provided they’re documented, applied consistently, and actually reasonable given your risk.
Alongside the monitoring mandate, Nacha formally named a new fraud category — “false pretenses” — to capture the scenario that dominates vendor disbursement fraud: a payment that looks fully authorized because someone lied about who they were, what authority they held, or which account should receive the funds. For AP teams, this is the vendor bank-change scam in regulatory language. The payment clears every internal approval because nothing about the mechanics looks wrong; the fraud is baked into the instruction itself.
One more point worth emphasizing, because it changes the incentive calculus: none of this shifts fraud losses onto your bank. In most credit-push fraud scenarios — where your organization is tricked into voluntarily sending money to a criminal — your company, not your ODFI, bears the loss. The rule isn’t just a compliance exercise. It’s Nacha formalizing the loss-prevention work you already had every financial reason to be doing.
What Compliant Actually Looks Like
Because the rule is deliberately non-prescriptive, “compliant” is best understood as a set of controls that examiners, auditors and your own ODFI are likely to expect to see documented and in active use:
- Dual control on higher-risk payments. A second, independent approver for payments above a defined threshold or flagged as unusual — one person can be fooled; two independently is harder.
- Account validation before first payment, and re-validation on any change. Confirm the receiving account is open, active and really belongs to the party you intend to pay — not just that the routing number is well-formed.
- Out-of-band verification for any bank-detail change. Call the vendor back using a phone number already on file — never the number or email address supplied in the change request itself.
- Multi-factor authentication on payment initiation and approval systems, favoring authenticator apps or hardware tokens over SMS codes where practical.
- Written, risk-based monitoring procedures, reviewed at least annually and any time your payment process or risk profile changes materially.
- A defined response and escalation path — who investigates a flagged item, who has authority to pause a payment run, and how your ODFI gets notified if fraud is confirmed.
Nacha has been explicit that the old standby of “two people sign off” is no longer sufficient on its own for organizations of any real scale. Dual control remains a foundational piece, but the rule expects it to sit inside a broader, documented monitoring program — not to stand in for one.
Where Compliance Actually Stands
Unfortunately, adoption has lagged the calendar. Industry surveys taken in the run-up to Phase 2 painted a rather stark picture. One analysis from LSEG Risk Intelligence found that roughly four out of five financial institutions surveyed had either not started preparing or were still trying to determine what the rule required of them, even as the deadline approached. Separately, industry estimates cited by payment-fraud vendors have put the share of firms lacking adequate ACH fraud monitoring at around seven in ten.
Those figures should be read with a grain of salt — they come from firms with a commercial interest in compliance technology, and “adequate” is doing a lot of work in that second statistic. But directionally, they line up with what auditors and advisory firms have been reporting since the deadline passed: a meaningful share of covered Originators, particularly smaller and mid-sized ones without dedicated treasury or compliance staff, do not yet have a written, risk-based ACH fraud monitoring procedure they could hand to an examiner today. If that describes your organization, you are not alone — but you are also not compliant, and the exposure is real. Nacha’s National System of Fines allows for financial penalties, requires corrective action and, in more serious cases, suspension or termination of ACH origination privileges.
A 7-Point Self-Check for Originators
Before you assume your organization is covered, run through this with whoever owns AP, treasury, and payment operations at your organization:
- Do we send or receive ACH payments of any kind, at any volume?
- Do we have a written fraud-monitoring procedure — not just informal habits — that someone could produce on request?
- Does every vendor bank account change request trigger an out-of-band callback, using contact information already on file?
- Does a second, independent person review or approve higher-risk or higher-value payments?
- Do we validate new vendor bank accounts before the first payment and re-validate when details change?
- Is payment-system access protected by multi-factor authentication?
- When did we last review — and formally document that we reviewed — these procedures?
If you can’t answer “yes” to most of these items, or you’re answering from memory rather than pointing to a document, that gap is your starting point. The good news is that the highest-leverage control — out-of-band verification of vendor bank-detail changes — is also one of the cheapest to implement and closes off the single most common vector for credit-push fraud losses.
| Where to start if you’re behind Begin with vendor bank-change verification: it’s low-cost, high-impact and directly addresses the “false pretenses” fraud type Nacha named in this rule.Formalize what you already do informally. Many organizations have reasonable practices that simply aren’t written down — documentation is often the biggest gap, not the controls themselves.Size your controls to your actual risk. A risk-based program doesn’t require enterprise fraud software; it requires a defensible, consistently applied process scaled to your payment volume and exposure.Put a review date on the calendar now. Nacha expects at least annual review — treat that as a floor, not a target. |
The Bottom Line
The deadline isn’t approaching — it has passed, for every category of Originator. Nacha’s rule doesn’t expect perfection, and it doesn’t mandate a specific vendor or platform. What it expects is a real, risk-based documented process that your organization truly follows, reviews and can produce evidence of. If you’re an AP or finance leader who hasn’t formally revisited your ACH fraud controls against this standard since the rule took full effect in June, that review is worth doing this month — before an incident, or an audit, forces the question.
To learn how VendorInfo’s Automated Vendor Bank Account Verification can help you meet the Nacha requirements, contact us.


