GENERATE POSITIVE PAY FILE#
Processing Information#
Positive Pay is the process of periodically sending a list (via transmission file) of all issued and voided checks. This information allows the bank to reject attempts to cash checks not issued by the sending agent. This service is not provided by all US banks and is not always called ‘Positive Pay’, however if the intent is the same, then Personality will provide the functionality through the Generate Positive Pay function.This program is differentiated from the similar (soon to be deprecated) function UPPOSPAY in that the output file is configurable by the user in its output. The IDIF form is used to define the interface layout. Each client must set up their own interface format choosing from the record types provided (X_INF_VARIABLE_NAME (20). A sample interface format has been provided that includes a ‘bare bones’ interface file. You can choose from the record types and columns provided to customize your own formats. The supplied format code is named HL$POSPAY. Do NOT modify this format, since any modifications would be wiped out on a new release of the application.
All checks that have been either issued or voided within the date range provided since the last time UPPOSPAYW or UPPOSPAY was executed are picked up and recorded in the output file.
The output Interface file is sorted by Check Number.
Formats can NOT exceed 1022 bytes in length. If this is encountered, an exception message will be issued, and the record will be not be written to the interface file.
Replacement checks as well as the associated void check are included. Manual checks and manually voided checks are also included.
Derivation expressions are supported in the IDIF set up for Positive pay, however, the derivations do not support the call to other variables in the same manner as the UEEF and UPPHF. Only the inbound variable represented by the tilde key (~) can be used in a derivation.
Report Parameters #
| Report Parameters | |
|---|---|
| Payroll Bank Account | Mandatory, LOV Available The bank account from where the checks were drawn. |
| Up to Issue Date | Mandatory, Date, LOV Available The latest issue date of the checks. |
| Header Record One | Optional, Text An optional record output on the file as a header. Can only contain text.There is no Variable Substitution in these records. |
| Header Record Two | Optional, Text An optional record output on the file as a header. Can only contain text.There is no Variable Substitution in these records. |
| Interface Code | Mandatory, LOV Available The report definition selected will determine the format of the output file (if any),as well as the columnar content of the report. |
| Interface Directory | Mandatory, Text Must be a directory on the data base server for which the data base serve process has write access. For example the entry ‘C:\TEMP’ accesses the ‘TEMP’ directory on the server, not the local directory for the computer terminal being used. |
| File Name | Optional, Text Enter the name of the file that will be created in the interface directory specified. If not provided, the file name specified on the IDIF definition will be used. |
| Exception Level | Mandatory, LOV Available Users may increase the level of logging done from exception to user, legislation, usercalc, program or utility levels. |
| Trial | Optional, Toggle If ‘On’ then the update is not committed and UPPOSPAY may be run again. If ‘OFF’ then the update is committed. Once UPPOSPAY is completed in a non-Trial mode, the check record will be updated with the execution id of the UPPOSPAY run. The field is MEX_ID_SENT from the P2K_PR_CHECKS table. All checks with a non-null MEX_ID_SENT will be bypassed on subsequent processing of the UPPOSPAY program. |
| User Comment | Optional, Text This line will appear on the report only. |
