Non-EDI Based Message Category (All SEC Codes except CTX, CCD, ENR, PPD, and TRX)

Edit online

The non-EDI based message category uses two maps, one for generating the entry detail record, and an optional map for generating the addenda record. The values in the batch header record are specified in the envelope. The process of generating the entry detail and addenda records is as follows:

  1. The entry detail map is run on the input file to obtain the 77 characters defining the ACH Entry Detail record. This process is repeated until the data in the input file is exhausted, resulting in a list of entry detail records. The map specified can be either a Sterling B2B Integrator map or a WebSphere® Transformation Extender map.
  2. The addenda map, if present, is run on the input file (starting from the beginning of the input data) to obtain the 76 characters defining the addenda record. This process is repeated until the data in the input file is exhausted, resulting in a list of addenda records. The map specified can be either a Sterling B2B Integrator map or a WebSphere Transformation Extender map.
    Note: The same file is used for generating both the entry detail and addenda records.
  3. The entry detail records are paired with their corresponding addenda records and output in the ACH file.

The Sterling B2B Integrator Map Editor is installed with predefined map structures for the various addenda and entry detail types. See Creating an ACH Map for more information.

Non-EDI Based Message Category (ENR)

ENR differs from other non-EDI based messages because it does not use an entry detail map (the entry detail records are generated based on the envelope settings). The process for generating an ENR from an input file is as follows:

  1. The entry detail record is generated based on values defined in the envelope.
  2. The addenda map is run on the input file to generate a 76 character addenda record. This process is repeated until the data in the input file is exhausted.
  3. All of the addenda records generated in step 2 are associated with the entry detail record from step 1, and output in the ACH file.

Non-EDI Based Message Category (TRX)

TRX does not use an entry detail map. The process for generating a TRX from an input file is as follows:

  1. The addenda map is run on the input file to generate the output data. The output of the addenda map is expected to be formatted in the National Association for Check Safekeeping syntax.
  2. The output of step 1 is split into addenda records of the appropriate length, and a corresponding entry detail record is generated based on the envelope settings. The total amount for the entry detail record is determined by the enveloping service based on the data generated in step 1.
  3. Steps 1 and 2 are repeated on the input file until the data is exhausted.