ACCESS UG NACHA File Specifications 1
ACCESS UG NACHA File Specifications 1
July 2016
Payments
2
Payments
Table of Contents
General Information ............................................................................................................................................................ 5
Cash Concentration or Disbursement – (CCD) Application ............................................................................................ 6
FILE HEADER RECORD (1) ................................................................. 6
BATCH HEADER RECORD (5) ............................................................... 7
ENTRY DETAIL RECORD (6) ................................................................ 8
ADDENDA RECORD (7)* ................................................................... 9
BATCH CONTROL RECORD (8) ............................................................ 10
M=Mandatory; R=Required; O=Optional ....................................................... 10
FILE CONTROL RECORD (9)............................................................... 11
Corporate Trade Exchange Entries – (CTX) Application ............................................................................................... 12
FILE HEADER RECORD (1) ................................................................ 12
BATCH HEADER RECORD (5) .............................................................. 13
ENTRY DETAIL RECORD (6) ............................................................... 14
ADDENDA RECORD (7)* .................................................................. 15
BATCH CONTROL RECORD (8) ............................................................ 16
FILE CONTROL RECORD (9)............................................................... 17
Prearranged Payment and Deposit – (PPD) Application................................................................................................ 18
FILE HEADER RECORD (1) ................................................................ 18
BATCH HEADER RECORD (5) .............................................................. 19
DETAIL ENTRY RECORD (6) ............................................................... 20
BATCH CONTROL RECORD (8) ............................................................ 21
FILE CONTROL RECORD (9)............................................................... 22
Internet-Initiated Entries – (WEB) Application ................................................................................................................ 23
FILE HEADER RECORD (1) ................................................................ 23
BATCH HEADER RECORD (5) .............................................................. 24
3
Payments
DETAIL ENTRY RECORD (6 ............................................................... 25
BATCH CONTROL RECORD (8) ............................................................ 26
FILE CONTROL RECORD (9)............................................................... 27
4
Payments
General Information
Please refer to the information below, which relates to various parameters throughout this document:
Mandatory: A “Mandatory” field is necessary to ensure the proper routing and/or posting of an ACH entry. Any “Mandatory” field not
included in an ACH record will cause that entry, batch or file to be rejected by the ACH Operator. ACH Operator-rejected entries will be
returned to J.P. Morgan Chase (JPMC). ACH Operator-rejected batches and files will also be reported to JPMC.
Required: The omission of a “Required” field will not cause an entry reject at the ACH Operator, but it may cause a reject at the
Receiving Depository Financial Institution (RDFI). An example is the Depository Financial Institution (DFI) account number field in the
Entry Detail Record (6). If the Originating Depository Financial Institution (ODFI) omits the field, the RDFI may return the entry as
unable to post. You, as the Originator, and ODFI should include data classified as “Required,” to avoid processing and control
problems at the RDFI.
Optional: The inclusion or omission of an “Optional” data field is at the discretion of the Originator and the ODFI.
RIGHT JUSTIFY all numeric fields using zeros to fill the remainder of the field unless indicated otherwise.
LEFT JUSTIFY all ALPHAMERIC fields using blank spaces to fill the remainder of the field unless indicated otherwise.
5
Payments
Cash Concentration or Disbursement – (CCD) Application
FILE HEADER RECORD (1)
Field Field Field
Field Name File Contents Required Comments
No. Position Length
13 87-94 8 REFERENCE CODE LEAVE BLANK O Fill field with blank spaces.
(CCD) Application 6
Payments
BATCH HEADER RECORD (5)
Field Field
Field Field Name File Contents Required Comments
No. Length
Position
(CCD) Application 7
Payments
ENTRY DETAIL RECORD (6)
Field Field
Field Field Name File Contents Required Comments
No. Length
Position
Fill field using value indicated under ‘File Contents’
1 1-1 1 RECORD TYPE CODE 6 M column.
Credit
23 For Checking Pre-notes
22 For Checking Dollars
33 For Savings Pre-notes
32 For Savings Dollars
ONE OF THE
FOLLOWING: Debit
2 2-3 2 TRANSACTION CODE M 28 For Checking Pre-notes
Credit: 23, 22, 33, 32 27 For Checking Dollars
38 For Savings Pre-notes
Debit: 28, 27, 38, 37 37 For Savings Dollars
Please include a minimum of 15 transactions
with dollar amounts in your test file. This will
assist in the proofing of your batch and file
totals.
3 4-11 8 RECEIVING DFI ID TTTTAAAA** M Must be a valid Routing Number
4 12-12 1 CHECK DIGIT NUMERIC M Routing Number Check Digit
5 13-29 17 DFI ACCOUNT NUMBER ALPHANUMERIC R Must be left-justified and blank space filled.
6 30-39 10 DOLLAR AMOUNT $$$$$$$$¢¢ M Must be right-justified and zero filled.
INDIVIDUAL
Must be left justified and blank space filled.
7 40-54 15 IDENTIFICATION ALPHANUMERIC O Note: This is a MANDATORY field for JPMC.
NUMBER
8 55-76 22 INDIVIDUAL NAME ALPHANUMERIC R Must be left justified and blank space filled.
9 77-78 2 DISCRETIONARY DATA LEAVE BLANK O Fill field with blank spaces.
ADDENDA RECORD 0 If no addenda record
10 79-79 1
INDICATOR
0 or 1 M 1 If addenda record
Example:
11 80-94 15 TRACE NUMBER NUMERIC M Middle eight digits of your Immediate Origin
followed by a seven-digit incremental counter.
M=Mandatory; R=Required; O=Optional
** TTTTAAAA = 4-digit Federal Reserve Routing Symbol + 4-digit ABA Institution Identifier
NOTE: For testing purposes please include a minimum of 15 transactions (Entry Detail Records).Please use as much test data that will validate the
integrity of the information from your system. This will help minimize any problems when your application goes live.
(CCD) Application 8
Payments
ADDENDA RECORD (7)*
Field
Field Field
Position Field Name Field Contents Required Comments
No. Length
(CCD) Application 9
Payments
BATCH CONTROL RECORD (8)
Field Field
Field Field Name File Contents Required Comments
No. Length
Position
Fill field using value indicated under ‘File
1 1-1 1 RECORD TYPE CODE 8 M
Contents’ column.
(CCD) Application 10
Payments
FILE CONTROL RECORD (9)
TOTAL DEBIT
Must be equal to the total debit dollar amount
6 32-43 12 ENTRY DOLLAR $$$$$$$$$$¢¢ M
in the file.
AMOUNT IN FILE
TOTAL CREDIT
Must be equal to the total credit dollar amount
7 44-55 12 ENTRY DOLLAR $$$$$$$$$$¢¢ M
in the file.
AMOUNT IN FILE
(CCD) Application 11
Payments
Corporate Trade Exchange Entries – (CTX) Application
FILE HEADER RECORD (1)
IMMEDIATE
3 4-13 10
DESTINATION
b021000021 M b represents a blank space.
IMMEDIATE JPMORGAN
11 41-63 23 O
DESTINATION NAME CHASE
IMMEDIATE COMPANY Your Company Name (Long)
12 64-86 23 O
ORIGIN NAME NAME
13 87-94 8 REFERENCE CODE LEAVE BLANK O
(CTX) Application 12
Payments
BATCH HEADER RECORD (5)
Field Field Field
Field Name File Contents Required Comments
No. Position Length
COMPANY
4 21-40 20
DISCRETIONARY DATA
LEAVE BLANK O/R
COMPANY
5 41-50 10
IDENTIFICATION
0000000000 M Assigned by JPMC.
STANDARD ENTRY
6 51-53 3 CTX M
CLASS CODE
COMPANY ENTRY
7 54-63 10
DESCRIPTION *
ALPHAMERIC M Example: Payment
COMPANY Example:
8 64-69 6
DESCRIPTIVE DATE *
ALPHAMERIC O
JAN 03 (January 2003) or JAN 25 (January 25)
Must be in YYMMDD format.
EFFECTIVE ENTRY
9 70-75 6
DATE*
YYMMDD R Must be greater than the File Creation Date
in the File Header record, Field No. 5
SETTLEMENT DATE This field can be left blank; if blank JPMC will fill
10 76-78 3
(JULIAN)
JULIAN DATE R
field in automatically.
ORIGINATOR STATUS
11 79-79 1
CODE
1 M
(CTX) Application 13
Payments
ENTRY DETAIL RECORD (6)
Field Field Field
Field Name File Contents Required Comments
No. Position Length
1 1-1 1 RECORD TYPE CODE 6 M
22 FOR CHECKING DOLLARS (CR)
23 FOR CHECKING PRENOTES (CR)
ONE OF THE 24 FOR CHECKING ZERO DOLLAR WITH
REMITTANCE DATA(CR)
FOLLOWING:
2 2-3 2 TRANSACTION CODE M
27 FOR CHECKING DOLLARS (DR)
22,23,24,27,28,29 28 FOR CHECKING PRENOTES (DR)
29 FOR CHECKING ZERO DOLLAR
REMITTANCE DATA (DR)
3 4-11 8 RECEIVING DFI ID TTTTAAAA** M Must be a valid Routing Number
Routing Number Check Digit. If necessary, refer to
4 12-12 1 CHECK DIGIT NUMERIC M Check Digit Calculation documentation included in
your Implementation Package.
5 13-29 17 DFI ACCOUNT NUMBER ALPHAMERIC R Must be left justified and blank space filled.
6 30-39 10 TOTAL AMOUNT $$$$$$$$¢¢ M Must be right justified and zero filled.
IDENTIFICATION Must be left justified and blank space filled.
7 40-54 15
NUMBER
ALPHAMERIC O Note: This a MANDATORY field for JPMC.
NUMBER OF ADDENDA
8 55-58 4
RECORDS
NUMERIC M
RECEIVING COMPANY
9 59-74 16 ALPHAMERIC R
NAME/ID NUMBER
10 75-76 2 RESERVED ALPHAMERIC BLANK
11 77-78 2 DISCRETIONARY DATA LEAVE BLANK O Fill field with blank spaces.
0 if no addenda record
ADDENDA RECORD
12 79-79 1
INDICATOR
0 OR 1 M
1 if addenda record
Example: Middle eight digits of your immediate
13 80-94 15 TRACE NUMBER NUMERIC M Origin followed by a seven-digit incremental
counter.
M=Mandatory; R=Required; O=Optional
** TTTTAAAA = 4-digit Federal Reserve Routing Symbol + 4-digit ABA Institution Identifier
NOTE: For testing purposes please include a minimum of 15 transactions (Entry Detail Records). Please use as much test data that will validate the integrity of the
information from your system. This will help minimize any problems when your application goes live.
(CTX) Application 14
Payments
ADDENDA RECORD (7)*
RECORD TYPE
1 1-1 1
CODE
7 M
ADDENDA TYPE
2 2-3 2
CODE
05 M
(CTX) Application 15
Payments
BATCH CONTROL RECORD (8)
Example:
ORIGINATING DFI
10 80-87 8
IDENTIFICATION
NUMERIC M
Middle eight digits of your Immediate Origin.
Same as in the Batch Header Record, Field No.
11 88-94 7 BATCH NUMBER NUMERIC M
13, positions 88-94.
(CTX) Application 16
Payments
FILE CONTROL RECORD (9)
(CTX) Application 17
Payments
Prearranged Payment and Deposit – (PPD) Application
FILE HEADER RECORD (1)
Field Field Field
Field Name File Contents Required Comments
No. Position Length
Fill field using value indicated under ‘File Contents’
1 1-1 1 RECORD TYPE CODE 1 M
column.
Fill field using value indicated under ‘File Contents’
2 2-3 2 PRIORITY CODE 01 R
column.
IMMEDIATE
3 4-13 10 b021000021 M b represents a blank space.
DESTINATION
13 87-94 8 REFERENCE CODE LEAVE BLANK O Fill field with blank spaces.
(PPD) Application 18
Payments
BATCH HEADER RECORD (5)
Field Field Field
Field Name File Contents Required Comments
No. Position Length
Fill field using value indicated under ‘File
1 1-1 1 RECORD TYPE CODE 5 M
Contents’ column.
Fill field using value indicated under ‘File
2 2-4 3 SERVICE CLASS CODE 200 M
Contents’ column.
3 5-20 16 COMPANY NAME * COMPANY NAME M Your Company Name (Short)
COMPANY
4 21-40 20 LEAVE BLANK O/R Fill field with blank spaces.
DISCRETIONARY DATA
COMPANY
5 41-50 10 0000000000 M Assigned by JPMC.
IDENTIFICATION
STANDARD ENTRY Fill field using value indicated under ‘File
6 51-53 3 PPD M
CLASS CODE Contents’ column.
COMPANY ENTRY A 10 character description of the batch Example:
7 54-63 10 ALPHANUMERIC M
DESCRIPTION * PAYROLL
Example:
COMPANY
8 64-69 6 ALPHANUMERIC O JAN 03 (January 2003) or JAN 25 (January
DESCRIPTIVE DATE *
25)
Must be in YYMMDD format.
EFFECTIVE ENTRY
9 70-75 6 YYMMDD R
DATE* Must be greater than the File Creation Date
in the File Header record. (Refer to Field 5)
SETTLEMENT DATE This field can be left blank; if blank JPMC will
10 76-78 3 JULIAN DATE R
(JULIAN) fill field in automatically.
ORIGINATOR STATUS Fill field using value indicated under ‘File
11 79-79 1 1 M
CODE Contents’ column.
ORIGINATING DFI
12 80-87 8 NUMERIC M Client defined
IDENTIFICATION
Example:
13 88-94 7 BATCH NUMBER NUMERIC M Start with 0000001 and increment by 1 for
each next batch.
M=Mandatory; R=Required; O=Optional
* The information in these fields will appear on the bank statement of the individual who is receiving the transaction.
(PPD) Application 19
Payments
DETAIL ENTRY RECORD (6)
Field Field Field
Field Name File Contents Required Comments
No. Position Length
Fill field using value indicated under ‘File
1 1-1 1 RECORD TYPE CODE 6 M Contents’ column.
Debit
28 For Checking Pre-notes
27 For Checking Dollars
38 For Savings Pre-notes
37 For Savings Dollars
ONE OF THE
FOLLOWING: Credit
23 For Checking Pre-notes
2 2-3 2 TRANSACTION CODE M 22 For Checking Dollars
Debit: 28, 27, 38, 37 33 For Savings Pre-notes
Credit: 23, 33, 33, 32 32 For Savings Dollars
(PPD) Application 20
Payments
BATCH CONTROL RECORD (8)
(PPD) Application 21
Payments
FILE CONTROL RECORD (9)
3 8-13 6 BLOCK COUNT NUMERIC M Must be equal to the number of blocks in the file.
(PPD) Application 22
Payments
Internet-Initiated Entries – (WEB) Application
FILE HEADER RECORD (1)
Field Field Field
Field Name File Contents Required Comments
No. Position Length
IMMEDIATE
3 4-13 10 b021000021 M b represents a blank space.
DESTINATION
IMMEDIATE JPMORGAN
11 41-63 23 O
DESTINATION NAME CHASE
IMMEDIATE Your Company Name (Long)
12 64-86 23 COMPANY NAME O
ORIGIN NAME
(WEB) Application 23
Payments
BATCH HEADER RECORD (5)
Field Field Field
Field Name File Contents Required Comments
No. Position Length
COMPANY
4 21-40 20 LEAVE BLANK O/R
DISCRETIONARY DATA
COMPANY
5 41-50 10 0000000000 M Assigned by JPMC.
IDENTIFICATION
STANDARD ENTRY
6 51-53 3 WEB M
CLASS CODE
COMPANY ENTRY Example:
7 54-63 10 ALPHANUMERIC M
DESCRIPTION * PYMT COLL
Example:
COMPANY
8 64-69 6 ALPHANUMERIC O JAN 03 (January 2003) or JAN 25 (January
DESCRIPTIVE DATE *
25)
Must be in YYMMDD format.
EFFECTIVE ENTRY
9 70-75 6 YYMMDD R
DATE* Must be greater than the File Creation Date
in the File Header record. (Refer to Field 5.)
SETTLEMENT DATE This field can be left blank; if blank JPMC
10 76-78 3 JULIAN DATE R
(JULIAN) will fill field in automatically.
ORIGINATOR STATUS
11 79-79 1 1 M
CODE
ORIGINATING DFI Example:
12 80-87 8 NUMERIC M
IDENTIFICATION Middle eight digits of your Immediate Origin
Example:
13 88-94 7 BATCH NUMBER NUMERIC M Start with 0000001 and increment by 1 for
each next batch.
M=Mandatory; R=Required; O=Optional
* The information in these fields will appear on the bank statement of the individual who is receiving the transaction.
(WEB) Application 24
Payments
(WEB) Application 25
Payments
BATCH CONTROL RECORD (8)
Example:
ORIGINATING DFI
10 80-87 8 NUMERIC M Middle eight digits of your Immediate Origin.
IDENTIFICATION
(WEB) Application 26
Payments
FILE CONTROL RECORD (9)
3 8-13 6 BLOCK COUNT NUMERIC M Must be equal to the number of blocks in the file.
(WEB) Application 27