This page (revision-9) was last changed on 05-Oct-2023 14:23 by Kevin Higgs

This page was created on 26-Nov-2021 10:22 by RForbes

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
9 05-Oct-2023 14:23 4 KB Kevin Higgs to previous
8 05-Oct-2023 14:22 4 KB Kevin Higgs to previous | to last
7 26-Nov-2021 10:22 3 KB RForbes to previous | to last
6 26-Nov-2021 10:22 3 KB RForbes to previous | to last HL$POSPAY ==> IDIF-HL$POSPAY
5 26-Nov-2021 10:22 3 KB RForbes to previous | to last
4 26-Nov-2021 10:22 3 KB RForbes to previous | to last
3 26-Nov-2021 10:22 3 KB RForbes to previous | to last
2 26-Nov-2021 10:22 3 KB RForbes to previous | to last
1 26-Nov-2021 10:22 2 KB RForbes to last

Page References

Incoming links Outgoing links
UPPOSPAYW
UPPOSPAYW

Version management

Difference between version and

At line 4 changed one line
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.
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 [{$applicationname}] will provide the functionality through the Generate Positive Pay function.
At line 6 changed one line
This service is not provided by all US banks and is not always called ‘Positive Pay’, however if the intent is the same, then [{$applicationname}] will provide the functionality through the Generate Positive Pay (UPPOSPAYW) form. [{$applicationname}].
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 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.
At line 8 changed one line
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 [UPPOSPAYW] or [UPPOSPAY] was executed are picked up and recorded in the output file.
At line 10 removed 4 lines
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.
At line 16 changed one line
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.
%%information 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. %%
At line 18 changed one line
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.
Replacement checks as well as the associated void check are included. Manual checks and manually voided checks are also included.
At line 20 removed 10 lines
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.
At line 35 changed 5 lines
?|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.
|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\\Currently several banks are supported.
|Interface Directory|Mandatory, Text\\Must be a directory on the [data base server|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.
At line 41 changed one line
|Trial|Optional, Toggle\\If ‘On’ then the update is not committed and UPPOSPAY may be run again.\\If ‘OFF’ then the update is committed.
|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.
This page (revision-9) was last changed on 05-Oct-2023 14:23 by Kevin HiggsTop