Create CFA Bank - Bottomline Technologies

118. . . . .CHAPTER 3: CFA & ACH MODULESTransaction CodesBatch Header Record (excluding CBR and PBR)Field 1 2 3 4 5 6 7 8 9 10 11 12 13DataElementNameFieldInclusionRequire-mentRecordTypeCodeServiceClassCodeCompany Name CompanyDiscretionaryDataCompanyIdentificationStandardEntryClassCodeCompanyentryDescriptionCompanyDescriptiveDateEffectiveEntryDateSettlement Date(Julian)M M M O M M M O R inserted byACHOperatorContents “5” Numeric Alpha-# Alpha-# Alpha-# Alpha-# Alpha-# Alpha-#YYMMDDNumericOriginatorStatus Code Originating DFIIdentificationM M MAlpha-#TTTTAAAABatchNumberLength 1 3 16 20 10 3 10 6 6 3 1 8 7Position 01-01 02-04 05-20 21-40 41-50 51-53 54-63 64-69 70-75 76-78 79-79 80-87 88-94Numeric1 Record Type Code - a ‘5’ indicates that this is the Batch Header Record; the “five record”2 Service Class Code - Identifies the general classification of dollar entries to be exchanged; numbers forACH transactions are 200-299. Some examples are: ‘200’ ACH Entries Mixed Debits and Credits;‘220’ ACH Credits Only; ‘225’ ACH Debits Only; ‘280’ ACH Automated Accounting AdviceOOD: ‘Service Class Code’ field of Batch Header Record within Bank Setup (Format Tab) or PB Logic3 Company Name – Name of entity originating the ACH fileOOD: ‘Company Name’ field of Batch Header Record within Bank Setup (Format Tab) or Company Setup, within ACHBank Setup (linked to Company ID)4 Company Discretionary Data – Optional file descriptionOOD: FIELD(BATCH_DISCRETIONARY) or ‘Company Discretionary Data’ field of Batch HeaderRecord within Bank Setup (Format Tab)5 Company Identification - ID Number of entity originating the ACH file; generally a Tax ID is usedOOD: Directly from Bank Setup, but indirectly from FIELD(COMPANY_ID)/FIELD(TRANSIT)/FIELD(ONUS) orParticipant Setup (from Par Lookup at process time)6 Standard Entry Class Code – i.e. ‘PPD’, ‘CCD’, ‘CTX’OOD: FIELD(ENTRY_CLASS) or Participant Lookup or PB logic (CT(B) + w/RMR lines|w/addenda|w/o RMRLines|w/o addenda = CTX|CCD+|CCD|CCD; CT(P) w/addenda|w/o addenda = PPD+|PPD)7 Company Entry Description - Description for receiver; examples include ‘Gas Bill’; ‘Ins. Prem’, etc.NOTE: this field had mandatory values when sending reversal entries, reclamation entries, and nonsettledentries.OOD: FIELD(BATCH_DESCRIPTION) or ‘Company Entry Description’ field of Batch Header Record within BankSetup (Format Tab)8 Company Descriptive Date - Date as Originator wants it to be displayed to receiver. Date shown onreceiver’s statement.OOD: ‘Company Descriptive Date’ field of Batch Header Record within Bank Setup (Format Tab). User can use a formatmask or hard coded date.9 Effective Entry Date - Date which Originator intends transaction to be settledOOD: FIELD(PAYMENT_DATE)10 Settlement Date – Date entered by the ACH Operator that is the actual settlement date of the transaction.Equals the Effective date but in Julian Date Format.OOD: ‘Settlement Date’ field of Batch Header Record within Bank Setup (Format Tab). User can use aformat mask or hard coded date.11 Originator Status Code - Identifies the Originator as a depository financial institution that has agreed tobe bound by the ACH Rules vs. a federal government entity or agency not subject to these rules. ‘1’ –DFI, ‘2’ – Federal Government AgencyOOD: ‘Originator Status Code’ field of Batch Header Record within Bank Setup (Format Tab) or PB Logic12 Originating DFI Identification - used to identify the DFI originating entries within a given batch.OOD: ‘Originating DFI Identification’ field of Batch Header Record within Bank Setup (Format Tab) or Bank SetupIntransit Number13 Batch Number – A unique number assigned in ascending sequence to each batch contained within a file(the batch number should be the same for corresponding ‘5’ and ‘8’ records).118 CFA & ACH Reference Manual