ACH File Details

Standard Entry Class Codes

Each ACH application has a unique Standard Entry Class (SEC) Code that identifies a single ACH debit used by an Originator for the conversion of an eligible source document received via the U.S. mail or delivery service, at a lockbox location, or in person at a manned location for the payment of a bill. 

The SEC Code generally indicates:

  • The nature of the transaction as consumer or corporate in nature (i.e., whether the funds transfer affects a consumer account or a corporate account at the RDFI). 
  • Whether the transaction is single-entry or recurring.
  • The specific computer record format that will be used to carry the payment and payment-related information relevant to the application.

Commonly Used SEC Codes

SEC Code

ACH Application

Application Use

Debit / Credit

Consumer / Corporate

Authorization Requirements

ARC

Accounts Receivable Entries

A single ACH debit used by originator for the conversion of an eligible source document received via the U.S. mail or delivery service; at a lockbox location; or in person at a manned location for the payment of a bill.

Debit

Consumer to Corporate

Notification is required prior to acceptance of the check.

BOC

Back Office Conversion

A single ACH debit initiated by an originator based on an eligible source document provided at the point-of-purchase or at a manned bill payment location for subsequent conversion during back office conversion.

Debit

Consumer to Corporate

Notification is required prior to acceptance of the check.

CCD / CCD+

Corporate Credit or Debit

A single or a recurring ACH credit or debit originated to a corporate account. They are commonly used by Originators to pay vendors, concentrate funds from outlying accounts (cash concentration), to fund payroll, petty cash, or other disbursement accounts.

A CCD entry can contain a single addenda record to relay payment-related information.

Credit / Debit/Nonmonetary

Corporate to Corporate

Agreement required for transfers between companies; written authorization implied.

CIE

Customer Initiated Entries

A credit entry initiated by consumer through a bill payment service provider to pay bills.

Credit

Consumer to Corporate

Presumed agreement between consumer and company or paying agent.

CTX

Corporate Trade Exchange

A single or a recurring ACH credit or debit originated to a corporate account that supports up to 9,999 addenda records. They are commonly used in trading partner relationships because a full ANSI ASC X12 message or payment-related UN/EDIFACT information can be sent with the CTX entry.

Credit / Debit/Nonmonetary

Corporate to Corporate

Agreement required for transfers between companies; written authorization implied.

IAT

International ACH Transaction

An Entry that is part of a payment transaction involving a financial agency’s office that is not located within the territorial jurisdiction of the United States.

Credit / Debit

Corporate to Consumer/
Corporate to Corporate

for Consumer Credit Entries: oral/nonwritten 

for Consumer Debit Entries:  written

for Corporate Entries: agreement

POP

Point of Purchase

A single ACH debit initiated by an originator based on an eligible source document provided at a point-of-purchase or manned bill payment location.

Debit

Corporate to Consumer/
Corporate to Corporate

Notification prior to acceptance of the check and written authorization required.

POS

Point of Sale

Initiated at an electronic terminal using merchant issued physical card or other access device

Debit

Consumer

Written

PPD / PPD+

Pre-arranged Payment or Deposit

A single or a recurring ACH credit or debit sent by an originator to a consumer account to make or collect a payment, where authorization is obtained in writing.

Only one addenda record can be attached to each payment entry (the + denotes containing an addenda record)

Credit / Debit

Corporate to Consumer

Direct Deposit; Oral/Nonwritten; Direct Payments; Written

RCK

Re-presented Check Entries

Originators can re-present a check that has been processed through the check collection system as a paper or image item, and returned because of insufficient or uncollected funds 

Debit

Single Entry

Corporate to Consumer

Notification is required prior to acceptance of the check

TEL

Telephone Initiated Entries

A single or a recurring ACH debit that occurs when the consumer’s authorization for a transfer of funds is received orally via the telephone.

Debit

 

Corporate to Consumer

For Single, recorded oral authorization or written notice provided to the consumer confirming the oral authorization.*  For Recurring, a copy of the authorization must be provided to the consumer.

WEB

Internet-Initiated/Mobile Entries

Credit WEB Entries: A Person-to-Person entry transmitted on behalf of one natural person to another natural person, or between accounts belonging to the same natural person.

Debit WEB Entries: ACH entry initiated according to an authorization obtained via the internet or a wireless network (e.g. mobile device) except for an oral authorization via a telephone call.

Credit / Debit

Single Entry or Recurring Entry

Corporate to Consumer

For credit WEB Entries: no authorization by the Receiver

For debit WEB Entries: similarly authenticated*

 

 

Note: "Similarly Authenticated” standard allows signed, written authorization to be provided electronically.  An electronic authorization may meet the requirement that the authorization be in writing, provided that the authorization is displayed on a computer screen or other visual display that enables the consumer to read the communication.  The authorization must be readily identifiable as an authorization and must have clear and readily understandable terms. 

Tax Payments:  Many taxing agencies accept ACH transactions for tax payments. They typically require an ACH Addenda record to help identify the tax payer, along with the details of the tax being paid. These addenda records are known as TXP, which is not an official SEC code, but a convention for the various tax addenda records. Specifications around these TXP addenda is controlled by the individual taxing agency.

ACH File Header and Trailer

Note: ACH File layouts are more fully defined in the Nacha Operating Rules in Appendix Three.  There is much more detail as to the specific requirements and contents of these fields.

All Entries File Header record

File Header Record (Type 1) (Same for all SEC Codes)

Field Number

Field Name

Position in Record

Length

Data Required?

Content

Description/Notes

1

Record Type Code

1

1

Y

1

Always "1"

2

Priority Code

2-3

2

Y

01

Always "01."

3

Immediate Destination

4-13

10

Y

Bnnnnnnnn

The nine-digit routing number of the institution receiving the ACH file for processing, preceded by a blank. Typically, this is your bank’s routing and transit number.

4

Immediate Origin

14-23

10

Y

Bnnnnnnnn

The nine-digit routing transit number of the institution sending (originating) the ACH file, preceded by a blank. (Often your ODFI will have you insert your company ID in this field.)

5

File Creation Date

24-29

6

Y

YYMMDD

The date that the ACH file was created.

6

File Creation Time

30-33

4

N

HHMM

The time that the ACH file was created using a 24-hour, military time format.

7

File ID Modifier

34

1

Y

A-Z, 0-9

For a single processing day, each file submitted by the financial institution should have a unique ID to allow for thorough duplicate file identification.

8

Record Size

35-37

3

Y

094

Always "094" because every record contains 94 characters.

9

Blocking Factor

38-39

2

Y

10

Always "10" because the blocking factor is 10.

10

Format Code

40

1

Y

1

Always "1."

11

Immediate Destination Name

41-63

23

N

alphanumeric

Name of the financial institution receiving the payment file.

12

Immediate Origin Name

64-86

23

N

alphanumeric

Name of the financial institution sending the payment file.

13

Reference Code

87-94

8

N

alphanumeric

This field is reserved for information pertinent to the business.

 

All Entries File Control Record

File Trailer Record (Type 9) (Same for all SEC Codes)

Field Number

Field Name

Position in Record

Length

Data Required?

Content

Description/Notes

1

Record Type Code

01-01

1

Y

9

Always "9"

2

Batch Count

02-07

6

Y

numeric

Count of the number of batches within the file.

3

Block Count

08-13

6

Y

numeric

Count of the number of blocks of 10 rows within the file.

4

Entry/Addenda Count

14-21

8

Y

numeric

Total count of the number of entries and addenda records within the file.

5

Entry Hash

22-31

10

Y

numeric

The sum of the Entry Hash fields contained within the Company/Batch Control Records of the file.

6

Total Debit Entry Dollar Amount in File

32-43

12

Y

$$$$$$$$$$cc

Sum of the amount of debit entries contained within the file.

7

Total Credit Entry Dollar Amount in File

44-55

12

Y

$$$$$$$$$$cc

Sum of the amount of credit entries contained within the file.

8

Reserved

56-94

39

N/A

blank

 

ACH Batch Header and Trailer

All Entries Company/Batch Header Record (Except IAT)

Batch Header Record (Type 5) (Same for all SEC codes except for IAT)

Field Number

Field Name

Position in Record

Length

Data Required?

Content

Description/Notes

1

Record Type Code

01-01

1

Y

5

Always "5"

2

Service Class Code

02-04

3

Y

numeric

Identifies the general classification of dollar entries to be exchanged. [Click for Service Class Codes

3

Company Name

05-20

16

Y

alphanumeric

Name of the Originator known and recognized by the Receiver.

4

Company Discretionary Data

21-40

20

N

alphanumeric

Originator/ODFI may include codes of significance only to them to enable specialized handling of all entries within the batch.

5

Company Identification

41-50

10

Y

alphanumeric

Used to identify the Originator.  Assigned by the ODFI.

6

Standard Entry Class Code

51-53

3

Y

alphanumeric

Three-character code used to identify distinct types of entries. [Click for SEC Codes

7

Company Entry Description

54-63

10

Y

alphanumeric

Originator inserts this field's value to provide the Receiver with a description of the entry's purpose; however some SEC Codes require specific values for this field.

8

Company Descriptive Date

64-69

6

 

alphanumeric

Originator establishes this field as the date it would like to see displayed to the Receiver for descriptive purposes.  

9

Effective Entry Date

70-75

6

 

YYMMDD

The banking day the Originator intends a batch of entries to be settled.

10

Settlement Date (Julian)

76-78

3

 

numeric

Inserted by ACH Operator.

11

Originator Status Code

79-79

1

 

alphanumeric

The code refers to the ODFI initiating the entry.

12

Originating DFI Identification

80-87

8

 

TTTTAAAA

The routing number of the DFI originating the entries within the batch.

13

Batch Number

88-94

7

 

numeric

The ODFI assigns this number in ascending sequence to each batch in a file of entries.  The batch number in the Company/Batch Header record and the Company/Batch Control record must be the same.

 

All Entries Company/Batch Control Record (Except IAT)

Batch Trailer Record (Type 8) (Same for all SEC codes except for IAT)

Field Number

Field Name

Position in Record

Length

Data Required?

Content

Description/Notes

1

Record Type Code

01-01

1

Y

8

Always "8."

2

Service Class Code

02-04

3

Y

numeric

Identifies the general classification of dollar entries to be exchanged.

3

Entry/Addenda Count

05-10

6

Y

numeric

A tally of each Entry Detail record and each Addenda Record processed within the batch.

4

Entry Hash

11-20

10

Y

numeric

The sum of all the Receiving DFI Identification fields contained within the Entry Detail Records in a batch.

5

Total Debit Entry Dollar Amount

21-32

12

Y

numeric

Contains the accumulated entry detail debit totals within the batch.

6

Total Credit Entry Dollar Amount

33-44

12

Y

numeric

Contains the accumulated entry detail credit totals within the batch.

7

Company Identification

45-54

10

Y

alphanumeric

Contains the value of the Company Identification field 5 in the Company/Batch Header record.

8

Message Authentication Code

55-73

19

N

numeric

The 8-character code from a special key used in conjunction with the DES algorithm.  It it sued to validate the authenticity of the ACH Entries.

9

Reserved

74-79

6

N/A

blanks

 

10

Originating DFI Identification

80-87

8

Y

numeric

Contains the value of the Originating DFI Identification field 12 of the Company/Batch Header record.

11

Batch Number

88-94

7

Y

numeric

Contains the value of the Batch Number in field 13 of the Company/Batch Header Record.

PPD, CCD, WEB, TEL Entry records

PPD and CCD Entry:

Field Number

Field Name

Position in Record

Length

Data Required?

Content

Description/Notes

1

Record Type Code

01-01

1

Y

6

Always "6."

2

Transaction Code

02-03

2

Y

numeric

Trancode for the transaction - see Common Data Elements for trancode definitions.

3

Receiving DFI Identification

04-11

8

Y

TTTTAAAA

This is the first 8 digits of the routing and transit number of the receiving bank (where the recipient account is located).

4

Check Digit

12-12

1

Y

numeric

This is the check digit (9th digit) of the routing and transit number of the receiving bank (where the recipient account is located).

5

DFI Account Number

13-29

17

Y

alphanumeric

This is the account number of the recipient.

6

Amount

30-39

10

Y

$$$$$$$$cc

This is the amount of the transaction.

7

Identification Number

40-54

15

N

alphanumeric

This is an optional field to identify the transaction to the Receiver.

8

Receiving Individual/Company Name

55-76

22

Y

alphanumeric

Entered by the Originator to provide additional identification of the Receiver and may be helpful in identifying return entries.

PPD Return Fee entries authorized by notice must contain the same information identified within the Individual Name field of the ARC, BOC, or POP entry to which the Return Fee Entry relates.

9

Discretionary Data

77-78

2

N

alphanumeric

ODFI may include codes, of significance to them, to enable specialized handling of the entry.

10

Addenda Record Indicator

79-79

1

Y

numeric

For Health Care EFT Transactions (except Prenotification Entries), the Addenda Record Indicator of the CCD Entry must always contain a value of "1."

11

Trace Number

80-94

15

Y

numeric

Assigned by the ODFI in ascending sequence that uniquely identifies each entry within a batch and the file.

 

PPD, CCD, and WEB Addenda records

Field Number

Field Name

Position in Record

Length

Data Required?

Content

Description/Notes

1

Record Type Code

01-01

1

Y

7

Always "7."

2

Addenda Type Code

02-03

2

Y

05

Always "05."

3

Payment Related Information

04-83

80

N

alphanumeric

This is an optional freeform text field that will travel with the payment instruction to the RDFI.  Please note that this information may or may not be displayed to the recipient, based on the bank's capabilities, and method of access (i.e., online banking, statement, etc.)

For Health Care EFT Transactions, this must always contain the ASC X12 Version 5010 835 TRN Segment.

4

Addenda Sequence Number

84-87

4

Y

numeric

PPD, CCD and WEB only allow for one addenda per record, therefore the value will always be "1."

5

Entry Detail Sequence Number

88-94

7

Y

numeric

This number is the same as the last seven digits of the trace number of the related Entry or Corporate Entry Detail Record.

 

WEB and TEL Entry:

Field Number

Field Name

Position in Record

Length

Data Required?

Content

Description/Notes

1 Record Type Code 01-01 1 Y 6 Always "6."

2

Transaction Code

02-03

2

Y

numeric

Trancode for the transaction - see Common Data Elements for trancode definitions.

3

Receiving DFI Identification

04-11

8

Y

TTTTAAAA

This is the first 8 digits of the routing and transit number of the receiving bank (where the recipient account is located).

4

Check Digit

12-12

1

Y

numeric

This is the check digit (9th digit) of the routing and transit number of the receiving bank (where the recipient account is located).

5

DFI Account Number

13-29

17

Y

alphameric

This is the account number of the recipient.

6

Amount

30-39

10

Y

$$$$$$$$cc

This is the amount of the transaction.

7

Individual Identification Number

40-54

15

N

alphanumeric

For Person-to-Person WEB credit Entries, this field is required and contains the name of the consumer Originator.

For WEB debit Entries, this field is optional, and is used at the discretion of the Originator.

8

Individual Name

55-76

22

Y

alphanumeric

Entered by the Originator to provide additional identification of the Receiver and may be helpful in identifying return entries.

9

Payment Type Code

77-78

2

Y

alphanumeric

For recurring TEL and WEB entries, this field must contain the value "R".

For Single-Entry TEL, this field must either be the value "S" or space-filed.

For Single-Entry WEB, this field must contain the value "S."

Beginning on Sept. 17, 2021, this field will allow Originators to include codes, of significance to them, to enable specialized handling of the entry. There is no standardized interpretation for the value of this field.

10

Addenda Record Indicator

79-79

1

Y

numeric

For TEL, the value will be "0" - TEL does not allow for an addenda record.

For WEB, the value will be "0" or "1" - WEB allows for one optional addenda record.

11

Trace Number

80-94

15

Y

numeric

Assigned by the ODFI in ascending sequence that uniquely identifies each entry within a batch and the file.