There are usually two options for this to happen:
- Produce a report that can be sent to payroll staff to manually enter the changes
- Use a Paylink module that transfers the changes that have recently occurred in to the payroll system
We have several paylink modules and each one is created to fit a different payroll application. For all other payroll applications we have a Universal Paylink . Some Paylink modules will only send changes or newly inserted records to the payroll where as the Universal Paylink will send the entire record even if only one field has been amended.
The following diagram displays the process –
Create Output Data
This is the first stage in the paylink process. Validation of the data is performed during this process to ensure data is within specification. The paylink code compares the personnel records with the data that has previously been transferred to the payroll application held in a separate table. Any records that have been changed are in the diagram above.
This exports the group of records selected from the Create Output Data process to a file on the network. This file is usually a CSV (Comma Separated Values) file.
3rd Party Paylink Process
Controlled by the Payroll Application this process is where the Payroll Application users will import the changes in to the payroll database. These will then be used to create the payslips.
Once the payroll is complete and the output file has been satisfactorily imported then the payroll records area in Ciphr People is updated. This makes the changes permanent but up to this point the payroll can be returned to its original state pre-payrun.