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

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. 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.
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. \\
At line 6 removed one line
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 7 added 2 lines
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|IDIF-HL$POSPAY]. Do NOT modify this format, since any modifications would be wiped out on a new release of the application.
At line 11 changed 3 lines
%%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. %%
\\
\\
%%label-danger 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 added 3 lines
\\
\\
%%label-info 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. %%
At line 37 added 5 lines
----
![Notes|Edit:Internal.UPPOSPAYW]
[{InsertPage page='Internal.UPPOSPAYW' default='Click to create a new notes page'}]