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, not required.

Long Description: Used to describe the common code, not required.

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 has EFT payments. 

2-5: Not Required, but available options:   

• PRENOTE: Use to generate an EFT file as a pre-notification to send 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.  

• ASCII: Enter to generate the EFT file in an ASCII format; by default, the file is created in a binary format. 

• PAPER REMIT: Enter 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.  Requires an SPFM form definition for the EFT CKID. This is done through mask SYSPUB, or you may have to contact BusinessPLUS services if you are unable to define a form. 

• DEBIT: Enter to generate a record 6 with debit transaction codes: 

  • 27 = Debit to Check Account 

  • 37 = Debit to Savings Account 

Associated Descriptions: 

1: Enter the chosen EFT filename (max 8 characters). By default, the system will overwrite this file every time a check run (APOHPPPA) is processed that has EFT payments. 

• Available Options: 

  • UNIQUE → System‑generated filenames based on Julian Date with a ‘1’ + sequential letter (e.g., EF02561D) appended at the end. Creates a new file for each check run. Will generate multiple files per day if ran. 

  • APPEND → System‑generated filename based on Julian Date + “1A” appended at the end (e.g., EF02561A). Appends EFT payments into one file per day. 

2-5: Not Required, but available options: 

• If the Option of “DEBIT” is designated in an Associated Code, the accompanying Associated Description is required to contain the appropriate Bank Routing Number and Bank Account Number separated by a comma (,).  For example: “111111,2222222222”.   

• BLANK-REF: Enter 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.