8.2 NOC Timelines: RDFI Origination & Originator 6-Day Mandatory Action

Key Takeaways

  • 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:

Mandatory  Update  Deadline=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})

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 StepOperational RequirementGoverning Rule & Calendar Window
ODFI Review & ValidationODFI automated systems or exception operators identify invalid change data (e.g., non-existent RTN or mismatched trace).Immediately upon NOC receipt
Refused NOC TransmittalODFI transmits COR batch containing Refused NOC addenda record (Addenda 98) to ACH Operator.Within 15 calendar days of NOC Settlement Date
ACH Operator SettlementACH Operator clears zero-dollar Refused COR entry to RDFI.Next scheduled settlement cycle
RDFI Post-Refusal ResolutionRDFI researches internal account database. RDFI cannot originate another automated NOC for that specific original entry.Internal exception handling
Loading diagram...
NOC Compliance Timelines & Originator Action Logic
Test Your Knowledge

What is the mandatory timeframe for an RDFI to originate and transmit an automated Notification of Change (COR) to the ACH Operator under Nacha Rules?

A
B
C
D
Test Your Knowledge

An Originator originates monthly utility bill debits. On March 2, the Originator receives an NOC specifying an updated account number for a customer whose next monthly bill debit will be initiated on March 25. By when must the Originator update its records?

A
B
C
D
Test Your Knowledge

If an ODFI receives an invalid or untimely Notification of Change from an RDFI, what is the maximum permissible deadline for the ODFI to transmit a Refused NOC (C61–C69) through the ACH Operator?

A
B
C
D
Test Your Knowledge

What regulatory enforcement mechanism does Nacha utilize to penalize Originators and ODFIs that repeatedly fail to act on valid Notifications of Change?

A
B
C
D