We are pleased to confirm the upcoming release of InPay V10.3. This will be available to you on Monday, March 3 2025.
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 managementif you wish to discuss anything further.
All previous release notes can be found here:InPay release notes.
| Anchor | ||||
|---|---|---|---|---|
|
Key highlights
We have made all the legislative changes required for 2025/26, including the new statutory neonatal care pay (SNCP) and leave (SNCL) requirements.
New features
Custom import: Ability to bulk import statutory overrides, Ability to ignore footer rows during import, Ability to fill missing data from current record, Changes to the import order, Enable validation fields for custom import
Reporting: Exceptions new report completely replaces the exceptions report, Ability to include tax changes by period range report to group reporting, Addition of neonatal payments to various reports
Absences: New absence type to support SNCP and SNCL, Ability to set SSP offset at absence level
New service length field added to employee general and export data
Payslip impersonation for non-payslip portal account holders
Ability to resend payslip emails
Added corporation tax reference to company details
Legislative and system changes for P60 and P32 forms
Improvements
Reporting: Enhancements to NEST pension reports, Improvements to holiday report, Improvements to standard life joiners report, Improvements to employee headcount report
New exception warnings for employee email and address change
Improved validation on deleting supplementary runs
Improvements in batch processing of timesheets
Highlight Details
Legislative Changes
| Anchor | ||||
|---|---|---|---|---|
|
The data for the 2025-2026 tax year thresholds has been uploaded. Also, the year-end guide for 2024-25 is available here: Year End Guide.
Statutory neonatal care pay (SNCP) and leave (SNCL) is a government-mandated benefit that allows eligible employees to take time off work to care for their new-borns receiving neonatal care.
To qualify for statutory neonatal care pay and leave, employees must meet certain criteria, such as:
The entitlement applies to parents of children born on or after 6 April 2025 and who are employed in England, Scotland or Wales.
The child must enter into neonatal care within 28 days of birth and spend at least 7 continuous days in care.
One week of neonatal absence is accrued for every full week the child spent in neonatal care, up to a maximum of 12 weeks.
Neonatal absence can only be booked in weekly blocks of 7 consecutive days.
Neonatal absence must be completed within 68 weeks of the child's birth or matched date.
For complete details, refer to the information available on the gov.uk website.
New features details
Custom import
Ability to bulk import statutory overrides
| Anchor | ||||
|---|---|---|---|---|
|
We have introduced a new employee statutory override table within the custom import format. This feature allows you to add statutory override fields and bulk import these overrides. It supports the override of statutory payments for various absence types, such as SSP and SMP, as well as pension payments. Additionally, it includes system payments like tax paid and threshold values for NI and tax calculations. Multiple rows of statutory override payments per employee are supported, and the imports default to the current pay period.
Ability to ignore footer rows during import
| Anchor | ||||
|---|---|---|---|---|
|
We have introduced a new footer field to the custom import feature. Data preceding the first matching footer will be considered for import, and any data following the footer will be ignored. If a value is entered, the import process will halt before the first row that matches the footer text. For example, if you enter total in the footer field, the system will match the complete string total and import only the valid data prior to the footer.
Additionally, a regular expression pattern can also be provided in the footer field, starting with ^ (matches the beginning of a line) or $ (matches the end of a line). For example, ^total matches any string starting with total, such as total, total sum, total amount, while $pay matches any string ending with pay, such as pay, total pay, basic pay, etc.
Ability to fill missing data from current record
| Anchor | ||||
|---|---|---|---|---|
|
We have introduced an as update field for the following date columns in custom import:
Employee job - date of change
Employee location - start date
Employee NI - start date
Employee P45 - P45 start date
Employee pay/ded - date of change
Employee tax - start date
Employee work schedule - start date
Employee pension - date of change
During import, if the as update checkbox is selected, it will insert a new record with the specified date if an update is required, for example, a different annual amount for a payment. This works in the same way as when not specifying a date but will insert the record with the entered date instead of the default (usually period start date).
The system will automatically fill in any missing data using the existing information for the employee. For instance, when importing changes to employee job details, like job title or net hours, the system can pull the missing information from the existing employee record, provided the as update flag is checked for the employee job - date of change field.
Changes to the import order
| Anchor | ||||
|---|---|---|---|---|
|
We have changed the order of importing to ensure correct tax codes can be applied to leaving employees in all scenarios. The employee starter checklist data is now imported before the employee leaver data.
Enable validation fields for custom import
| Anchor | ||||
|---|---|---|---|---|
|
We have introduced a pages to import section for standard formats [Standard]Employee on-off payments, [Standard]Employee leaver, and [Standard]Employee payments. This section clearly identifies which pages are imported and which are not. Pages that are not imported can still be utilized for validation purposes, if set.
These formats now include surname and NI number as validation fields. These fields will not be imported but can be used to validate the data. For instance, if the import file contains a surname or NI number, the import will only proceed if it matches the employee surname or NI number in the system. If it does not match, the import will fail with a validation error. This validation allows for multiple lines for one employee, enabling multiple payments and adjustments.
Reporting
Exceptions new report completely replaces the exceptions report
| Anchor | ||||
|---|---|---|---|---|
|
The exceptions report is no longer available under standard reports → employee category. Exceptions report definitions are no longer listed under group reporting definitions and run report definitions, across all user roles. Exceptions new report should be used instead of the previously available exceptions report.
Ability to include tax changes by period range report to group reporting
| Anchor | ||||
|---|---|---|---|---|
|
You can now generate a tax changes by period range report under the standard reports → employee category for the current pay period. To generate the report for the current pay period, enter 0 in the pay period from and pay period to fields. This report can then be included in the group reporting definition and sent to clients.
Addition of neonatal payments to various reports
| Anchor | ||||
|---|---|---|---|---|
|
The relevant nominals and reports have been updated to include neonatal payments for statutory neonatal care pay (SNCP) and leave (SNCL).
Absences
New absence type to support SNCP and SNCL
| Anchor | ||||
|---|---|---|---|---|
|
We have introduced a new absence type neonatal care under absence → absence entry to support the statutory neonatal care pay (SNCP) and leave (SNCL) legislative requirements.
Please note the following criteria for SNCP and SNCL:
The entitlement applies to parents of children born on or after 6 April 2025 and who are employed in England, Scotland or Wales.
The child must enter into neonatal care within 28 days of birth and spend at least 7 continuous days in care.
One week of neonatal absence is accrued for every full week the child spent in neonatal care, up to a maximum of 12 weeks.
Neonatal absence can only be booked in weekly blocks of 7 consecutive days.
Neonatal absence must be completed within 68 weeks of the child's birth or matched date.
For complete details, refer to the information available on the gov.uk website.
New service length field added to employee general and export data
| Anchor | ||||
|---|---|---|---|---|
|
We have introduced a new service length field on the employee → general details screen, which displays the duration of an employee's employment. This field calculates the time from the employee's date of joining or service start date to the end date of the current period or the employee's leaving date. The service start date can be exported, allowing users to include this information in reports, formatted as years, months, and days.
Payslip impersonation for non-payslip portal account holders
| Anchor | ||||
|---|---|---|---|---|
|
InPay users with access to the pay → payslip viewer can now view payslips for employees without a payslip portal account using impersonate option, provided an RSM InTime host is set on the company > general screen. This view mirrors the payslip view that RSM InTime users see when using single sign-on to access the payslip portal.
Ability to set SSP offset at absence level
| Anchor | ||||
|---|---|---|---|---|
|
We have introduced SSP offset checkbox on the absence → absence entry screen. This feature allows users to mark SSP offset against individual absence entries, ensuring that the amount of SSP paid is accurately reflected on the payslip. The update allows the flag to be set for individual absences, enabling selective offsetting based on specific records. Previously, the SSP offset flag was applied at the employee level, affecting all absences for that employee.
Ability to resend payslip emails
| Anchor | ||||
|---|---|---|---|---|
|
You can resend or delete payslip emails using the new resend selected emails and delete selected emails buttons under the email log table in the company → email screen. This feature allows you to select and manage emails that have failed, either by deleting them or resending them.
Additionally, you can select a specific payroll to resend the most recent payslip emails by using the resend last payslips emails button in the resend email payslips section.
Added corporation tax reference to company details
| Anchor | ||||
|---|---|---|---|---|
|
We have added the corporation tax reference (COTAX) to the company → details screen. It accepts a 10-digit value and must be a unique reference. This 10-digit code will be reflected in the FPS generation and submission, starting from the tax year 2025.
Legislative and system changes for P60 and P32 forms
| Anchor | ||||
|---|---|---|---|---|
|
Following changes have been introduced for P60 and P32 forms to support legislative and system changes for the tax year transition from 2024 to 2025.
Tax year (2024/25) is displayed on the tax year drop down for pay → P60 viewer and pay → payslip viewer
Tax year (2024/25) is displayed on the P60 form.
You can generate and download P32 and P60 report for relevant tax year under report → statutory category.
The P32 and P32 YTD reports display the SNCP compensation and SNCP recovered values.
The processes → P32 adjustments screen for tax year 2025/2026 includes SNCP recovered and SNCP compensation fields.
For more details, refer to the InPay Year End Guide 2024/25.
New CitiDirect Bacs format
| Anchor | ||||
|---|---|---|---|---|
|
A new CitiDirect Bacs format is introduced. Bacs files will be generated in .CSV format. Documentation on the available Bacs formats can be accessed at Bacs formats.
Improvement details
Reporting
Enhancements to NEST pension reports
| Anchor | ||||
|---|---|---|---|---|
|
The alternative unique identifi field on NEST Contribution Pension and NEST Enrolment Pension reports, under the standard reports → pension exports category, now populates with the membership field value from the employee's pay → pensions page. If the membership field on the employee's pay → pensions page is empty, the employee number will be displayed in the alternative unique identifi field.
Improvements to holiday report
| Anchor | ||||
|---|---|---|---|---|
|
The average rate is now accurately displayed for all scheme types, including hourly, daily, and periodic, in the holiday plain report under the employee category.
Improvements to standard life joiners report
| Anchor | ||||
|---|---|---|---|---|
|
We have improved the standard life joiners report under pension exports category to include employees with date of joining and pension joining date in the previous period.
Improvements to employee headcount report
| Anchor | ||||
|---|---|---|---|---|
|
The employee headcount report under the employee category now includes employees who started and left on the same day.
New exception warnings for employee email and address change
| Anchor | ||||
|---|---|---|---|---|
|
The employee → exceptions new report has been updated to include details of employee email and address change, under the email address change and address changed sections.
Improved validation on deleting supplementary runs
| Anchor | ||||
|---|---|---|---|---|
|
We have introduced a validation to stop accidental deletion of supplementary runs when multiple users are viewing the page at the same time. We have also introduced a lockout of 3 seconds on click of delete supp run-2 button.
Improvements in batch processing of timesheets
| Anchor | ||||
|---|---|---|---|---|
|
When a batch of timesheets is exported from RSM InTime, it may contain records for employees who have left or been deleted. The InPay timesheet service (EmployeeTimesheetV4 endpoint) now ensures that only the timesheets for these former employees fail, while the rest of the batch processes successfully. The response provides a detailed list of succeeded and failed timesheets, ensuring that only the problematic entries are flagged, and the remainder are processed correctly.