We are pleased to confirm the upcoming release of InPay V9.01. This will be available to you on 12th June 2023.
Listening to our users is important to us, and therefore we hope that you find these changes useful, and they help in streamlining your business processes. We always value feedback, so please contact account management if you wish to discuss anything further.
All previous release notes can be found here: InPay release notes.
Key highlights
Ability to lock created exports - You can now lock selected export formats.
New columns and tables for exporting - We have developed further tables and added more columns to a variety of our exporting formats.
New features:
Ability to edit overpayment balance
Ability to lock created exports
New tables and columns for exporting: New columns within the pay summary current export table; ability to export specific pension scheme information; nominal code columns on employee location table; new tables for occupational sick pay; work & SSP patterns
Custom imports: Cost centre importing; new fields for employee pension custom import; reducing balances for salary sacrifice
Report filtering: Zero pay filter option; ability to report separately on pension salary sacrifice
Improvements:
Importing: Data analysis code for starters; custom import performance; employee benefit importer
Exporting: Formulas now rounded to 2 decimal places
salary sacrifice and reporting; payslip overview report
Apply tax rebate when leave date entered
New features details
Ability to edit overpayment balance
You will now be able to edit overpayment balances for the current pay period within the employee overpayment screen, this will then recalculate the balance amount. There is a new overpayment override history table displaying an audit of all override of overpayment values. For more information on this functionality go to employee overpayment repayments.
Ability to lock created exports
You can now lock any export formats you have built, stopping them from being deleted in error. Within the export screen, select the export format you wish to secure and click lock.
Once locked the delete button will be greyed out. You can unlock the export if you no longer require it, and the delete button will be selectable.
We have also added an additional step when deleting to help protect your data. When clicking delete you will see a message advising you this cannot be undone, you must click delete within 12 secs to go ahead with the deletion.
What do I do if I accidentally delete an export?
Currently deleting an export only performs a soft delete. While you cannot see the export yourself, support can retrieve this. You will need to know the name of the export deleted in error, and support will organise the export to be reinstated for you.
New tables and columns for exporting
We have developed further columns and tables of data within our export data function to help you build more meaningful reports with powerful data.
New columns within the pay summary current export table
Within the pay summary current table, you can now include the columns class1AErsNI, and apprenticeship levy. Go to import/export in the top menu heading and select export data. Choose pay summary current within the table field and you will see the new fields you can add within the column dropdown.
You can also now export permanent payments and deductions within the pay summary current table. These are identified by adding the prefix perm under column section.
Ability to export specific pension scheme information
There is a new table named pension schemes current available within export data. The new table will have defined columns for each pension scheme, for example, the export can show a separate column for Ees% or NI savings across all schemes. Pension scheme details will only populate when an employee has contribution towards the particular scheme you have chosen to report on.
Nominal code columns on employee location table
There are now two additional fields to capture cost centre nominal codes and department nominal codes. These columns are within the employee location table, and will populate the nominal code values mapped to respective cost centre and department within the company - nominal mask screen.
New tables for occupational sick pay
There are now 2 tables named employee OSP YTD & employee OSP. These exports will allow you to capture sickness taken and number of sickness days left against each band for an employee. InPay allows you to create occupational schemes for sick pay & absence, this is useful if you have a probation period for sick pay, or have a company maternity pay structure different to the statutory thresholds.
Work & SSP patterns
There is a new table called employee patterns, this will allow you to export all work and SSP schedule details for your employees. Using work schedules allows you to define the normal working days for your employees for the purposes of apportioning pay in part-period payments. You can also use SSP schedules to define your employees normal days of working, so statutory sick pay is paid correctly according to qualifying days.
Custom imports
We have continued to develop our custom import functionality with new fields added to 2 areas of importing.
Cost centre importing
There are six new fields added to the employee location table with the custom import. This will now allow you to import three cost centres and their respective splits %.
New fields for employee pension custom import
We have added four new date fields to employee pension format within the custom import. These are: opted out date, terminated date, opt in date, & postponement date.
Reducing balances for salary sacrifice
You can now use the custom importer to import salary sacrifice payments with a reducing balance & amount outstanding. You will now see both fields are available to select within the employee pay/ded table. You will mark the reducing balance with Y or N, and then the amount within the amount outstanding.
Report filtering
To help provide further data we have made changes our reports within standard reports. Go to reporting and standard reports and select the relevant category and report you need.
NP-2213 Zero pay filter option All users
There is now a tick box option to include zero pay within your pay summary details plain report. Once you have selected your report, you will see the tick box option at the bottom of the screen.
Ability to report separately on pension salary sacrifice
Within the total summary of pay report, you will now have a tick box option to separate pension sal sac ees & ers.
Improvement details
Importing
Data analysis code for starters
Previously the custom importer for new starters was not populating the fields with data analysis codes, and no error message would show. This will now work as expected.
Custom import performance
We have improved the importing function for large files. Previously files that would take more than 10 minutes to import may have received a timeout and a failed import. These files will now successfully import.
Employee benefit importer
Previously if the column CarCalcPrice had a value in the field with a decimal, an error would occur. The employee benefit importer will now allow values that include a decimal.
Exporting
Formulas now rounded to 2 decimal places
Exporter output fields are now restricted to 2 decimal places when a corresponding field is built using the formula option.
Reporting
Salary sacrifice and reporting
Going forward analysis of payments and pay method reports will include entries for salary sacrifice. These will show if there is a deduction against the worker and there are bank details against the pay element.
Payslip overview report
We have enhanced the payslip overview report when sorting by surname. The report will sort by surname and then forename as a default.
HSBC XML UK BACS format
In line with HSBC upgrading their file requirements, the HSBC XML UK BACS format has been updated in accordance with this. The message ID tags are limited to 35 characters and end to end, and ID needs to be unique for every payment instruction within the file. The change applies to standard BACS file, P32, and subsequent runs