ACH Prenotification Entries (Prenotes)

When to use Prenotification Entries and who initiates them

Prenotification Entries (Prenotes) are non-monetary ACH entries used to signal intent to send future Entries and to surface account/routing issues before (or, under updated practice language, during re-validation phases of) live activity.

Who initiates:

• Originator/ODFI transmits Prenotification Entries.
• RDFI response behavior (including NOC/return events) informs next action.

Rule limits and boundaries (NACHA-aligned)

1. Non-monetary intent
   Prenotes are account-validation/notification entries, not value movement entries.

2. Waiting-period control
   If your flow uses prenote waiting logic, first live value entry is generally gated until the required banking-day window has elapsed and no blocking response requires remediation.

3. Scope control
   Prenote validates posting-path signals; it does not by itself validate ownership, mandate sufficiency, or fraud posture.

4. Re-validation usage
   Current rules language/practice allows use of prenotification entries beyond only “first-ever entry” contexts, useful for dormant-account re-validation programs.

Practical samples

Sample 1: First-time vendor payout setup

• Scenario: AP onboarding a new supplier account.
• Action: send prenote and hold first value payment until policy waiting period and response checks clear.
• Control point: if NOC/return is received, correct data before releasing value entry.

Sample 2: Dormant account reactivation

• Scenario: recurring customer account has been inactive and is re-enabled.
• Action: re-validate with prenote workflow before next production debit/credit.
• Control point: do not auto-trust historical success from older account state.

Sample 3: Mixed validation stack (prenote + risk checks)

• Scenario: enterprise risk policy requires layered controls.
• Action: run prenote plus authorization verification and fraud screening.
• Control point: all validation gates must pass before live settlement path opens.

Sample data (illustrative) and highlight points

Prenotification Batch Header (5 Record)
  Company Name: ACME AP
  Company ID: 1231231230
  SEC Code: CCD
  Company Entry Description: PRENOTE
  Effective Entry Date: 260506

Prenote Entry Detail (6 Record)
  Transaction Code: 23
  RDFI Routing: 026009593
  Account Number: 445566778899
  Amount: 0000000000   (=$0.00)
  Receiver Name: VENDOR A
  Trace Number: 054001230330001

Decision Log
  Waiting Window Complete: true
  NOC Received: C01 (account correction)
  Action: apply corrected account before first live payment

Highlight

• Prenote 本身是 $0.00 非金额分录，重点是验证“可达性/数据正确性”。
• 如果收到 NOC/return，必须先修正再发第一笔有金额分录。
• “没有返回”不等于“已验证授权与所有权”，仍需其他控制。
• 需要把 prenote 事件和第一笔 live entry 做审计关联。

Operator checklist

1. Confirm whether prenote is required by your program/ODFI policy.
2. Generate prenote entries with correct receiver data and routing context.
3. Enforce waiting-period and response-review controls.
4. Process NOC/return responses before live entry release.
5. Keep prenote separate from ownership/auth/fraud validation controls.
6. Persist audit trail linking prenote event to first subsequent live entry.