Ability for bureaus to download usage by employer stats into CSV/XLSX
The per employer usage stats held at tenant level are very useful, particularly for client billing as it contains number of payslips processed but also for analysis as it contains variance/change to prior month also but it is only available on scr...
There are instances where it's not advisable to send copies of P45 documents to employees. Having the option to prevent the sending of P45 documents to selected employees would be greatly beneficial in such situations. One of the scenarios is Tupe...
Srilakshmi Patlolla
7 months ago
in Payrun
2
Pending Review
Separate columns for forename and surname on Advance Variance Report
Client has made a comment about having employee's full name in one column making it difficult to filter or search on a name. All other reports display surnames in their own column.
Separate automation settings for each pay frequency
We have clients with several different frequencies under one PAYE ref and it would be good to have different automation settings for each of these. For example finalise one frequency on pay day and another 6 days before.
Emily Libby
3 months ago
in Bureau
0
Future consideration
The current audit logs do not appear to track the changes on all employee profile data fields, and therefore it is difficult to back track to find the reason for issues etc, as well as who and when it was changed.
For automating payments file uploads to 3rd party BACS providers (Access Pay in this case as Bottomline have lost the plot) it would be useful for Staffology to transfer the BACS payment files to an SFTP so they can be automatically collected.
Pay codes must be blocked from being deleted if there are any values against them.
The system must block the deletion of any pay codes that have a value against them. Amongst other things, this causes the journal to be out of balance.
Lisa Ramos
26 days ago
in Settings
0
Future consideration