ACH Exception Reporting - Automated Clearing House (ACH) Reference Guide

About ACH Exception Reporting

Use the ACH Exception Report service to request and display summary and detailed information for ACH batches with recurring payments and errors found during processing.

ACH Exception Report Selection Page

ACH Exception Report Selection

Use this page to set options for generating an ACH Exception Report with ACH batches that include recurring payments and errors found during processing.

To help you efficiently identify information for the report, you can search for one or more specific ACH companies by filtering the list by batch code or batch name.

Fields

Field Name Description

Header section (not labeled)

Field Name Description

User, date, and time Identifier for the user logged on to the system, the current date, and the current time

Search section

Available Companies Drop-down selection list of ACH companies to which you have permission

Filter By Batch Code Limits the display of batches to those associated with this batch code. Maximum 12 alphanumeric characters

Filter By Batch Name Limits the display of batches to those associated with this batch name. Maximum 12 alphanumeric characters. The system filters the displayed batch list by the first character of the batch name.

Available Recurring

Batch section Batches available for reporting that match your search criteria for the selected company. Displays only for corporate users, not bank users

Company ID Identifier for the ACH Company

Batch Identifiers for the batches you are permitted to access Batch Name Name for the batch

Report Criteria section

Type of Date Drop-down selection list of the types of dates you can use to filter the report. Options are:

• Activation - date the batch was activated

• Effective Entry Date - date the bank posts the transactions to customer accounts

The default is Effective Entry Date.

From Date and To Date Range of dates to display on the ACH Exception Report. The From date must be the same as or before the To date. You can enter the date manually or click the calendar to select a date.

Exceptions Reasons Drop-down selection list of reasons why batches with recurring payments had errors. Options are:

• Invalid Permissions

• Limits Error

• Possible Duplicate Error

• Invalid State Error

• System Error

• Other Errors Characteristics

section

Group By Drop-down selection list to specify how you want to group batches on which you are reporting. Options are:

ACH Exception Reporting

Buttons

Button Description

Search Identifies ACH batches created for the ACH company selected from the Available Companies drop-down selection list

Select All Activates all batches displayed in the Available Recurring Batches section so you can include them on an ACH exception report Calendar Displays calendar for you to select range of dates for which you

want to generate an ACH report

Submit Displays the ACH Exception Report page with the information you requested for recurring payments and errors found during

processing

Clear Removes entries from fields and displays default values

ACH Exception Report Page

ACH Exception Report Page

Use this page to review

• Summary information for batches with recurring payments that did not process correctly when activation was automatically run.

• Descriptions of details that caused errors in the batches. You cannot change

information on this page.

The ACH Exception Report page provides the total number of batches and the debit and credit items and amounts. The report is sorted by batch ID within a group.

If the system modifies the effective entry date for a batch, the date is highlighted and the following message displays:

Highlighted Eff Entry Date indicates a system modification

For information about permitting corporate users to perform recurring payments, see Chapter 2: ACH Settings.

Fields

Field Name Description

Header section (not labeled)

User, date, and time Identifier for the user logged on to the system, the current date, and the current time

Bank Name Name of the bank associated with the report information Report Summaries

Type of date/report

date Type of date for the report (Activation or Effective Entry) and the date the report was generated

Company Identifier for the ACH Company associated with the batch Company Name Name for the ACH Company associated with the batch

Batch Identifier for the batch

Batch Name Identifier for the batch name

Tran Type Identifier for the type of transaction in the batch composed of Standard Entry Class (SEC) codes and transaction formats Eff Entry Date Date the bank posts the transactions to customer accounts. The

value in this field appears in the Effective Entry Date field on the ACH Header record (5 record).

Debit Total number of active debit entries in the batch and the total monetary amount for the active debit entries

Credit Total number of active credit entries in the batch and the total monetary amount for the active credit entries

Error Details section Descriptions of the errors that caused the batch with recurring payments to fail during the automatic activation process. Bank users can view exceptions related to one or more corporate customers.

Corporate users can view errors related to one or more ACH companies.

ACH Exception Reporting

Buttons

Button Description

+ -- Expand/Collapse icon. Plus sign (+) expands the Error Detail section of the page, and minus sign (-) closes the Error Detail section of the page

Return to ACH Exception Report Selection Page

Displays the ACH Exception Report Selection page

Appendix A: ACH Transaction Type Codes

Transaction Type Codes Table

The following table lists the transaction type codes delivered with the ACH product.

Code Addenda Description

CBR+CO Required Corporate cross-border payment, credits only CBR+DO Required Corporate cross-border payment, debits only

CCD+CD Allowed Cash concentration or disbursement, credits and debits CCD+CO Allowed Cash concentration or disbursement, credits only CCD+DO Allowed Cash concentration or disbursement, debits only CCDCD No Cash concentration or disbursement, credits and debits CCDCO No Cash concentration or disbursement, credits only CCDDO No Cash concentration or disbursement, debits only PAYCO No Prearranged payment and deposit, credits only PBR+CO Required Consumer cross-border payment, credits only PBR+DO Required Consumer cross-border payment, debits only

PPD+CD Allowed Prearranged payment and deposit, credits and debits PPD+CO Allowed Prearranged payment and deposit, credits only PPD+DO Allowed Prearranged payment and deposit, debits only PPDCD No Prearranged payment and deposit, credits and debits PPDCO No Prearranged payment and deposit, credits only PPDDO No Prearranged payment and deposit, debits only RCKDO No Represented check entries, debits only

SBACO Required Small business administration, credit only TAXCO Required Cash concentration or disbursement, credits only TELDO No Telephone-initiated entry, debit only

TELCO No Telephone-initiated entry, credit only (used only for reversals)

Code Addenda Description

WEB+DO Allowed Internet-initiated entry, debits only

Note: The PAYCO and TAXCO transaction type codes are available only for the

Consolidated Payments product. For more information, see the Consolidated Payments

Reference Guide.

Confidential and Proprietary ACH File Formats

Appendix B: ACH File Formats

About ACH File Formats

This Appendix contains the ACH file formats that the ACH product supports for batch transactions.

About ACH File Formats

The ACH product uses the file record formats to

• Build ACH files

• Validate import and pass-thru ACH files.

Cutoff-Generated NACHA File Formats

Each ACH file contains several different types of records. Each record contains specific information for the ACH file. The ACH record types are:

• File header record - Also known as a 1 record. Each ACH file must contain only one file header record. However, if the ACH file format setting for the leadbank is Single File per Leadbank (Separate Customer Files), the ACH file must contain one file header record for each customer.

• Batch header record - Also known as a 5 record. An ACH file must contain at least one batch header record. For each batch header record, the ACH file must contain one corresponding batch control record.

• Entry detail record - Also known as a 6 record. The entry detail records in an ACH file are grouped within a batch header record and a batch control record.

Each batch in an ACH file can contain one or more entry detail records.

• Addenda record - Also known as a 7 record. The ACH file can contain only one addenda record for each entry detail record. Each addenda record must follow its associated entry detail record.

• Batch control record - Also known as an 8 record. An ACH file must contain one batch control record for every batch header record.

• File control record - Also known as a 9 record. Each ACH file must contain only one file control record. However, if the ACH file format setting for the leadbank is Single File per Leadbank (Separate Customer Files), the ACH file must contain one file control record for each customer.

If you want to export a NACHA file, the resulting file is a standard NACHA formatted file that you can import back into the system using ACH Import.

Record Size

The system adds one carriage return (Hex OD) and one line feed (Hex OA) to the end of

every

record in an ACH file, which causes every record in the ACH file to be 96 characters in length.

The bank must remove these extra characters.

Record Formats

The ACH product supports the following record formats. These formats conform to the formats defined in the 2001 NACHA ACH Rules Guide. The supported record formats are:

• File Header Format (1 record)

• Standard Batch Header Format (CCD, CTX, PPD, RCK, WEB)

• Cross-Border Batch Header Format (CBR and PBR)

• CBR Entry Detail Format

• CCD Entry Detail Format

• CTX Entry Detail Format (Pass-Thru Only)

• PBR Entry Detail Format

• PPD Entry Detail Format

• RCK Entry Detail Format

• WEB Entry Detail Format

• Standard Addenda Format (CCD, CTX, PPD, WEB)

• Cross-Border Addenda Format (CBR and PBR)

• Batch Control (Trailer) Format (8 record)

• CSV File Format Sample (9 record)

• NACHA File Report Sample

Consolidated Payments

The system uses ACH file formats to process payment requests from the Consolidated Payments product. For more information, see the Consolidated Payments Reference Guide.

Corporate Trade Exchange (CTX)

The system supports the Corporate Trade Exchange (CTX) SEC code only for pass-thru files. For more information about pass-thru files, see the ACH User Guide.

Mandatory and Required Fields

For each record format, the information in the Required column indicates whether the

field is:

ACH File Formats

Confidential and Proprietary ACH File Formats

• Required - The record should contain this field. If a required field is missing or incorrect, the ACH operator does not fail the ACH file, but the receiving depository financial institution (RDFI) could reject the record.

• Optional - The record does not have to contain this field.

CSV File Format

The CSV File format is a comma-separated value file. This file format allows you to easily sort and manipulate bank data. If you export a CSV file, you can then import the resulting file back into the system using ACH Import, provided you set up a map

definition for CSV files in the ACH Map Definition service. For information see Chapter 9: ACH Map Definition.

File Header Format

Following is the format for ACH header records.

Field Length Position Required Description

Record Type Code

1 01-01 Mandatory Indicates the record is the file header.

ACH File Creation - When the system builds the ACH file, it sets the value in this field to 1.

Validation - For import and pass-thru, this field must contain the value 1. Otherwise, the system issues an error.

Priority Code

2 02-03 Required Indicates the processing priority for the ACH file.

ACH File Creation - When the system builds the ACH file, it sets the value in this field to 01.

Validation - For import and pass-thru, this field must contain the value 01. Otherwise, the system issues an error.

Immediate Destination

10 04-13 Mandatory Indicates the immediate destination for the ACH file.

ACH File Creation - When the system builds the ACH file, it sets the value in this field to the value in the Immediate Destination field on the ACH Settings page.

Validation - For import, there is no validation.

For pass-thru, this field must contain a value.

Otherwise, the system issues a warning.

Field Length Position Required Description

Immediate

Origin 10 14-23 Mandatory Indicates the immediate origin for the ACH file.

ACH File Creation - When the system builds the ACH file, it sets the value in this field to either the

• End point code (if the corporate customer is associated with an end point), or

• Value in the Immediate Origin field on the ACH Settings page.

Validation - For import, there is no validation.

For pass-thru, this field must contain a value.

Otherwise, the system issues a warning.

File Creation Date

6 24-29 Mandatory Indicates the date the ACH file was built.

ACH File Creation - When the system builds the ACH file, it sets the value in this field to the current system date using the YYMMDD format.

Validation - For import and pass-thru, this field must contain a valid date using the YYMMDD format. Otherwise, the system issues a warning for import and an error for pass-thru.

File Creation Time

4 30-33 Optional Indicates the time the ACH file was built.

ACH File Creation - When the system builds the ACH file, it sets the value in this field to the current system time using the HHMM format.

Validation - For import and pass-thru, this field must contain a valid time using the HHMM format. Otherwise, the system issues a warning for import and pass-thru.

File ID Modifier

1 34-34 Mandatory Indicates the system-assigned identifier for the leadbank. This identifier increments

sequentially during the processing day from A through Z, and then, from 0 through 9.

ACH File Creation - When the system builds the ACH file, it sets the value in this field to the incremental identifier assigned to the leadbank.

Validation - For import and pass-thru, this field must contain a value of A through Z or 0 through 9. Otherwise, the system issues a warning for import and an error for pass-thru.

Rule: The value A through Z must be in uppercase text.

Record Size

3 35-37 Mandatory Indicates the number of characters contained in the record.

ACH File Creation - When the system builds the ACH file, it sets the value in this field to 094.

Validation - For import and pass-thru, this field

ACH File Formats

Confidential and Proprietary ACH File Formats

Field Length Position Required Description

Blocking

Factor 2 38-39 Mandatory Indicates the number of physical records within a block.

ACH File Creation - When the system builds the ACH file, it sets the value in this field to 10.

Validation - For import and pass-thru, this field must contain the value 10. Otherwise, the system issues a warning for import and an error for pass-thru.

Format Code

1 40-40 Mandatory This field is reserved for future format changes.

ACH File Creation - When the system builds the ACH file, it sets the value in this field to 1.

Validation - For import and pass-thru, this field must contain the value 1. Otherwise, the system issues a warning for import and an error for pass-thru.

Immediate Destination Name

23 41-63 Optional Indicates the immediate destination name for the ACH file.

ACH File Creation - When the system builds the ACH file, it sets the value in this field to the value in the Destination Name field on the ACH Settings page.

Validation - For import and pass-thru, there is no validation.

Immediate Origin Name

23 64-86 Optional Indicates the immediate origin name for the ACH file.

ACH File Creation - When the system builds the ACH file, it sets the value in this field to the value in the Originator Name field on the ACH Settings page.

Validation - For import and pass-thru, there is no validation.

Reference

Code 8 87-94 Optional Indicates information that is relevant to the originator.

ACH File Creation - When the system builds the ACH file, it sets the value in this field to the value in the Reference Code field on the ACH Settings page.

Validation - For import and pass-thru, there is no validation.

Standard Batch Header Format

Following is the format for standard ACH batch header records (CCD, CTX, PPD, RCK,

and WEB).

Field Length Position Required Description

Record Type

Code 1 01-01 Mandatory Indicates the record is a batch header. This field must contain the value 5.

ACH File Creation - When the system builds the ACH file, it sets the value in this field to 5.

Validation - For import and pass-thru, this field must contain the value 5. Otherwise, the system

• Skips the following records until the next 5 record is found for import

• Issues an error for pass-thru.

Service

Class Code 3 02-02 Mandatory Indicates the service class code for the batch.

This field must contain one of the following values:

• 200 - batch contains credits and debits

• 220 - batch contains only credits

• 225 - batch contains only debits

ACH File Creation - When the system builds the ACH file, it uses the transaction type from the batch or payment request to determine the value for this field.

Validation - For import and pass-thru, this field must contain one of the valid values and must match the value in the Service Class Code field in the batch control record (8 record). Otherwise, the system

• Skips the entire batch and issues an error for import

• Issues an error for pass-thru, which fails the file.

Company Name

16 05-20 Mandatory Indicates the ACH company name associated with the batch or payment request.

ACH File Creation - When the system builds the ACH file, it sets the value in this field to the ACH company associated with the batch or payment request.

Validation - For import there is no validation. For pass-thru this field must contain a value. Otherwise, the system issues an error.

Company Discretionary Data

20 21-40 Optional Indicates additional information that describes the batch.

ACH File Creation - When the system builds the ACH file, it sets the value in this field to the value in the Company Discretionary Data field from the batch.

ACH File Formats

Confidential and Proprietary ACH File Formats

Field Length Position Required Description

Company

Identification 10 41-50 Mandatory Indicates the ACH company ID associated with the batch or payment request.

ACH File Creation - When the system builds the ACH file, it sets the value in this field to the value in the Company field from the batch or payment request.

Validation - For import, the system verifies that the value in this field is a valid company identifier in the system and that it matches the value in the Company Identification field

In document Automated Clearing House (ACH) Reference Guide (Page 181-200)