Currently Accepted Characters in the ACH Network
This rule will document the current set of characters that are accepted by both ACH Operators. Identifying the specific currently accepted characters in the ACH data specifications, rather than referencing standards outside the Nacha Operating Rules, will eliminate uncertainty about the characters that the ACH Operators accept. Industry participants in a technical role have requested this update to rule language for several years, eliminating any definition interpretation and replacing with definitive character values.
Details
This rule is a documentation clarification regarding already-acceptable characters; there is no change to current ACH Operator processing specifications or requirements, or the applicability of ACH data specification to other financial institution systems. ACH participants could receive any of the currently accepted characters today. ODFIs may accept all valid characters or a subset from their Originators, depending on their system capabilities.
Technical
This rule aims to improve the way processing of accepted characters is communicated by defining specific (currently accepted) valid characters in a table format. No changes will be made by the ACH Operators.
- The characters shown in the table include all single-byte characters that meet the current definition for valid characters and are currently accepted by all ACH Operators.
- Multi-byte characters have not been included and are not recommended for use in an ACH Record, as adjustment is needed to ensure an ACH Record line does not exceed 94 bytes.
- Some characters not included in the table may be accepted by only one ACH Operator. In the instance that such a character is submitted to an Operator that accepts the character but requires processing by another Operator, the character may be wild-carded (meaning the output value may not match the submission.)
- If a batch or file is submitted to an ACH Operator containing a character that it does not accept, the batch/file may be pended or rejected, as per individual Operator customer specifications.
This rule becomes effective January 1, 2027.
Although the proposal is to codify and document existing practices, with no operational or technical change requirements, this effective date is typical of editorial changes that appear in the following year’s rulebook (i.e., the 2027 Nacha Operating Rules and Guideline) and would provide time for documentation production, distribution and inclusion in rules publications, as appropriate.
Impact
Anticipated Benefits
- The characters in Appendix One and proposed language deletion in Appendix Two are aligned with current definition and practices by ACH Operators – no changes will be made by the Operators.
- Identifying the currently accepted valid characters for the ACH Network provides consistency for all participants.
- Clarification of characters accepted by both ACH Operators may help reduce the number of pended or rejected ACH batches/files during origination processes.
- Support of accepted extended characters by parties that were previously unsure about their validity may aid in the accuracy of legal identification of transaction participants; a change will be at that party’s discretion.
Potential Impacts
- This rule is a clarification regarding already-acceptable characters, and there is no change to the applicability of this rule to other downstream systems. ODFIs may continue to determine their acceptable characters from origination customers based upon their own system limitations that may be more restrictive than the Nacha Operating Rules.
- Software owners (vendors, FIs, third-parties, etc.) that were previously unsure about the validity of specific characters may choose to make updates, if necessary and at their discretion.
