R14 | Invalid individual ID
This code indicates the individual identification information in the ACH entry was deemed invalid by the receiving institution’s processing rules.
What This Code Means
R14 is returned when the RDFI determines that the individual identifier included with the entry does not meet required validation rules or is not acceptable for posting. ACH entries often include an “Individual Identification Number” (or comparable identifier field) used for internal matching, posting controls, or compliance screening. When that identifier is missing, malformed, or fails the RDFI’s acceptance criteria, the entry may be returned with R14. This is an administrative/validation outcome, not a funds availability result. It does not necessarily mean the account number is invalid; it indicates a related identity/identifier field did not validate for processing.
Where Users Usually See This Code
- ACH return files for payroll, bill pay, or consumer debits
- Processor dashboards showing administrative returns
- Back-office reports where entry-level identifiers are logged
Why This Code Appears
- Individual ID field is missing or formatted incorrectly
- Identifier fails receiving bank validation requirements
- The identifier does not match the receiving bank’s internal posting or screening expectations
- Data mapping or file generation issues produced an invalid ID value
What Typically Happens Next
- The entry is returned with R14
- The originator receives the return and marks the transaction as failed/returned
- Subsequent entries with the same identifier pattern may return again until corrected upstream
What This Code Is Not
- It is not a closed account status (see R02)
- It is not an invalid account number result (see R04)
- It is not an unauthorized debit claim (see R05/R10)
Troubleshooting Checklist
- □ Review the entry’s individual ID field and confirm it conforms to your origination specification
- □ Compare against prior successful entries to detect formatting differences
- □ Record the return code and associated entry metadata for reconciliation
- □ If using a processor, follow the official exception workflow to validate required identifier fields
Notes And Edge Cases
Validation strictness can differ by RDFI and by entry context, meaning the same upstream data may pass at one bank and fail at another. Some institutions may treat certain identifiers as optional, while others require them for specific entry classes. In multi-system workflows, the “individual ID” may be populated by a middleware processor or payroll platform, and returns may spike after configuration changes. The return code does not specify which rule failed, so upstream logging is often needed to isolate formatting or mapping issues.