OHEF - CONTROL
This common code defines the name of the EFT file to be generated. In addition, this common code can be used to activate options such as generating a Pre-notification EFT file, Paper Remits, utilizing an ASCII format or including a Record 6 in the file.
Code Category: OHEF
Code Value: CONTROL or CONTxx
The common code may be made specific to the Bank ID being processed. Where xx represents the two-character Bank ID code (e.g., CONTAP).
Short Description: Enter OFF to inactivate the EFT/ACH feature.
Medium Description: Used to describe the common code.
Long Description: Used to describe the common code.
Associated Numeric Values
1-5: Reserved for future use.
Associated Codes
1: Enter "FILE" in order to generate the EFT file in the user's data group. By default, the system will overwrite this file every time a check run (APOHPPPA) is processed that contain EFT payments.
2-5: Not required. Available Options are PRENOTE, ASCII, PAPER REMIT, or DEBIT. Descriptions of each option are as follows:
PRENOTE: Enter in order to generate the EFT file as a whole as a pre-notification to be sent to the bank to validate format and account information before funds are actually transferred. To process a "PRENOTE" transaction the vendor must have a real transaction to pay in the database. When either the vendor or file is flagged as "PRENOTE" the EFT file will be created for $0 dollars. Not required.
ASCII: Enter in order to generate the EFT file in an ASCII format, by default the file is created in a binary format.
PAPER REMIT: Enter in order to generate paper remits of the EFT payments. This feature is global and will apply to any Vendor in which an EFT payment will be produced. Note that you will need to an SPFM form definition for the EFT CKID. This is done through mask SYSPUB, or you may have to contact BusinessPLUS if you are unable to define a form.
DEBIT: Enter in order to generate a record 6 with a transaction code value that will be a debit for the client (27 – Debit destined for a Check Account) (37 – Debit Destined for a Savings Account).
Associated Descriptions
1: Enter the chosen EFT filename, using a maximum of 8 characters. If left blank the filename used is "EFTAP." Please note that by default the system will overwrite this file every time a check run (APOHPPPA) is processed that contain EFT payments. In addition, this field also allows the ability to activate additional options which are described as follows:
UNIQUE: Enter in order to use a system generated filename based upon the Julian Date with a "1" and a sequential letter (e.g., A to Z) appended at the end. For example, EF02561D. A new file will be created for each subsequent check run. There will be as many files for a given day as there were check runs processed with EFT payments.
APPEND: Enter in order to use a system generated filename based upon the Julian Date with a "1A" appended at the end of the filename. For example, EF02561A. Then with each check run (APOHPPPA) the EFT payments will be appended into the same file rather than generating one file per check run (APOHPPPA). Therefore, there will be one file generated per day.
2-5: Not required. Available Options are described as follows:
If the Option of DEBIT is used, the accompanying Associated Description will need to contain the appropriate Bank Routing Number and Bank Account Number delimited by a comma (,). For example: "111111,2222222222." To be clear, if Associated Code (4) has DEBIT then Associated Description (4) will need to have the appropriate Bank Routing and Account Number information.
BLANK-REF: Enter in order to opt for the Reference Code on Record 1 to be blank, by default the Reference Code is the Bank ID and Job Number appended together, e.g., EP143289.