Global Payments and Cash Management

National Automated Clearing House Association

NACHA

File Format Specifications

USA

Version 3.0
July 2018

Copyright© 2005 HSBC Bank USA, N.A.

All rights Reserved
 NATIONAL AUTOMATED CLEARING HOUSE ASSOCIATION
NACHA
FILE SPECIFICATIONS
HSBC Bank USA will use this record format to submit entries to the Automated Clearing
House. This format allows multiple entry descriptions by grouping entries into batches,
with each batch containing the entry description which appears on the receiver's bank
statement. The following pages detail the contents of a file by each record format. The
code values and data elements are in the attached Glossary.

The basic record sequence for ACH files is as diagrammed

File Header Record
Company Batch
Header Record
First
Entry Detail
Record
Second
Entry Detail
Record
*
*
*
Last
Entry Detail
Record
Company Batch
Control Record
*
*
*
Company Batch
Header Record
First
Entry Detail
Record
*
*
*
Last
Entry Detail
Record
Company Batch
Control Record
File Control Record
9999.99999

©Copyright. HSBC Bank plc. 2005. ALL RIGHTS RESERVED Page 1 of 12

No part of this document may be reproduced, stored in a retrieval system, or transmitted, on any form or by any means, electronic,
mechanical, photocopying, recording, or otherwise, without the prior written permission of HSBC Bank plc.
FILE HEADER RECORD FORMAT (Record Type "1")
Designates physical file characteristics and identifies the immediate origin and destination of the entries
contained within the file or within the transmitted batch data. In addition, this record includes date, time, and
fields which uniquely identify the file.

Field Position Size Status Contents Data Element Name (See Glossary)
1 01-01 1 M Numeric '1' Record Type Code
2 02-03 2 R Numeric '01' Priority Code
b022000020 Immediate Destination
3 04-13 10 M
b=Blank Space Identification HSBC Bank USA
4 14-23 10 M INNNNNNNN* *Company Identification. Your 10-digit
company number assigned by HSBC (PEP ID)
5 24-29 6 M YYMMDD Transmission (File Creation) Date
6 30-33 4 O HHMM Transmission (File Creation) Time
Alphanumeric File ID Modifier (For I.D. of multiple
7 34-34 1 M
'A' 'B' ect. files on the same day). Code to distinguish
among multiple input files sent per day. Label
the first (or only) file “A” (or “0”) and continue
in sequence.
8 35-37 3 M Numeric '094' Record Size
9 38-39 2 M Numeric '10' Blocking Factor. Number of records per block.
10 40-40 1 M '1' Format Code
Immediate Destination Name
11 41-63 23 M Alphanumeric
"HSBC Bank USA"
12 64-86 23 R Alphanumeric Immediate Origin Name. Your Company’s
name, up to 23 characters including spaces.
Alphanumeric
13 87-94 8 O Reference Code
or Blanks

*The value of the leading ("I") digit defines the kind of identification number used as follows:

For DIRECT DEPOSIT files use a "1" followed by the IRS Employer Identification Number.
For DIRECT DEBIT files use a "9" followed by the IRS Employer Identification Number.

Example:
101 02200002012345678090706210953A094101HSBC BANK USA ABC Company Inc

NACHA HSBC File Format Specifications 07/17/2018 Page 2 of 12

COMPANY/BATCH HEADER RECORD FORMAT (Record Type "5")
Identifies the Originator and briefly indicates the reason for the transaction originated. The transit routing /
ABA number is included the Originating bank for settlement, routing of returns, and other control purposes.
The effective date can indicate the effective date of all transactions within the batch. The information
contained in this record applies uniformly to all subsequent Entry Detail Records.

Field Position Size Status Contents Data Element Name (See Glossary)
1 01-01 1 M Numeric '5' Record Type Code
2 02-04 3 M Numeric Service Class Code. Identifies the type
ACH Mixed Debits and Credits ‘200’ of entries in the batch.
ACH Credits Only ‘220’
ACH Debits Only ‘225’
3 05-20 16 M Alphanumeric ** Company Name. NACHA rules
require the RDFI to print this value on
the receiver’s statement so you will
want to make this value as clear
as possible.
Alphanumeric
4 21-40 20 O Company Discretionary Data.
or Blanks
5 41-50 10 M INNNNNNNNN * Company Identification, your 10-
digit company number assigned by
HSBC. Collection Application ID (CA)

6 51-53 3 M Alphanumeric Standard Entry Class. A mnemonic,

“PPD” (Ex: Payroll) designated by NACHA, which permits
“CCD” (Vendor/Company entries to be distinguished. Identifies
Payments) etc. the specific record format used to carry
payment and payment-
related information.
7 54-63 10 R Alphanumeric ** Company Entry Description
8 64-69 6 O Alphanumeric ** Company Descriptive Date
9 70-75 6 M YYMMDD Effective Entry Date (Settlement). Date
you desire funds to post to receiver’s
account.
10 76-78 3 M Blanks Reserved
11 79-79 1 M 1 Originator Status Code
Originating Financial Institution
12 80-87 8 M 02200002
Identification
13 88-94 7 R Numeric Batch Number
*The value of the leading ("I") defines the kind of Identification Number. This field is used by HSBC as
follows:
For DIRECT DEPOSIT files use a "1" followed by the IRS Employer Identification Number.
For DIRECT DEBIT files use a "9" followed by the IRS Employer Identification Number.
**These fields may be printed on customer/employee statements exactly as provided by the originating
company. Therefore, contents of these fields should be carefully controlled.

Example:
5200ABC Company Inc 1234567809PPDExpenses 080621 1022000020000001

NACHA HSBC File Format Specifications 07/17/2018 Page 3 of 12

ENTRY DETAIL RECORD (Record Type "6")
Contains information sufficient to relate the transaction to the receiver and the receiver's bank. The
information in the Company/Batch Header must be incorporated with entry detail records to fully describe
each detailentry.

Field Position Size Status Contents Data Element Name (See Glossary)
1 01-01 1 M Numeric '6' Record Type Code
2 02-03 2 M Numeric Transaction Code (see below)
*Receiving Bank Identification.
3 04-11 8 M TTTTAAAA
Transit Routing Number of the receiver’s
financial institution.
4 12-12 1 M Numeric *Check Digit. The ninth number of the
RDFI Routing Transit Number.
5 13-29 17 R Alphanumeric Receiving Bank Account Number
6 30-39 10 M $$$$$$$$cc Amount **
7 40-54 15 O Alphanumeric Individual Identification Number
8 55-76 22 R Alphanumeric Individual Name
9 77-78 2 O Alphanumeric Discretionary Data
10 79-79 1 M Numeric '0' Addenda Record Indicator
Numeric Trace Number. The field is constructed as
11 80-94 15 M
(zeroes) follows:
Positions 80-87 should be the same as Field
12 of the Company Batch Header 02200002.
Positions 88-94 are filled with the Entry
Detail Sequence Number. This number must
be assigned in ascending order to entries
within each batch, although the numbers
need not be continuous. HSBC reassigns
new trace numbers when we send entries to
the clearing house.

*Receiving Bank Transit Routing Number + Check Digit = 9 Digit which is the receiving bank
routing number (must be valid)
**Prenotification records are non-dollar entries with unique transaction codes and must contain zeroes in the
Amount field.
Transaction Codes:
Credit (deposit) to checking account ‘22’
Prenote for credit to checking account ‘23’
Debit (withdrawal) to checking account ‘27’
Prenote for debit to checking account ‘28’
Credit to savings account ‘32’
Prenote for credit to savings account ‘33’
Debit to savings account ‘37’
Prenote for debit to savings account ‘38’
Example:
6221234567871234567890 0000004700000585800000001AC Milan 0022000020000001

NACHA HSBC File Format Specifications 07/17/2018 Page 4 of 12

COMPANY/BATCH CONTROL RECORD FORMAT (Record Type "8")
Contains the counts, hash totals, and total dollar controls for the preceding detail entries within the indicated
batch.

Field Position Size Status Contents Data Element Name (See Glossary)
1 01-01 1 M Numeric '8' Record Type Code
2 02-04 3 M Numeric Service Class Code. Must match the value
ACH Mixed Debits and Credits ‘200’ used in the Batch Header Record 5, above.
ACH Credits Only ‘220’
ACH Debits Only ‘225’
3 05-10 6 M Numeric Entry/Addenda Count. Total number of Entry
Detail Records plus addenda records (Record
Type “6” and “7”) in the batch. Requires 6
positions, right-justify, left zero-fill.
4 11-20 10 M Numeric Entry Hash. Total of eight-character Transit
Routing/ABA numbers in the batch (field 3
of the Entry Detail Record 6). Do not include
the Transit Routing Check Digit. Enter the
ten low-order (right most) digits of this
number. For example, if the sum were
112233445566, you would enter 2233445566
5 21-32 12 M $$$$$$$$$$cc Total Debit Entry Dollar Amount in Batch
6 33-44 12 M $$$$$$$$$$cc Total Credit Entry Dollar Amount in Batch
7 45-54 10 M INNNNNNNN* * Company Identification. Your 10-digit
company number assigned by HSBC.
Collection Application ID (CA). Must match
Field 5 of the Company Batch Header
Record.
8 55-73 19 M Blanks Reserved
9 74-79 6 M Blanks Reserved for Federal Reserve Use
Originating Financial Institution
10 80-87 8 M 02200002
Identification
11 88-94 7 M Numeric Batch Number. Number of the batch for
which this is a control record. Number the
batches sequentially within each file. Must
match Filed 13 of the company Bach Header
Record 5.

*The value of the leading ("I") defines the kind of Identification Number. This field is used by HSBC as
follows:
For DIRECT DEPOSIT files use a "1" followed by the IRS Employer Identification Number. For
DIRECT DEBIT files use a "9" followed by the IRS Employer Identification Number.

Example:
820000000400136411330000000272000000000272001234567809 022000020000001

NACHA HSBC File Format Specifications 07/17/2018 Page 5 of 12

FILE CONTROL RECORD FORMAT (Record Type "9")
Summarizes the information carried in the Company/Batch Control records. It contains dollar, entry, and hash
total accumulations from the Company/Batch Control records in the file. This record also contains counts of
the number of blocks and the number of batches within the file.

Field Position Size Status Contents Data Element Name (See Glossary)
1 01-01 1 M Numeric '9' Record Type Code
2 02-07 6 M Numeric Batch Count
3 08-13 6 M Numeric Block Count
4 14-21 8 M Numeric Entry/Addenda Count. Total number of Entry
Detail and addenda Records (Record Types “6”
and “7”) in the file
5 22-31 10 M Numeric Entry Hash. Total of eight-character Transit
Routing/ABA numbers in the file (field 3 of the
Entry Detail Record). Do not include the Transit
Routing Check Digit. Enter the ten low-order
(right most) digits of this number. For example,
if the sum were 998877665544, you would enter
8877665544.
6 32-43 12 M $$$$$$$$$$cc Total Debit Entry Dollar Amount in File
7 44-55 12 M $$$$$$$$$$cc Total Credit Entry Dollar Amount in File
8 56-94 39 M Blanks Reserved

Example:

9000001000001000000040013641133000000027200000000027200

NACHA HSBC File Format Specifications 07/17/2018 Page 6 of 12

Glossary

Field Inclusion Requirements

The following information defines the need for inclusion of certain data fields in ACH entries. This involves
the standardization of three definitions: Mandatory, Required, and Optional.

Mandatory (M)
Any "Mandatory" field not included in an ACH entry will cause that entry, batch, or file to be rejected by the
first ACH processing of the file. A "Mandatory" field is necessary to ensure the proper routing and/or
posting of an ACH entry.

Required (R)
The omission of a "Required" field will not cause an entry reject at the ACH but may cause a reject at the
receiving bank. Data classified as "Required" should be included by the originator and the originating bank
to avoid control problems at the receiving bank.

Optional (O)
The inclusion or omission of an "Optional" data field is at the discretion of the originator and originating bank.

Data Element Definitions

Addenda Record Indicator - 1 Position - Entry Detail Record - Mandatory

This field indicates the existence of an Entry Detail Addenda Record. A value of "0" indicates that no such
record is present.

Amount - 10 Positions - Entry Detail Record - Mandatory

The receiving bank posts the debit or amount to the appropriate account authorized by the individual. A zero
amount is acceptable only with non-dollar (prenotification) codes. A specific amount must be present for all
non-prenotification transaction codes.

Batch Count - 6 Positions - File Control Record - Mandatory

The value of this field must be equal to the number of Company/Batch Header Records in the file.

Batch Number - 7 Positions - Company/Batch Header and Control Records - Required

This number is assigned in ascending sequence to each batch by the sending point in a given file of entries.
The ascending sequence number should be assigned by batch and not by record.

Block Count - 6 Positions - File Control Record - Mandatory

The Block Count contains the number of physical blocks in the file, including both the File Header and File
Control Records.

Blocking Factor - 2 Positions - File Header Record - Mandatory

The Blocking Factor should be '10'.

NACHA HSBC File Format Specifications 07/17/2018 Page 7 of 12

Check Digit - 1 Position - Entry Detail Record - Mandatory
The check digit is computed using Modulus 10 as follows:
(1) Multiply each digit in the transit/routing number by a weighting factor. The weighting factors for each
digit are:
Position: 1 2 3 4 5 6 7 8
Weights: 3 7 1 3 7 1 3 7
(2) Add the results of the eight multiplications.
(3) Subtract the sum from the next highest multiple of 10. The result is the check digit.

Example:
Transit/ABA Numb 0 7 6 4 0 1 2 5
Multiply By 3 7 1 3 7 1 3 7
0 49 6 12 0 1 6 35
Sum = 109
Check Digit = 1 (110 minus 109)

Company Descriptive Date - 6 Positions - Company/Batch Header Record - Optional

The originator establishes this field as the date it would like to see displayed to the receiver for descriptive
purposes. This field is never used to control timing of any computer or manual operation. It is solely for
descriptive purposes.
Company Discretionary Data - 20 Positions - Company/Batch Header Record - Optional This field
allows originators and/or originating banks to include codes (one or more), of significance only to them, to
enable specialized handling of all subsequent entries in that batch. There will be no standardized interpretation
for the value of the field. This field must be returned intact on any return entry.

Company Entry Description - 10 Positions - Company/Batch Header and Control - Required The
originating company establishes the value of this field to provide a description of the entry to be displayed
back to the receiver. For example, "GAS BILL", "REG SALARY", "INS PREM", etc.

Company Identification - 10 Positions - File Header, Company/Batch Header and

and Control Records - Mandatory
Companies are identified by a unique identification number. ANSI standard identifiers should be used where
pratical and formatted with the nine-digit identification number preceded by the ANSI one-digit Identification
Code Designator (IDC).

The most frequently used ANSI ICD identification numbers for companies are:
1 = IRS Employer Identification Number (EIN)
2 = DUNS Data Universal Numbering System
9 = User Assigned Number
The first digit in the ANSI format is always the ICD followed by the appropriate nine-digit number
(INNNNNNNNN).
The company identification field should be used on all prenotification records and should be included on each
entry initiated pursuant to such prenotification. An absence of or change in this information may cause a
receiving bank to reject the entry for "No Prenotification On File".

NACHA HSBC File Format Specifications 07/17/2018 Page 8 of 12

Company Name - 16 Positions - Company/Batch Header Record - Mandatory
The value of this field is established by the company for purposes of further identifying the source of the
entry, and for descriptive purposes of the receiver.

Discretionary Data - 2 Positions - Entry Detail Record - Optional

This field in the entry detail record allows originating companies and/or banks to include codes of
significance only to them, to enable specialized handling of the entry. The will be no standardized
interpretation for the value of this field. It can either be a single two-character code, or two distinct one-
character codes, according to the needs of the originating bank and company. This field must be returned
intact for any returned entry.

Effective Entry Date - 6 Positions - Company/Batch Header Record - Required

The effective entry date is the date specified by the originator on which it intends a batch of entries to be
settled. For credit entries, the effective entry date shall be either one or two banking days following the
banking day of processing as established by the originating ACH (the processing date). For debit entries, the
effective entry date shall be one banking day following the processing date.

Batches of entries containing an effective entry date beyond the designated number of days allowed will be
rejected by the ACH and returned to the originating bank. If this field is blank or zero, or partially blank or
partially non-numeric, or contains an incomplete date, day numbers higher than 31 or month numbers
higher than 12, the originating ACH shall insert the next banking day after the processing date as the
effective entry date.
Entry/Addenda Count
6 Positions - Company/Batch Control Record - Mandatory
8 Positions - File Control Record - Mandatory
This count is a tally of each entry detail record and each entry detail addenda record processed, within either
the batch or file, as appropriate.

Entry Hash - 10 Positions - Company/Batch Control and File Control Records

The critical Transit/Routing Number in each entry is hashed to provide a check against inadvertent alteration
of data contents due to hardware failure or program error. (NOTE: Entry Detail Addenda Records are not
hashed.)
The eight-character Transit/Routing number is accumulated into the pertinent 10-character Entry Hash Field,
within either the batch or file, as appropriate. (Note: Ignore any overflow beyond the 10-character size.)
File ID Modifier - 1 Position - File Header Record - Mandatory
Permits multiple files created on the same date and between the same participants to be distinguished. Only
upper-case A-Z and numeric 0-9 are permitted.
Format Code - 1 Position - File Header Record - Mandatory
This code has been provided to allow for future format variations (eg. data transmission).
The value should be '1'.

Immediate Destination - 10 Positions - File Header Record - Mandatory

This field contains the Transit/Routing number of the ACH receiving point to which the file is being sent.

NACHA HSBC File Format Specifications 07/17/2018 Page 9 of 12

Immediate Destination Name - 23 Positions - File Header Record - Mandatory
This field contains the name of the ACH or receiving point for which that file is destined.

Immediate Origin Name - 23 Positions - File Header Record - Required

The field contains the name of the ACH or sending point that is sending the file.

Individual Identification Number - 15 Positions - Entry Detail Record - Optional

This field contains the accounting number by which the individual is known to the company. It is included
for further identification, and for descriptive purposes. The receiving bank should assume no specific format
to be present (e.g. presence or absence of dashes), but can assume that the field is pre-edited so that it is
suitable for description as is (including blanks in unused positions.)

Individual Name - 22 Positions - Entry Detail Record - Required

This field entered by the company provides additional identification for the recipient and may be helpful in
identifying returned entries.

Originating Financial Institution Identification - 8 Positions - Company/Batch Header

and Control Record - Mandatory
The transit routing number is used to identify the financial institution originating entries within a given batch.
The value that should be utilized is 02200002.

Originator Status Code - 1 Position - Company/Batch Header Record - Mandatory

This code is assigned by the ACH to indicate to the receiving bank the type of warranties associated with
the entries in a given batch. The value of the Originator Status Code should be ‘1’.

Priority Code - 2 Positions - File Header Record - Required

This field is included to allow for some future scheme for priority handling of files. At this time, a value of
'01' should be used.

Receiving Bank Account Number - 17 Positions - Entry Detail - Required

The bank account number, the receiving bank's customer identification, is obtained from the "on-us" field of
the MICR line of a voided check or deposit ticket. Dash cue symbols in the field must be included;
however, they are recorded in a translated mode as "-" (hyphen). If fewer than 17 characters are required, left
justify and leave the unused spaces blank. Exact formatting of the account number is essential
to ensure standard positioning of account number characters when entries are received for processing at the
receiving bank.

Receiving Bank Identification - 8 Positions - Entry Detail Record - Mandatory

The transit/routing number of the receiving bank.

Record Size - 3 Positions - File Header Record - Mandatory

The record size field indicates the number of characters contained in each record. At this time, the value '094'
must be used.

NACHA HSBC File Format Specifications 07/17/2018 Page 10 of 12

Record Type Code - 1 Position - All Record Formats - Mandatory
The first position of each record, identifies the type of record.

1 = First line of file (File Header Record)

5 = First line of a batch (also known as a "transaction-set")
6 = Second line of a batch (Entry Details Record)
8 = Final line of a batch (Company/Batch Control Record)
9 = Last line of file (File Control Record )

Reference Code - 8 Positions - File Header Record - Optional

This field is reserved for information pertinent to the originator.
Service Class Code - 3 Positions - Company/Batch Header and Control Record - Mandatory
A value of "200" in this field allows for a free mixture of debits, credits, and prenotifications in any batch.
Other class codes would be more restrictive.

Standard Entry Class - 3 Positions - Company/Batch Header - Mandatory

This field is a mnemonic which permits various kinds of entries to be distinguished. For payroll applications,
the alphabetic mnemonic to identify entries is "PPD".
Other codes that can be used:

Definition Term
ACK Acknowledgement Entry
CCD Corporate Credit or Debit
BOC Back Office Conversion
POS Point of Sale
POP Point of Purchase
ARC Accounts Receivable Entry
CBR Corporate Cross Border Payment
CIE Customer Initiated Entry
COR Automated Notification of Change
CTX Corporate Trade Exchange
DNE Death Notice Entry
PBR Consumer Cross Border Payment
PPD Prearranged Payment and Deposit Entry
RCK Re Presented Check Entry
TEL Telephone Initiated Entry
WEB Internet Initiated Entry

Total Debit or Credit Entry Dollar Amount - 12 Positions - Company/Batch Control and
File Control Records - Mandatory
These fields contain accumulated entry detail debit and credit totals within a given batch (Company/Batch
Control Record) and accumulated Company/Batch Control Record debit and credit totals within a given file
(File Control Record.)
Trace Number - 15 Positions - Entry Detail Record - Mandatory
The Trace Number (zeroes from the customer) is reassigned by HSBC in ascending sequence and included
on all entry detail records. Trace Numbers uniquely identify each entry within a batch in an ACH input file.
In association with the Batch Number, Transmission (File Creation) Date, and File ID Modifier, the Trace
Number uniquely identifies an entry within a given file.

NACHA HSBC File Format Specifications 07/17/2018 Page 11 of 12

Throughout the entire processing cycle (from HSBC to Receiving Bank) the Trace Number is retained with
the entry record. The Trace Number is critical in routing returned entries from the Receiving Bank back to
HSBC through the ACH.

The trace number is constructed as follows:

Positions:
01 - 04 Transit routing number of originating bank (usually head office)
05 - 08 ABA number of originating bank (usually head office)
09 - 15 Item number assigned in ascending order to records within each batch

Provisions should be made by the originating bank to avoid duplication of trace numbers if multiple data files
are prepared on the same day. Trace numbers are not required
to be contiguous.

Transaction Code - 2 Positions - Entry Detail Record - Mandatory

Transaction codes have been defined to identify various types of debit and credit entries. Demand Account
Credits

22 Automated Deposit
23 Prenotification of Demand Credit Authorization Demand Account Debits
27 Automated Payment (debit)
28 Prenotification of Demand Debit Authorization Savings Account Credits
32 Automated Deposit
33 Prenotification of Savings Credit Authorization Savings Account Debits
37 Automated Payment (Debit)
38 Prenotification of Savings Debit Authorization

Transmission (File Creation) Date - 6 Positions - File Header Record - Mandatory The transmission
(file creation) date is the date on which the file is prepared by an originating bank or company (ACH input
files) or the date (exchange date) on which a file is transmitted from ACH to ACH, or from ACH to receiving
banks (ACH output file).

Transmission (File Creation) Time - 4 Positions - File Header Record - Optional

The transmission (file creation) time is expressed in an "HHMM" (24-hour clock) format.

NACHA HSBC File Format Specifications 07/17/2018 Page 12 of 12