Nacha, the organization that governs the ACH network, has announced updates to its operating rules that affect businesses and organizations that originate ACH payments. These changes are designed to strengthen fraud prevention and improve clarity across ACH transactions network‑wide.
This page provides additional details, examples, and guidance to help you understand how the new rules may apply to your ACH activity.
What's Changing
Standardized Company Entry Descriptions
Beginning March 20, 2026, certain ACH transactions will require standardized wording in the Company Entry Description field. This allows participants to better identify the purpose of the transactions, which can help support fraud transaction monitoring. Standardized use of data can help parties manage risk and improve ACH quality.
Payroll Payments
Originators and Third Parties sending payroll payments via ACH Credits must use the word PAYROLL in the Company Entry Description in the Batch Header Record of a Nacha file.
- This includes payment of wages, salaries and similar types of compensation.
Online Consumer Purchases
Originators and Third Parties sending ACH Debits for consumer e-commerce purchases must use the word PURCHASE in Company Entry Description field of the Nacha file.
- For this purpose, an e-commerce purchase is a debit Entry authorized by a consumer Receiver for the online purchase of goods, including recurring purchases first authorized online. An e-commerce purchase uses the WEB debit SEC Code, except as permitted by the rule on Standing Authorization to use the PPD or TEL debit SEC Code.
Questions about standardized ACH descriptions?
Find answers to common questions about when and how the required PAYROLL and PURCHASE descriptions should be used, with examples and screenshots.
Scroll Down to FAQs
ACH Fraud Detection Requirement
Nacha has also introduced a new ACH fraud detection requirement for organizations involved in ACH origination. The rule requires affected parties to establish and maintain risk‑based processes and procedures designed to help identify potentially unauthorized ACH transactions or transactions authorized under false pretenses.
Effective Date
- Phase 1: March 20, 2026 - For Originators who processed more than 6 million items in 2023
- Phase 2: June 22, 2026 - For all other Originators
Rule Language
Each Non-Consumer Originator; each Third-Party Sender; each ODFI; and each Third-Party Service Provider that performs any functions of ACH processing on behalf of an Originator, Third-Party Sender, or ODFI must:
- establish and implement risk-based processes and procedures relevant to the role it plays in the authorization or Transmission of Entries that are reasonably intended to identify Entries that are suspected of being unauthorized or authorized under False Pretenses;
- and at least annually review these processes and procedures and make appropriate updates to address evolving risks.
These processes and procedures do not require the screening of every ACH Entry individually and do not need to be performed prior to the processing of Entries.
What Does This Mean?
- This rule applies to all ACH originators.
- Organizations should implement risk‑based processes and procedures designed to help protect against account takeover and other methods used to initiate unauthorized ACH transactions.
- These processes may include controls related to changes in payment information for vendors or payroll, such as avoiding reliance on email alone to update account details.
- Processes and procedures should be reviewed at least annually and updated as risks evolve.
- Screening every individual ACH transaction is not required.
- Screening may occur before or after ACH transactions are submitted.
Conduct an ACH Fraud Risk Assessment
The decision on what to do to comply with the new rules should come from identifying the risks, gaps, and weaknesses resulting from your risk assessment. Use the results of your risk assessment to drive "risk-based processes and procedures".
Examples of questions you may want to ask:
- What are the existing or potential/emerging fraud threats that your organization/industry faces?
- What has been your organization's or industry's fraud experience?
- Define scenarios that you consider to be high-risk. (Hint: Risk is elevated whenever there is change)
- Prioritize - which payment use cases represent the most risk?
- Assess your present state: What processes and procedures/tools do you currently use to mitigate payment fraud risk?
- What changes or improvements do you need to make?
FAQs