Study guide
8.2 NOC Timelines: RDFI Origination & Originator 6-Day Mandatory Action
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
8.2 NOC Timelines: RDFI Origination & Originator 6-Day Mandatory Action
Key Takeaways Explain This Topic AI
The RDFI must transmit an automated Notification of Change (COR) to the ACH Operator within two (2) banking days of the Settlement Date of the original entry being corrected.
The ODFI is required to deliver or make available the corrected NOC information to the Originator within two (2) banking days of the Settlement Date of the NOC.
Under Nacha Operating Rules, the Originator is legally mandated to update its records with the corrected data within six (6) banking days of receipt of the NOC data, OR prior to initiating the next live entry to the Receiver's account, whichever is later.
Repeated failure by an Originator to update records after receiving an NOC is a willful rules violation enforceable through Nacha's National System of Fines (Appendix Nine), carrying progressive financial penalties.
An ODFI has a strict deadline of fifteen (15) calendar days from the Settlement Date of the NOC to originate a Refused Notification of Change (C61–C69).
Last updated: August 2026
8.2 NOC Timelines: RDFI Origination & Originator 6-Day Mandatory Action
Core Principle: The effectiveness of the Notification of Change framework relies on strict adherence to standardized operational timelines. If an RDFI delays generating an NOC, or if an Originator ignores the corrected information and continues submitting transactions with defective data, the ACH Network suffers operational friction, increased return rates, and elevated processing costs. The Nacha Operating Rules establish legally binding deadlines across every participant in the NOC chain, backed by formal enforcement under the National System of Fines .
1. End-to-End Operational Lifecycle & Transmission Deadlines
The lifecycle of an NOC involves four sequential, time-sensitive operational milestones across the RDFI, ACH Operator, ODFI, and Originator: +---------------------------------------------------------------------------------------------------------+
- | NOC TIMELINE & OPERATIONAL MILESTONES |
- +-----------------------------------+---------------------------------------------------------------------+
- | Operational Milestone | Mandatory Deadline Under Nacha Operating Rules |
- +-----------------------------------+---------------------------------------------------------------------+
- | 1. Original Entry Settlement | Day 0 (Settlement Date of live credit or debit entry) |
- | 2. RDFI Transmits NOC to ACH Oper | Within **2 Banking Days** of original entry Settlement Date |
- | 3. ODFI Distributes NOC to Orig | Within **2 Banking Days** of NOC Settlement Date |
- | 4. Originator Updates Records | Within **6 Banking Days** of receipt OR **prior to next live entry**|
- | | (Whichever is LATER) |
- | 5. ODFI Transmits Refused NOC | Within **15 Calendar Days** of NOC Settlement Date (if defective) |
- +-----------------------------------+---------------------------------------------------------------------+
Step-by-Step Operational Breakdown:
Step 1: RDFI Origination Window (2 Banking Days)
Rule Requirement: The RDFI must transmit the automated NOC entry ( COR ) to the ACH Operator no later than the ACH Operator cutoff time on the second (2nd) banking day following the Settlement Date of the original entry.
Example: If a live PPD Direct Deposit settles on Tuesday (Day 0) , the RDFI must generate and transmit the COR entry to the ACH Operator by the close of business on Thursday (Day 2) .
Step 2: ODFI Forwarding Window (2 Banking Days)
Rule Requirement: Upon receipt of the settled NOC from the ACH Operator, the ODFI must transmit or make available the corrected information to the Originator within two (2) banking days of the Settlement Date of the NOC.
Delivery Mechanism: ODFIs provide this data via automated electronic data interchange (EDI) files, secure client web portals, automated API webhooks, or daily exception reports.
2. Mandatory Originator Action Timeline: The "Whichever Is Later" Rule
A central focus of the AAP exam is the exact statutory timeline governing when an Originator must apply the corrected NOC data to its internal billing or payroll master files.
The Legal Formula:
Under Nacha Operating Rules, the Originator MUST make the changes specified in the Notification of Change within: M a n d a t o r y U p d a t e D e a d l i n e = max ( 6 Banking Days from Receipt , Initiation Date of Next Live Entry ) \mathbf{Mandatory\;Update\;Deadline} = \max(\text{6 Banking Days from Receipt},\; \text{Initiation Date of Next Live Entry}) Mandatory Update Deadline = max ( 6 Banking Days from Receipt , Initiation Date of Next Live Entry )
In plain terms: Within six (6) banking days of receiving the NOC data, OR prior to initiating the next live entry to the Receiver's account, whichever is LATER. +---------------------------------------------------------------------------------------------------------+
- | SCENARIO ANALYSIS: APPLYING THE "WHICHEVER IS LATER" RULE |
- +---------------------------------------------------------------------------------------------------------+
- | Scenario A: High-Frequency Payment (Weekly Payroll) |
- | - NOC Received: Monday, June 1 |
- | - 6 Banking Days Expiration: Tuesday, June 9 |
- | - Next Payroll Initiation Date: Wednesday, June 3 (only 2 days away) |
- | -> Result: Originator has until Tuesday, June 9 (6 banking days) to update. The June 3 payroll entry |
- | MAY still use the old account number without violating Nacha Rules. |
- +---------------------------------------------------------------------------------------------------------+
- | Scenario B: Low-Frequency Payment (Monthly Mortgage Debit) |
- | - NOC Received: Monday, June 1 |
- | - 6 Banking Days Expiration: Tuesday, June 9 |
- | - Next Mortgage Debit Initiation Date: June 28 (27 days away) |
- | -> Result: Originator MUST apply the change BEFORE initiating the June 28 entry. Initiating on June 28 |
- | with the old data is a strict rules violation! |
- +---------------------------------------------------------------------------------------------------------+
- | Scenario C: Daily Corporate Disbursements (B2B Vendor Payments) |
- | - NOC Received: Thursday, October 10 |
- | - 6 Banking Days Expiration: Friday, October 18 (accounting for weekend) |
- | - Next Vendor Payment Initiation Date: Monday, October 14 |
- | -> Result: Originator has until Friday, October 18. Payments initiated between Oct 11–17 may use old |
- | data without penalty. Any entry initiated on or after October 19 MUST use corrected data. |
- +---------------------------------------------------------------------------------------------------------+
- 3. Nacha Compliance & Enforcement: National System of Fines
When an Originator fails to act on an NOC and continues to transmit subsequent ACH entries with obsolete or incorrect information, the RDFI is subjected to recurring manual intervention, exception posting, and administrative costs. Nacha enforces compliance through the National System of Fines (Appendix Nine of the Nacha Operating Rules ). +---------------------------------------------------------------------------------------------------------+
- | NATIONAL SYSTEM OF FINES: NOC ENFORCEMENT PROCESS |
- +---------------------------------------------------------------------------------------------------------+
- | Phase 1: RDFI Filing | RDFI submits a Rules Violation Report to Nacha at nacha.org/violation,|
- | | documenting repeated NOCs the Originator has ignored. |
- | Phase 2: Nacha Investigation | Nacha sends Notice of Possible Rules Violation to ODFI. ODFI has |
- | | 10 banking days to respond with Originator's remediation plan. |
- | Phase 3: ACH Rules Enforcement | If willful or uncorrected, the ACH Rules Enforcement Panel (ACHREP) |
- | Panel Evaluation | evaluates the violation and classifies the infraction severity. |
- | Phase 4: Tiered Penalty Levies | Nacha assesses progressive financial fines directly against the ODFI. |
- +---------------------------------------------------------------------------------------------------------+
Progressive Fine Schedule (Appendix Nine):
Class 1 Rules Violation: A repeat of the same infraction by the same party within one year of the initial resolution date. A first-time infraction draws a Notice, not a fine; the Class 1 fines are progressive — up to $1,000 for the first recurrence, $2,500 for the second and $5,000 for the third, with a fourth recurrence escalating to Class 2.
Class 2 Rules Violation: Serious procedural failure — including failing to respond to a Nacha notice or continued failure to correct NOC data after a Class 1 finding. Fines of up to $100,000 per month until the violation is resolved.
Class 3 Rules Violation: Willful, egregious, or a Class 2 violation left unresolved for three consecutive months. Fines of up to $500,000 per month , and Nacha may direct the ODFI to suspend the Originator's or Third-Party Sender's origination privileges.
Key Principle: Fines under Appendix Nine are assessed by Nacha directly against the ODFI . Under standard ODFI-Originator ACH Origination Agreements, the ODFI passes these fines, along with legal and operational processing surcharges, directly through to the offending Originator.
4. Refused NOC Timeline & Procedure (15 Calendar Days)
If the ODFI receives an NOC that is unprocessable, contains erroneous routing information, or represents an untimely transmission by the RDFI, the ODFI originates a Refused Notification of Change ( C61–C69 ).
Process Step Operational Requirement Governing Rule & Calendar Window
ODFI Review & Validation ODFI automated systems or exception operators identify invalid change data (e.g., non-existent RTN or mismatched trace). Immediately upon NOC receipt
Refused NOC Transmittal ODFI transmits COR batch containing Refused NOC addenda record (Addenda 98) to ACH Operator. Within 15 calendar days of NOC Settlement Date
ACH Operator Settlement ACH Operator clears zero-dollar Refused COR entry to RDFI. Next scheduled settlement cycle
RDFI Post-Refusal Resolution RDFI researches internal account database. RDFI cannot originate another automated NOC for that specific original entry. Internal exception handling