Study guide
7.5 Dishonored Returns (R61-R70) & Contested Dishonored Returns (R71-R76)
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
7.5 Dishonored Returns (R61-R70) & Contested Dishonored Returns (R71-R76)
Key Takeaways Explain This Topic AI
The ACH exception resolution process follows a three-tiered lifecycle: (1) Original Return by RDFI, (2) Dishonored Return by ODFI, and (3) Contested Dishonored Return by RDFI.
An ODFI may dishonor an improper, duplicate, or untimely return by transmitting a Dishonored Return (R61–R70) within five (5) banking days of the return settlement date.
An RDFI may challenge an ODFI's dishonor by transmitting a Contested Dishonored Return (R71–R76) within two (2) banking days of the dishonor settlement date.
A Contested Dishonored Return marks the absolute end of electronic ACH Network automated dispute routing; any further disputes must be settled off-network or through formal Nacha Arbitration.
Common dishonor reasons include R68 (Untimely Return), R67 (Duplicate Return), and R69 (Field Errors), matched by RDFI contest codes R73 (Timely Original Return) and R74 (Corrected Return).
Last updated: August 2026
7.5 Dishonored Returns (R61-R70) & Contested Dishonored Returns (R71-R76)
Core Principle: When an RDFI transmits an ACH Return, the ODFI is not obligated to accept the return if the RDFI violated Nacha operational standards—such as returning an entry past the legal deadline, transmitting a duplicate return, or formatting mandatory fields incorrectly. The Nacha Operating Rules establish a structured, automated Three-Tiered Exception Resolution Lifecycle : (1) Original Return, (2) Dishonored Return (ODFI pushback within 5 banking days) , and (3) Contested Dishonored Return (RDFI challenge within 2 banking days) .
1. The Three-Tiered ACH Exception Lifecycle +---------------------------------------------------------------------------------------------------------+
- | THE THREE-TIERED ACH EXCEPTION LIFECYCLE |
- +---------------------------------------------------------------------------------------------------------+
- | TIER 1: ORIGINAL RETURN ENTRY (RDFI =====> ODFI) |
- | - Standard Two-Banking-Day Rule (R01-R04, R08, R16, R20, R29) OR Extended 60-Day Rule (R05, R07, R10, R11)|
- | |
- | TIER 2: DISHONORED RETURN ENTRY (ODFI =====> RDFI) |
- | - ODFI challenges an improper return (R61-R70). |
- | - Strict Deadline: Made available to RDFI within FIVE (5) BANKING DAYS of Return Settlement Date. |
- | |
- | TIER 3: CONTESTED DISHONORED RETURN ENTRY (RDFI =====> ODFI) |
- | - RDFI refutes the dishonor or provides corrected data (R71-R76). |
- | - Strict Deadline: Made available to ODFI within TWO (2) BANKING DAYS of Dishonor Settlement Date. |
- | |
- | [ END OF AUTOMATED NETWORK PROCESSING ] =====> Off-Network Settlement / Nacha Arbitration (App. Ten) |
- +---------------------------------------------------------------------------------------------------------+
- 2. Tier 2: Dishonored Returns (Codes R61–R70)
Under Nacha Operating Rules Section 3.9 ( Dishonor of Return Entries ) , an ODFI may dishonor an ACH Return transmitted by an RDFI if the return entry is erroneous, duplicate, untimely, or non-compliant with Nacha specifications.
Operational Rules & Deadlines for Dishonored Returns
Initiated By: The ODFI.
Mandatory Deadline: The ODFI must transmit the Dishonored Return entry to the ACH Operator so that it is made available to the RDFI no later than the opening of business on the fifth (5th) banking day following the settlement date of the Return Entry .
Cash Flow Effect: Dishonoring a return reverses the financial debit previously charged against the ODFI, returning the funds to the ODFI's settlement account.
Master Breakdown of Dishonored Return Reason Codes (R61–R70)
Dishonor Code Title / Reason Operational Trigger & Specific Conditions
R61 Misrouted Return The RDFI transmitted the return to the wrong ODFI (routing transit number in the Return Entry Detail does not match the original ODFI).
R62 Return of Erroneous Reversing-Debit RDFI returned an erroneous reversing debit that was properly originated in compliance with reversal rules.
R67 Duplicate Return The RDFI transmitted more than one return entry for the exact same original entry (ODFI was debited twice).
R68 Untimely Return The original return was not transmitted within mandatory deadlines (e.g., standard return sent past Day 2, or unauthorized return sent past Day 60).
R69 Field Error(s) Mandatory fields in the Return Addenda Record contain invalid data, wrong trace numbers, or corrupt character strings.
R70 Permissible Return Entry Not Accepted ODFI has received authorization / signed agreement from Receiver, or return was ineligible.
Exam Key Point: The most frequently tested dishonor codes are R68 (Untimely Return) —used when an RDFI misses the 2-banking-day or 60-calendar-day window—and R67 (Duplicate Return) —used when system glitches cause an RDFI to fire double returns for a single item.
3. Tier 3: Contested Dishonored Returns (Codes R71–R76)
Under Nacha Operating Rules Section 3.10 ( Contested Dishonor of Return Entries ) , if the RDFI believes the ODFI's dishonor was incorrect, or if the RDFI can cure the technical defect, the RDFI may challenge the dishonor by transmitting a Contested Dishonored Return .
Operational Rules & Deadlines for Contested Dishonored Returns
Initiated By: The RDFI.
Mandatory Deadline: The RDFI must transmit the Contested Dishonored Return entry to the ACH Operator so that it is made available to the ODFI no later than the opening of business on the second (2nd) banking day following the settlement date of the Dishonored Return Entry .
Cash Flow Effect: Contesting a dishonor reverses the funds back to the RDFI.
Master Breakdown of Contested Dishonor Codes (R71–R76)
Contested Code Title / Reason Operational Trigger & Paired Dishonor Code
R71 Misrouted Dishonored Return The ODFI sent the dishonored return to the wrong RDFI (pairs against improper R61).
R72 Untimely Dishonored Return The ODFI transmitted the dishonored return after its 5-banking-day deadline expired.
R73 Timely Original Return The RDFI proves that its original return WAS timely (e.g., deposited before Day 2 cutoff or within 60 days), refuting ODFI's R68 .
R74 Corrected Return The RDFI corrects the field error identified in the ODFI's R69 dishonor and re-submits the clean, corrected return entry.
R75 Return Not Duplicate The RDFI demonstrates that the original returns represented two distinct original entries, refuting ODFI's R67 .
R76 No Errors Found The RDFI asserts that the original return contained no field errors, refuting ODFI's R69 .
4. Code Pairing Matrix: How Dishonors and Contests Interact +---------------------------------------------------------------------------------------------------------+
- | DISHONOR & CONTESTED DISHONOR PAIRING MATRIX |
- +---------------------------------------------------------------------------------------------------------+
- | ODFI Dishonor Reason (Tier 2 - 5 Banking Days) | RDFI Contested Dishonor Response (Tier 3 - 2 Banking Days)|
- +-------------------------------------------------+-------------------------------------------------------+
- | R68 (Untimely Return) | ====> R73 (Timely Original Return) |
- | R67 (Duplicate Return) | ====> R75 (Return Not Duplicate) |
- | R69 (Field Error(s)) | ====> R74 (Corrected Return) OR R76 (No Errors Found) |
- | Any Dishonor Sent Late (> 5 Banking Days) | ====> R72 (Untimely Dishonored Return) |
- | Dishonor Sent to Wrong RDFI | ====> R71 (Misrouted Dishonored Return) |
- +---------------------------------------------------------------------------------------------------------+
- 5. End of the Automated Network Lifecycle & Off-Network Resolution
A critical rule on the AAP exam is understanding where automated ACH processing terminates: +---------------------------------------------------------------------------------------------------------+
- | FINALITY OF THE ACH EXCEPTION ROUTING CYCLE |
- +---------------------------------------------------------------------------------------------------------+
- | 1. No Further Automated Pushbacks: |
- | Under Nacha Operating Rules, there is NO TIER 4 in the automated ACH Network. An ODFI CANNOT |
- | dishonor a Contested Dishonored Return (R71-R76) through the ACH Operator! |
- | |
- | 2. Off-Network Settlement / Direct Communication: |
- | If the ODFI still disputes the validity of the transaction, the financial institutions must contact |
- | each other directly and settle the matter off-network via wire transfer, cashier's check, or credit. |
- | |
- | 3. Formal Nacha Arbitration (Appendix Eight): |
- | If the dispute fits the scope and filing requirements of Nacha arbitration, the aggrieved DFI |
- | may file a formal Complaint for Arbitration under Appendix Eight of the Nacha Operating Rules. |
- +---------------------------------------------------------------------------------------------------------+