Delimited EDI Based ACH Application

Edit online

If you select the ACH Message Category as Delimited EDI Based ACH Application, the options displayed for the SEC codes ACK, ATX, CBR, CCD, CIE, COR, DNE, ENR, MTE, PBR, POS, PPD, SHR, TRX, and WEB are as follows:

Field
Description
Expect an acknowledgment for messages sent using this envelope
Specify if you would like to receive an acknowledgment for the messages sent using this envelope. Valid values are:
  • Yes
  • No (default)
Note: Only displayed if the SEC code selected is CCD.
Acknowledgment overdue after (hours)
Duration in hours in which the acknowledgment is due. Optional.
Note: Only displayed if the SEC code selected is CCD.
Acknowledgment overdue after (minutes)
Duration in minutes in which the acknowledgment is due. Optional.
Note: Only displayed if the SEC code selected is CCD.
Service Class Code
Select the service class code from the list provided. Valid values are:
  • * (Wildcard)
  • 200 (Mixed Debits and Credits)
  • 220 (Credits Only)
  • 225 (Debits Only)
  • 280 (Automated Accounting Devices)
Note: Only displayed if the SEC Code selected is COR.
Is the COR Message from an IAT?
Whether the Notification of Change is related to an IAT entry. Valid values are:
  • Yes
  • No (default)
Note: Only displayed if the SEC Code selected is COR.
Company Discretionary Data
Field in the Company/Batch Header Record. Allows Originators and ODFIs to include codes of significance only to them, to enable specialized handling of all subsequent entries in that batch. There is no standardized interpretation for the value. Optional.
Company Descriptive Date
The Originator establishes this field as the date it would like to be displayed to the Receiver for descriptive purposes. Optional.
Effective Entry Date Offset
Type the effective entry date offset. The effective entry date is the date specified by the Originator on which it intends a batch of entries to be settled. For credit entries, the effective entry date shall be either one or two banking days following the banking day of processing as establish by the Originating ACH Operator (the processing date). For debit entries, the effective entry date shall be one banking day following the processing date. The offset is an offsetting transaction to either credit or debit for the total amount of the batch. Required.
Discretionary data
Field in Entry Detail Record allows ODFIs to include codes of significance only to them, to enable specialized handling of the entry. There is no standardized interpretation for the value in this field. Optional.
Note: Only displayed if the SEC code selected is CCD or ENR.
Item Type Indicator
This field indicates the type of items being truncated. Optional.
Note: Only displayed for the SEC code TRX.
Use addenda records with each entry detail record?
Specify if you want to use addenda records with each entry detail record. The addenda record is translated by the addenda map specified in the envelope. Valid values are:
  • Yes
  • No
Addenda Map Name Mode
Mode in which to specify the map to perform a compliance check. Required. Valid values are:
  • Specify
  • Generate from data
Note: Only displayed if Use addenda records with each entry detail record? is set to Yes.
Name of map to be used for generation of Addenda record
Select a previously created Sterling B2B Integrator or WebSphere® Transformation Extender map name to associate with this envelope. Required.
Note: Only displayed if Addenda Map Name Mode is set to Specify.
Primary Name Format
Check boxes to instruct what information to include when generating and matching a name for the map. Optional.

Select from:

  • SEC Code (selected by default)
  • Receiving DFI Identification (selected by default)
  • DFI Account Number
  • Originating DFI Identification (selected by default)
  • Company identification
Note: If you are using a generated map name (If Addenda Map Name Mode is set to Generate from data), the Sterling B2B Integrator tries to generate and match the following maps:
  • First, it tries to generate and match the map in the primary name format (replacing the values that are selected for the corresponding value in the message).
  • Second, it tries to generate and match the First Backup Name.
  • Third, it tries to generate and match the Second Backup Name.
  • Fourth, if there is not an existing map that matches the names generated in steps 1-3, an error is generated.

Only occurs if Generate an error if no matching map is found is set to Yes.

First Backup Name Format
The first backup name format to use when generating a map name. The system allows for two alternatives if the Primary Name Format is not found—checking for the First Backup Name Format and then, if that is not found, checking for the Second Backup Name Format. Optional.

Select from:

  • SEC Code (selected by default)
  • Receiving DFI Identification
  • DFI Account Number
  • Originating DFI Identification
  • Company identification
Note: If you are using a generated map name (If Addenda Map Name Mode is set to Generate from data), the Sterling B2B Integrator tries to generate and match the following maps:
  • First, it tries to generate and match the map in the primary name format (replacing the values that are selected for the corresponding value in the message).
  • Second, it tries to generate and match the First Backup Name.
  • Third, it tries to generate and match the Second Backup Name.
  • Fourth, if there is not an existing map that matches the names generated in steps 1-3, an error is generated.

Only occurs if Generate an error if no matching map is found is set to Yes.

Second Backup Name Format
The second backup name format to use when generating a map name. The system allows for two alternatives if the Primary Name Format is not found—checking for the First Backup Name Format and then, if that is not found, checking for the Second Backup Name Format. Optional.

Select from:

  • SEC Code
  • Receiving DFI Identification
  • DFI Account Number
  • Originating DFI Identification
  • Company identification
Note: If you are using a generated map name (If Addenda Map Name Mode is set to Generate from data), the Sterling B2B Integrator tries to generate and match the following maps:
  • First, it tries to generate and match the map in the primary name format (replacing the values that are selected for the corresponding value in the message).
  • Second, it tries to generate and match the First Backup Name.
  • Third, it tries to generate and match the Second Backup Name.
  • Fourth, if there is not an existing map that matches the names generated in steps 1-3, an error is generated.

Only occurs if Generate an error if no matching map is found is set to Yes.

Generate an error if no matching map is found
Specifies whether to generate an error if the map name selected is not found. Valid values are Yes (default) and No.
Note: Only displayed if Addenda Map Name Mode is set to Generate from data.
Map Name Mode
Mode in which to specify the map to use to perform a compliance check.

Required. Valid values are:

  • Specify
  • Generate from data
  • Default
Map Name
Select the Sterling B2B Integrator or WebSphere Transformation Extender map to be used to perform a compliance check. The map must already be checked in. Optional.
Note: Only displayed if Map Name Mode is set to Specify.
Primary Name Format
Check boxes to instruct what information to include when generating and matching a name for the map. Optional.

Select from:

  • SEC Code (selected by default)
  • Receiving DFI Identification (selected by default)
  • Originating DFI Identification (selected by default)
  • Standard contained in addenda (selected by default)
  • X12 Transaction Set /EDIFACT Message Type (selected by default)
  • X12 Group Version ID Code/EDIFACT Message Version and Release Number (selected by default)
Note: If you are using a generated map name (If Map Name Mode is set to Generate from data), the Sterling B2B Integrator tries to generate and match the following maps:
  • First, it tries to generate and match the map in the primary name format (replacing the values that are selected for the corresponding value in the message).
  • Second, it tries to generate and match the First Backup Name.
  • Third, it tries to generate and match the Second Backup Name.
  • Fourth, if there is not an existing map that matches the names generated in steps 1-3, an error is generated.

Only occurs if Generate an error if no matching map is found is set to Yes.

First Backup Name Format
The first backup name format to use when generating a map name. The system allows for two alternatives if the Primary Name Format is not found—checking for the First Backup Name Format and then, if that is not found, checking for the Second Backup Name Format. Optional.

Select from:

  • SEC Code (selected by default)
  • Receiving DFI Identification
  • Originating DFI Identification
  • Standard contained in addenda (selected by default)
  • X12 Transaction Set /EDIFACT Message Type (selected by default)
  • X12 Group Version ID Code/EDIFACT Message Version and Release Number (selected by default)
Note: If you are using a generated map name (If Map Name Mode is set to Generate from data), the Sterling B2B Integrator tries to generate and match the following maps:
  • First, it tries to generate and match the map in the primary name format (replacing the values that are selected for the corresponding value in the message).
  • Second, it tries to generate and match the First Backup Name.
  • Third, it tries to generate and match the Second Backup Name.
  • Fourth, if there is not an existing map that matches the names generated in steps 1-3, an error is generated.

Only occurs if Generate an error if no matching map is found is set to Yes.

Second Backup Name Format
The second backup name format to use when generating a map name. The system allows for two alternatives if the Primary Name Format is not found—checking for the First Backup Name Format and then, if that is not found, checking for the Second Backup Name Format. Optional.

Select from:

  • SEC Code
  • Receiving DFI Identification
  • Originating DFI Identification
  • Standard contained in addenda
  • X12 Transaction Set /EDIFACT Message Type
  • X12 Group Version ID Code/EDIFACT Message Version and Release Number
Note: If you are using a generated map name (If Map Name Mode is set to Generate from data), the Sterling B2B Integrator tries to generate and match the following maps:
  • First, it tries to generate and match the map in the primary name format (replacing the values that are selected for the corresponding value in the message).
  • Second, it tries to generate and match the First Backup Name.
  • Third, it tries to generate and match the Second Backup Name.
  • Fourth, if there is not an existing map that matches the names generated in steps 1-3, an error is generated.

Only occurs if Generate an error if no matching map is found is set to Yes.

Generate an error if no matching map is found
Specifies whether to generate an error if the map name selected is not found. Valid values are Yes (default) and No.
Note: Only displayed if Map Name Mode is set to Generate from data.

In the Confirm page, verify the settings and click Finish to save the configurations for the envelope.

If you select the ACH Message Category as Delimited EDI Based ACH Application, the options displayed for the SEC codes ADV, ARC, BOC, CTX, POP, RCK, TEL, TRC, and XCK.

Field
Description
Expect an acknowledgment for messages sent using this envelope
Specify if you would like to receive an acknowledgment for the messages sent using this envelope. Valid values are:
  • Yes
  • No (default)
Note: Only displayed if the SEC code selected is CTX.
Acknowledgment overdue after (hours)
Duration in hours in which the acknowledgment is due. Optional.
Note: Only displayed if the SEC code selected is CTX.
Acknowledgment overdue after (minutes)
Duration in minutes in which the acknowledgment is due. Optional.
Note: Only displayed if the SEC code selected is CTX.
Company Discretionary Data
Field in the Company/Batch Header Record. Allows Originators and ODFIs to include codes of significance only to them, to enable specialized handling of all subsequent entries in that batch. There is no standardized interpretation for the value. Optional.
Company Descriptive Date
The Originator establishes this field as the date it would like to be displayed to the Receiver for descriptive purposes. Optional.
Effective Entry Date Offset
Type the effective entry date offset. The effective entry date is the date specified by the Originator on which it intends a batch of entries to be settled. For credit entries, the effective entry date shall be either one or two banking days following the banking day of processing as establish by the Originating ACH Operator (the processing date). For debit entries, the effective entry date shall be one banking day following the processing date. The offset is an offsetting transaction to either credit or debit for the total amount of the batch. Required.
Discretionary data
Type the value for the discretionary data. Optional.
Note: Only displayed if the SEC code selected is CCD.
ACH Operator Data
The data operator for ACH. Optional.
Note: Only displayed if the SEC code selected is ADV.
Routing Number of ACH Operator
Receiving point to which the message is being sent. Required.
Note: Only displayed if the SEC code selected is ADV.
Map Name Mode
Mode in which to specify the map to use to perform a compliance check.

Required. Valid values are:

  • Specify
  • Generate from data
Map Name
Select the Sterling B2B Integrator or WebSphere Transformation Extender map to be used to perform a compliance check. The map must already be checked in. Optional.
Note: Only displayed if Map Name Mode is set to Specify.
Primary Name Format
Check boxes to instruct what information to include when generating and matching a name for the map. Optional.

Select from:

  • SEC Code (selected by default)
  • Receiving DFI Identification (selected by default)
  • Originating DFI Identification (selected by default)
  • Standard contained in addenda (selected by default)
  • X12 Transaction Set /EDIFACT Message Type (selected by default)
  • X12 Group Version ID Code/EDIFACT Message Version and Release Number (selected by default)
Note: If you are using a generated map name (If Map Name Mode is set to Generate from data), the Sterling B2B Integrator tries to generate and match the following maps:
  • First, it tries to generate and match the map in the primary name format (replacing the values that are selected for the corresponding value in the message).
  • Second, it tries to generate and match the First Backup Name.
  • Third, it tries to generate and match the Second Backup Name.
  • Fourth, if there is not an existing map that matches the names generated in steps 1-3, an error is generated.

Only occurs if Generate an error if no matching map is found is set to Yes.

First Backup Name Format
The first backup name format to use when generating a map name. The system allows for two alternatives if the Primary Name Format is not found—checking for the First Backup Name Format and then, if that is not found, checking for the Second Backup Name Format. Optional.

Select from:

  • SEC Code (selected by default)
  • Receiving DFI Identification
  • Originating DFI Identification
  • Standard contained in addenda (selected by default)
  • X12 Transaction Set /EDIFACT Message Type (selected by default)
  • X12 Group Version ID Code/EDIFACT Message Version and Release Number (selected by default)
Note: If you are using a generated map name (If Map Name Mode is set to Generate from data), the Sterling B2B Integrator tries to generate and match the following maps:
  • First, it tries to generate and match the map in the primary name format (replacing the values that are selected for the corresponding value in the message).
  • Second, it tries to generate and match the First Backup Name.
  • Third, it tries to generate and match the Second Backup Name.
  • Fourth, if there is not an existing map that matches the names generated in steps 1-3, an error is generated.

Only occurs if Generate an error if no matching map is found is set to Yes.

Second Backup Name Format
The second backup name format to use when generating a map name. The system allows for two alternatives if the Primary Name Format is not found—checking for the First Backup Name Format and then, if that is not found, checking for the Second Backup Name Format. Optional.

Select from:

  • SEC Code
  • Receiving DFI Identification
  • Originating DFI Identification
  • Standard contained in addenda
  • X12 Transaction Set /EDIFACT Message Type
  • X12 Group Version ID Code/EDIFACT Message Version and Release Number
Note: If you are using a generated map name (If Map Name Mode is set to Generate from data), the Sterling B2B Integrator tries to generate and match the following maps:
  • First, it tries to generate and match the map in the primary name format (replacing the values that are selected for the corresponding value in the message).
  • Second, it tries to generate and match the First Backup Name.
  • Third, it tries to generate and match the Second Backup Name.
  • Fourth, if there is not an existing map that matches the names generated in steps 1-3, an error is generated.

Only occurs if Generate an error if no matching map is found is set to Yes.

Generate an error if no matching map is found
Specifies whether to generate an error if the map name selected is not found. Valid values are Yes (default) and No.
Note: Only displayed if Map Name Mode is set to Generate from data.

In the Confirm page, verify the settings and click Finish to save the configurations for the envelope.

The pages displayed for the SEC code IAT are as follows:

Field
Description
Company Discretionary Data
Field in the Company/Batch Header Record. Allows Originators and ODFIs to include codes of significance only to them, to enable specialized handling of all subsequent entries in that batch. There is no standardized interpretation for the value. Optional.
Company Descriptive Date
The Originator establishes this field as the date it would like to be displayed to the Receiver for descriptive purposes. Optional.
Effective Entry Date Offset
Type the effective entry date offset. The effective entry date is the date specified by the Originator on which it intends a batch of entries to be settled. For credit entries, the effective entry date shall be either one or two banking days following the banking day of processing as establish by the Originating ACH Operator (the processing date). For debit entries, the effective entry date shall be one banking day following the processing date. The offset is an offsetting transaction to either credit or debit for the total amount of the batch. Required.
Foreign Exchange Indicator
Select the type of Foreign Exchange Indicator. Valid options are:
  • Fixed-To-Variable
  • Variable-To-Fixed
  • Fixed-To-Fixed

Required.

ISO Destination Country or Region Code
Type the ISO Destination Country or Region Code. It should be two characters in length. Required.
ISO Originating Currency Code
Type the ISO Originating Currency Code. It should be three characters in length. Required.
ISO Destination Currency Code
Type the ISO Destination Currency Code. It should be three characters in length. Required.
Foreign Exchange Reference Indicator
Indicates the content of the Foreign Exchange Reference field. Valid options are:
  • Foreign Exchange Rate
  • Foreign Exchange Reference Number
  • Space filled
Note: Only displayed if the Foreign Exchange Indicator is set to Fixed-To-Variable or Variable-To-Fixed.
Enter in a non-runtime value for foreign exchange reference
A non-runtime value for foreign exchange reference. Valid values are:
  • Yes (default)
  • No

Only displayed if Foreign Exchange Reference Indicator is set to Foreign Exchange Rate.

Foreign Exchange Reference
Type the reference for the Foreign Exchange.
Use addenda records with each entry detail record?
Specify if you want to use addenda records with each entry detail record. The addenda record is translated by the addenda map specified in the envelope. Valid values are:
  • Yes
  • No
Addenda Map Name Mode
Mode in which to specify the map to perform a compliance check. Required. Valid values are:
  • Specify
  • Generate from data
Note: Only displayed if Use addenda records with each entry detail record? is set to Yes.
Name of map to be used for generation of Addenda record
Select a previously created Sterling B2B Integrator or WebSphere Transformation Extender map name to associate with this envelope. Required.
Note: Only displayed if Addenda Map Name Mode is set to Specify.
Primary Name Format
Check boxes to instruct what information to include when generating and matching a name for the map. Optional.

Select from:

  • SEC Code (selected by default)
  • Receiving DFI Identification (selected by default)
  • DFI Account Number
  • Originating DFI Identification (selected by default)
  • Company identification
Note: If you are using a generated map name (If Addenda Map Name Mode is set to Generate from data), the Sterling B2B Integrator tries to generate and match the following maps:
  • First, it tries to generate and match the map in the primary name format (replacing the values that are selected for the corresponding value in the message).
  • Second, it tries to generate and match the First Backup Name.
  • Third, it tries to generate and match the Second Backup Name.
  • Fourth, if there is not an existing map that matches the names generated in steps 1-3, an error is generated.

Only occurs if Generate an error if no matching map is found is set to Yes.

First Backup Name Format
The first backup name format to use when generating a map name. The system allows for two alternatives if the Primary Name Format is not found—checking for the First Backup Name Format and then, if that is not found, checking for the Second Backup Name Format. Optional.

Select from:

  • SEC Code (selected by default)
  • Receiving DFI Identification
  • DFI Account Number
  • Originating DFI Identification
  • Company identification
Note: If you are using a generated map name (If Addenda Map Name Mode is set to Generate from data), the Sterling B2B Integrator tries to generate and match the following maps:
  • First, it tries to generate and match the map in the primary name format (replacing the values that are selected for the corresponding value in the message).
  • Second, it tries to generate and match the First Backup Name.
  • Third, it tries to generate and match the Second Backup Name.
  • Fourth, if there is not an existing map that matches the names generated in steps 1-3, an error is generated.

Only occurs if Generate an error if no matching map is found is set to Yes.

Second Backup Name Format
The second backup name format to use when generating a map name. The system allows for two alternatives if the Primary Name Format is not found—checking for the First Backup Name Format and then, if that is not found, checking for the Second Backup Name Format. Optional.

Select from:

  • SEC Code
  • Receiving DFI Identification
  • DFI Account Number
  • Originating DFI Identification
  • Company identification
Note: If you are using a generated map name (If Addenda Map Name Mode is set to Generate from data), the Sterling B2B Integrator tries to generate and match the following maps:
  • First, it tries to generate and match the map in the primary name format (replacing the values that are selected for the corresponding value in the message).
  • Second, it tries to generate and match the First Backup Name.
  • Third, it tries to generate and match the Second Backup Name.
  • Fourth, if there is not an existing map that matches the names generated in steps 1-3, an error is generated.

Only occurs if Generate an error if no matching map is found is set to Yes.

Generate an error if no matching map is found
Specifies whether to generate an error if the map name selected is not found. Valid values are Yes (default) and No.
Note: Only displayed if Addenda Map Name Mode is set to Generate from data.
Map Name Mode
Mode in which to specify the map to use to perform a compliance check.

Required. Valid values are:

  • Specify
  • Generate from data
  • Default
Map Name
Select the Sterling B2B Integrator or WebSphere Transformation Extender map to be used to perform a compliance check. The map must already be checked in. Optional.
Note: Only displayed if Map Name Mode is set to Specify.
Primary Name Format
Check boxes to instruct what information to include when generating and matching a name for the map. Optional.

Select from:

  • SEC Code (selected by default)
  • Receiving DFI Identification (selected by default)
  • Originating DFI Identification (selected by default)
  • Standard contained in addenda (selected by default)
  • X12 Transaction Set /EDIFACT Message Type (selected by default)
  • X12 Group Version ID Code/EDIFACT Message Version and Release Number (selected by default)
Note: If you are using a generated map name (If Map Name Mode is set to Generate from data), the Sterling B2B Integrator tries to generate and match the following maps:
  • First, it tries to generate and match the map in the primary name format (replacing the values that are selected for the corresponding value in the message).
  • Second, it tries to generate and match the First Backup Name.
  • Third, it tries to generate and match the Second Backup Name.
  • Fourth, if there is not an existing map that matches the names generated in steps 1-3, an error is generated.

Only occurs if Generate an error if no matching map is found is set to Yes.

First Backup Name Format
The first backup name format to use when generating a map name. The system allows for two alternatives if the Primary Name Format is not found—checking for the First Backup Name Format and then, if that is not found, checking for the Second Backup Name Format. Optional.

Select from:

  • SEC Code (selected by default)
  • Receiving DFI Identification
  • Originating DFI Identification
  • Standard contained in addenda (selected by default)
  • X12 Transaction Set /EDIFACT Message Type (selected by default)
  • X12 Group Version ID Code/EDIFACT Message Version and Release Number (selected by default)
Note: If you are using a generated map name (If Map Name Mode is set to Generate from data), the Sterling B2B Integrator tries to generate and match the following maps:
  • First, it tries to generate and match the map in the primary name format (replacing the values that are selected for the corresponding value in the message).
  • Second, it tries to generate and match the First Backup Name.
  • Third, it tries to generate and match the Second Backup Name.
  • Fourth, if there is not an existing map that matches the names generated in steps 1-3, an error is generated.

Only occurs if Generate an error if no matching map is found is set to Yes.

Second Backup Name Format
The second backup name format to use when generating a map name. The system allows for two alternatives if the Primary Name Format is not found—checking for the First Backup Name Format and then, if that is not found, checking for the Second Backup Name Format. Optional.

Select from:

  • SEC Code
  • Receiving DFI Identification
  • Originating DFI Identification
  • Standard contained in addenda
  • X12 Transaction Set /EDIFACT Message Type
  • X12 Group Version ID Code/EDIFACT Message Version and Release Number
Note: If you are using a generated map name (If Map Name Mode is set to Generate from data), the Sterling B2B Integrator tries to generate and match the following maps:
  • First, it tries to generate and match the map in the primary name format (replacing the values that are selected for the corresponding value in the message).
  • Second, it tries to generate and match the First Backup Name.
  • Third, it tries to generate and match the Second Backup Name.
  • Fourth, if there is not an existing map that matches the names generated in steps 1-3, an error is generated.

Only occurs if Generate an error if no matching map is found is set to Yes.

Generate an error if no matching map is found
Specifies whether to generate an error if the map name selected is not found. Valid values are Yes (default) and No.
Note: Only displayed if Map Name Mode is set to Generate from data.

In the Confirm page, verify the settings and click Finish to save the configurations for the envelope.