Rolling back a clone company would help when having to calculate historical corrections on a payroll. As an example, it would allow you to accurately calculate a net overpayment figure where a leaver has been overpaid and the client wishes to claw...
The limits in place for API calls are currently far too low, this almost makes the current API unusable for anything more than a single query. Could you please increase this to allow us to make the most of the system.
Mark Smith
almost 2 years ago
in Paycircle / API
1
Planned
Being able to have workflow stages assigned to multiple people
It would be useful to be able to assign workflow stages to multiple people especially the payroll input stage. This would be useful when clients are on holiday as they could have someone else to send in the input on their behalf.
We use the standard mid month salary change calculations on an averaged basis. This means the method being used by Paycircle come out with vastly different calculations and our company are having to manually overwrite these figures. The averaged b...
Include the last 4 digits for the relevant tax year and month on the HMRC notifcation emails.
Clients are paying HMRC using the reference given which is just the account office reference. HMRC are not allocating the payments made to the correct months.
Back Dated NI Liabilities Reported in Next Pay Run
Currently any back dating of NI reported changes the reports in the month the change should have happened. This has caused us to miss an underpayment of NI and HMRC have fined the client. Our previous software reported back dated NI calculations i...
Disabling bespoke reporting for some users. In our case this relates to our accounts team.
Our internal policy is that we don't provide payroll reports to our accounts team with all employee data on, this is to reduce the number of people who have access to the sensitive personal information held by payroll. When generating reports for ...
0
0
