This page (revision-13) was last changed on 26-Nov-2021 10:22 by kparrott

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

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
13 26-Nov-2021 10:22 11 KB kparrott to previous
12 26-Nov-2021 10:22 11 KB kparrott to previous | to last
11 26-Nov-2021 10:22 11 KB kparrott to previous | to last
10 26-Nov-2021 10:22 11 KB kparrott to previous | to last
9 26-Nov-2021 10:22 11 KB kparrott to previous | to last
8 26-Nov-2021 10:22 11 KB kparrott to previous | to last
7 26-Nov-2021 10:22 11 KB kparrott to previous | to last
6 26-Nov-2021 10:22 11 KB kparrott to previous | to last
5 26-Nov-2021 10:22 11 KB kparrott to previous | to last
4 26-Nov-2021 10:22 10 KB JAiken to previous | to last
3 26-Nov-2021 10:22 10 KB JAiken to previous | to last
2 26-Nov-2021 10:22 10 KB JEscott to previous | to last
1 26-Nov-2021 10:22 10 KB JEscott to last

Page References

Incoming links Outgoing links

Version management

Difference between version and

At line 4 changed one line
This following describes the set up and processes that provide the ability in [{$applicationname}] to handle payments to AP Vendors for selected employee deductions. [{$applicationname}] provides for the creation of an ‘Interface File’ for input to an external accounts payable system. [{$applicationname}] also provides for the ability to print checks for vendors with the same program that prints the regular employee checks. The choice to interface, or print a check is at the vendor level.
This following describes the set up and processes that provide the ability in Personality to handle payments to AP Vendors for selected employee deductions. Personality provides for the creation of an ‘Interface File’ for input to an external accounts payable system. Personality also provides for the ability to print checks for vendors with the same program that prints the regular employee checks. The choice to interface, or print a check is at the vendor level.
At line 15 changed one line
On the ‘Accts/Arrears’ tab, record the default Vendor Number. If this is left blank, then the vendor number must be entered on each appropriate transaction for this [pay component|PAY COMPONENTS]. The number is selected from the [X_AP_VENDORS] lexicon.
On the ‘Accts/Arrears’ tab, record the default Vendor Number. If this is left blank, then the UPVEND will NOT process the PC and report it a vendor. The Vendor number is selected from the [X_AP_VENDORS] lexicon.
At line 24 changed one line
This list should contain only those vendors that will be used in [{$applicationname}], and not the entire list of AP vendors.
This list should contain only those vendors that will be used in Personality, and not the entire list of AP vendors.
At line 36 changed one line
If you choose to pay vendors using [{$applicationname}], then you will need a ‘Vendor Check’ written to support [UPSTUBVCW] (Print Vendor Check). To pay vendors within [{$applicationname}] set up the vendor as an ‘Employee’ use ‘V’ plus the vendor number as the person code.
If you choose to pay vendors using Personality, then you will need a ‘Vendor Check’ written to support [UPSTUBVCW] (Print Vendor Check). To pay vendors within Personality set up the vendor as an ‘Employee’ use ‘V’ plus the vendor number as the person code.
At line 44 changed one line
[{$applicationname}] can be used to print a check or create a direct deposit for a vendor by setting up the vendor as an employee.
Personality can be used to print a check or create a direct deposit for a vendor by setting up the vendor as an employee.
At line 56 changed one line
When [UPVEND] is executed, [{$applicationname}] decides whether a vendor is written to the output flat file, OR creates a disbursement record for check printing OR creates a direct deposit.
When [UPVEND] is executed, Personality decides whether a vendor is written to the output flat file, OR creates a disbursement record for check printing OR creates a direct deposit.
At line 62 added 3 lines
\\ \\
__NOTE:__ UPSTUBVCW must be used for NG 5.00+. UPSTUBCW will work for 4.11/4.50 for vendor checks.
\\ \\
At line 99 changed one line
The [UPVEND] function is run to create anAccounts Payable (AP) interface file. This can only be launched after all pay runs for the given payroll period are closed ([UPCLOZ]). This function provides a detailed list of all AP invoices to be exported to an interface file named in this function.
The [UPVEND] function is run to create an Accounts Payable (AP) interface file. This can only be launched after all pay runs for the given payroll period are closed ([UPCLOZ]). This function provides a detailed list of all AP invoices to be exported to an interface file named in this function.
At line 101 changed one line
The following setup determines if the UPVEND will process a deduction:
The following setup determines if the UPVEND will report a deduction:
At line 103 changed one line
# All PC’s that must be processed by UPVEND must have on the IPPC - PC DETAILS tab, the REFERENCE set to ‘Enter Vendor Code’ and on ACCT/ARREARS tab, the AP VENDOR must contain a Vendor name.
# All PCs that are to be processed by UPVEND must have on the IPPC – PC DETAILS tab, the REFERENCE set to ‘Enter Vendor Code’ and on the ACCT/ARREARS tab, the AP VENDOR must contain a Vendor name.
# Pay Amounts to be sent to a Vendor that are created by Non-Sundry (Benefits, UserCalcs, etc.) will get processed by UPVEND and sent to the AP Vendor that is setup on the PC.
# Sundry amounts that are to be processed by UPVEND must have the PC setup as described in Point 1 above, as well as have a Vendor code entered in the Reference field on the IPSN record. If the IPSN does not have a Vendor, it is considered to be an adjustment for the employee and will not be processed by UPVEND.
# If there is no Vendor entered on the IPPC (in the AP Vendor field) for a Pay Amount or Sundry, it will not be processed by UPVEND.
At line 105 removed 6 lines
# Pay Amounts to be sent to a Vendor that are created by Non-Sundry (Benefits, UserCalcs, etc) will get processed and sent to the AP Vendor that is on the PC by UPVEND.
# Sundry amounts that are to be processed by UPVEND, must have the PC setup as described in point 1, as well as have a Vendor code entered in the Reference field on the IPSN record. If the IPSN does not have a Vendor, it is considered to be an adjustment for the employee and will not be processed by UPVEND.
# If there is no Vendor entered on the IPPC (in the AP Vendor field) for a Pay Amount or Sundry, it will not be processed by UPVEND.
At line 113 changed one line
When using eP to create checks versus sending the information into an Accounts Payable system, the [UPVEND] process does not create any additional General Ledger journal entries. The journal entries must be created by the Payroll General Ledger interface program ([UPGL]).
When using Personality to create checks versus sending the information into an Accounts Payable system, the [UPVEND] process does not create any additional General Ledger journal entries. The journal entries must be created by the Payroll General Ledger interface program ([UPGL]).
At line 156 changed 2 lines
![Notes|Edit:Internal.ACCOUNTS+PAYABLE+-+UPVEND]
[{InsertPage page='Internal.ACCOUNTS+PAYABLE+-+UPVEND' default='Click to create a new notes page'}]
![Notes|Edit:Internal.ACCOUNTS PAYABLE - UPVEND]
[{InsertPage page='Internal.ACCOUNTS PAYABLE - UPVEND' default='Click to create a new notes page'}]