Non EDI Based ACH Application

Edit online

If you select the ACH Message Category as Non EDI Based ACH Application, the pages displayed are as follows:

Field: Description
Company/Originator Identification: Type the company identification. Required.
DFI Account Number (For lookup only, except ENR and TRX): The Depository Financial Institution account number.
Note: For lookup only, except ENR and TRX.

The pages displayed for the SEC code ACK, CCD, CIE, DNE, MTE, POS, PPD, SHR, 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.

Company Entry Description

The Originator establishes the value of this field to provide a description of the purpose of the entry to be displayed to the receiver. Required.

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.

Company Name

Type the name of the company. Required.

Entry Detail Map Name Mode

Mode in which to specify the map to use to perform generation of the Entry Detail record(s). Required. Valid values:

Specify
Generate from data

Name of map to be used for generation of Entry Detail record(s)

Select the Sterling B2B Integrator or WebSphere® Transformation Extender map to be used to perform generation of the Entry Detail record(s). The map must already be checked in. Optional

Primary Name Format

Check boxes to instruct what information to include when generating the Entry Detail record(s). Optional.

Select from:

SEC Code (selected by default)
Receiving DFI Identification (selected by default)
DFI Account Number (For lookup only, except ENR and TRX) (selected by default)
Originating DFI Identification (selected by default)
Company/Originator Identification (selected by default)

Note: If you are using a generated map name (If Entry Detail 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 an Entry Detail record. 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 (selected by default)
DFI Account Number (For lookup only, except ENR and TRX)
Originating DFI Identification (selected by default)
Company/Originator Identification

Note: If you are using a generated map name (If Entry Detail 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 an Entry Detail record. 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 (For lookup only, except ENR and TRX)
Originating DFI Identification
Company Identification

Note: If you are using a generated map name (If Entry Detail 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 Entry Detail Map Name Mode is set to Generate from data.

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:

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.

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

The pages displayed for the SEC code ADV, ARC, BOC, CTX, POP, RCK, TEL, TRC, and XCK 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 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 Entry Description

The Originator establishes the value of this field to provide a description of the purpose of the entry to be displayed to the receiver. Required.

Company Discretionary Data

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

Company Name

Type the name of the company. Required.

Entry Detail Map Name Mode

Mode in which to specify the map to use to perform generation of the Entry Detail record(s). Required. Valid values:

Specify
Generate from data

Name of map to be used for generation of Entry Detail record(s)

Select the Sterling B2B Integrator or WebSphere Transformation Extender map to be used to perform generation of the Entry Detail record(s). The map must already be checked in. Optional

Primary Name Format

Check boxes to instruct what information to include when generating the Entry Detail record(s). Optional.

Select from:

SEC Code (selected by default)
Receiving DFI Identification (selected by default)
DFI Account Number (For lookup only, except ENR and TRX) (selected by default)
Originating DFI Identification (selected by default)
Company/Originator Identification (selected by default)

Note: If you are using a generated map name (If Entry Detail 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

Select from:

SEC Code (selected by default)
Receiving DFI Identification (selected by default)
DFI Account Number (For lookup only, except ENR and TRX)
Originating DFI Identification (selected by default)
Company/Originator Identification

Note: If you are using a generated map name (If Entry Detail 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

Select from:

SEC Code
Receiving DFI Identification
DFI Account Number (For lookup only, except ENR and TRX)
Originating DFI Identification
Company Identification

Note: If you are using a generated map name (If Entry Detail 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 Entry Detail Map Name Mode is set to Generate from data.

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.

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

The pages displayed for the SEC codes ATX, CBR, COR, IAT, and PBR are as follows:

Field

Description

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 Entry Description

The Originator establishes the value of this field to provide a description of the purpose of the entry to be displayed to the receiver. Required.

Company Discretionary Data

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

Company Name

Type the name of the company. Required.

Entry Detail Map Name Mode

Mode in which to specify the map to use to perform generation of the Entry Detail record(s). Required. Valid values:

Specify
Generate from data

Name of map to be used for generation of Entry Detail record(s)

Select the Sterling B2B Integrator or WebSphere Transformation Extender map to be used to perform generation of the Entry Detail record(s). The map must already be checked in. Optional

Primary Name Format

Check boxes to instruct what information to include when generating the Entry Detail record(s). Optional.

Select from:

SEC Code (selected by default)
Receiving DFI Identification (selected by default)
DFI Account Number (For lookup only, except ENR and TRX) (selected by default)
Originating DFI Identification (selected by default)
Company/Originator Identification (selected by default)

Note: If you are using a generated map name (If Entry Detail 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

Select from:

SEC Code (selected by default)
Receiving DFI Identification (selected by default)
DFI Account Number (For lookup only, except ENR and TRX)
Originating DFI Identification (selected by default)
Company/Originator Identification

Note: If you are using a generated map name (If Entry Detail 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

Select from:

SEC Code
Receiving DFI Identification
DFI Account Number (For lookup only, except ENR and TRX)
Originating DFI Identification
Company Identification

Note: If you are using a generated map name (If Entry Detail 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 Entry Detail Map Name Mode is set to Generate from data.

Entry Detail Transaction Code

Type the Entry detail transaction code. Value is 2 characters long. Required.

Note: Not displayed for the IAT SEC code.

Identification Number

Type the Identification Number. Optional.

Note: Not displayed for the IAT SEC code.

Receiving Company Name

Type the name of the Receiving company. Required.

Note: Not displayed for the IAT SEC code.

Is this a CBR, IAT, PBR, or cross-border COR entry?

Check if this envelope is intended to be processed as a CBR, PBR, or a cross-border COR entry.

Valid values are:

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

Note: 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:

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

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

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.

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

The pages displayed for the SEC codes ENR and TRX are as follows:

Field

Description

Company Discretionary Data

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

Item Type Indicator

This field indicates the type of items being truncated. Optional.

Note: Only displayed if the SEC Code selected is TRX.

Company Name

Type the name of the company. 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.

Entry Detail Transaction Code

Type the Entry detail transaction code. Value is 2 characters long. Required.

Identification Number

Type the Identification Number. Optional.

Receiving Company Name

Type the name of the Receiving company. Required.

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:

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

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

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.

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