ACH Inbound File-Level Envelope Properties, Document Level

Edit online

The following table describes ACH inbound File-Level envelope properties at the document level:

Field

Description

* Destination Identification

Routing number of the ACH Operator or receiving point to which the message is being sent. Required.

* Origin Identification

Routing number of the ACH Operator or sending point that is sending the message. Required.

Validate immediate origin as

Type of validation for the Origin Identification field. Valid options are:

Routing number
Alphanumeric

Required.

* Destination Name

Name of the ACH or receiving point for which the message is destined. Optional.

* Origin Name

Name of the ACH Operator or sending point that is sending the message. Optional.

Perform duplicate File ID Modifier check

When receiving an ACH File Level envelope, will duplicate File ID checking be performed. Valid values are Yes and No. Required.

Maximum age of File ID Modifier History Record in days

Maximum days to retain a history of File ID Modifier to use for duplication determinations. Valid value is nine standard characters. Optional.

Stop processing of a file on a translation or EDI validation error

Provides an option to process the entire transaction within the file when a component of the file errors out. Valid values are Yes and No. Required.

Check interchange for duplicate batches (ODFI + batch number)

Verifies if there is a unique batch number processed for a given ODFI in the ACH Interchange. Valid values are:

Yes (default)
No

Required.

Perform sequence checking on trace numbers

Whether to compare the sequence of trace numbers in the data with the Trace Number parameter for this envelope. Valid values are Yes and No.

Required.

Invoke a business process for file-level compliance errors

Required. Valid values are Yes and No.

Invoke a business process for batch-level compliance errors

Required. Valid values are Yes and No.

Error Business Process Name Mode

How to determine the business process name to use if there were errors in the compliance check. Required. Valid values are:

Specify (specifying a Business Process name—this is the default)
Generate from data (generating a Business Process name from the data—this is useful if you want to share across envelopes)

Note: Only displayed if Invoke a business process for file-level compliance errors or Invoke a business process for batch-level compliance errors is set to Yes. If you select this option, you must select at least one parameter for Primary Name Format.

Business Process for Non-Compliant Documents

Select the business process for the non-compliant documents from the list. Optional.

Note: Only displayed if Error Business Process 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 error business process name. Optional.

Select from:

Destination Identification (selected by default)
Destination Name (selected by default)
Origin Identification (selected by default)
Origin Name (selected by default)

Note: If you are using a generated error business process name (If Error Business Process Name Mode is set to Generate from Data), the Sterling B2B Integrator tries to generate and match the following business process:

First, it tries to generate and match the business process 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 business process that matches the names generated in steps 1-3, an error is generated.

Only occurs if Generate an error if no generated business process name exists in the system is set to Yes.

First Backup Name Format

The first backup name format to use when generating an error business process 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:

Destination Identification (selected by default)
Destination Name
Origin Identification (selected by default)
Origin Name

First, it tries to generate and match the business process 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 business process that matches the names generated in steps 1-3, an error is generated.

Only occurs if Generate an error if no generated business process name exists in the system is set to Yes.

Second Backup Name Format

The second backup name format to use when generating an error business process 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:

Destination Identification
Destination Name
Origin Identification
Origin Name

First, it tries to generate and match the business process 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 business process that matches the names generated in steps 1-3, an error is generated.

Only occurs if Generate an error if no generated business process name exists in the system is set to Yes.

Generate an error if no generated business process name exists in the system

Specify whether to generate an error if there is no match to the generated business process name in the system. Valid values are Yes (default) and No.

Note: Only displayed if Error Business Process Name Mode is set to Generate from Data.