Nacha Fraud Monitoring Rules 2026: Phase 1 and Phase 2

Industry:Banking and Finance       Added By:Admin       Posted On:Nov. 20, 2026

Key points

  • Phase 1 (March 20, 2026) covered all ODFIs, non-consumer Originators, TPSPs and TPSs with 6 million+ 2023 ACH originations, and RDFIs with 10 million+ 2023 receipts.
  • Phase 2 took effect June 19, 2026 (practically June 22, after the Juneteenth holiday) for every other non-consumer Originator, TPSP, TPS and RDFI.
  • Monitoring must be risk-based, target unauthorized and False Pretenses entries, and be reviewed at least annually; no specific software is required.
  • The rules do not change UCC Article 4A rights or the allocation of liability for fraud losses.
  • “PAYROLL” and “PURCHASE” Company Entry Descriptions have been mandatory since March 20, 2026.

The Nacha fraud monitoring rules that took effect in 2026 require every ODFI and every non-consumer Originator, Third-Party Service Provider (TPSP) and Third-Party Sender (TPS) to run risk-based processes that identify ACH entries suspected of being unauthorized or authorized under False Pretenses. RDFIs must monitor incoming ACH credits the same way. Phase 1 started March 20, 2026, and Phase 2 started June 19, 2026 (in practice Monday, June 22), so every covered party should already have a working, documented program.

Nacha rules 2026 at a glance

Four Nacha Operating Rules changes took effect in 2026. The fraud monitoring rules are the largest; the sections below cover each one.

Effective dateRule changeWho it applies to
March 20, 2026Fraud monitoring Phase 1All ODFIs; non-consumer Originators, TPSPs and TPSs with 6 million or more 2023 ACH originations; RDFIs with 10 million or more 2023 ACH receipts
March 20, 2026“PAYROLL” and “PURCHASE” Company Entry Descriptions become mandatoryOriginators of payroll PPD credits and of WEB debits for online purchases of goods
June 19, 2026 (June 22 in practice)Fraud monitoring Phase 2All other non-consumer Originators, TPSPs, TPSs and RDFIs
September 18, 2026Non-Same Day ACH credits must be available by 9:00 a.m. RDFI local time on the Settlement DateRDFIs

Nacha fraud monitoring rules 2026: what they require

Before these amendments, Nacha’s fraud detection requirements for Originators reached only WEB debits and Micro-Entries. The 2026 rules extend monitoring to ACH activity generally, including the credit-push payments that business email compromise and impersonation scams depend on.

The rules set out two obligations:

  • Fraud monitoring by originating parties. ODFIs, non-consumer Originators, TPSPs and TPSs must establish and implement risk-based processes and procedures, relevant to their role, that are reasonably intended to identify entries suspected of being unauthorized or authorized under False Pretenses.
  • RDFI ACH credit monitoring. RDFIs must have risk-based processes and procedures to identify incoming credit entries suspected of being unauthorized or authorized under False Pretenses, and to decide what to do with the ones they flag. Nacha cites this as Subsection 3.1.10 of the Rules.

Both obligations include a review requirement. Each party must review its processes and procedures at least annually and update them to address evolving risks. Reviewing more often is allowed. The review fits naturally alongside the Nacha audit requirements, since the annual Rules Compliance Audit is due by December 31.

What counts as “False Pretenses” in ACH?

Nacha defines False Pretenses as the inducement of a payment by a person misrepresenting (a) their identity, (b) their association with or authority to act for another person, or (c) the ownership of the account to be credited. That covers business email compromise, vendor impersonation and payroll impersonation, where the payment is technically authorized but the payer was deceived. It does not cover scams involving fake, non-existent or poor-quality goods or services.

Nacha fraud monitoring Phase 1 and Phase 2: who had to comply, and by when?

The rollout was split by 2023 ACH volume. Consumer Originators are not covered by the monitoring requirement.

WhoRequirementEffective date
All ODFIs, regardless of volumeRisk-based fraud monitoring of ACH entries, reviewed at least annuallyMarch 20, 2026 (Phase 1)
Non-consumer Originators, TPSPs and TPSs with 2023 ACH origination volume of 6 million or moreRisk-based fraud monitoring of ACH entries, reviewed at least annuallyMarch 20, 2026 (Phase 1)
RDFIs with 2023 ACH receipt volume of 10 million or moreRisk-based monitoring of incoming ACH credits (Subsection 3.1.10), reviewed at least annuallyMarch 20, 2026 (Phase 1)
All other non-consumer Originators, TPSPs and TPSsRisk-based fraud monitoring of ACH entries, reviewed at least annuallyJune 19, 2026; practical date June 22, 2026 (Phase 2)
All other RDFIsRisk-based monitoring of incoming ACH credits, reviewed at least annuallyJune 19, 2026; practical date June 22, 2026 (Phase 2)
Originators of PPD credits for wages, salaries and similar pay to consumer accountsCompany Entry Description “PAYROLL”March 20, 2026
Originators of WEB debits to consumer accounts for online purchases of goodsCompany Entry Description “PURCHASE”March 20, 2026

Why do some sources say June 19 and others June 22?

Both are correct. Nacha’s Phase 2 rule page lists the effective date as June 19, 2026, then explains that because June 19 is a federal holiday (Juneteenth), the practical effective date is the next banking day, Monday, June 22, 2026. Use June 19 as the rule date and June 22 as the first processing day the rule applied to.

ACH fraud monitoring rules in practice: what “risk-based” means

The Rules do not prescribe specific processes, procedures or software. Nacha’s Phase 1 rule page says solutions may be built in-house or bought from vendors, and that each party’s approach should fit its role, volume and risk. For the controls businesses use to stop these payments before they are sent, see how to prevent ACH fraud.

Several points from Nacha’s guidance shape what “risk-based” allows:

  • You do not have to screen every ACH entry individually.
  • Monitoring before entries are processed is not required, though Nacha notes it gives the best chance of stopping fraud.
  • For debits, a strong return and return-rate monitoring program can serve as the minimum level of fraud monitoring.
  • If you rely on another party in the origination chain to do some of the monitoring, the basis for that reliance should be reasonable and clear.
  • A risk-based approach cannot be used to conclude that no monitoring is needed at all.

What RDFIs need for credit monitoring

RDFI credit monitoring must include a risk assessment that separates higher-risk from lower-risk activity. The rule does not require pre-posting monitoring of credits. Nacha’s examples of warning signs include an SEC Code that doesn’t match the account type, unusually large amounts, bursts of similar credits, and activity on new, dormant or suspected money-mule accounts.

When an RDFI flags a credit, it can return it with R17, or with R06 if the ODFI asks for it back. An RDFI that monitors before posting may also use the funds availability exemption for suspect credits. RDFIs may use third-party service providers to meet these obligations. The full list of codes and deadlines is in the guide to ACH return codes.

Do the new rules shift liability for authorized-but-fraudulent payments?

No. Nacha says the amendments include express disclaimers that they do not modify rights and obligations under UCC Article 4A, and do not create any duty other than each party’s commitment to Nacha to comply with the Rules. Nacha states this lets it manage compliance without upsetting the allocation of liability among participants.

In practical terms, an RDFI that misses a False Pretenses credit does not become liable for the loss because of these rules, and an Originator tricked into paying an impostor does not gain a new claim against its bank. What changes is your rules compliance exposure. Nacha can enforce the monitoring and annual review requirements like any other Rule.

What are the PAYROLL and PURCHASE Company Entry Descriptions?

A separate rule in the same package, effective March 20, 2026, made two descriptions mandatory. These are required, not optional:

  • “PAYROLL” must be used for PPD credits that pay wages, salaries and similar compensation to consumer accounts. It must sit in the leftmost seven characters of the ten-character field; the other three characters are optional.
  • “PURCHASE” must be used for ACH debits to consumer accounts for online purchases of goods, normally sent as WEB entries (TEL is allowed where the standing authorization rules permit it). Purchases of services are not included.

The ODFI has no obligation to check that “PURCHASE” is present or accurate, and RDFIs are not required to act on either description, though they may use it in their own monitoring. Details are on Nacha’s Company Entry Descriptions rule page.

Other Nacha 2026 rule changes that work with fraud monitoring

Timeline of Nacha fraud monitoring rules: October 1, 2024 groundwork rules, March 20, 2026 Phase 1 and PAYROLL/PURCHASE descriptions, June 19, 2026 Phase 2, September 18, 2026 funds availability
The Nacha fraud monitoring rules from the October 2024 groundwork to the 2026 effective dates. Tap the image to open it full size.

The 2026 monitoring rules close out a package Nacha approved in 2024. The first part took effect October 1, 2024, and gives RDFIs and ODFIs the tools to act on what their monitoring finds. Nacha’s October 1, 2024 rule page lists:

  • R17 for suspected fraud: RDFIs may, but are not required to, use Return Reason Code R17 to return an entry they believe is fraudulent, including False Pretenses credits.
  • Expanded Request for Return (R06): An ODFI may ask the RDFI to return an entry for any reason. Returning is still at the RDFI’s discretion, but since April 1, 2025 the RDFI must tell the ODFI the status of the request.
  • Funds availability exemption: An RDFI that reasonably suspects a credit is unauthorized or authorized under False Pretenses may hold it outside the normal availability deadlines. Use is optional, and an RDFI that uses it must contact the ODFI.
  • Prompt return of unauthorized debits: An RDFI that uses the extended timeframe to review a debit must return it promptly once it determines the debit was unauthorized.

One more change affects RDFI posting. Under the non-Same Day credit funds availability rule effective September 18, 2026, funds for all non-Same Day credits must be available by 9:00 a.m. RDFI local time on the Settlement Date. If your credit monitoring runs before posting, check that alerts are worked within that window or that holds clearly fit the False Pretenses exemption.

ACH fraud monitoring checklist: how to check your program

Use this list to test whether your program would stand up in an ACH rules audit or an ODFI review:

  • A written policy names your role (ODFI, Originator, TPSP, TPS or RDFI) and the Phase that applied to you.
  • A documented risk assessment explains which entries, SEC Codes and customers you treat as higher risk, and why.
  • Monitoring covers False Pretenses scenarios, not just unauthorized debits: changes to vendor or employee bank details, new payees, first-time high-dollar credits.
  • Change-control steps for payment instructions require verification through a known channel, not the email or call that requested the change.
  • Alerts have owners, response times and a record of how each was resolved.
  • Return and return-rate monitoring is in place for debits, with thresholds you can explain.
  • RDFIs can show how flagged credits are handled, including when R17 is used and how R06 requests are answered.
  • Any reliance on a bank, processor or vendor is documented, with what they monitor and what you still do yourself.
  • Payroll PPD credits carry “PAYROLL” and consumer e-commerce debits carry “PURCHASE”.
  • The last annual review is dated, signed off and lists what changed.

What to do now

  1. Confirm which Phase applied to you and record it in your policy, using your 2023 origination or receipt volume.
  2. Pull your current procedures and compare them to the checklist above. Write down every gap with an owner and a due date.
  3. Sample ten to twenty recent alerts and trace each one from detection to resolution to prove the process works as written.
  4. If you are an ODFI, ask your Originators, TPSPs and TPSs for evidence of their own monitoring rather than relying on a contract clause.
  5. Schedule the next annual review now, and set triggers for an earlier one, such as a new fraud pattern, a new product or a large loss.
  6. Train operations and treasury staff on False Pretenses red flags. The webinar 2026 Nacha Rules Changes (Part 1): Fraud Monitoring & Ops Bulletins covers the monitoring rules and related operations bulletins in more depth. More payments sessions are listed under banking and finance webinars.

Frequently asked questions

What are the new Nacha rules for 2026?

The main 2026 changes require risk-based fraud monitoring by ODFIs, non-consumer Originators, TPSPs and TPSs, and risk-based monitoring of incoming ACH credits by RDFIs, phased in on March 20 and June 19, 2026. A related rule made the Company Entry Descriptions “PAYROLL” and “PURCHASE” mandatory from March 20, 2026. Nacha also has funds availability and IAT changes effective later in 2026 and 2027.

Does Nacha require specific fraud monitoring software?

No. The Rules do not prescribe specific processes, procedures or products. Nacha says solutions may be built in-house or bought from vendors, as long as they are risk-based, fit your role and are reviewed at least annually.

Do the Nacha fraud monitoring rules apply to small businesses?

Yes, if they originate ACH entries as non-consumer Originators. Phase 2, effective June 19, 2026, removed the volume threshold, so every non-consumer Originator is covered regardless of size. Consumer Originators are not covered.

What is a False Pretenses ACH payment?

It is a payment induced by someone misrepresenting their identity, their authority to act for another person, or the ownership of the account to be credited. Business email compromise, vendor impersonation and payroll redirect scams are typical examples. Scams over fake or poor-quality goods and services are not included.

Do RDFIs have to screen every incoming ACH credit before posting?

No. Nacha says RDFIs do not have to screen every entry individually and are not required to monitor credits before posting. Monitoring must still be risk-based and include a risk assessment that separates higher-risk from lower-risk activity.

When does Nacha fraud monitoring Phase 2 take effect?

Phase 2 took effect June 19, 2026. Because June 19 is the Juneteenth federal holiday, Nacha says the practical effective date was the next banking day, Monday, June 22, 2026. Phase 2 covers every non-consumer Originator, TPSP, TPS and RDFI that Phase 1 did not, regardless of volume.

Get Nacha and ACH rule changes as they happen

The 247Compliance newsletter sends new rules, effective dates and upcoming payments webinars to your inbox.

Subscribe

This article is general information, not legal or tax advice. Check the official sources above or consult a qualified advisor for your situation.