ACH
You may click the Cash Management tab at the top of any Business Online Banking page followed by the ACH navigation link to create ACH transaction sets and templates, import NACHA files, manage active ACH sets, manage ACH templates, view processed ACH sets, and request ACH reports as described in this section.
Note: Some ACH functions may not be available, depending on how your financial institution configures the business online banking system.
To better understand how ACH functions work, introductory data is provided in the following sections:
- ACH Terms – Describes the basic terms that apply to ACH functions.
- ACH Types – Describes each ACH type that a business, credit union, or subsidiary company may use to create an ACH transaction set or template.
- ACH Transaction Files – Explains the data included in each of these files containing detailed transaction records.
- ACH Amount Files – Explains the data included in each of these files containing transaction amount records.
- Status Values for ACH Transaction Sets – Describes the status values that may be assigned to an ACH set during each step to approve, release, process or reject the set, etc.
- ACH Errors – Describes each error message that may occur when you attempt to approve or release an ACH set (refer to the Approving & Releasing an ACH Set section).
- Import NACHA File Errors – Describes the errors can occur when a NACHA file is imported.
- Using the ACH Transaction Reversal Feature – Describes various rules and considerations that apply when you create an ACH reversal set or template (refer to Reversing an ACH Set and Reversing an ACH Template).
- ACH Export Files – Describes the ID information used to identify export files created in the .csv or NACHA format to back up data in ACH sets or templates.
All of the ACH functions are described in the following sections:
- Manage Active ACH Transaction Sets
- Manage ACH Transactions
- Manage ACH Templates
- View Processed ACH Sets
- Request ACH Reports
- Incoming ACH

Before you use the ACH functions, it is helpful to understand the following terms:
- ACH – The Automated Clearing House (ACH) is an Electronic Funds Transfer (EFT) network that processes large volumes of credit and debit transactions formatted into ACH transaction sets.
- ACH Transaction Set – A group of ACH transactions that have the same attributes. For example, a Point of Purchase set contains POP or Point-of-Purchase transactions. You may either create an ACH transaction set from an existing ACH template or individually to send once to your financial institution. If you create ACH sets from a template, you do not need to enter detailed information each time a set is released to your financial institution for processing.
- ACH Template – Stores ACH transactions that may be sent once or repeatedly. Each template can be added and/or edited for changes in amounts, account numbers, etc.
- Transaction Set Approval – Depending on how your financial institution configures the business online banking system:
-
An ACH transaction set may be released immediately to your financial institution,
OR - An ACH set may require the approval of one or two business online banking users before it is released.
-
An ACH transaction set may be released immediately to your financial institution,
- NACHA File – A file containing ACH transaction sets and templates formatted for submission to the ACH network.

All ACH types (defining different types of ACH transaction sets and templates) are strictly regulated by the Federal Reserve to identify transactions submitted for specific purposes. Each ACH type is governed by NACHA rules with a specific format and transaction codes associated with the file type. The ACH types provided by the Business Online Banking system correspond to Standard Entry Class (SEC) codes in the NACHA rule book.
Note: The ACH types of ARC, BOC and POP can only be created using the Import NACHA feature.
- Accounts Receivable – This “ARC” type may be selected to convert check(s) received through the mail into electronic transaction(s).
- Back Office Conversion – Identifies an ACH set or template containing a single transaction for a check or share draft provided by the receiver at the point of purchase that is used by the originator as a source document for the receiver’s routing number, account number, check serial number, and dollar amount. BOC files can only be created by reading a customer’s check with an image reading device.
- To/from Corporate Accounts – This basic “CCD” type may be used to create ACH transactions to/from corporate accounts.
- Child Support – May be used to submit garnished child support payments through the ACH network.
- Federal Taxes – ACH transactions created using this “FED” transaction type may be used to pay corporate Federal Taxes using.
- State Taxes – ACH transactions created using this transaction type may be used to pay corporate State Taxes.
- Corporate Trade Exchange – This “CTX” type may be used to import and pass multiple addenda records using one ACH transaction in accordance with ANSI ASC X12.5 and X12.6 syntax.
- Point of Purchase – Applies to transactions initiated at the point of purchase, that is, POP or Point-of-Purchase transactions.
- To/From Personal Accounts – This “PPD” type may be used to create transactions to/from personal accounts (also called Prearranged Payment and Deposit or PPD transactions).
- Re-Presented Checks – This “RCK” type may be used for returned check items.
- Consumer Initiated Telephone – This “TEL” type applies to transactions authorized over the telephone.
- Consumer Initiated Web – Applies to “WEB” type transactions authorized over the Internet.

You may create an ACH transaction file using Microsoft® Excel® or another similar spreadsheet program to import detailed transaction records into an ACH set or template. A standard ACH transaction code is included in each record to identify the type of transaction. The valid codes for the indicated account types are listed below:
Account Type |
ACH |
Description |
---|---|---|
Checking, NOW, share draft |
22 |
Automated Deposit |
27 |
Automated Withdrawal |
|
Savings |
32 |
Automated Deposit |
37 |
Automated Withdrawal |
|
General Ledger* |
42 |
Automated GL Credit |
47 |
Automated GL Debit |
|
Loan |
52 |
Automated Credit |
55 |
Automated Loan Account Debit – Reversals Only |
Note: General Ledger account type access is not available to each business or credit union; it must be assigned by an administrator.
Use Excel or another spreadsheet program to enter the following data into the cells in each row of a spreadsheet in the indicated order. Do not add headings for the cells. The file must be saved in a CSV (comma delimited) format for import into Business Online Banking.
Field |
Description |
---|---|
Name |
Maximum of 22 characters for the name of the receiving party |
Account Number |
Maximum of 17 characters for the receiving account number |
Routing Number |
Maximum of 9 characters identifying the routing and transit number for the financial institution with the receiving account Note: If the routing number begins with a leading zero (0), make sure the cell format is set to ‘test’ or a similar format to retain the leading zero. |
ID |
Maximum of 15 characters for the identifying number of the receiving party |
Amount |
Transaction amount in the number format with two decimals |
Transaction Code |
A two-character ACH code listed in the previous table. |
Addenda Indicator |
Enter Y if addenda information is specified in the next field. |
Addenda Information |
If Y is entered in the previous field, enter a maximum of 80 characters of addenda information. |
Note: The ACH transaction file format does not support the Payment Type Code (single vs. recurring) for WEB and TEL transaction sets. Each WEB and TEL set must be edited after the transaction file is imported into Business Online Banking to enter a value for the Payment Type Code field.

You may also create an ACH amount file using Microsoft Excel or another similar spreadsheet program to update the transaction amounts in an ACH set or template. Instead of manually changing transaction amounts, you can update the amounts for all transactions in a set or template, or update some of the transactions by importing a file containing the ACH ID number, amount, and optional account number for each transaction.
Enter the following data into the cells in each row of a spreadsheet in the indicated order. Do not add headings for the cells. The file must be saved in a CSV (comma delimited) format for import into Business Online Banking.
Field |
Description |
---|---|
ID |
Maximum of 15 characters for the identifying number of the receiving party |
Amount |
Transaction amount in the number format with two decimals |
Account Number |
Maximum of 17 characters for the receiving account number (optional) |
The comma-delimited file below illustrates an ACH amount file that may be used to update the amounts in three transactions. Each line in the file contains two or three fields: the ID, amount, and account number (optional).
555333,356.97
32698,103.25,111222
32698,160.03,222666

After an ACH set is created, the business online banking system assigns a different status to the set during each step to approve, release, process it, etc. Each status is described below:
Transaction Set Status |
Description |
---|---|
Unapproved |
Assigned to each newly-added ACH set that can be edited on the business online banking system before it is sent to your financial institution. |
Part-Approved |
One approval of two required approvals has taken place. |
Approved |
All required approvals have taken place. |
Released |
The ACH set was released to your financial institution for processing. After a set is released, the set cannot be edited. |
Processing |
Your financial institution has started to process the ACH set, however items still exist that have not yet been included in a file sent to the ACH Operator. |
Processed |
All transactions within the ACH set have been completely processed by your financial institution. The set is no longer available for processing; it has been moved to a history file and is available through ACH History Reports. |
Rejected |
Your financial institution has rejected the ACH set. The set will remain active until it is restored or the rejection is confirmed. |
Confirmed Rejected |
The Rejected status for the ACH set has been confirmed, and the set has been moved to a history file and is available through ACH History Reports. The set is no longer available for processing. |

One of the following error messages may be returned when you attempt to approve or release an ACH set (or batch).
Error |
Corrective Action |
---|---|
This would exceed your company's daily withdrawal limit. |
A daily withdrawal limit is assigned by your financial institution. Contact a representative to receive authority to raise your daily limit. You cannot release the ACH set until your daily limit is modified. |
This would exceed your company's deposit item limit. |
A Transaction limit defined for your company has been exceeded. Go to the Company Set up page described in the Editing Company Setup Data section to review transaction limits. |
This would exceed your company's batch deposit limit. |
A Total ACH limit defined for your company has been exceeded. Go to the Company Set up page described in the Editing Company Setup Data section to review the transaction set limits. |
Batch contains no valid Transactions. |
No valid transactions are in the batch or ACH set you selected. |
An Effective Date cannot be in the past. |
NACHA rules do not allow back dated items to be processed without approval. You cannot submit an ACH set with an effective date in the past. |
An invalid routing number is entered. |
There is an invalid routing and transit number assigned to a transaction within the ACH set. Select Edit in the Action column to review the transaction information. |
This batch cannot be released at this time because there is not sufficient time to process the set before the submitted effective date. |
Your financial institution sets a deadline for daily processing. The effective date for each batch or ACH transaction set determines when the ACH set must be processed. This error displays if you attempt to release a set after the daily deadline with an effective date before the number of days in advance required by your financial institution. Change the effective date of the set. |

The following errors can occur when a NACHA file is imported as described in the Importing a NACHA File section. Each error message identifies the line (n) in the file where the error occurred. Correct any errors using the software that created the file; unless an error indicates the software used to create the file does not prepare a NACHA compliant file. If the file is not compliant, you cannot use Business Online Banking to import the file.
Error Message |
Cause |
---|---|
Error in line n: Not an ACH file |
The identified line is more than 94 characters long. |
Error in line n: |
Indicates a zero-byte file. |
Error in line 1: Not an ACH file |
The first line or line “1” was found somewhere other than the first line in the file. |
Error in line n: Service Class Code must be numeric |
Service Class Code in line “5” is not numeric. |
Error in line n: Settlement date not found. |
Settlement Date in line “5” is not numeric. |
Error in line n: ODFI must be numeric |
ODFI in line “5” is not numeric. |
Error in line n: ACH Set Number must be numeric |
ACH set number in line “5” is not numeric. |
Error in line n: Unexpected ‘5’ record |
“5” record encountered other than after a “1” record or an “8” record. |
Error in line n: Transaction code must be numeric |
Transaction Code in line “6” is not numeric. |
Error in line n: Unexpected ‘6’ record. |
“6” record found outside of an ACH set. |
Error in line n: Addenda Type Code must be numeric. |
Addenda Type Code in line “7” is not numeric. |
Error in line n: Unexpected ‘7’ record |
Addenda “7” record found other than where expected. |
Error in line n: Unexpected ‘8’ record. |
“8” record found other than where expected. |
Error in line n: Not an ACH file |
“9” record found other than where expected. |
Error in line n: Not an ACH file |
Blank line found, except after the “9” record. |
Error in line n: Not an ACH file |
First line starts with an invalid character. |
Error in line n: Unexpected initial char: ‘X’ |
Any other line (other than line “1”) starts with an invalid character. |
Error in line n: File control record not found |
End-of-file reached without reaching a “9” record. |

This feature allows you to create ACH sets or templates that reverse the following types of transactions in Cash Concentration or Disbursement (CCD) sets (i.e., To/From Corporate Accounts), CCD templates, Prearranged Payment and Deposit Entry (PPD) sets (i.e., To/From Personal Accounts), or PPD templates.
Transaction Code |
Description |
---|---|
22 |
Demand Credit Record – Automated Deposit |
27 |
Demand Debit Record – Automated Payment |
32 |
Savings Account Credit Record – Automated Deposit |
37 |
Savings Account Debit Record – Automated Payment |
42 |
Financial Institution General Ledger Credit Record – Automated Deposit |
47 |
Financial Institution General Ledger Debit Record – Automated Payment |
The following rules apply to this feature:
- It can only be used to reverse transactions in CCD sets, CCD templates, PPD sets, or PPD templates. No other ACH types are supported.
- It can only be used to reverse transactions in the ACH types listed above (CCD & PPD). For example, if an ACH set contains a deposit to a loan account, the loan transaction will not be reversed.
- Addenda are not copied from the original ACH set or template to the reversal set/template.
- A reversal ACH set can be created from an ACH set in an Unapproved, Approved, or Processed status. A reversal set cannot be created from a set that is in the Released, Processing, or Rejected status.
Note: This feature does not provide the ACH reversal capability defined in the ACH Rules (Section III Functional Responsibilities, Chapter IV Reversals, Reclamations, and ODFI Requests for Return). The Reversal feature cannot be used to create an ACH set that will reverse an entry or file of entries introduced into the ACH system, as described in the ACH Rules. The ACH Rules book contains ACH Operating Rules for participating financial institutions and companies.

Export files may be created in the .csv or NACHA format to provide backup copies of data in ACH sets or templates. When an export file is created in either format, the file name includes ID information in the following order:
- Name of the ACH set or template containing data in the file
- Current date and time in YYYYMMDDHHMMSS format
- A “type indicator”: ‘T’ for template or ‘B’ for an ACH transaction set
- File extension (i.e., .csv for CSV format files or .txt for NACHA format files)
For example, an exported CSV file for the Payroll template is named:
Payroll_20110615171342_T.csv
A business or credit union can create an archive of Payroll sets and templates to include the following files:
Payroll_20110615171342_B.csv
Payroll_20110615171342_T.csv
Payroll_20110616091543_B.csv
Payroll_20110616091543_T.csv
Payroll_20110617121947_B.csv
Payroll_20110617121947_T.csv
The naming convention for the exported files automatically sorts the files by name, date, and “type” (ACH transaction set vs. template).
Note: When a .csv file is opened automatically using Microsoft Excel, the leading zeroes are stripped from numbers such as ABA routing numbers, resulting in invalid ABA numbers when the file is saved. If your Excel program opens .csv files automatically, click the Save button and save the file before opening it. In addition, be careful when you use Excel to edit and save a .csv file. In this case, you may need to restore leading zeroes to ABA routing numbers in the file.