This is version 1 2 3 4 5 6 7 8 9 . It is not the current version, and thus it cannot be edited.

Back to current versionRestore this version

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 Wiki will provide the functionality through the Generate Positive Pay (UPPOSPAYW) form. Wiki.

This program is differentiated from the similar (soon to be deprecated) function UPPOSPAY in that it is configurable by the user in its output. The IDIF form is used to define the interface layout.

All checks that have been either issued or voided within the date range provided since the last time UPPOSPAY was executed are picked up and recorded in the output file.

Each client must set up their own interface format choosing from the record types provided in this document. 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.

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.

There are two report parameters for ‘File Header’ records. These are optional and can contain ONLY text. There is no Variable Substitution in these records.

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.

Replacement checks as well as the associated void check are included.

Manual checks and manually voided checks are also included.

This function can be used to supply the bank with a list of issued checks if the bank is providing a reconciliation service.

---

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. ?|File Format|Mandatory, LOV Available
Currently several banks are supported.

Custom Header Record

Optional, Text

?|Interface Directory|Mandatory, Text
Must be a directory on the server for which the current user (as signed onto the
client’s network) has write capability. 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	Mandatory, Text Enter the name of the file that will be created in the interface directory specified.
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.