3.3 RDFI Warranties, Receipt Obligations & Statement Requirements

3.3 RDFI Warranties, Receipt Obligations & Statement Requirements

Quick Reference: While ODFIs originate transactions and make extensive warranties, Receiving Depository Financial Institutions (RDFIs) bear critical operational and legal responsibilities under Nacha Rules Article Three. An RDFI must accept all valid ACH entries, post transactions in accordance with strict funds availability schedules (such as 9:00 AM local time for payroll direct deposits), enforce the prohibition on early debit posting, deliver mandatory periodic statement disclosures, and warrant the accuracy and timeliness of any Return Entries and Notifications of Change (NOC) it generates.

---

1. Mandatory Receipt and Processing Obligations (Article 3.1)

Under Nacha Rules Article 3.1, every financial institution participating in the ACH Network as an RDFI assumes a fundamental duty of universal receipt:

• Universal Acceptance: An RDFI cannot arbitrarily reject, block, or discriminate against specific Standard Entry Class (SEC) codes, Originators, or ACH Operators, provided the entries conform to Nacha technical specifications.
• Processing Timeliness: The RDFI must retrieve files from its ACH Operator in a timely manner and process entries to meet regulatory settlement and posting deadlines.

---

2. The Account Number Reliance Rule (Posting Mechanics)

A foundational principle enabling automated clearing is account-number reliance. The Nacha Rules permit posting based on the account number; UCC Article 4A-207 supplies a corresponding rule for covered commercial credit payment orders:

                     Account Number vs. Name Discrepancy

    Entry Detail Record (Field 7): Account # 123456789 (Belongs to John Smith)
    Entry Detail Record (Field 9): Individual Name "Alice Williams"

    ► Legal Result: RDFI is legally protected if it posts solely to Account # 123456789.
    ► Legal effect: Nacha account-number reliance applies to ACH posting; UCC 4A-207 separately governs covered commercial credit payment orders.

Key Principles of Account Number Reliance

1. Automated Processing: Under the Nacha Rules, an RDFI may post using the account number supplied in the Entry Detail Record without routinely matching the Receiver name.
2. Commercial Credit Orders: For a payment order governed by UCC 4A-207, a beneficiary bank may rely on the account number when it lacks actual knowledge that the name and number identify different persons. Actual knowledge changes the analysis.
3. Exceptions: For specific federal government entries (such as benefit payments subject to 31 CFR Part 210) or International ACH Transactions (IAT) requiring OFAC screening, specialized name review and screening protocols apply.

---

3. Funds Availability Mandates (Article Three, Section 3.3)

Nacha Operating Rules establish strict, enforceable deadlines by which an RDFI must make credit funds available for withdrawal or cash out by the Receiver:

                             Funds Availability Deadlines
  ┌─────────────────────────────────────────┼────────────────────────────────────────┐
  │                                         │                                        │
  ▼                                         ▼                                        ▼
1. PPD Direct Deposit Credits      2. Standard Next-Day Credits            3. Same Day ACH Credits
   ► 9:00 AM RDFI Local Time          ► Opening of Business on                ► Window 1: 1:30 PM Local
     on Settlement Date                  Settlement Date                      ► Window 2: 5:00 PM Local
                                                                              ► Window 3: 6:00 PM Local

1. PPD Direct Deposit / Payroll Credits (The 9:00 AM Rule - Subsection 3.3.1.1)

• Rule Requirement: For credit entries formatted with the PPD (Prearranged Payment and Deposit) SEC code (such as payroll direct deposits, pension distributions, and government benefits), the RDFI must make funds available for cash withdrawal or transfer no later than 9:00 AM in the RDFI's local time zone on the Settlement Date.
• Condition (through September 17, 2026): The entry must be made available to the RDFI by its ACH Operator no later than 5:00 PM local time on the banking day preceding the Settlement Date.
• From September 18, 2026 — the rule in force for the October 2026 test window: the 5:00 PM receipt condition is eliminated. Subsection 3.3.1.1 requires the RDFI to make the amount of any non-Same Day credit Entry available for withdrawal no later than 9:00 a.m. (RDFI's local time) on the Settlement Date, including credits that arrive in the 6:00 a.m. ET ACH Operator file. See Section 11.4.

2. Standard Next-Day ACH Credits

• For non-PPD credit entries (e.g., CCD corporate vendor disbursements, CIE customer-initiated bill payments), funds must be made available for withdrawal no later than the opening of business on the Settlement Date (or by the end of the settlement day for other standard entries).

3. Same Day ACH Credit Availability Schedule

Same Day ACH operates across three distinct processing windows, each tied to mandatory funds availability deadlines:

Prohibition on Early Debit Posting

• Strict Prohibition: An RDFI is strictly prohibited from debiting a Receiver's account prior to the Settlement Date indicated in the batch header record, even if the ACH file arrives at the RDFI days in advance. Posting debits prior to the Settlement Date constitutes a severe Nacha rule violation and exposes the RDFI to regulatory sanctions and overdraft liability under Regulation E.

---

4. Consumer Periodic Statement Disclosure Requirements (Article 3.4 & Reg E)

Under Nacha Rules Article 3.4 and Regulation E (12 CFR § 1005.9), the RDFI must provide comprehensive electronic or paper periodic statements to consumer account holders. Every ACH entry must display specific mandatory data elements:

---

5. RDFI Legal Warranties on Exception Items

While ODFIs warrant origination, the RDFI makes strict legal warranties when initiating exception workflows:

1. RDFI Warranty on Return Entries (Article 3.8.1)

When an RDFI transmits a Return Entry (using an R-code like R01, R03, R10), it warrants to the ODFI, ACH Operator, and Nacha that:

• The return is transmitted within the strict deadlines established by the Rules (by the ACH Operator deposit deadline on the second banking day following settlement for general returns, or within 60 calendar days for consumer unauthorized returns with a valid WSUD).
• The return entry contains the correct Return Reason Code accurately reflecting the factual reason for return.
• The information in the return entry matches the original Entry Detail Record without unauthorized modification.

2. RDFI Warranty on Extended Returns & Written Statement of Unauthorized Debit (WSUD)

When initiating an extended return for unauthorized consumer debits (R05, R07, R10, R11, R51) within the 60-day window, the RDFI warrants that:

• It has obtained a completed, signed Written Statement of Unauthorized Debit (WSUD) from the consumer under penalty of perjury.
• The WSUD was executed in accordance with the Subsection 3.12.4 (Form of Written Statement of Unauthorized Debit) requirements.
• The RDFI will provide a copy of the WSUD to the ODFI within ten banking days of receiving a written request.

3. RDFI Warranty on Notifications of Change (NOC / COR) (Article 3.9.1)

When an RDFI generates an NOC (COR entry) to request corrected banking details (e.g., C01 for incorrect account number, C02 for incorrect routing number), it warrants that:

• The corrected information provided in the NOC is completely accurate and reflects the authentic account records maintained by the RDFI for that Receiver.
• The NOC is transmitted within two banking days of the Settlement Date of the original entry.