Biweekly 15-Minute Implementation Updates

ACH Readiness Briefings

Preparing for the 2026 Nacha ACH fraud monitoring rule changes requires more than awareness — it requires operational clarity. The ACH 2026 Readiness Brief is a focused, biweekly discussion designed to help financial institutions navigate implementation decisions, examiner expectations, and evolving ACH fraud trends in 15 minutes or less. 

2nd ACH Readiness Briefing-1

What This Series Covers 

Each session addresses practical questions financial institutions are actively working through:

  • Group 12 (1) Phase 1 vs Phase 2 implementation requirements
  • Group 12 (1) Manual vs automated monitoring expectations
  • Group 12 (1) SAR filing and ACH fraud trend data
  • Group 12 (1) New account risk exposure
  • Group 12 (1) Staffing and workflow sustainability
  • Group 12 (1) Audit documentation
iStock-1436927152

Who Should Attend

 

  • Group 12 (1) Compliance Officers
  • Group 12 (1) BSA/AML Officers
  • Group 12 (1) Risk & Fraud Teams
  • Group 12 (1) Operations Leadership
  • Group 12 (1) Executive Management evaluation ACH monitoring strategy
iStock-1446223587

Submit Your Questions or Request an Indepth Consultation

Submit A Question for an Upcoming Session

 
Many institutions are working through similar implementation challenges. If you have a specific question related to the 2026 ACH fraud monitoring requirements, submit it below.
 
Selected questions will be addressed in upcoming sessions.
 
 
Submit Your Question!

Need More Direct Guidance?

 If your institution is evaluating how to meet the 2026 monitoring requirements — whether through manual processes or automation — we are available to walk through implementation considerations specific to your environment. 

 

Schedule A Consultation

March 4th Recording Recap

  • Key compliance deadlines: Phase 1 – March 20, 2026 | Phase 2 – June 19, 2026
  • How the rules apply to Originating Depository Financial Institutions (ODFIs)
  • What fraud monitoring expectations NACHA is establishing
  • What actions banks should consider when suspicious ACH activity is identified

 

 

March 17th Recording Recap

  • What action should an ODFI consider taking if an entry is identified as suspect?

    Phase 1 for March is based on volume of 2023. Is the volume based on dollar amount or number of ACH transactions?

  • Phase 1 for March is based on volume of 2023. Is the volume based on dollar amount or number of ACH transactions?

  • Other than the institution requirements to determine if a financial institution falls under March or June dates, are there any different requirements for each date.

  • Does NACHA have any templates for updates to existing agreements?

March 31st Recording Recap

  • Key compliance deadlines: Phase 1 – March 20, 2026 | Phase 2 – June 19, 2026
  • For the Company Entry Description, does PAYROLL, PURCHASE, etc. required to be in all caps?    
  • If we do the risk rating manually, how do you recommend handling the scoring of the risk tiers (low/medium/high)?  What would be examples of each tier?
  • Do you recommend the financial institution send a letter to their customers asking if they are in compliance with the requirements? Should the letter be signed by the customer and sent back to the financial institution?

April 14th Recording Recap

  • How should we monitor Reversals/Returns? Just high velocity or something else? 
  • Do we need to track the various return codes as well? (R01, R02, etc.) 
  • How should we monitor for Notice of Change (NOC) transactions? 
  • How should we score IAT transactions? All high risk tier?

 

 

April 28th Recording Recap

  •  Do you have a checklist template available for FI's to use to have their originator customers sign? If not, please give us some things to consider putting in the document. 
  •  At the time of the new account opening, should we consider developing a questionnaire for the new account rep to get the customer to complete to provide the bank information regarding their ACH activity? 
  •  If we monitor ACH manually, what documentation will we be expected to provide to the examiners during an examination? 
  •  How detailed do you think ACH examinations will be after the June deadline date? Do you think they will give us time before they start doing a detailed examination?

May 13th Recording Recap

 

  • What are the expectations for Receiving Depository Financial Institutions for Fraud Monitoring?

  •  Provide tips for Originators to comply with the Nacha Fraud Monitoring Rules.

  •  What is the retention timeframe for fraud monitoring documentation.

  •  What are the consequences of not conducting Fraud Monitoring?  

June 2 Registration

YOU MAY NEED TO KNOW

Frequently Asked Questions

Does Every ODFI Need ACH Fraud Monitoring in 2026?

Yes. ODFIs are central participants in the ACH network and are expected to maintain fraud monitoring processes designed to identify suspicious ACH origination activity. Under the 2026 Nacha changes, institutions involved in ACH origination should review controls, customer due diligence, transaction monitoring, and escalation workflows.

ODFIs are often viewed as the first line of defense because they introduce transactions into the ACH network.

Practical Focus Areas

  • New originators
  • Sudden ACH volume growth
  • Unusual payment timing
  • Elevated unauthorized returns
  • High-risk industries
Do Banks Need to Screen Every ACH Transaction in 2026?

No. Most institutions interpret the updated rules as requiring a risk-based fraud monitoring program, not manual review of every ACH transaction. Banks should implement reasonable processes to identify suspicious activity based on customer risk, behavior, and anomalies.

Better Approach

  • Risk scoring
  • Alert thresholds
  • Return code reviews
  • Originator segmentation
  • Historical behavior comparisons
What Is Risk-Based ACH Monitoring?

isk-based ACH monitoring means applying stronger oversight where fraud exposure is higher rather than treating all transactions equally. This allows institutions to focus resources on higher-risk activity while maintaining efficient operations.

High-Risk Examples

  • Newly onboarded businesses
  • Large first-time files
  • Unusual counterparties
  • Sharp volume spikes
  • High return rates

Why It Matters

Risk-based monitoring is often more practical and defensible than blanket manual review.

Do RDFIs Need ACH Fraud Monitoring in 2026?

Yes. RDFIs should evaluate inbound ACH credit activity for suspicious behavior and fraud indicators. Updated expectations expand focus beyond origination risk alone.

RDFI Monitoring Examples

  • New account incoming credits
  • Mule account behavior
  • Immediate cash-out patterns
  • Elder exploitation indicators
  • Unusual inbound transaction spikes
What ACH Return Codes Should Banks Monitor?

Banks commonly monitor return codes tied to unauthorized or problematic activity.

Common Examples

  • R05 Unauthorized debit to consumer account
  • R07 Authorization revoked
  • R10 Unauthorized / customer advises not authorized
  • R11 Error in authorization terms
  • Administrative return trends

Return activity can reveal fraud, onboarding weaknesses, or customer dissatisfaction.

How Should Banks Risk Rate ACH Originators?

Banks often risk rate ACH originators based on operational, financial, and behavioral factors.

Typical Inputs

  • Business type
  • Monthly volume
  • Average file size
  • Return history
  • Years in business
  • Prior fraud issues
  • Ownership transparency

Example

A stable local payroll company may rate lower than a new online merchant with fast-growing debit activity.

How Do Banks Detect ACH Fraud?

Banks typically detect ACH fraud through layered controls that combine data, behavior, and exception monitoring.

Common Methods

  • Velocity alerts
  • New counterparty detection
  • Dollar anomaly detection
  • Return code trends
  • Originator profile deviations
  • Manual investigations

No single control is sufficient. Strong programs usually combine several methods.

What Is False Pretense ACH Fraud?

False pretense ACH fraud generally involves transactions authorized because the customer was deceived. The customer may technically authorize payment, but the authorization was obtained through fraud.

Examples

  • Impersonation scams
  • Vendor payment diversion
  • Romance scams
  • Business email compromise
  • Urgent fake invoice requests

This category has received increased attention in fraud monitoring discussions.

How Should Banks Monitor Incoming ACH Credits?

Banks should review inbound ACH credits for behavior inconsistent with customer history or known risk patterns.

Common Monitoring Triggers

  • New account receives large credits
  • Multiple credits followed by withdrawals
  • Sudden activity after dormancy
  • High-risk counterparties
  • Elder customer unusual activity

Why It Matters

Inbound funds can be part of mule activity, scams, or first-party fraud schemes.

Do you have a checklist template available for FI's to use to have their originator customers sign? If not, please give us some things to consider putting in the document.

SFE has a Sample Originator’s Checklist available in our online store. Please visit SFE's Sample Originators Responsibilities Checklist. This is a document that can be tailored based on your originator portfolio. The document is complimentary to SFE members and only $15.00 for others.

At the time of the new account opening, should we consider developing a questionnaire for the new account rep to get the customer to complete to provide the bank information regarding their ACH activity?

This may be overkill but could be helpful. Not many people really understand the payment rails and exactly what ACH is.

If we monitor ACH manually, what documentation will we be expected to provide to the examiners during an examination?

We recommend financial institutions document basic procedures for monitoring fraud risks, focusing on simple reviews tailored to fraud trends, with a low compliance bar: complete periodic checks and update as needed.

Key Monitoring Requirements

What to review: Specify report names (e.g., ACH reports) and frequency (e.g., each ACH window or daily morning)

Who monitors: Identify the department or individuals responsible.

Sign-off process: Detail how reviewers initial or sign reports to confirm completion

Fraud trend adaptation: Adjust monitoring based on past institution fraud or common industry patterns; evaluate if it's sufficient to detect these.

Documentation Needs

Include write-ups for report items: Note if fraud was found, actions taken (e.g., for confirmed cases), and who reviewed (beyond just the signer)

Expect low detail overall: periodic reviews and changes suffice for compliance; deeper info may appear in early risk assessments tied to the FI's risk tolerance, not audits.

General Best Practices from Compliance Guides

Start with risk assessment to prioritize high-impact areas, then define policies, controls, and key performance indicators.

Use techniques like regular audits, automated tools, and self-assessments.

Document everything: test dates, results, testers, and fixes; conduct ongoing entity-level checks by operations staff.

Train staff, report to management, and improve based on findings.

How detailed do you think ACH examinations will be after the June deadline date? Do you think they will give us time before they start doing a detailed examination?

Since the rules don’t say what needs to be done, we would recommend providing auditors with documentation that you are doing something. SFE’s ACH audit team shared they will ask what is being done and documentation. We are seeing Fis already updating ACH policies to indicate they are monitoring and including that an annual review will be performed and update(s) will be completed if needed.

How detailed do you think ACH examinations will be after the June deadline date? Do you think they will give us time before they start doing a detailed examination?

Since the rules don’t say what needs to be done, we would recommend providing auditors with documentation that you are doing something. SFE’s ACH audit team shared they will ask what is being done and documentation. We are seeing Fis already updating ACH policies to indicate they are monitoring and including that an annual review will be performed and update(s) will be completed if needed.

Based on familiarity with FDIC examiners:

We do not think the examiners will weigh in on any compliance components outside of reviewing the ACH audit to ensure it is being performed.

They typically identify monitoring programs they like and share that information with any FI’s they feel are deficient. The difficulty with most FDIC examiners is they don't typically tell you what you MUST do, just share what they see in the industry and let you guess what's needed.

What are the expectations for Receiving Depository Financial Institutions for Fraud Monitoring??

Fraud monitoring includes more than OFAC Screening, KYC, and Anti-Money Laundering (AML). If you are performing these and utilizing technology software to identify suspect transactions, this is great – you are on the right path. This can be your foundation for fraud detection activity and will continue to be important. For RDFIs you are expected to monitor for ACH Credits.

Fraud monitoring should consist of reviewing out of norm or anomaly behavior. What is unusual activity to what you are normally seeing in the receipt of ACH entries. Suspect entries may be identified on characteristics of the Entry and the receiving account such as:

  • SEC Code does not align with the type of receiving account (CCD entry to a consumer account)
  • A high-dollar transaction that is atypical for the receiving account
  • Series of similar credit Entries received within a short period of time (multiple payroll or benefit payments)
  • Utilize the “PAYROLL” and “PURCHASE” standard Company/Entry Description Field

Any of the above to a:

New Account / Dormant Account / Account acting as a mule

Additional Guidance:

  • Behavioral Tolerances and Pattern Recognition
  • Name Matching (not a new rule)
  • Dollar Tolerances

To investigate the appropriateness of the entry, an RDFI may delay funds availability

Nacha rules provide an exemption to funds availability requirements when the RDFI reasonably suspects fraud.

 

Communication is key to investigating suspected entries

  • Internally with relationship managers
  • Between RDFI and Receiver
  • Between RDFI and ODFI
  • Nacha’s Risk Management Portal and ACH Contact Registry for ODFI contact info to help in its determination

RDFI’s options to return entries:

  • R06 - Per ODFI Request, when permission for the return has been granted
  • R17 – QUESTIONABLE (Must be returned within two Banking Days)
Provide tips for Originators to comply with the Nacha Fraud Monitoring Rules.

Nacha and its Risk Management Advisory Group (RMAG) have previously published best practices and asked Originators to help protect themselves and their customers from fraudsters, but this is the first time Originators are required to implement fraud monitoring and detection under the Rules. The controls, processes, and procedures used should be risk based and scaled for the size and operational complexities of the organization. Originator controls can be developed internally, provided by an Originator’s financial institution, or created by third-party solution providers. Many of these controls can be used in concert to provide layered security.

 

Dual Controls – Dual control requires more than one individual to initiate a payment. One individual may authorize the creation of an ACH entry with another confirming the entry and releasing it to the financial institution. A fraudster may be able to get past one individual, but will have difficulty tricking two. Dual control is often offered by financial institutions to their corporate customers, and it may even be required.

Account Validation – Account validation tools are used to assess new accounts and changes on existing accounts. These tools can be used to confirm that, at a minimum, an account with that account number is open at the RDFI. Other account ownership verification tools may go beyond simple account validation and into Know Your Customer (KYC) identification. These tools provide much richer data about the account owner, including details such as the name, address, balance of the account, and even the IP address associated with the location of the account owner. These services are regularly offered by third parties.

Multi-factor Authentication - – Multi-factor authentication is considered more robust than password-only authentication. A second factor in addition to the password can be a second credential, operator intervention, or a biometric input. A fraudster can use social engineering to steal a username and password but cannot obtain the second factor required to access the system. A physical token or biometric solution is preferred to a solution using a code via text or email because fraudsters have developed tools to intercept the content of these channels.

Out-of-Band Authentication – Authenticate payment requests or changes to payment instructions by independently verifying the request/change using a method other than the method used by the original request. For example, if a vendor calls to request a change to their routing and account information for future payments, use contact information contained within your organization’s internal database to contact the vendor via phone or email.

Routine and Red Flag Reporting – Review and reconcile accounts daily. Generate regular reports that identify transactions to new relationships, transactions of existing customers to new accounts, or abnormal activity. Verify that these transactions were intentional.

Review User Rights – Review user rights to online banking systems regularly and promptly remove access for terminated or transferred employees who no longer require access.

 

Secure Systems and Applications – Ensure maintenance of firewalls and make sure antivirus software is up to date. Ensure all system components and software have the latest vendor-supplied security patches installed.

Credit-push fraud schemes rely on social engineering to trick victims into sending the fraudster money. Social engineering fraud isn’t complex; controls can be simple, but they must be utilized to be effective. Financial institutions should encourage their Originators to utilize services offered by their organization and to seek other tools to ensure payments are originated only by their employes for verified and authorized purposes.  

What is the retention timeframe for fraud monitoring documentation?

Six years is the retention timeframe for ACH entries originated and received. We would suggest that as a best practice for the fraud monitoring documentation. Some systems only retain it for 13 months, so we would suggest retaining the documentation for bank examiners to review. Some examiners are on an 18 month basis so 2 years may be sufficient.

What are the consequences of not conducting Fraud Monitoring?

Nacha enforces its operating rules through a structured system of fines, warnings, and escalated penalties designed to correct violations and protect the integrity of the ACH Network. Nacha rule noncompliance can lead to escalating fines (from hundreds to up to $500,000 per month for repeated or unresolved violations), suspension from originating ACH entries, operational disruption, and reputational damage with financial partners and customers.