Bank of America AUTOMATED CLEARING HOUSE SERVICES NACHA File Layout User Guide Electronic Payment ServicesCONFIDENTIAL INFORMATION “This user guide contains proprietary and confidential information of Bank of America and was prepared by the staff of Bank of America. This user guide may not be reproduced or disclosed to others in whole or in part without the written permission of Bank of America Permitted reproductions shall bear this notice and the Bank of America copyright notice “The user ofthis user guide acknowledges the rights of Bank of America in the contents and agrees f0 maintain this user guide and its contents in confidence. ‘This user guide applies to services that are available through an office or branch in the states listed below. Services available through offices or branches in other states may be different from those described ia this user guide. Fees may vary from state to state Bank of America NT&SA in California and Illinois a Member FDIC © 1998 BankAmerica Corporation ‘Adapted from 1998 ACH Rules, A Complete Guide ro Rules and Regulations Governing the ACH Network, National Automated Clearing House Association (NACHA) © 1998 Al rights reserved. None of the enclosed material may be reproduced or published without permission of Bank of Ameria. CCM.970 (Rev. 898) 23 rocycies PaperContents ‘SECTION 1 INTRODUCTION About This Guide ‘SECTION 2 INPUT FILES TO BANK OF AMERICA Overview. NACHA Data Entry Spe Field Inclusion Requirements. Sequence of Records. Sequence of Records Diagram, Input File Descriptions, Contingency: Magnetic Tape File Requirements ‘SECTION 3 ACH RECORD FORMATS FOR ORIGINATED FILES (PPD, CCD, CTX anb REVERSAL FILES) Overview, Prearranged Payment and Deposit Format (PPD).. File Header Record - PPD Format . Company/Batch Header Record - PPD Format Entry Detail Record - PPD Format ‘Company/Batch Control Record - PPD Format. File Control Record - PPD Format Cash Concentration or Disbursement Format (CCD) File Header Record - CCD Format Company/Batch Header Record - CCD Format Entry Detail Record - CCD Format Special Addenda Record - CCD Format Company/Batch Control Record - CCD Format. File Control Record - CCD Format. Contents i‘SECTION 3 (CONTINUED) Corporate Trade Exchange (CTX), File Header Record - CTX Format ‘Company/Batch Header Record - CTX Format. Entry Detail Record - CTX Format. Special Addenda Record - CTX Format Company/Batch Control Record - CTX Format. File Control Record - CTX Format. Reversal File Specifica File Header Record (Record Type “I Company/Batch Header Record (Record Type “S"). Entry Detail Record (Record Type “6") Company/Batch Control Record (Record Type “8"). File Control Record (Record Type “9. ‘SECTION 4 OUTPUT FILES (REPORTING) FROM BANK OF AMERICA, RETURN ENTRIES AND NOTIFICATIONS OF CHANGE iv Contents Sequence of Records.. Diagram of Sequence of Records for CCD, PPD. and CTX Return Entries and Notifications of Change. 43 Record Format Descriptions ~ Return Entries and Notifications of Change. : 7 File Header Record for Return Entries and Notitications of Change . 4 Company/Batch Header Record - Return Entry 44 Entry Detail Record - Return Entry 45 ‘Addenda Record - Return Entry 46 Company/Batch Control Record - Return Entry... 46 ‘Company/Batch Header Record - Notification of Change 47 Entry Detail Record - Notification of Chang 47 ‘Addenda Record - Notification of Change... 48 Company/Batch Control Record - Notification of Change 49 File Control Record - Return Entries and Notifications of Change... 4-9—”=? ———————— ‘SECTIONS CODE VALUES AND GLOSSARY Code Values... ‘Addenda Record Indicator Record Type Codes, Service Class Codes. Standard Entry Class Codes. Transaction Codes Glossary of Data Elements. Contents voo ES Introduction IN THIS SECTION About This Guide 12a About This Guide 1-2. NACHA Fue Layout User Guide The NACHA File Layout User Guide is intended for systems analyst and systems support functions. The purpose of this guide is to provide technical information regarding National Automated Clearing House Association (NACHA) formatted files. All originating companies must transmit NACHA-formatted files according to the NACHA format specifications provided here. Sections 2 through 5 provide the following information: Section 2. Input Files to Bank of America Section 3, ACH Record Formats for Originated Files 1m Section 4. Output Files (Reporting) from Bank of America, Return Entries, and Notifications of Change m Section 5. Code Values and Glossary Refer to the Contents for quick reference to any topic: Effective 08/08<6 ES eee Input Files to Bank of America IN THIS SECTION Overview et 22 NACHA Data Entry Specifications. 23 Field Inclusion Requirements. sensnnnnnennnee 2A Sequence of Records un ennnnnnn 25Overview Automated Clearing House (ACH) entries must be delivered to Bank of ‘America (Bank or BofA) in the National Automated Clearing House ‘Association (NACHA) format. The NACHA format is a national standard accepted by all ACH member financial institutions. The processing of these entries is governed by NACHA Operating Rules, which is the contract binding all participants. In this section, information is provided for: m= NACHA Data Entry Sper m= Field Inclusion Requirements cations Sequence of Records and Input File Descriptions 2.2 NACHA File Layout User Guide Ettecive 04/88€ NACHA Data Entry Specifications Etfectve 0408 The table below contains specifications for data entry in NACHA format Entry Type | Permited Characters ‘Alphanumeric Fields Numeric Fields Specifications 08 AZ (upper case only) = Blank «= Fill any unused spaces with blanks. 1 Use uppercase on all alpha felds. Asterisk cl Ampersand [8] Comma ul Hyphen Cl Decimal = [.] DoliarSign [5] Lefjustfy al alphanumeric elds. Rightjustly all numeric fields Fill any unused spaces tothe le with zeros. Leave all numeric fds unsigned. Include cents with all amounts but do not include a decimal ma Ingut Files to Bank of America 2-3a 6 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 (M), Required (R), and Optional (0), 1 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. As a result, the Bank will edit for these same values so that your ACH entries will not reject further in the processing stream 1m Required. The omission of a “Required” field will not cause an entry reject at the ACH Operator, but may cause a reject at the RDFI. An example is the DFI Account Number field in the Entry Detail Record. If this field is omitted by an ODFI, the RDF may retum the entry as nonpostable. Data classified as “Required” should be included by the Originator and ODFI to avoid processing and control problems at the RDFL. Optional. The inclusion or omission of an “Optional” data field is at the discretion of the Originator and ODF. However, if a DFI does originate files using optional data fields, these fields must be retumed to the ODFI if the entry is returned, C 24 NACHA File Layout User Guide Effective 04/08a €& Sequence of Records ‘An input file consists of the following record types: ACH Header Logon Record, File Header Record, Company/Batch Header Record, Entry Detail Record, Company/Batch Control Record and File Control Record. The Special Addenda Record may optionally be included with the Entry Detail Record. All records are 94 characters in length, Each file begins with an ACH Header Logon Record, then the File Header record. After the File Header may be any number of batches. Each Batch is identified by a Batch Header Record and contains one or more Entry Detail Records. The number of addenda records that accompany each entry is dependent upon the Standard Entry Class Code. At the end of each bateh is a Batch Control Record. Each file is ended with a File Control Record and an ACH Trailer Logon Record, Refer to page 2-6 for a diagram that illustrates the Sequence of Records. Complete descriptions of each record begin on page 2-7. Etectve 04/68 Input Files to Bark of America 2-5EEE 6 ‘SEQUENCE OF RECORDS DIAGRAM The following diagram shows the sequence of records for NACHA formatted files. ACH HEADER LOGON RECORD FILE HEADER RECORD COMPANY/BATCH HEADER RECORD ENTRY DETAIL RECORD(S) SPECIAL ADDENDA RECORD (optional) COMPANY/BATCH CONTROL RECORD COMPANY/BATCH HEADER RECORD ENTRY DETAIL RECORD COMPANY/BATCH CONTROL RECORD FILE CONTROL RECORD 2.6 NACHA File Layout User Guide Etrectve 04/88fa INPUT FILE DESCRIPTIONS ACH Header Logon Record This record permits data to be processed by the Bank of America transmission system. This record includes Company ID and proc: specifications. File Header Record ‘The File Header Record designates physical file characteristics and identifies the immediate origin of the entries contained within the file or within the transmitted batched data. In addition, this record includes date, time, and file identification fields that can be used to identify the file uniquely. Company/Batch Header record | “The Company/Batch Header Record identifies the Originator and briefly | describes the purpose of the entry. For example, “GAS BILL" or “REG SALARY" indicates the reason for the transaction originated by the Originator. It also indicates the intended effective entry date of all € > transactions within the batch. The information contained in the Company/Batch Header Record applies uniformly to all subsequent Entry Detail Records in the batch, Entry Detail Records Entty Detail Records contain that information sufficient to relate the entry to the Receiver, ie, individual DFI account number, identification number, name, and the debit or credit amount as indicated by the Transaction Code. The information in the Company/Batch Header Record must be incorporated withthe Entry Detail Records to describe fully that entry and all participants in the transaction. The information in the Company/Batch Header Record identifies the Originator; the Trace Number (which Bank of America assigns) identifies the ODFI; DFI account information identifies both the RDF and the specific account. In addition to the basie entry format, Transaction Codes for Entry Detail Records have been defined to accommodate prenotification records, zero dollar entries, and retum entries Prenotifications are identical to the basic entry format but contain appropriate Transaction Codes and zeros in the Amount field. Prenotifications can be batched with other dollar entries or batched separately, Effective 04/98 Input Files to Bank of America 2-7€ 2.8 NACHA File Layout User Guide Zero dollar entries are identical to the basic entry format but contain appropriate Transaction Codes and zeros in the Amount field. Zero dollar entries can be batched with other CCD or CTX dollar entries or batched separately. A zero dollar entry must be accompanied by at least one ‘Addenda Record. Retum entries are distinguished by special Transaction Code and must be batched separately from other dollar entries. If you wish to receive a NACHA-formatted file of your returns, please turn to the section in this ‘guide that describes the NACHA Record Format Descriptions. ~ Addenda Records ‘Addenda Records are optional. They are used by the Originator to supply additional information about Entry Detail Records which will be passed fiom the ODFI through the ACH Operator to the RDF Tote: With any Entry Detal Record being returned, nly the fist Addenda Record [ssociated withthe original Entry Detal Record wil be included withthe raturn. Only NACHA sanctioned formats will be permitted, as specified by the ‘Addenda Type Code. Addenda record information may only be used for the purpose of transmitting payment related information, Any other use is, C prohibited. L For CCD, PPD, and CTX applications, the corresponding number of ‘optional addenda records is listed below: ‘Maximum Number Application Contents Addenda Records CCD, PPD ANSIASC X12 data segments, payment 1 ‘elated data formatted to banking industry | standards, | crx ‘ANSI ASG X12 5 and X126 syntax, an ASC 9,999 X12 tansaction set containing a BPR or BPS | data segment, or payment related | UNEDIFACT syntax Ettecive 0498SE Company/Batch Control Record 6 ‘The Company/Batch Control Record contains the counts, hash totals, and total dollar controls for the preceding detail entries within the indicated batch. All Entry Detail Records are hashed. Both Entry Detail Records and ‘Addenda Records are included in the entry/addenda counts; Batch Header and Batch Control Records are not included. File Control Record ‘The File Control Record 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 (or batched data transmitted to a single destination). € effective 04/08 Input Files to Bank of America 2-96 ES eee ACH Record Formats for Originated Files (PPD, CCD, CTX and Reversal Files) IN THIS SECTION OVErVIEW nnn sennomene 32 Prearranged Payment and Deposit Format (PPD) 33 cx Cash Concentration or Disbursement Format (CCD)... 3-10 € Conant Tae Eehage (CTX) sa Reversal File Specifications nnn 3:26P| € Overview ‘The ACH record format specifications are designed to assist ACH participants in properly formatting and retrieving transaction information This section details the contents ofthe various record formats and defines the code values and data elements. The inclusion requirements, contents, and lengths of data elements are illustrated in the record formats, which are arranged according to their sequence in the file. The glossary in Section 5 defines and explains the application of each fied. On the following pages are the ACH record formats for PPD, CCD, CTX and Reversal Files, as listed below. Detailed examples are given within the tables and further help is provided in Section 5, “Code Values and Glossary.” m= Prearranged Payment and Deposit Format (PPD) File Header Record ‘Company/Batch Header Record Entry Detail Record ‘Company/Batch Control Record File Control Record ‘4 Cash Concentration or Disbursement Format (CCD) File Header Record CompanyBatch Header Record ¢ Entry Detail Record Special Addenda Record ‘Company/Batch Control Record File Control Record = Corporate Trade Exchange (CTX) File Header Record. Company/Batch Header Record Entry Detail Record Special Addenda Record ‘Company/Batch Control Record File Control Record Reversal File Specifications File Header Record Company/Batch Header Record Entry Detail Record Company/Batch Control Record File Control Record 3-2 NACHA File Layout User Guide Etfecive 04/98Cc Prearranged Payment and Deposit Format (PPD) ‘The Record Formats in this subsection apply to: '& Electronic Deposit Service (EDS). The initiation of preauthorized credit entries to consumer accounts to disburse recurring payments (c.g., payroll), ‘Electronic Consumer Payment (ECP). The initiation of preauthorized debit entries and/or the issuance of checks drawn on consumer accounts to collect recurring payments (e.g, health club and insurance premium dues) ACH Record Formats for Originated Fes 3-3 Etfective 04/08PIL € Fie HEADER RECORD - PPD FORMAT ‘The File Header Record designates physical file characteristics. t also : identifies the Bank as the immediate destination and your company as the immediate origin of the file. od Gor ce MRO a re Record Type | Code identifying the File Header Recordis | | M Code 1 2 | 0203 | 2 [-o1" Priority Code _ | Currenty, only “01"is used R 3 | 0413 | 10 [ENNNNNNNNN [immediate | BofA assigned number that identifies BofA | M Destination —_| as the destination of your input files. b121108250 = San Francisco | (b" indicates a blank space) [4 | 1423 [710 [NNNNNNNNN | immediate ‘Your 10-digit company number assigned by | M | i Origin BofA 5 | 2429 | 6 [vymmoD File Creation | The date you create or transmit the input fle: | M | Date "YY" = Last two digits of the Year “bors oern ost Month in two digits 6 | s033 | 4 7 [seas [1 JUPPERGASE [Fie 10 Moaiter [Code o distinguish among mulple put | M az fies Label the frst or on Tle“A° and | cain in eaquenen, 3 | 3537 | 3 [ose Record Size | Number of bytes per record " @ | seve | 2 [to Blocking Factor | Number of records per block M [ie [aoa [tr Fomat Code | Curent, ony“ is used M 71] 4163 | 23 |Aphenumene [ark Name | Describes BotA asthe orgnatng franca | M institution (e.g. "BOFA SAN FRANCISCO) Assigned by BofA, 12 | 6486 | 23 [Alphanumeric | Company ‘Your company’s name, up to 23 characters | M | Name including spaces. 73 | e724 | 8 [Alphanumeric [Reference | Youmay use this field to describe the input | 0 Code file for internal accounting purposes. 2-4 NAGHA File Layout User Guide Etrecive 04188rearranged Payment and Deposit Format (PPD) COMPANY/BATCH HEADER RECORD - PPD FORMAT The Company/Batch Header Record identifies your company, briefly describes the Entry Detail Records in the batch and designates the effective entry date Field Position Size Contents Gc ae co 1 [oro [ot [os Record Type | Code identifying the CompanyiBatch Header | | M Code Record is “5 2 | 0204 | 3 |200" ‘Service Class | Identifies the type of entries in the batch. Mw Code Code "200" indicates debit, credit and | prenotification entries. 3 | 0520 | 16 [Alphanumeric | company Your company name. This may appearon | M Name | payee's account statements 4 | 21-40 | 20 | Alphanumeric | Company | For your company’s internal use. ° Discretionary Data 5 | 41-50 | 10 [NNNNNNNNN | Company ‘Your 10-digit company number assigned by | M N Identification | BotA. 6 | srss | 3 [PPD ‘Standard Entry | Identifies the ACH record type in a batch M Class Code | “PPD” (Prearranged Payment and Deposit) sed for preautharized credit/deposit entries and receiver debit entries. 7 | 8463 | 10 [Alphanumeric | Company Entry | Description of the purpose of the entries M Description | (e.g, "PAYMENT" or PAYROLL’) This may print on the payee's account statements. 3 | 6469 | 6 [Alphanumeric | Company Date you choose to identify the envies for | 0 Descriptive | descriptive purposes only. Can be in any Date format 9 | 7075 | 6 [vymmoo Effective Entry | Date you desire funds to post to payee's R Date account, “YY"= Last two digits of the Year “MMT = Month in two digits "DD" = Day in two digits 10 | 76-78 | 3 [Blank ‘Settlement Date | Fill wth blanks. This field is used by the R receiving ACH to indicate the actual settlement date, 1 | vere [ot [or ‘Originator Identifies the originator as a financial M Status Code _| institution 32 | 60-87 | 8 |NNNNNNNN | Originating DFI | BofA assigned number: M Identification | 42110825" = San Francisco 13 | aec4 | 7 [Numeric Batch Number | Assign batch numbers sequentially in ™ ascending sequence Effective 04/98 ACH Record Formas for Orginated Files 2 5Seer ENTRY DETAIL RECORD - PPD FORMAT ‘One Entry Detail Record is created for each entry. It contains the information required to post the entry to the payee's account, Field Name Entry Information Record Type | Code identitying the Entry Detail Record is | M Code a 2 | 0203 | 2 [Numeric Transaction | Two-digit code that identifies checking’ and | Mt Code savings account credits/debits or Prenotifications.** Valid codes are: 22 = Automated deposit (checking credit) 23 = Prenotifcation of checking credit Authorization (non-dollar) 27 = Automated payment (checking debit) 28 = Prenotifcation of checking debit ‘authorization (non-dollar) 32 = Automated deposit (savings credit) 33 = Prenotifcation of savings credit ‘authorization (non-doliar) 37 = Automated payment (savings debit) 28 = Prenosicaton of savings debit ¢ auivorzabon (non eota) 3 | oat [ @ [TrTTAAAA —[ROFITransit | Transit Routing/ABA number of the M Routing/ABA | receiver's financial institution. Identification Number umber used to route entries to the appropriate RFI. 4 [tata [1 [Numeric Transit Routing | The ninth character in the Transit M Check Digit | Routing/ABA number. Used to check for transpositions, 5 | 1329 | 17 [Alpnanumeric | OF! Account | Receiver's account number atthe ROFI that | M Number ‘may be found on the MICR line of a voided check. Enter the MICR Oash Cue Symbol as a hyphen ("). Account numbers vary in format. If the account number has less than 17 characters, letjustiy, blankcfil. Ignace any blank spaces within the account number. 6 | 30-39 | 10 [sssssssse¢ | Amount Entry amount in dollars with two decimal ™ places. Right-ustty left zero-fil. Do not enter a decimal point. Enter 10 zeros for rnon-doliar prenotification entries," Continued on next page * Checking includes checking accounts, NOW and share draft accounts. ** Prenotification records are non-dollar entries with unique transaction codes and must contain zeros in the ‘Amount Field. 3.6 NACHA File Layout User Guide Effective 04/98EI ENTRY DETAIL RECORD - PPD FORMAT (CONTINUED) Field Position Size Contents ae ey oo 7 | 4054 | 15 [Alphanumeric | individual ‘Company's identification number for the ° Identification | receiver. The number may print on the Number payee's account statement. 8 | 85-76 | 22 [Alphanumeric | individual Name| Name of payee, R 9 | 77-78 | 2 [Alphanumeric | Reserved Debit Entries ONLY (Transaction Codes “27° and “37: | “17° = BofA to choose best way - Electronic | ‘or preauthorized check. if you plan on using this feature, please contact Customer Service, "ob" = Electronic only “1 = Preauthorized check only Leave this field blank for all other entries. to | 7979 | 1 [Numeric ‘Addenda “0° = No addenda supplied. M Record Indicator at | 20.04 [ 15 [Numeric Trace Number | Fillwith zeros, BofA assigns and enters the | M trace number. ** Prenotification records are non-dollar entries with unique transaction codes and must contain zeros in the Amount Field. Etfecive 04/08 ACH Record Formats for Originated Files. 3-7ene) ( ‘COMPANYIBATCH CONTROL RECORD - PPD ForMAT ‘The Company/Batch Control Record concludes the batch and contains the item count and dollar totals for the Entry Detail Records in the batch Eee Field Name Entry Information cod 1 | ovor [1 [a Record Type | Code identifying the Company! Batch mt Code Header Record is “8” 2 | o2os | 3 [+2007 ‘Service Class _| Identifies the type of entries in the batch, M Code Code “200” indicates debit, credit and prenatifcation entries 3 | 05-40 | 6 [Numeric Entry! otal number of Entry Detail Records M (Record Type 6°) in the batch. Requires 6 Addenda Count | positions, rightjustity, left zero 4 | 14-20 | 10 [Numeric Entry Hash | Total of eight-character Transit Routing/ABA | M numbers in the batch (field 3 of the Entry Detail Record). Do not include the Transit Routing Check Digit. Enter the ten low-order | Gagnt most) digits of this number | 3 | are | 12 [ssssssssssee | Total Dede | Ooliartotal of debit entries inthe baton | M Entry Dollar | none, 280i the field. Do not enter a Amountin | decimal point. Right justify, let zero Batch Beas | 12 [Ssssssssssee | Total Great | Dollar total of creat entries inthe batch. | M Entty Dollar | none, zeros the field. Do not enter a Amountin | decimal pint. Rightjusty eft zero Batch 7 | 4554 | 10 [NNNNNNNNN [Company | Your 10-digit company number assigned by | M N Identifcatin | BofA, Must match Field § ofthe Company! Batch Header Record. 3573 | 19 [Aphanumere [Reserved | Leave tis field blank ‘Alphanumeric [Reserved | Leave this feld biank 70 | 8087 | 8 [NNNNNNNN | Originating OF! | BotA assigned number: ™ 'dentifcaton |+42110825" = San Francisco at | essa [7 [Numeric ‘Batch Number | Number of the batch for which this is a ™ control record. Number the batches sequentially. Must match Field 13 of the Company/Batch Header Record. 3:8 NACHA File Layout User Guide Ettectve 04/98Ene FILE CONTROL RECORD - PPD FORMAT The File Control record contains dollar, entry, and hash totals from the file's ‘Company/Batch Control Records. This record also contains counts of the blocks and batches in the file. Po GL teed cor 1] oor] 1 [ro Record Type | Code identitying the File Control Recordis | M Code 7 2 | 0207 | 6 [Numeric Batch Count | Total number of Company/Batch Header Mw Records (Record Type °S") in the file. 3 | 0843 | 6 [Numeric Block Count | Total number of physical blocks in the file, M including the File Header and File Control | Records, 4 | 1421 | 8 [Numeric Entry/ Addenda | Total number of Entry Detail Records M Count (Record Type 6") in the fl 5 | 221 | 10 [Numeric Entry Hash | Total of eight character Transit RoutingiABA | M numbers in the file (Field 3 of the Entry Detail Record). Do not include the Transit Routing Check Digit. Enter the 10 low-order (oght most) digits of this number. | 3243 | 12 [ssssssssssee [Total Debt | Dollar total of debit entries in the file. none, | M Entry Dollar | zerosfil the field. Do nat enter a decimat Amountin File | point. Right-ustily left zero-fi. 7 | 4455 | 12 [sssssssssse¢ | Total Creat | Dollar total of credit entries in the file. If M Entry Dollar | none, zero-fil the field. Do not enter a Amount in File | decimal point. Rightjustily, left zero-fl 3 | s604 | 39 [Blank Reserved Leave this field blank R Effectve 08/98 ACH Record Formats for Onginated Files 3:9a ¢ Cash Concentration or Disbursement Format (CCD) ‘The Record Formats in this subsection apply to: m Electronic Trade Payments (ETP). The initiation of preauthorized debit and/or credit entries and the issuance of checks to move funds to or from accounts of other companies. Electronic Concentration Service (ECS). The initiation of credit and/or debit entries and the issuance of checks to move funds between the customer's account at Bank of America and accounts owned or controlied by the customer. 3:10 NACHA File Layout User Guide Etectve 04/08[Cash Concentration or Disbursement Format (CCD) Fite HEADER RECORD - CCD FORMAT ‘The File Header Record designates physical file characteristics. It also identifies the Bank as the immediate destination and your company as the immediate origin of the file. oe Field Name Entry Information MRO 1 [ovo for [ar Record Type | Code identitying the File Header Record is. | M Code at 2 | 0203 “OF Priority Code _ | Currently, only 01" is used R 3 | 04-43 [10 [bNNNNNNNNN | immediate | BofA assigned number that identifies BofA | M Destination _| as the destination of your input fies: 121108250 = San Francisco Cb" indicates a blank space) 4 | 14:23 [10 [NNNNNNNNN [immediate | Your 1O-digit company number assigned by | _M N Origin BofA 5 | 2429 | 6 |vymmoo File Creation | The date you create or transmit the input fie: | _M Date’ "YY" = Last two digits of the Year “MNT = Month in two digits 6 | 3033 | 4 [HHMM File Creation — | Time of day you create or transmit the input | Date file. This fied is used to distinguish among input files if you submit more than one per day: “HH = Hour based on a 24 hr clock "MMT = Minutes in two digits 7 | 3434 | 1 [UPPERCASE [File ID Modifer | Code to distinguish among multiple input M AZ files. Label the first (or only) fie “A” and continue in sequence, a | s6a7 [3 Record Size _| Number of bytes per record M 9 | seas | 2 Blocking Factor | Number of records per block M to | 4040 | 1 Format Code _ | Currently, only 1" is used M 11 | 41-63 | 23 [Alphanumeric [BankName | Describes BofA as the originating financial | M institution (e.g. “BOFA SAN FRANCISCO") ‘Assigned by BofA, 12 | 6486 | 23 |Ajpnanumerie | Company ‘Your company's name, up to 23 characters | M Name including spaces. 13 | 97-94 | 8 [Alphanumeric | Reference | You may use this field to describe the input | © Code file for internal accounting purposes, Etfectve 04/98 [ACH Record Formats for Originated Files. 3-11CMS) COMPANY/BATCH HEADER RECORD - CCD FORMAT ‘The Company/Batch Header Record identifies your company, brief describes the Entry Detail Records in the batch and designates the effective entry date. Date “YY” = Last two digits of the Year Identification | «42410825" = San Francisco sates 3:12. NACHA File Layout User Guide Etfectve 04/98EI Entry DETAIL RECORD - CCD FORMAT ‘One Entry Detail Record is created for each entry. It contains the information required to post the entry to the receiving company’s account. Gee ce ee co + | oro | |e Record Type | Code identitying the Entry Detail Record is. | M Code 6" 2 | 0203 | 2 [Numeric Transaction | Two-digit code that identifies M Code checking/savings accounts, credits/debits or prenotifications.“* Valid codes are: 22 = Automated deposit (checking credit) 23 = Prenotifcation of checking credit authorization (non- 0 Record Format Descriptions ~ Return Et Notifications of Change ..nsnininnnnnnnnnninnsines 44,Sequence of Records 42. NACHA File Layout User Guide (Output files are in NACHA format for return entries and notifications of change and consist ofthe following record types: File Header Record, Company/Batch Header Record, Entry Detail Record(s), Addenda Record(s), Company/Batch Control Record and File Control Record. Each file begins with @ File Header record. Following the File Header Record may be any number of batches. Retum Entries and Notifications of Change will be batched separately within the same file. Each Batch is identified by a Batch Header Record and contains one or more Entry Detail Records. Each Entry Detail Record has an Addenda Record that relays additional information such as the Return or Change Reason Code and the ‘Trace Number of the original item. Each Addenda Record must be formatted in accordance with ANSI ASC X12.5 and X12.6 syntax, an ASC X12 transaction set containing a BPR or BPS data segment, or payment related UN/EDIFACT syntax. Word of caution: W thie formation isnot formatted correctly, your receivers nancial, institutions wil nt be able to process your With any Entry Detail Record being retuned, only the first Addenda Record associated with the original Entry Detail Record will be included with the retum. At the end of each batch is a Batch Control Record. Each file is ended with a File Control Record. Refer to the next page for a diagram that illustrates the Sequence of Records for CCD, PPD, and CTX return entries and notifications of change. Effective 04/98Emre DIAGRAM OF SEQUENCE OF RECORDS FOR CCD, PPD, AND CTX RETURN ENTRIES AND NOTIFICATIONS OF CHANGE | ————— One per fie frst logical record on fle (Gompanyiiatch Header Record] —————— One per baten | (FistEniyDetaiRecord] © Each entry detaihas an addenda record (Agenda Record} | GBecond Detail Record] | Batch 1 (Cast entry Davai Record) | | (Fesdenda Revd) . @ ‘CompanyiBaich Header Record] ———————- One per batch | — Batches 2 through net (Campanyibaten Header Reserd) Fist Envy etal Record i (Gamera Rees) Batch [ast Eiiyy Detail Reco ‘adenda Reesed ([CampanyiBaich Convo! Record] Fis Contre Record —— ne per fte—tast logical record Etective 04/08 (Output Files rom Bank of America, Return Enties, and Notifications of Change 4-3re Record Format Descriptions - Return Entries and Notifications of ¢ Change FILE HEADER RECORD FOR RETURN ENTRIES AND { NOTIFICATIONS OF CHANGE | ‘This file is prepared in a manner similar to the file containing the o entries. For more information on how the file is created, see the NACH Operating Rules. In these applications, the RDFI of the original entries is the ODFI of the Return Entries and Notifications of Change , and the ODFI of the original ! entries is the RDFI of the Retum Entries and Notifications of Change. | | Note that there are some differences between file level information in this file and file level information in the origination file you sent to the Bank. In | the Return Entry and Notification of Change file, the immediate destination and the immediate destination name will have a Bank assigned number and. name. This is different from the information included in the origination file, since the company must send the Bank's transit routing number in the immediate destination field and the Bank’s name in the immediate destination name field, The immediate origin field will contain the Bank's transit routing number and the immediate origin name will have Bank of € 4 Rasiersnrs ( CompPaNy/BATCH HEADER RECORD - RETURN ENTRY The ttc headers you tesive wil be denial t thse you sent inthe sega he Reuse and Noueatons of Change wil fe gouped under maa ater ats eal io thoasogiahyso. Rumer ways satchel sepoely fons Notcavons of Change Allis are he same as they were in the CompanyBatch Header ofthe nes october toed Theis conan ifoeaton Site om te gil enya shown Glow Originating DFI Identi n ‘he Originating D1 Idntcaton i changed fom “12110825 (Bank of Sse TeTRE ug Nua athe natutn ntatng the Noeaton oFtage tie RFT of Orginal Ey). Batch Number The Batch Number eld caries he number pemangthe Ream aay BS tA C\4 q 4-4 NACHA File Layout User Guide Etfecive 08/98Record Format Descriptions ee @ ENTRY DETAIL RECORD - RETURN ENTRY Al fields are the same as they were in Entry Detail Record of the original entry unless noted otherwise. Each field of the Entry Detail Record that has changed from the original entry is highlighted below. Transaction Code ‘The Transaction Code is “21,” 26," “31,” or "36" to reflect that this is a retumed item. For example, ifthe original item had a “22” Transaction Code, the returned item would have a “21” Transaction Code; and so forth for each of the original transaction codes of the returned items, RDF Identification ‘The RDFI Identification field contains “121 10825,” which is the Routing Number of the institution receiving the retumed entry (B of A), Check Digit ‘The Check Digit is calculated based on the RDFI Identification field (ie., the Routing Number of B of A). Addenda Record Indicator The Addenda Record Indicator is changed to “1” to indicate that an addenda | is carried with this entry. Trace Number ‘The Trace Number is generated by the institution preparing the return, Effective 04198 (Output Files fem Bank of America, Retumn Entries, and Notifications of Change 4-5Rae ee ¢ ADDENDA RECORD - RETURN ENTRY An Addenda Record is required for return entries. The Addenda Record carries the original entry trace number and the Routing Number of the RDFI {original entry). Addenda Type Code This field value is “99” because itis a return entry. Original Entry Trace Number ‘The original Entry Trace Number field contains the trace number of the original item as assigned by Bank of America when the file was created, Original RDFI Identification ‘The Routing Number field carries the Routing Number of the RDF! of the original Entry. ‘Trace Number The Trace Number field is assigned by the financial institution originating the return, In this example, the trace number is “123918710000001.” COMPANY/BATCH CONTROL RECORD - RETURN ENTRY | The Company/Batch Control Record summarized the information contained | inthe batch. It contains the counts, hash totals, and total dollar controls for | the preceding detail entries within the batch, For an explanation of the Company/Batch Control Record and how it is, prepared, refer to the NACHA Operating Rules. 4.6 NACHA File Layout User Guide Etectve 04/88' eee eee Ettectve 04/08 COMPANY/BATCH HEADER RECORD - NOTIFICATION OF CHANGE All fields are the same as they were in the Company/Batch Header of the original entry unless otherwise noted. The fields that carry information different from the Original Entry are explained below. Standard Entry Class The Standard Entry Class is changed to “COR" for Notification of Change. Originating DFI Identification ‘The Originating DFI Identification is changed from “121 10825" to the Routing Number of the institution initiating the Notification of Change (the RDFI of the Original Entry) Batch Number The Batch Number is assigned by the institution preparing the Notification of Change. ENTRY DETAIL RECORD - NOTIFICATION OF CHANGE All fields in the Entry Detail Record are the same as they were in the Entry Detail Record of the original entry unless otherwise noted, The fields ofthe Entry Detail Record that carry information different from the Original Entry are explained below. Transaction Code ‘The Transaction Code field is changed to "21," 26," “31,” of “36” because this entry is a Notification of Change. For example, ifthe original item had a ‘Transaction Code, the Notification of Change would have a “21” Transaction Code; and so forth for each of the original Transaction Codes of the corrected items. RDFI Identification ‘The RDFI Identification is changed to "121 10825" to reflect the Routing Number of the institution receiving the Notification of Change (the ODF of, the Original Entry, or BofA). Output Files trom Bank of America, Retuin Enties. and Notfcatons of Change 4-7RE eee ee 4-8 NACHA File Layout User Guide Check Digit The Check Digit is re-calculated based upon the RDFI Identification carried in the Notification of Change Amount The Amount field is Zero for Notification of Change. Trace Number ‘The Trace Number is changed to the Trace Number assigned by the institution preparing the Notification of Change. ‘ADDENDA RECORD - NOTIFICATION OF CHANGE, An Addenda Record carries the corrected information back to the ODFI of the Original Entry The fields of the Addenda Record that cary information different from the Original Entry are explained below. Addenda Type Code ‘The Addenda Type Code is "98" to indicate that the Addenda Record contains automated change information, Change Code ‘The Change Code indicates the information to be corrected. Refer to NACHa Rules for a complete list and explanation of codes. For instance, a Change Code of “COI” indicates “Incorrect Account Number.” Original Entry Trace Number The Original Entry Trace Number carries the Trace Number of the original entry. Original RDF! Identification The Routing Number field contains the data carried in positions 04-11 of the original Entry Detail Record (the RDFI's Routing Number). Corrected Data ‘The Corrected Data field carries the change (corrected) information corresponding to the change code used. Effective 04798 €{ COMPANY/BATCH CONTROL RECORD - NOTIFICATION OF CHANGE in the batch. It contains the counts, hash totals, and total dollar controls for | ‘The Company/Batch Control Record summarized the information contained the preceding detail entries within the batch. i For an explanation of the Company/Batch Control Record and how it is } prepared, refer to the NACHA Operating Rules. FILE CONTROL RECORD - RETURN ENTRIES AND NOTIFICATIONS OF CHANGE | ‘The Fite Control Record summarizes the information carried in the Company/Batch Conteol 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 For an explanation of the File Control Record and how it is prepared, refer to 5 e the NACHA Operating Rules. Ettecive 04188 ‘Output Files from Bank of America, Return Enties, and Notiicatons of Change 49EE Code Values and Glossary IN THIS SECTION Code Values is? Glossary of Data Elements sun 54Code Values 5-2 NACHA File Layout User Gude ‘ADDENDA RECORD INDICATOR Record Format Location: Entry Detail Record and Corporate Entry Detail Record 0 Noaaddenda record follows the entry 1 One or more addenda records follow the entry RECORD TYPE CODES Record Format Location: The first position of all record formats. These codes are uniquely assigned for each type of record as follows: File Header Record Format ‘Company/Batch Header Record Format Entry Detail Record Format (Consumer and Corporate) ‘Addenda Record Formats ‘Company/Batch Control Record Format File Control Record Format SERVICE CLASS CopEs Record Format Location: Company/Batch Header Record and ‘Company/Batch Control Record 200 ACH Entries Mixed Debits and Credits ‘STANDARD ENTRY CLASS CODES Record Format Location: Company/Batch Header Record CCD Cash Concentration or Disbursement COR Automated Notification of Change and Automated Refused Notification of Change CTX Corporate Trade Exchange PPD Prearranged Payment and Deposit Entry Effective 04/08TRANSACTION CODES | Record Format Location: Entry Detail Record Demand Credit Records (for checking, NOW, and share draft accounts) | 21 Automated Return or Notification of Change for original transaction code 22, 23, oF 24 22 Automated Deposit 23. Prenotification of Demand Credit Authorization (non dollar) 24 Zero dollar with remittance data (for CCD and CTX entries only) Demand Debit Records (for checking, NOW, and share draft accounts): 26 Automated Return or Notification of Change for original transaction code 27, 28, of 29 27 Automated Payment 28 _Prenotification of Demand Debit Authorization (non-dollar) 29 Zero dollar with remittance data (for CCD and CTX entries only) ‘Saving Accounts Credit Records: 31 Automated Return or Notification of Change for original j transaction code 32, 33, or 34 32 Automated Deposit 33. Prenotification of Savings Credit Authorization (non dollar) 34 Zero dollar with remittance data (for CCD and CTX entries only) Saving Accounts Debit Records: 36 Automated Retum or Notification of Change for original transaction code 37, 38, or 39 37 Automated Payment 38 Prenotification of Savings Debit Authorization (non-dollar) 39 Zero dollar with remittance data (for CCD and CTX entries only) Effective 04708 Code Values and Glossary 5-3Glossary of Data Elements 5.4 NACHA File Layout User Guide Addenda Information (CCD, CTX, PPD, returns, contested dishonored returns, COR): 44 Positions - Addenda Record - Optional ‘Addenda Information is associated with the immediately preceding Entry Detail Record. The Addenda Information field of a Retumn Entry is used by the RDFI to relay explanatory information that is required with the use of Return Reason Codes “R11” (Check Truncation Return) and “R17” (File Record Edit Criteria), and to return any information contained in an Addenda Record accompanying the original entry. Return entries that have been automated by the RDFI will retain the Standard Entry Class Code of the original entry (i.e, CCD, COR, CTX, or PPD), and therefore must be identified by the transaction code and the Addenda Type Code “99.” Paper return items, which are rare, have been converted to automated returns by the ACH Operator and are designated by the Standard Entry Class Code “RET.” Addenda Record Indicator (CCD, CTX, PPD, returns, dishonored returns, contested dishonored retums, COR): I Position - Entry Detail Record and Corporate Entry Detail Record - Mandatory This field indicates the existence of an Addenda Record. A value of “1” indicates that one or more addenda records follow, and “0” means no such record is present. (See currently assigned “Code Values” on page 5-2.) 2 CCD and CTX ‘This field indicates the existence of Addenda Record(s) following this Corporate Entry Detail Record. A value of “0” means that no such record is present. A value of “1” means one or more Addenda Record(s) is following, @ Zero Dollar, Automated Notification of Change Return, Automated Dishonored Return, and Automated Contested Dishonored Return ‘The value of this field will always be “1.” Ettective 0408