|Input file types that are supported by this function:||X9 support:||ACH support:|
Bind allows incoming x9 files to be automatically validated per customer requirements, where the appropriate x9 rules are applied based on the type and attributes of the current x9 file. The goal is to assign the correct x9 rules whenever possible on an automated basis. X9Assist refers to this processing as binding, where the proper x9 rules are automatically identified and applied as appropriate.
For many financial institutions, the combination of Origination and Destination ABA can be used to define the validation rules that are to be applied to any given x9 file. X9Assist allows this definition to be done on a generic basis by Origination ABA, Destination ABA, or the combination of these two fields. For example, you can define an x9 configuration to be applied to a specific Destination ABA regardless of origination. Or you can define the configuration to be applied to a specific Origination ABA regardless of destination.
To allow this to be done automatically, information from the x9 file header is used during the binding process to select the configuration that will be used to validate the file. Binding is accomplished using the following file header fields:
- Origination ABA
- Destination ABA
- Standard Level
- Universal Companion Document (UCD) Indicator
In many environments, the configuration can be assigned from the file header Standard Level and UCD Indicator, with no need to drill down to the Origination and Destination ABA levels.
The following additional tools support this process:
- The Configuration Editor is used to define logical configurations. Each configuration consists of a group of rules that are used by the file validation process.
- The Mapping Editor is used to define which configuration will be used to validate any given incoming file.
Through use of the Mapping Editor, you can provide automated instructions to the binding process which allow you to define overrides (exceptions) that are based upon the Origination and Destination ABA from the x9 file header. This allows you to ensure that X9Assist will automatically use the correct configuration file based on your specific requirements.
Through use of program options, you can override the bind process to always use a specific configuration file. For example, if your standard is to always use the newer X9.100-187 + UCD validation rules, then you can define this in your program options. In this way, binding is no longer dynamic based on the contents of the file header, but instead will always be done using your specified configuration.
There may be times that you want to validate an x9 file using a specific configuration, regardless of you program options setting, and regardless of the contents of the x9 file header.
From the menu bar, use the “Configuration” drop down to select a specific configuration that you want to use for validation. This configuration will to all subsequent files that are opened and validated for the current session only. You can always use program options to set your default configuration, which is saved and applies to all future user sessions.