This page (revision-73) was last changed on 29-Sep-2022 11:27 by Lilia Urtan

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

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
73 29-Sep-2022 11:27 13 KB Lilia Urtan to previous
72 26-Nov-2021 10:22 13 KB Karen Parrott to previous | to last
71 26-Nov-2021 10:22 13 KB Karen Parrott to previous | to last
70 26-Nov-2021 10:22 13 KB Karen Parrott to previous | to last
69 26-Nov-2021 10:22 13 KB mmcfarland to previous | to last
68 26-Nov-2021 10:22 13 KB mmcfarland to previous | to last
67 26-Nov-2021 10:22 13 KB kparrott to previous | to last
66 26-Nov-2021 10:22 13 KB kparrott to previous | to last
65 26-Nov-2021 10:22 13 KB kparrott to previous | to last
64 26-Nov-2021 10:22 13 KB kparrott to previous | to last
63 26-Nov-2021 10:22 11 KB kparrott to previous | to last
62 26-Nov-2021 10:22 11 KB khiggs to previous | to last
61 26-Nov-2021 10:22 10 KB mmcfarland to previous | to last

Page References

Incoming links Outgoing links
UPDISBV
UPDISBV

Version management

Difference between version and

At line 4 changed one line
[{$applicationname}] handles payments to Accounts Payable vendors for selected employee deductions. This process extracts from closed employee pays and populates the disbursement tables so that individual vendors can be paid. Vendors reside in a separate Payroll code and can be paid in a separate pay cycle from regular employees. Vendor payments may also be extracted for payment in some other supporting system. This capability is, of course, unique in each situation. This process describes how vendor payments are placed into the disbursement tables and not how they are actually paid.
[{$applicationname}] handles payments to Accounts Payable vendors for selected employee deductions. This process extracts from closed employee pays and populates the disbursement tables so that individual vendors can be paid. Vendors reside in a separate ‘Payroll Code’ and can be paid in a separate pay cycle from regular employees. Vendor payments may also be extracted for payment in some other supporting system. This capability is of course unique in each situation. This process describes how vendor payments are placed into the disbursement tables and not how they are actually paid.
At line 6 changed one line
There is a separate section, [Child Support Direct Deposit|UPDISBV#ChildSupportACHDirectDeposit], that outlines the setup needed to use the ACH interface for direct payment to vendors for Child Support payments.
There is a separate section, [Child Support Direct Deposit|UPDISBV#ChildSupportACHDirectDeposit], that outlines the setup needed to use the ACH interface for direct payment to vendors for Child Support Payments.
At line 11 changed one line
On the ‘Accts/Arrears’ tab, record the default Vendor number. This vendor could be simply a ‘Dummy’ vendor if the same pay component is used for multiple vendors. In this situation, the vendor is entered in [IPSN] or in [IPPH] when the transaction is keyed.
On the ‘Accts/Arrears’ tab, record the default Vendor number. This vendor could be simply a ‘Dummy’ vendor if the same pay component is used for multiple vendors. In this situation, the vendor is entered in [IPSN] or in [IPPH] when the transaction is keyed.
At line 18 changed one line
On the PC Rules tab, the reference column must be marked as ‘Enter Vendor Code’
On the PC Rules tab, the reference column must be marked as ‘Enter Vendor Code’
At line 23 changed 2 lines
The list of valid vendor numbers is stored in a user-defined lexicon with the lexicon name ‘X_AP_VENDORS’. These vendor numbers must be the exact vendor number to be passed to the external Accounts Payable system when any interface file is required.\\
Both the ‘Display Value’ and the ‘Meaning’ should contain the vendor name.
The list of valid vendor numbers is stored in a user-defined lexicon with the lexicon name ‘X_AP_VENDORS’. These vendor numbers must be the exact vendor number to be passed to the external Accounts Payable system when any interface file is required.\\
Both the ‘Display Value’ and the ‘Meaning’ should contain the vendor name.
At line 57 changed one line
When UPDISBV is executed, vendors with a person code equal to the letter ‘V’ plus the vendor number are eligible to be processed. For example, if the vendor number id 2311, then UPDISBV looks for an employee with the person code ‘V2311’. If located, then a disbursement is created.
When UPDISBV is executed, vendors with a person code equal to the letter ‘V’ plus the vendor number are eligible to be processed. For example, if the vendor number id 2311, then UPDISBV looks for an employee with the person code ‘V2311’. If located, then a disbursement is created.
At line 60 changed one line
!!UPDISBV – Disburse Vendor Payments
!!UPDISBV – Disburse Vendor Payments
At line 80 changed one line
In situations where UPDISBV has been executed and must be backed out, the Undisburse Vendor Payments ([UPUNDISB]) screen can be executed to ‘Undo’ the work from a previous execution of UPDISBV. [UPUNDISB] can also be used to undo executions of regular employee UPCALC executions.
In situations where UPDISBV has been executed and must be backed out, the Undisburse Vendor Payments ([UPUNDISB]) screen can be executed to ‘Undo’ the work from a previous execution of UPDISBV. [UPUNDISB] can also be used to undo executions of regular employee UPCALC executions.
At line 87 changed one line
In addition to the payment record, these particular direct deposits will have an ACH ‘Addenda Record’ sent along with the payment record. This event is triggered by the existence of any of the Child Support user fields documented in the pages following. The [UPDISBV] process therefore will not create this special addenda record unless the information needed is supplied in the [IPSN] form where the recurring deduction is maintained.
In addition to the payment record, these particular direct deposits will have an ACH ‘Addenda Record’ sent along with the payment record. This event is triggered by the existence of any of the Child Support user fields documented in the pages following. The [UPDISBV] process therefore will not create this special addenda record unless the information needed is supplied in the [IPSN] form where the recurring deduction is maintained.
At line 89 changed one line
There are four user fields that can be added to the table ‘P2K_PR_SUNDRY_LINES’ as shown below. Remember to refer to lexicon ‘X_YES_NO’ on the medical indicator, so that the value entered in [IPSN] can only be ‘Y’ or ‘N’. Case Number is mandatory, and the other three are optional. If these are set up without any data provided in [IPSN], then the [UPVEND] process will use the correct defaults without any problem. The names of these user fields must be exactly as shown.
There are four user fields that can be added to the table ‘P2K_PR_SUNDRY_LINES’ as shown below. Remember to refer to lexicon ‘X_YES_NO’ on the medical indicator, so that the value entered in [IPSN] can only be ‘Y’ or ‘N’. Case Number is mandatory, and the other three are optional. If these are set up without any data provided in [IPSN], then the [UPVEND] process will use the correct defaults without any problem. The names of these user fields must be exactly as shown.
At line 95 changed one line
UPDISBV will insert the ACH ‘Addenda Information’ as a user field named ‘ACH ADDENDA DATA’ attached to the disbursement. It can be viewed with the ‘UDF’ button in [IPDS]. This user field does not have to be added manually since UPDISBV will create it automatically the first time it is needed.
UPDISBV will insert the ACH ‘Addenda Information’ as a user field named ‘ACH ADDENDA DATA’ attached to the disbursement. It can be viewed with the ‘UDF’ button in [IPDS]. This user field does not have to be added manually since UPDISBV will create it automatically the first time it is needed.
This page (revision-73) was last changed on 29-Sep-2022 11:27 by Lilia UrtanTop