How ACH Enveloping Works

Edit online

To use the ACH Envelope service, you should use the supplied Data Definition Format (DDF) on the output map to ensure that the document used for the ACH Enveloping service is formatted correctly. The ACH Envelope service locates a file that has all the fields in the entry detail record, with the exception of: the Record Type Code, Addenda Record Indicator, and Trace Number fields. DDFs for both entry detail records and addenda are installed as part of the Sterling B2B Integrator Map Editor install and can be found in the Samples directory.

Note: The specified map is invoked multiple times on the input file until the input file is completely processed. Users can generate multiple entry detail records from the same input file.

Addenda records are also generated in a similar manner. If the structure of the entire Addenda Record has been fully defined by the ACH standard, the Sterling B2B Integrator provides corresponding DDFs. Customers should use the appropriate addenda DDF on the output side of the map. For applications in which addenda records contain payment related information, you should define the structure for the output side of an addenda map. The output of the addenda map will be used to generate the Payment Related Information field.

Note: The same input document is used to generate both entry detail records and addenda records.

ACH Enveloping supports transformation and message validation using WebSphere® Transformation Extender. With WebSphere Transformation Extender installed and integrated with Sterling B2B Integrator, the option Use WebSphere Transformation Extender Compliance Checking becomes available for the use of WebSphere Transformation Extender compliance checking. The valid values for this option are Yes and No (default).