X9Ware LLC offers a product line that includes a wide variety of x9 support tools that will improve your productivity levels when working with x9 image cash leX9Assist includes extensive support for the Canadian Payments Associated (CPA) Standard 015 specification. This functionality was initially implemented with the R2.05 release and has been improved with subsequent releases.
CPA 015 is an X9.100-187 extension and defines the x9 standard used to exchange image files between CPA member Direct Clearer Financial Institutions. X9Assist currently has two x9 specifications that are associated with Canadian x9 support:
- x9rules_x9.100-187_CCD.xml is an X9Assist base x9 document which defines CPA 015 forward presentment and returned items specifications. This X9Assist definition was defined per the requirements that are outlined in the “Canadian Payments Association Standard 015” document.
- Our implementation includes the addition of record type 61 (credit reconciliation) and type 68 (user record for payee endorsements). Note: this support is not specific to an industry accepted use of the Records 61 and 68 but can be used if an FI elects to use these record types in conjunction with a Remote Deposit Capture (RDC) stream or possibly cross-border exchange with a US Correspondent bank. X9Assist can be configured to an institution’s specific use of such records.
- x9rules_CPA_GrayScale.xml is a CPA 015 variant that supports gray scale images that are somtimes included within an x9 file that is typically targeted for an image archive
The X9Assist Configuration Editor supports the definition of unique x9 configurations that are used for file validation. This is standard functionality within X9Assist. Each x9 configuration consists of four components: an x9 rules file; a TIFF rules file; a messages file; and an options file. The combination of these components provides the basis for all x9 file validation within X9Assist. The most important of these is the x9 rules file, which defines all x9 record types, fields, and field level validations. The TIFF rules file is equally important and defines the validation rules that are applied to images. In a more secondary role, the messages file defines all error messages including their text and severity levels. Finally, the options file defines X9Assist program options to be applied during overall processing.
The Configuration Editor is invoked from the Editors menu bar and will display a panel that provides both inquiry and update to the configuration table.
When an x9 file is opened, X9Assist will attempt to use the appropriate x9 specification for validation based on the contents of the type 01 file control header. This automated detection is selected from the Validate function on the menu bar, using the “auto” option.
It may not be possible for X9Assist to always identify the appropriate x9 specification based on the file header content. Because of that, the Validate menu function allows the user to explicitly identify which x9 specification is to be used for the validation process. In certain situations, it may be desired to validate a file using several x9 specifications in rapid succession in order to see what types of errors are generated based on which standard is used for validation. X9Assist easily supports this type of analysis using the Validate function.
X9Assist currently has logic that attempts to automatically identify CPA and CPA Print files based on the contents of the x9 file name and the type 01 file control header. This X9Assist strategy will evolve over time and X9Ware LLC certainly welcomes user comments as to how we can improve the process. The CCD auto-detect process utilizes several mechanisms, which are as follows:
- CPA 015 files are identified using the standard file naming conventions that are documented within the CPA Standard 015 specification. An incoming x9 file name that matches this detection process will be internally assigned the UCD Indicator of “C” to facilitate mapping by the X9Assist binder.
- CPA 015 files are also identified based on the contents of the destination and origin routing numbers in the type 01 file header. This assignment first requires that the standards level be set to “03”. The binder will then determine if the immediate destination and immediate origin RT fields are both in ‘CP00RSNNN’ format, then the x9 file is assumed to be CCD. Similarly, if the immediate destination RT is in the ‘CP00RSNNN’ format and the immediate origin RT is in ABAmod10 format, then the x9 file is assumed to beCPA 015. In this situation, X9Assist will internally assign the UCD Indicator to a value of “C” to facilitate mapping by the X9Assist binder.
- X9 files not matching the above criteria are assumed to NOT be a CPA file. X9Assist will continue with the automated x9 file type detection process, which will result in the assignment of one of the alternate x9 specifications (UCD, x9.100-187, etc).