Section 45-3-007 - TECHNICAL REQUIREMENTS007.01 Section 007 applies to all accounts and required data set forth in Sections 004, 005, and 006 of this Rule.007.01A Record Identification007.01A1 Identification of record types within a file. Various types of records such as account, header, trailer, or control, are normally maintained within a file. Each record type must be identified by a unique code in the same field of each like record. Any method of recording the code is acceptable.007.01A2 Identifying Records for a given bank. Two methods are in general use and either is acceptable: 007.01A2a A separate file for each bank processed by the data center.007.01A2b Multiple bank records on one file with each identified by a unique code. It is also acceptable to record more than one account type (demand deposit, savings, etc.) with either of the above methods. However, records for each account type should be identified by a unique code located in the same record.
007.01A3 Identification of accounts. Certain accounts (public funds, trust funds, etc.) must be identified if the accounts are maintained in the file. The following guidelines apply to all account types: 007.01A2a A unique code or codes can be established by the data center, common to all users, or the data center can provide any method for the bank to identify specified types of accounts. In the event a bank establishes its own codes, an up-to-date list must be maintained by the bank. The data center must be able to specify where within the record the codes established by the bank are maintained. It is recommended that banks use the coding structure provided by the data center.007.01A2b A range of account numbers is not an acceptable method of coding.007.01A2c The type account code should be maintained in either the master account record or an associated record or file. "Master account record" is defined as that record where financial activity is recorded versus any other associated record or file such as name and address master.007.01A2d Provision for expansion of type account code should be considered for future use.007.01A2e For purposes of processing, different types of accounts may be identified on a multi-bank file by a separate bank number. Example: Regular passbook savings versus accounts that receive a periodic statement, or club savings account versus regular savings account.007.02 Banks and/or data centers may use any other codes to identify accounts not specified herein for their own purposes (such as sub-type of account) provided that the minimum standards set forth in this Rule are satisfied. These standards are not intended to limit or exclude the coding of account types.007.02A Identifying Status of Account. Codes are needed to identify the status of an account. Standards applicable to identifying status for all applications are: 007.02A1 A unique code (or combination of codes) should be used to identify status.007.02A2 The status code should be maintained either in the master account record or any associated record or file. (Master account record is defined as that record where the financial activity is recorded as opposed to any associated record or file such as master name and address.)007.02A3 A range of account numbers is not an acceptable method of coding.007.02A4 Provide for expansion of status codes.007.03 Any code or combination of codes may be used to identify the status of an account. Any recording method is acceptable provided that the method is uniform from record to record for a given bank. Banks and/or data centers may establish status classifications other than those specified in this Rule for other purposes. These standards are not intended to limit or exclude the identification of accounts by a status indicator.007.04 Data Fields Within a Record 007.04A Record-keeping Guidelines 007.04A1 Data may be recorded using any of the standard techniques provided by the manufacturer. Acceptable recording methods include, but are not limited to: 007.04A1a standard alpha numeric (character data)007.04A1b packed signed; signs may be high or low order007.04A1c packed unsigned007.04A1d zone decimal signed; may be high or low order007.04A1e zone decimal unsigned007.04A2 Any unique space savings recording technique or recording techniques designed for security purposes are acceptable. The data center must be able to clearly describe the technique to the Department.007.04A3 The recording technique used for any given field should be consistent for all like records within a given file.007.04A3 The format of data recorded in any given field should be consistent for all like records. Example: If the format for a given date fields is MMDDYY, it should be recorded in that format for the given date field for all like records.007.04A4 All fields of data handled arithmetically should be initialized. Blanks are normally not considered to be a sound record-keeping technique for an arithmetic field. All amount and date fields should be initialized with numeric zeros in the absence of specific values, except in those instances when, for security or coding purposes, a string of non-numeric characters is recorded in the field. Documentation must clearly describe the reason for non-numeric values.007.04A5 All the data for a given item of information should be recorded as a single contiguous field.45 Neb. Admin. Code, ch. 3, § 007
Adopted effective 11/25/2023