ACH File Structure and Setup

An ACH file uses a precise format to guarantee transactional integrity.  Internally, an ACH file uses a single digit between 1 and 9 to indicate a type of entry in the file.

 

1

File Header

5

Batch Header

6

Batch Entry

7

Batch Entry Addenda

8

Batch Footer

9

File Footer

 

All information in an ACH file is created by ACH Universal based on either information in an imported file or on settings stored in ACH Universal to identify your company in the file.

 

If you need to modify any stored settings, see Account Setup

If you need to create a new account, see Creating An Account

 

File Header - 1

 

The file header contains information regarding an account's ACH transactions.  For example, if you create two ACH files, one each out of two different ACH Universal accounts, you will by definition have two ACH files.

 

Information contained in the file header includes:

Immediate Destination Code (Usually your bank's ABA)

Immediate Origin ID (Assigned by your bank to identify your company's ACH files. Usually federal tax ID)

Immediate Destination Name (Name of your bank)

Immediate Origin Name (Name of your company, as listed in bank records)

 

All this information comes from settings created during Account Setup.

 

Batch Header - 5

 

A batch creates a logical separation of transactions in an ACH file.  For any list of transactions, batches are separated by:

Date

Standard Class Entry Code

Origination Account (if desired)

 

There is no way to change the first two as they are a feature of the ACH format.  However, you can choose to separate batches by origination account if needed. See LINK Separating batches by origination account for more information.

 

There can be multiple batches per file, but there will always be a minimum of one batch.

 

Batch Entry - 6

 

A batch entry is simply one transaction. In order, a batch entry includes:

Transaction Code (identifying type of transaction)

Routing/ABA Number for transaction party

Account Number for transaction party

Amount of transaction

Name of transaction party

 

The first, Transaction Code, is automatically generated by ACH Universal based on the transaction.  The others are contained in file imports, either transaction or profile.

 

There can (and most likely will) be multiple batch entries per batch.

 

Batch Entry Addenda - 7

 

A batch entry addenda record, or addenda, is extra information on a transaction that may be necessary for the transacted party.  If you need to use an addenda, your bank or transaction party will inform you beforehand.  In PPD+/CCD+ format files, addenda records are limited to 1 per transaction.  The addenda can be a maximum of 80 characters.  In CTX files, there is no practical limit to the number of addenda records per transaction.

 

Batch Footer - 8

 

A batch footer denotes the end of a batch.

 

File Footer - 9

 

A file footer denotes the end of the file.  It contains information marking the file end and any padding needed to create proper file width.