Study guide
3.3 RDFI Warranties, Receipt Obligations & Statement Requirements
Nacha Accredited ACH Professional AAP
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: ACH Network Overview, Participants & Transaction Flow
1.1 ACH Network Structure, Governance & History 1.2 Five Key ACH Participants: Originator, ODFI, Operator, RDFI, Receiver 1.3 Third-Party Senders (TPS) and Third-Party Service Providers (TPSP) 1.4 End-to-End Transaction Flow, Clearing & Settlement Mechanics
2 Chapter 2: ACH File Architecture & Record Formatting
2.1 File Hierarchy: 94-Character Records, Blocking Factors & File Header (Type 1) 2.2 Company/Batch Header Record (Type 5) & Service Class Codes 2.3 Entry Detail Record (Type 6) & Addenda Records (Type 7) 2.4 Batch Control (Type 8), File Control (Type 9) & Entry Hash Calculations 2.5 Exception Record Formats: Return (Addenda 99) & Notification of Change (Addenda 98) Layouts
3 Chapter 3: Nacha Operating Rules Framework & Participant Warranties
3.1 Structure of Nacha Operating Rules, Rulemaking Process & Effective Dates 3.2 ODFI Warranties, Indemnifications & Participant Obligations 3.3 RDFI Warranties, Receipt Obligations & Statement Requirements 3.4 Nacha Return Rate Thresholds & Monitoring Requirements
4 Chapter 4: Standard Entry Class (SEC) Codes: Consumer Applications
4.1 PPD (Prearranged Payment and Deposit): Direct Deposit & Consumer Debits 4.2 WEB (Internet-Initiated Entries): Authorization, Authentication & Validation 4.3 TEL (Telephone-Initiated Entries): Inbound vs. Outbound Rules & Recording Requirements 4.4 CIE, MTE, POS & SHR: Machine and Point-of-Sale Consumer Entries 4.5 Same Day ACH: Windows, Limits ($1,000,000) & Eligibility Rules
5 Chapter 5: SEC Codes: Commercial, Check Conversion & Specialized Applications
5.1 CCD/CCD+ and CTX: Corporate Payments, Addenda & EDI / ASC X12 Formatting 5.2 Check Conversion SEC Codes: ARC, BOC & POP Rules and Notices 5.3 RCK (Re-presented Checks) & XCK (Destroyed Check Entries) 5.4 IAT (International ACH Transactions): Mandatory Addenda & OFAC Screening 5.5 Non-Monetary & Specialty Entries: Prenotifications, DNE & ENR
6 Chapter 6: Authorization Standards, Authentication & Record Retention
6.1 Fundamentals of Valid Authorization: Consumer vs. Commercial 6.2 E-SIGN Act Compliance, Electronic Signatures & Oral Authorizations 6.3 WEB Debit Account Validation Rule & Fraud Detection Systems 6.4 Authorization Retention (2 Years) & Copy Provision Rules
7 Chapter 7: Exception Processing: Returns & Return Reason Codes
7.1 Return Processing Overview: Two-Banking-Day Rule vs. Extended Return Rule 7.2 Administrative & Operational R-Codes (R01-R04, R08, R16, R17) 7.3 Unauthorized Consumer Returns: R05, R07, R10, R11 & The WSUD 7.4 Unauthorized Corporate Debits: R29, Contract Rights & the UCC Article 4A Boundary 7.5 Dishonored Returns (R61-R70) & Contested Dishonored Returns (R71-R76)
8 Chapter 8: Exception Processing: Notifications of Change (NOC) & Reversals
8.1 Notification of Change (NOC / COR): Structure & Change Codes (C01-C07) 8.2 NOC Timelines: RDFI Origination & Originator 6-Day Mandatory Action 8.3 Reversing Entries & Reversal Files: 5-Day Deadline & Erroneous Reasons 8.4 Federal Reclamation Procedures & Deceased Beneficiary Handling
9 Chapter 9: ACH Risk Management, Fraud Monitoring & Exposure Controls
9.1 ACH Risk Taxonomy: Credit, Operational, Fraud, Systemic & Compliance Risks 9.2 ODFI Originator Onboarding, Underwriting & Exposure Limits 9.3 Third-Party Sender (TPS) Due Diligence, Monitoring & Registration 9.4 Fraud Schemes: Business Email Compromise (BEC), Account Takeover & Controls 9.5 The 2026 Fraud Monitoring Rules: ODFIs, Originators, TPSPs & Third-Party Senders 9.6 RDFI ACH Credit Monitoring & the False Pretenses Definition 9.7 ACH Data Security: Article One, Sections 1.6 and 1.7 & the ACH Security Framework 9.8 Nacha's Risk Management Portal: Contact Registry, TPS & Direct Access Registration, Terminated Originator Database 9.9 ACH Risk Assessments, Regulatory Expectations & Operational Resilience
10 Chapter 10: Legal & Regulatory Framework for ACH
10.1 Regulation E (12 CFR 1005): Consumer Protections, Disclosures & Error Resolution 10.2 Uniform Commercial Code (UCC) Article 4A: Wholesale Funds Transfers & Security Procedures 10.3 BSA/AML, SAR/CTR Reporting & OFAC Sanctions Compliance in ACH 10.4 31 CFR Part 210 (The Green Book), Reg CC, Reg D & Reg J Interactions
11 Chapter 11: Nacha Rules Compliance Audit & National System of Fines
11.1 Annual ACH Rules Compliance Audit (Article One, §1.2.2): Scope & Requirements 11.2 Auditor Independence & 6-Year Audit Record Retention 11.3 National System of Fines: Complaint Process, Panel Review & Fine Classes 11.4 The Nacha Rules Effective-Date Calendar: 2026 Through 2028
12 Chapter 12: Alternative & Complementary Payment Systems
12.1 Fedwire Funds Service & CHIPS vs. ACH Network 12.2 Instant Payments: RTP and FedNow vs. Same Day ACH 12.3 Card Networks, Check 21 & Interoperability Across Payment Rails
3.3 RDFI Warranties, Receipt Obligations & Statement Requirements
Key Takeaways Explain This Topic AI
An RDFI must receive and process ACH entries under the Rules; receipt obligations do not eliminate permitted returns, stop-payment duties or applicable sanctions requirements.
For a covered commercial payment order, UCC 4A-207 permits account-number reliance when the beneficiary bank does not know the name and number identify different people; actual knowledge changes the analysis.
From September 18, 2026, non-Same Day ACH credits generally require availability by 9:00 a.m. RDFI local time on the Settlement Date. The old 5:00 p.m. receipt condition is gone; a separate territorial time-zone exception applies.
RDFIs are strictly prohibited from debiting a Receiver's account prior to the Settlement Date, even if the ACH file arrives days in advance of settlement.
When initiating exception items, the RDFI makes strict warranties that Returns are timely and contain accurate R-codes (backed by a valid WSUD for extended returns) and that Notifications of Change (NOCs) contain accurate corrected account data.
Last updated: October 2026
3.3 RDFI Warranties, Receipt Obligations & Statement Requirements
Operational distinction: receiving a file, posting an entry, making credit funds available, and returning an entry are separate actions. Identify the entry type and Settlement Date before selecting a deadline.
1. Receipt and Posting
RDFIs receive ACH entries addressed to their routing numbers and process them under the Nacha Rules. This obligation does not require posting an entry that must or may be returned under an applicable rule, override a valid stop-payment instruction, or displace sanctions obligations. Retrieve Operator files in time to meet the relevant processing and availability deadlines.
For PPD/CCD Entry Detail records, the DFI Account Number is field 5, positions 13–29 ; the Receiving Individual/Company Name is field 8, positions 55–76 . Do not confuse these with the Amount, which is field 6, positions 30–39 . Field numbers are specific to a record layout, not universal labels across all ACH records.
For commercial payment orders governed by UCC 4A-207 , a beneficiary bank that does not know that the name and account number identify different people may rely on the number. A bank with actual knowledge cannot assume that the same protection applies. Article 4A is not a substitute for the EFTA/Regulation E rules governing covered consumer transfers; federal payment and sanctions requirements also need separate consideration.
Example: a covered commercial credit names Alice but gives an account number belonging to John. The account number can control when the beneficiary bank lacks the knowledge specified in 4A-207. This is not a blanket instruction to ignore a mismatch the bank actually knows about.
- 2. Credit Availability: Apply the Current Rule
- Non-Same Day Credits from September 18, 2026
The general deadline is 9:00 a.m. RDFI local time on the Settlement Date . This applies to non-Same Day credits across SEC codes, including PPD payroll and corporate credits. Receipt by 5:00 p.m. on the preceding banking day is no longer a condition. Credits in the 6:00 a.m. ET Operator file are included.
A separate exception accommodates RDFIs east of the Atlantic Time Zone and west of the International Date Line . For a non-Same Day credit made available after 8:00 a.m. local time on the Settlement Date, availability is due by the end of that date; if delivery occurs after the RDFI has completed processing, the deadline is 9:00 a.m. local time on the next Banking Day. Do not apply that exception to an ordinary New York receiving bank.
Same Day Credit Windows
Operator cutoffs and interbank settlement times below are Eastern Time . The first two customer-availability deadlines are RDFI local time . The third is an operational milestone, not a fixed local clock time.
- Window ODFI submission deadline Operator settlement Credit availability
- First 10:30 a.m. ET 1:00 p.m. ET 1:30 p.m. RDFI local time
- Second 2:45 p.m. ET 5:00 p.m. ET 5:00 p.m. RDFI local time
- Third 4:45 p.m. ET 6:00 p.m. ET End of the RDFI’s processing day on the Settlement Date
Thus, 6:00 p.m. ET settlement is not a universal 6:00 p.m. local availability deadline . Nor may an RDFI postpone a first-window credit to the end of its processing day merely because that is the third-window rule.
Debit Posting
Do not debit the Receiver’s account before the Settlement Date. Receiving a file in advance does not authorize early debit posting. The ACH Operator inserts the Settlement Date in the batch header; it is distinct from the Originator’s requested Effective Entry Date.
3. Consumer Statements and File Data
Regulation E §1005.9(b) requires applicable transaction information on periodic statements, including amount, posting date, transfer/account type, relevant terminal location and third-party identity. It also requires account-level information such as balances, fees and inquiry contact details. A consumer’s statement is not simply a copy of the raw ACH file.
- Data used in statement preparation ACH source or context
- Amount PPD/CCD Type 6, field 6
- Originator identity Type 5, field 3: Company Name
- Purpose of payment Type 5, field 7: Company Entry Description
- SEC classification Type 5, field 6: Standard Entry Class Code
- Posting date RDFI posting records
- Check-conversion or terminal details Applicable SEC-specific record and disclosure rules
The transfer description must allow identification of the transaction. The Company Entry Description can support that purpose; the regulation does not prescribe one universal verbatim SEC-code label for every statement. Check serial and terminal data depend on the transaction type, so do not apply a PPD field number to every check-conversion layout.
An Originator’s corporate telephone number is not a universal transaction-level disclosure. The institution’s required inquiry telephone number is a different obligation.
4. Returns, WSUDs and NOCs
An RDFI returning an entry must select the reason that fits the facts and meet the relevant deadline. Ordinary returns generally must be available to the ODFI by opening of business on the second Banking Day following settlement . This is a receipt deadline, not permission to wait until an Operator cutoff late on that second day.
For an unauthorized consumer debit eligible for an extended return, the outer deadline is ODFI availability by opening of business on the Banking Day following the 60th calendar day after settlement . The RDFI must obtain the required Written Statement of Unauthorized Debit (WSUD). The outer limit is not permission to delay after the claim is ready: Nacha’s current guidance requires return by opening of the sixth Banking Day following completion of WSUD review . Regulation E investigation and provisional-credit duties remain separate.
A WSUD must satisfy the current Rules’ format, signature/authentication and retention requirements; electronic forms are permitted when they meet those requirements. Requested copies must be supplied through the Rules’ process.
A Notification of Change (COR/NOC) communicates corrected information. The RDFI is responsible for accuracy of the correction; it is not warranting that the Originator will never make another error. Distinguish the RDFI’s NOC transmission obligation from the Originator’s subsequent obligation to apply the correction. For most applicable entries, the Originator makes the change within six Banking Days of receiving the NOC information or before initiating another entry, whichever is later.
Sources and Edition Context
Nacha: non-Same Day funds availability, effective September 18, 2026
Nacha: territorial time-zone exception
Nacha: Same Day schedules — use its Same Day rows; its historical next-day receipt condition is superseded in 2026.