The purpose of the ACH Quick Reference Guide is to provide instruction to financial institution personnel involved in the day-to-day activities associated with receiving commercial ACH transactions. It is ideal for training personnel on ACH procedures and as a quick reference for ACH questions. The Guide contains an appendix with sample reports, Return and Notification of Change codes, and a glossary of ACH terminology.
This user-friendly guide is based on the 2022 Nacha Operating Rules (referred to as the ACH Rules), Regulation E and the Uniform Commercial Code Article 4A (UCC 4A) and supplements more extensive resource materials. It references various in- depth resource materials and is not intended as a substitute for referencing and complying with the rule requirements published in the ACH Rules. Procedures for handling federal government entries are not covered in this guide. Although many procedures may be similar, federal government entries are also subject to Title 31 Code of Federal Regulations Part 210 (31 CFR Part 210), which are outlined in the Green Book.
ACH Basics
What is the ACH Network?
The Automated Clearing House (ACH) Network is an electronic payments network used by individuals, businesses, financial institutions and government organizations. It allows funds to be electronically debited or credited to a checking account, savings account, financial institution general ledger account or credited to a loan account.
The ACH Network is the backbone for the electronic movement of money and other related data, providing a safe, secure, reliable network for direct consumer, business and government payments. Large and small financial institutions of all kinds jointly govern and utilize the ACH Network, facilitating billions of payments such as Direct Deposit via ACH and Direct Payment via ACH.
The ACH Network is a same day, batch processing, store-and- forward system. Transactions are stored by financial institutions throughout the day and processed at specified times in a batch mode.
The ACH Network exchanges funds and payment-related information throughout the United States, its territories and internationally.
Who are the ACH Participants?
There are five key participants that contribute to the successful completion of an ACH transaction. As each participant is discussed, the financial institution should better understand the role it plays in the system.
The Originator is the company/business that has been authorized by the Receiver to either credit or debit an account. When a company initiates a credit transaction to their employee’s account for payroll or to a business customer’s account for payment of goods and services, it is considered the Originator. Originators may also initiate debit transactions to a consumer or business account for payment of goods or services.
The Receiver can be either an individual or a company that has authorized the Originator (company) to credit or debit their account. The employee is the Receiver if his/her employer is initiating a Direct Deposit payroll credit. A business partner is the Receiver if the Originator is sending a credit to pay for goods or services. The Originator can also be a Receiver, in situations where another party is initiating credits or debits to their account.
The authorization is a key component of an ACH transaction, as it gives the Originator the authority to send credit or debit transactions to the Receiver’s account. The manner in which the authorization may be obtained varies based on the type of transaction and is discussed in greater detail in the Authorization section of this Guide.
The Originating Depository Financial Institution (ODFI) is the financial institution with which the Originator (company) has a contractual relationship for ACH services and is responsible for sending ACH entries into the ACH Network on behalf of the Originator. Through the warranties outlined in the ACH Rules, the ODFI has the greatest liability of all the participants in the ACH Network. The contractual relationship between the Originator and the ODFI outlines the rights and responsibilities of the two parties with respect to the ACH transactions being originated and provides the ODFI with a mechanism to pass some appropriate liabilities to the Originator (company).
An example of this relates to authorizations. The ODFI warrants to all the other Network participants that transactions are properly authorized; and yet, the Originator obtains and maintains this authorization. Hence, the agreement between the Originator and ODFI must address the Originator’s responsibilities regarding authorizations.
The ACH Operator is the central clearing facility for ACH transactions. The ACH Operator is responsible for accepting files of ACH entries from ODFIs, which are then sorted, batched and forwarded to the Receiver’s financial institution. The ACH Operator also performs some editing functions, ensuring that mandatory information required in ACH records is included. There are currently two ACH Operators, the Federal Reserve Bank and EPN (Electronic Payments Network).
The Receiving Depository Financial Institution (RDFI) is a financial institution with which the Receiver has an account relationship. Credit or debit entries sent to a Receiver’s account will be received by the RDFI from the ACH Operator and then posted to the Receiver’s account.
The RDFI’s primary responsibilities are to:
Post ACH entries to the Receiver’s account. Make funds available to the Receiver for credit entries or debit the Receiver’s account on the Settlement Date. Provide information regarding each ACH transaction to the Receiver on their statement. Return ACH entries, within the specified timeframes, when the transactions cannot be posted.
There are two other Network participants that may be involved in the flow of transactions, Third-Party Service Providers and Third-Party Senders.
A Third-Party Service Provider is a party which performs an ACH processing function on behalf of the Originator, ODFI or RDFI. A payroll processor is a common example of a Third-Party Service Provider used by Originators.
A Third-Party Sender (TPS) (Straddle) is an entity that has a contractual relationship with an ODFI to transmit debits or credits to the account of a Receiver on behalf of the Originator.
More specifically, a Third-Party Service Provider is a Third-Party Sender when there is a contractual relationship between the Originator and the Third-Party and there is NOT an agreement between the Originator and the ODFI.
Again, referencing the payroll processor example, if the Originator has an agreement with an ODFI for ACH origination and they use a payroll processor to create the ACH file on their behalf, the payroll processor is a Third-Party Service Provider. If the Originator has a contractual relationship with the payroll processor and the payroll processor sends the ACH file to the payroll processor’s financial institution for introduction into the ACH Network, the payroll processor is considered a Third-Party Sender.
How Does the ACH Network Function?
The Originator obtains authorization to initiate a transaction to the Receiver’s account or provides notice to the Receiver that a transaction will be initiated to the Receiver’s account.
The Originator initiates a file of ACH transactions and presents the file to its ODFI.
The ODFI collects ACH files from Originators with which it has contractual relationships, verifies the validity of these files and at specified times, transmits these files to the ACH Operator. The ODFI may consolidate these individual files as batches into a larger file that is then transmitted to the ACH Operator. The ODFI may retain entries within these files that are intended for account holders at its institution. These entries are known as on-us entries.
The ACH Operator receives ACH files from the ODFI, edits the files to make sure they are formatted properly and distributes files of entries to the RDFI.
The RDFI receives files of entries from the ACH Operator for its account holders. Entries are posted based upon the Settlement Date and account number. Periodic statements are provided to the Receiver with descriptive information about the ACH transaction, including the date of the transaction, dollar amount, Originator name and transaction description (e.g., payroll, water bill, internet purchase).
How are ACH Funds Settled?
Settlement is the actual transfer of funds between financial institutions to complete the payment instructions of an ACH entry. ACH settlement can only occur on banking days. The Federal Reserve Bank provides settlement services for ACH entries, for both the Federal Reserve ACH Operator and any private sector ACH Operator (currently only EPN). The Federal Reserve Bank calculates the net debit and credit positions of financial institutions and applies those debits or credits to the account of the financial institution or to the account of its correspondent financial institution.
The timing of settlement is based upon the Effective Entry Date indicated by the Originator on the ACH file and the time of its delivery to the ACH Operator. The Effective Entry Date is the date the Originator intends for the entries to post to the accounts of the Receivers (employees or customers).
When the ACH Operator processes an ACH file, the Effective Entry Date is read and a Settlement Date is assigned. Entries are settled by the ACH Operator on the Settlement Date.
In most cases, the Settlement Date is the same as the Effective Entry Date, but it is possible that the Settlement Date could be after the Effective Entry Date. For example, if the ACH Operator cannot settle on the Effective Entry Date due to untimely file delivery, a stale date, weekend or holiday, the ACH Operator will apply the next possible Settlement Date.
Since its inception, the ACH Network’s standard settlement period has been one to two business days after processing (i.e., debit entries are allowed to be sent one day in advance of the Effective Entry Date and credits up to two days in advance). While this processing environment will continue to be available, Originators now have same day processing and settlement of eligible ACH credit and debit payments.
ACH Network Management
Operations and compliance are two key aspects in the management of the ACH Network. ACH Operators facilitate the operations for transaction processing, while compliance is the primary focus of financial institutions, Payments Associations (PAs) and Nacha.
Nacha is a not-for-profit association that represents financial institutions through direct memberships and a network of PAs. Nacha develops operating rules and business practices for the ACH Network and for electronic payments in the areas of Internet commerce, electronic bill and invoice presentment and payment (EBPP, EIPP), electronic check conversions (e-checks), financial electronic data interchange (FEDI), international payments and electronic benefits services (EBS).
PAs provide access to the ACH Rules and guidelines for the efficient operation of the ACH Network as well as provide education to their members. PA members include financial institutions, companies and other interested parties. With the contributions of their members, PAs help create the ACH Rules.
ACH Rules and Regulations
There are many rules and regulations governing the transmission of ACH entries. Details on the rules and regulations having the most impact on the financial institution follow:
Office of Foreign Asset Control (OFAC) Regulation E and Electronic Fund Transfer Act (EFTA) Title 31 Code of Federal Regulation Part 210 (31 CFR Part 210) Uniform Commercial Code Article 4A (UCC 4A) ACH Rules
The ACH Rules serve as the primary source for rules and regulations for the Commercial ACH Network and are contract law that is made binding by agreements. Commercial ACH entries are originated by the private sector, which includes individuals, companies and state and local governments.
The ACH Rules define the obligations and liabilities of each financial institution, including a provision to perform an annual audit, and provide a mechanism for a receiving institution to return an entry to the sending institution. The ACH Rules help reduce risk in the Network and protect financial institutions from potential loss.
Office of Foreign Assets Control (OFAC)
The U.S. Department of the Treasury, Office of Foreign Assets Control, administers economic sanctions and embargo programs that require assets and transactions involving interests of targeted countries, targeted country nationals and other specifically identified companies and individuals to be frozen. OFAC maintains a list of Specially Designated Nationals and Blocked Persons (SDN List) to assist financial institutions in identifying blocked parties.
All U.S. participants in the ACH Network need to be aware that they may be held accountable for sanction violations and must understand their compliance obligations. As an RDFI, the financial institution should have a process in place to determine whether any of its account holders are identified as a blocked party on a current SDN List. Financial institutions are strongly encouraged to obtain a current SDN List and other compliance information directly from OFAC.
Regulation E and Electronic Fund Transfer Act (EFTA)
Regulation E carries out the purpose of the EFTA, which establishes the basic rights, liabilities and responsibilities of consumers who use electronic fund transfer services. The primary objective of this act and regulation is the protection of individual consumers engaging in electronic fund transfer services. Regulation E also addresses the responsibilities of financial institutions regarding disclosures, stop payments and unauthorized debit transactions to consumer accounts and defines the process for resolving errors.
State Law
Some state laws may impact ACH transactions if the law is more restrictive or provides greater consumer protection than other prevailing rules or regulations. For instance, some states allow companies to mandate employees to be paid by Direct Deposit; however, most state labor codes restrict companies from offering only Direct Deposit. Many states have mandated state taxes paid by businesses and corporations be initiated through the ACH. The states’ Attorneys General Offices can provide specifics.
Title 31 Code of Federal Regulation Part 210 (31 CFR Part 210)
31 CFR Part 210 provides the regulatory foundation for the use of the ACH Network for federal government agencies. It defines the rights and liabilities of agencies, Federal Reserve Banks, financial institutions and the public in connection with ACH entries. The Green Book is the procedures manual for financial institutions processing federal government payments. Among the procedures covered by the Green Book are the handling of federal government reclamations and enrollment in federal government benefit payment programs. By accepting a federal government benefit payment, a financial institution agrees to be bound to 31 CFR Part 210, and therefore, must adhere to these procedures.
Uniform Commercial Code Article 4A (UCC 4A)
Uniform Commercial Code (UCC) is a series of state laws that govern commercial transactions. Article 4A of the UCC governs corporate ACH transactions that are referred to as “corporate wholesale credit entries.” RDFIs may identify these transactions by Standard Entry Class Codes CCD or CTX. UCC 4A also addresses the ‘commercially reasonable security procedures’ that must be in place for ACH Origination to occur.
USA PATRIOT Act
Uniting and Strengthening America by Providing Appropriate Tools Required to Intercept and Obstruct Terrorism Act of 2001 establishes a wide variety of ways to combat international terrorism. Title III—International Money Laundering Abatement and Anti-Terrorist Financing, which contains provisions relating to money laundering and terrorist access to the financial system in our country is the section of the Act that affects financial institutions with regard to information sharing and customer identification programs (CIPs).
CIPs require financial institutions to complete the following prior to opening a new account:
Verify the identity of any person seeking to open an account. Maintain records of the information used to verify identity. Consult government known or suspected terrorist lists to determine whether the customer appears on any such list.
RULE OF THUMB: When conflicts are found among these various rules and regulations, the most restrictive rule or regulation applies. In other words, the one that benefits or provides the most protection to the consumer would be applied. Over the years, consumer and corporate customers have become more and more aware of the advantages of the electronic payments network. As a result, customers are more demanding and financially savvy. The ACH Network provides the ability to directly deposit employee payroll, permits automated bill payment services, allows for purchases online and can be used by companies to perform cash concentration and make corporate-to-corporate payments.
As migration from paper to electronic payment continues, the cost-effective ACH Network will grow and enable innovation that strengthens the industry with creative payment solutions.
ACH Transactions
Types of ACH Transactions
In general, there are two types of ACH transactions sent through the ACH Network:
Commercial—Entries originated by the private sector, including state and local government entities. Government—Entries originated by federal government agencies (i.e., Social Security Administration, Veteran’s Affairs, Civil Service, etc.). Commercial ACH entries can further be classified as follows:
Direct Deposit via ACH—Credit entries deposited into a consumer’s account. Direct Deposit includes payments such as payroll, travel reimbursements, government benefits, tax and other refunds, and annuities and interest payments. The deposits arrive and are made available more quickly than paper checks, and can be automatically divided among different accounts based on the Receiver’s direction. The various ACH applications are discussed in greater detail throughout this Guide. For a complete listing of ACH transaction types and their uses, see the Operating Guidelines of the ACH Rules. Direct Payment via ACH—Credit or debit entries sent or received by individuals or organizations for making a payment. Basically, any ACH payment that is not a Direct Deposit is known as Direct Payment. Direct Payment includes recurring and single-entry payments such as prearranged ACH payments, Internet-initiated ACH transactions and check conversion into the ACH Network. Direct Payment saves time by eliminating check writing, and since payments are automated, the potential for missing or forgetting payments is reduced. Increasingly, companies are realizing the benefits of Direct Payment for business-to-business payments. These payments reduce check preparation and distribution expenses, eliminate postage costs, improve cash flow and cash forecasting, can improve payment discounts and simplify account reconciliation. Additionally, payments can accommodate payment-related information in addenda records in standard electronic data interchange (EDI) formats or in Nacha-endorsed banking conventions.
The ACH Network can also be used by consumers and businesses to exchange funds and payment-related information internationally. In the international payment environment, a new participant, the Gateway, acts as the contact point for a financial institution. The Gateway assumes responsibility for foreign exchange conversion and settlement, format mapping and translation of data.
Transaction Codes
The ACH Network supports a number of different credit and debit applications. A Transaction Code identifies an entry as a debit or credit, and indicates the type of account to which the transaction is intended, i.e. checking, savings, financial institution general ledger or loan account. Only credit entries can be transmitted to loan accounts. Commonly used Transaction Codes are listed:
Demand Credit Records
21 Automated Return or NOC for a Demand Credit 22 Demand Credit 23 Prenote for a Demand Credit 24 Zero Dollar Entries w/Remittance Data (for CCD and CTX Entries Only)
Demand Debit Records
26 Automated Return or NOC for a Demand Debit 27 Demand Debit 28 Prenote for Demand Debit 29 Zero Dollar Entries w/Remittance Data (for CCD and CTX Entries Only)
Savings Account Credit Records
31 Automated Return or NOC for a Savings Credit 32 Savings Credit 33 Prenote for a Savings Credit 34 Zero Dollar Entries w/Remittance Data (for CCD and CTX Entries Only)
Savings Account Debit Records
36 Automated Return or NOC for a Savings Debit 37 Savings Debit 38 Prenote for a Savings Debit 39 Zero Dollar Entries w/Remittance Data (for CCD and CTX Entries Only)
Standard Entry Class (SEC) Codes
Each application has a unique Standard Entry Class (SEC) code which identifies:
The nature of the transaction as consumer or corporate/business, as well as whether the transaction is single-entry or recurring. The ACH Rules and other regulations governing the transaction, including the method for obtaining authorization or providing notice. The specific record format that is used to carry the payment and payment-related information relevant to the entry. It is important to know the SEC code of the ACH entry as it will define posting and return procedures. This is of utmost importance to the financial institution as proper handling of entries will mitigate any potential losses associated with human error. Commonly used SEC codes are listed below with their use.
Authorization
Originators must obtain authorization from or provide notification to a Receiver prior to initiating ACH transactions. Authorization requirements differ among the types of ACH transactions, also known as SEC codes. The Originator must keep copies of authorizations for two years from the termination or revocation of the authorization. For example, the Originator of a single-entry TEL must keep the original or copy of the oral authorization for two years from the date of the authorization. The table below identifies the authorization requirements of the more commonly initiated SEC codes.
Authorizations must be readily identifiable as an ACH credit or debit authorization and must contain terms that are clear and readily understandable. For recurring payments only, revocation language must also be included.
Authorizations may limit an Originator to debit or credit entries and may specify a fixed or variable amount. ACH authorizations should include language requiring consumers to acknowledge that ACH entries must comply with provisions of the laws of the United States.
AUTHORIZATION REQUIREMENT
*Revised Regulation E (2001) and the Electronic Signatures in Global and National Commerce Act (E-Sign Act) qualify electronic signatures as valid for consumer debit authorizations. This refers to authentication of the authorizing party by digital signature such as a unique PIN number.
Rules Compliance
Risk Management and Assessment
Risk management is every financial institution’s responsibility. There are three key types of risk affecting ACH payment processing that you should be aware of:
Credit Risk—the risk that a party to a transaction cannot provide funds for settlement Operational Risk—the risk of loss due to unintentional error Fraud Risk—the risk that a transaction may be initiated or altered in an intentional effort to misdirect or misappropriate funds
The ACH Rules require all financial institutions to perform a risk assessment of their ACH activities and to implement risk management programs based on the assessment, in accordance with the requirements of their regulator(s).
ACH Credit Risk
While credit risk is generally associated with ACH origination activities, RDFIs are also exposed to credit risk when they:
Post a credit entry prior to the Settlement Date, or Do not return a debit entry in a timely manner. Controlling Credit Risk
Credit risk is generally controlled by developing and implementing processing procedures, understanding compliance obligations and ensuring ACH operations staff are properly trained.
ACH Operational Risk
Operational risk represents the amount of loss related to unintentional errors, which may occur due to a hardware/software failure or clerical errors, such as untimely returns or the incorrect use of return reason codes. Any disruption in ACH processing can jeopardize the accurate and timely processing of ACH entries.
Controlling ACH Operational Risk
The evaluation of ACH operational risk and the determination of procedures to control those risks should include participation of auditors and outside professionals to ensure objectivity. Operational risk may be managed through automated security methods, as well as controlled operational procedures, which include cross-training of staff, dual controls and a contingency plan.
ACH Fraud Risk
Fraud risk represents risk that a transaction may be initiated or altered in an intentional effort to misdirect or misappropriate funds. Risks related to fraud are affected by internal as well as external factors. Fraudulent activities may be the work of dishonest employees, third-party processing personnel, originating company personnel or other outside parties.
Controlling ACH Fraud Risk
While controls related to ACH operational and credit risk may also be effective in diverting fraud, additional areas may include specific personnel practices and security.
Personnel Practices
The following are suggestions regarding practices and procedures that contribute to fraud risk management:
Limit use of temporary employees Screen potential full-time employees Change or rotate work assignments Mandate physical security (i.e., individual passwords, physical locks, etc.)
Security Practices
It is up to the financial institution to ensure that its ACH operations are secure. Sensitive operation sites, such as the area that houses the computer and communications equipment, should be kept secure. All portable data, such as CDs, USBs, reports and physical file folders, should be kept in secure areas, as well as protected from hazards such as flood or fire. Computer terminals should automatically logoff after a set period of time.
ACH processing software should be safeguarded with controls in place to ensure that only authorized changes can be undertaken. Communications software should provide security features, such as encryption or authentication to secure data during the process of transmission. In general, ACH processing security should conform to the organization’s data processing security policy.
ACH Audit