Skip to content

Latest commit

 

History

History
17 lines (16 loc) · 3.26 KB

File metadata and controls

17 lines (16 loc) · 3.26 KB

BatchHeader

Properties

Name Type Description Notes
ID String A client-defined ID used as a reference to this batch [optional]
serviceClassCode Integer Service Class Code - Mixed Debits and Credits '200', ACH Credits Only '220', or ACH Debits Only '225'
companyName String Company originating the entries in the batch
companyDiscretionaryData String The 9 digit FEIN number (proceeded by a predetermined alpha or numeric character) of the entity in the company name field [optional]
companyIdentification String Alphanumeric code used to identify an Originator. The Company Identification Field must be included on all prenotification records and on each entry initiated pursuant to such prenotification. The Company ID may begin with the ANSI one-digit Identification Code Designator (ICD), followed by the identification number. Possible ICDs are the IRS Employer Identification Number (EIN) "1", Data Universal Numbering Systems (DUNS) "3", or User Assigned Number "9".
standardEntryClassCode String Identifies the payment type (product) found within an ACH batch using a 3-character code.
companyEntryDescription String A description of the entries contained in the batch. The Originator establishes the value of this field to provide a description of the purpose of the entry to be displayed back to the receiver. For example, "GAS BILL," "REG. SALARY," "INS. PREM,", "SOC. SEC.," "DTC," "TRADE PAY," "PURCHASE," etc. This field must contain the word "REVERSAL" (left justified) when the batch contains reversing entries. This field must contain the word "RECLAIM" (left justified) when the batch contains reclamation entries. This field must contain the word "NONSETTLED" (left justified) when the batch contains entries which could not settle. [optional]
companyDescriptiveDate String 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. The RDFI should not assume any specific format. [optional]
effectiveEntryDate String Date on which the entries are to settle. (Format YYMMDD - Y=Year, M=Month, D=Day) [optional]
originatorStatusCode Integer ODFI initiating the Entry. 0 - ADV File prepared by an ACH Operator.
odFIIdentification String First 8 digits of the originating DFI transit routing number
batchNumber Integer BatchNumber is assigned in ascending sequence to each batch by the ODFI or its Sending Point in a given file of entries. Since the batch number in the Batch Header Record and the Batch Control Record is the same, the ascending sequence number should be assigned by batch and not by record.