Currently if you have calculated the payroll the system prevents tax code changes, changes to personal details and changes to the payroll. However, it does not prevent changes to pensions coming through. We are repeatedly finding that we have to go through a lot of work to rerun reports for our clients at the moment with people opting out of the pension and suddenly having a refund appear that wasn't there when we calculated the payroll. In most occasions where we process the payments this doesn't cause an issue, just extra work, and we can pick up on the discrepancy between the reports and the figure on the bank. However, some of our clients make payment themselves and this has caused an issue on one payroll where an employee had a refund showing on their payslip but they were never paid it because the reports we sent to the client didn't have the refund. We didn't pick up on this because we didn't run out a BACS file and so there was no discrepancy visible. We are now having to unpick this problem several months later when the employee has finally spoken up about not receiving their money correctly. It would be helpful if calculating the payroll put a pause on these changes as well and queued them to come through after the payroll was either uncalculated for changes to be made, or rolled forwards to the new payment period.
We initially raised this over a year ago and were told it was being worked on through the community but it is still an issue.
Describe the Challenge | We need to be certain that the figures we are sending to our clients to approve are the figures that are going through the payroll. This is currently a nightmare task and we can't trust the payroll not to have additional information processed which we need to undo. |