ACH Micro-Entries (Account Validation)

When to use Micro-Entries and who initiates them

Use Micro-Entries when the goal is account validation, not funds movement. Under NACHA language, these are account-validation Entries initiated by the Originator/ODFI flow.

Common use case:

• Validate that a Receiver account can receive and/or debit ACH entries before live payment traffic.

Who initiates:

• Originator (or service provider acting for Originator) transmits Micro-Entries.
• Receiver/RDFI responses are then used to complete validation logic.

Rule limits and boundaries (NACHA-aligned)

1. Definition and amount envelope
   Micro-Entries are account-validation Entries that include ACH credit(s) less than $1.00, and optional offsetting debit Micro-Entries.

2. Net-debit protection boundary
   If debit Micro-Entries are used, total debit amount must not exceed total corresponding credit Micro-Entries.

3. Formatting requirement
   Company Entry Description should use ACCTVERIFY for clear network identification.

4. Simultaneous transmission requirement
   Offsetting debit and credit Micro-Entries should be transmitted for the same settlement timing window (same effective date logic).

5. Future-entry gating
   Do not originate production/live entries simultaneously with Micro-Entries. Live traffic should start only after your validation process is complete and return conditions are acceptable.

6. Fraud-monitoring requirement
   Apply commercially reasonable fraud detection and monitor forward/return Micro-Entry volumes to detect abnormal activity.

Practical samples

Sample 1: New payout account onboarding

• Scenario: marketplace seller links a new bank account.
• Action: Originator sends Micro-Entry credit(s) with optional offset debit and ACCTVERIFY descriptor.
• Control point: lock payout release until validation workflow is complete.

Sample 2: Re-validation for dormant account

• Scenario: no ACH activity for months; account needs re-validation before reactivation.
• Action: transmit new Micro-Entries and collect receiver confirmation through your verification flow.
• Control point: treat as a new risk decision event, not a legacy “already verified” shortcut.

Sample 3: Return-heavy validation cohort

• Scenario: sudden increase in Micro-Entry returns from one origin channel.
• Action: trigger velocity/risk controls, reduce batch release rate, and escalate for fraud review.
• Control point: monitor baseline drift in both forward and return volumes.

Sample data (illustrative) and highlight points

Batch Header (5 Record)
  Company Name: ACME PLATFORM
  Company ID: 9876543210
  SEC Code: WEB
  Company Entry Description: ACCTVERIFY
  Effective Entry Date: 260506

Entry A (Credit Micro-Entry)
  Transaction Code: 22
  Amount: 0000000045   (=$0.45)
  Trace Number: 071000440120001

Entry B (Offset Debit Micro-Entry)
  Transaction Code: 27
  Amount: 0000000045   (=$0.45)
  Trace Number: 071000440120002

Risk Monitoring Snapshot
  Daily Micro-Entry Forwards: 12,440
  Daily Micro-Entry Returns: 1,102
  Return Ratio Spike: +3.1x baseline

Highlight

• Company Entry Description = ACCTVERIFY 是 Micro-Entries 的关键识别信号。
• 单笔 credit < $1.00，且 offset debit 总额不能超过对应 credit 总额。
• 同步发送（同结算窗口）有助于降低收款方账户体验与操作风险。
• 只要回退量异常上升，就要触发风控策略，而不是继续放量。

Operator checklist

1. Confirm account-validation purpose and authorization basis.
2. Build entries with Micro-Entry constraints (< $1 credits, offset rules).
3. Set Company Entry Description to ACCTVERIFY.
4. Transmit corresponding credit/debit Micro-Entries in the same processing window.
5. Block live entries until validation completes and exceptions are resolved.
6. Track Micro-Entry forward/return metrics and enforce anomaly controls.