5.5 Non-Monetary & Specialty Entries: Prenotifications, DNE & ENR

5.5 Non-Monetary & Specialty Entries: Prenotifications, DNE & ENR

Core Principle: Beyond moving monetary debits and credits, the ACH Network provides robust administrative and non-monetary communications channels. These specialty applications—including Prenotifications (Prenotes), Death Notification Entries (DNE), Automated Enrollment Entries (ENR), and Zero-Dollar Remittance Entries—validate banking credentials, alert institutions to deceased federal beneficiaries, enroll citizens in Direct Deposit, and transmit complex remittance records without moving funds.

---

1. Prenotifications (Prenotes): Account Validation Architecture

Definition and Operational Purpose

A Prenotification (Prenote) is a non-monetary, zero-dollar ($0.00) entry initiated by an Originator to verify that a Receiver's routing transit number and account number are valid and capable of receiving ACH entries before live dollar transactions are originated.

• Optional Status: Under Nacha Operating Rules, prenotes are optional for Originators, though many corporate originators and financial institutions mandate them as a best practice to prevent costly administrative returns (such as R03 No Account or R04 Invalid Account Number).
• Eligible SEC Codes: Prenotes can be originated for nearly all consumer and commercial SEC codes (PPD, CCD, CTX, WEB, TEL, IAT).

+---------------------------------------------------------------------------------------------------------+
|                                 PRENOTIFICATION TECHNICAL PROFILE                                       |
+---------------------------------------------------------------------------------------------------------+
| Parameter                     | Technical Specification                                                 |
+-------------------------------+-------------------------------------------------------------------------+
| Amount Field                  | Exactly ten zeros: `0000000000` ($0.00)                                 |
| Record Structure              | Standard 94-character Entry Detail Record (Type 6)                      |
| Addenda Indicator             | `0` (or `1` if required by SEC code such as IAT)                         |
| Transaction Code Pattern      | 2-digit codes ending in `3` (Credit Prenotes) or `8` (Debit Prenotes)   |
| Mandatory Waiting Period      | 3 Banking Days following settlement date before live entry origination   |
+---------------------------------------------------------------------------------------------------------+

Prenotification Transaction Codes

Prenote transaction codes are systematically distinguished from live monetary codes by ending in the digit 3 for credit entries and 8 for debit entries:

The Three-Banking-Day Waiting Period Rule

If an Originator chooses to originate a prenotification entry, Nacha Operating Rules impose a strict waiting period:

$\text{Earliest Live Entry Transmission} = \text{Settlement Date of Prenote} + 3 \text{ Banking Days}$

PRENOTE TIMELINE (Example: Monday Settlement; No Holidays)

+--------------------+--------------------+--------------------+--------------------+
| Monday (Day 0)     | Tuesday (Day 1)    | Wednesday (Day 2)  | Thursday (Day 3)   |
| Prenote Settles    | Waiting            | Waiting            | Earliest Day a     |
| ($0.00 / Code 23)  |                    |                    | Live Entry May Send|
+--------------------+--------------------+--------------------+--------------------+

RDFI Duties and Exception Responses to Prenotes

Upon receiving a prenote, the RDFI must verify that the routing number and account number exist within its core ledger system:

1. Valid Account: If the account exists and is valid, the RDFI takes no action and does not respond.
2. Account Valid but Details Incorrect: If the account is valid but contains outdated or slightly erroneous information (e.g., old account number or incorrect account type), the RDFI transmits a Notification of Change (NOC) with the appropriate change code (e.g., C01, C02).
3. Invalid / Non-Existent Account: If the account does not exist, is closed, or cannot receive entries, the RDFI must transmit a standard Return entry (e.g., R02 Account Closed, R03 No Account, R04 Invalid Account Number) within the standard two-banking-day return window.

[!NOTE] If the Originator receives no return or NOC by the conclusion of the 3-banking-day waiting period, it may safely presume the account is valid and proceed with live dollar transmissions.

---

2. Death Notification Entries (DNE)

A Death Notification Entry (DNE) is a specialized, zero-dollar ACH notice that only a federal agency may originate to tell an RDFI that a benefit recipient has died. Treasury's Green Book identifies SSA, OPM, and RRB as current DNE originators.

Technical Structure

• SEC code: DNE. It is not a PPD or CCD entry relabeled by an addenda record.
• Amount: Zero dollars.
• Addenda: The banking convention carries the date of death, the deceased person's Social Security number, and the amount of the next scheduled benefit payment. In the convention, the date of death appears in positions 18–23, the SSN in positions 38–46 (zeros if unavailable), and the expected payment amount begins in position 55.

RDFI Response

The RDFI should flag the deceased recipient, using name, SSN, or other identifying data precise enough to avoid returning a surviving joint owner's valid benefit. It must return later affected post-death federal benefit payments with R14 or R15 as appropriate.

A DNE provides notice of death, but it does not itself authorize the RDFI to seize, debit, or freeze customer funds already credited. Treasury explains that credited funds are property of the account holder or estate; the institution handles the existing balance under its account contract and responds to any later FS Form 133 reclamation through ARPS.

Federal agency learns of death
        ↓
Agency originates zero-dollar DNE
        ↓
RDFI identifies and flags the deceased recipient
        ↓
RDFI returns later affected federal benefit payments
        ↓
Any recovery of earlier credited benefits follows the federal reclamation process

---

3. Automated Enrollment Entries (ENR)

Definition and Purpose

The Automated Enrollment Entry (ENR) SEC code allows a Participating Depository Financial Institution (acting on behalf of an account holder) to electronically transmit Direct Deposit enrollment, modification, or cancellation instructions directly to participating Federal Government Agencies.

• Replaces Paper Forms: ENR replaces the manual paper Standard Form 1199A (Direct Deposit Sign-Up Form) and Direct Express paper enrollment pipelines.
• Originator: The financial institution (DFI) acts as the Originator.
• Receiver: The designated Federal Agency (e.g., SSA, VA, IRS, RRB).
• Amount: Non-monetary, zero-dollar entry ($0.00).

ENR DIRECT DEPOSIT ENROLLMENT FLOW
[Consumer Account Holder] ===(Requests Direct Deposit)===> [Financial Institution (DFI)]
                                                                  │
                                                                  ▼ (Originates ENR Batch)
[Federal Agency (SSA/VA)] <===(Updates Direct Deposit Database)<=== [ACH Operator (FedACH)]

Technical Structure of ENR

• SEC Code: ENR.
• Company Name Field: Contains the name of the enrolling DFI.
• Addenda Record: Must include an Addenda Record (Type 7, Addenda Type Code 05) conveying the account holder's Social Security Number / Claim Number, Agency Identifier, Account Number, and Account Type.

---

4. Zero-Dollar Remittance Entries (CCD / CTX Remittance)

In addition to prenotifications and federal specialty notices, commercial trading partners utilize Zero-Dollar Remittance Entries to transmit structured business data across the ACH Network without transferring monetary value.

Transaction Codes for Zero-Dollar Remittance Entries:

• 24: Demand Credit (Zero-Dollar Remittance)
• 34: Savings Credit (Zero-Dollar Remittance)
• 44: General Ledger Credit (Zero-Dollar Remittance)

Core Commercial Use Cases:

1. Full Offset via Trade Credit Memos: A buyer owes $100,000 across five invoices but holds $100,000 in return credit memos. The buyer originates a CTX entry with Transaction Code 24, $0.00 amount, and ANSI ASC X12 820 addenda records detailing the invoice-by-invoice offset.
2. Split Settlement Across Rails: A high-value corporate acquisition is settled via Fedwire funds transfer, while the detailed multi-page accounting breakdown is simultaneously transmitted via a zero-dollar CTX ACH entry.

---

5. Comparative Master Matrix: Non-Monetary & Specialty ACH Entries