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

Back to current versionRestore this version

DISBURSE PAYS#

After a payrun is closed, pays may be disbursed according to the net pay split done during the payroll calculation.

Report Parameter Form
Entity	Mandatory, LOV available Limits the process to the entity specified.
Calculate Rate For	Optional, LOV available
Create Zero Chks/Deposits	Optional, Toggle If ON, the checks and deposits with a 'zero' amount will be part of the allowed disbursement created.
Sort By	Mandatory, LOV available Disbursements will be processed in this order - destination, department then name or destination then name. This becomes the order that check numbers are assigned.
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 UPDISB maybe run again. If ‘OFF’ then the update is committed.

Report Filters
Payroll	Optional, LOV available Only one payroll may be selected per execution of this function.
Pay Run Number	Optional, Match, Multiple, and LOV available Multiple pay runs may be selected for processing.

The Disbursement form will handle one or more pay runs. Disbursements (Checks/Deposits) may be combined for an employee according to ‘Pay Issue Date’. Consolidate disbursements is determined at the ‘Pay Category’ level.

Clients will be provided with access to all data needed to print checks stubs and deposits from the disbursement table.

‘Pay Component’ information is always populated by pay component totals. This summary will be one record per pay component and stored in the ‘Stubs’ table. Pay component detail information will be optionally stored in the ‘Stub_Details’ table. A row will be created for each change in ‘Rate’ as well as a row for any adjustments made by a User Calc or possible benefit plan or leave policy type. The adjustment record will contain only the adjustment amount and no rates.

All data will be stored (PC Amounts, etc.) and any selection for checks, etc. will be done at reporting time from the disbursement system.

Only one set of ‘Stub’ information will be created for each disbursement. Due to consolidation, this is mandatory.

Statistics are available for printing on a remittance notification via the foreign key to ‘EMPLOYMENTS’ from the DISBURSEMENT record.

The disburse pays process will take the results of one or more pay runs and create the disbursement record for each employee / pay issue date combination.

Checks will respect ‘Pay to Order of’ when consolidating. The system does not consolidate ‘Hand Checks’.

Adjustments are not processed. If reversal pays are not processed through the UPDISB process, you have an overstatement in IPVT and on IPDS.

UserCalcs are executed to pick up any disbursement notes. Only those in production, identified as a ‘Disbursement Note’ type, and returning an alphanumeric variable will be executed.

When run in update mode (non-trial), the disbursement records will be created and each pay header processed will be updated to indicate that it was processed.