InPay now allows the creation of Supplementary Runs.
In essence this allows a worker to have multiple payslips within a pay period and also means that the runs can be paid via BACs and a sub set of reports run against it.
With Supplementary Runs configured InPay will continue to run in the same fashion. However a Supplementary Run button will be available through the Payroll -> Processing screen.
Initially the pay will process in the period as normal. The following payslip shows Test Worker paid their Basic Salary for the period
and this can be paid by BACs as Normal.
In this example the worker is due a Bonus in April which had not been paid. The user can go to the Pay -> Processing screen and click Create Supplementary Run (figure 1). The option becomes available to enter the pay date of the first payslip.
The original payslip will now show as below.
The "- 1" against the payslip highlights that the Supplementary Run functionality has been used.
By adding a Bonus payment against the worker, the payslip view in InPay will show as follows.
When all pay has been entered the Supplementary Run buttons should be clicked again. Once a supplementary run has been created in the current period there will also be the option to delete the previous Supplementary Run.
Once you have run another Supplementary Run then either of the runs will be available to pay by BACs.
Also, through the Reports screen the Pay Summary, Pay Summary Detailed, Pay Method Payslip Reports can be run at Supplementary Run level.
Please note that the pay period should be the six digit pay period followed by the Supplementary Run number without a hyphen as shown above. Two examples are shown below.
An important point is that once a Supplementary Run has been created in a pay period, any further pay must be created as a Supplementary Run before commit. If the user commits the payroll while there is additional pay the following error will occur.
Likewise any Supplementary Runs in a period must be deleted before a rollback is performed otherwise the following error occurs.
It should be noted that the functionality described above does not restrict the running of reports across the entire period as normal.