Introduce new options to improve the flexibility of pension data uploads/sync files. The goal is to allow users to combine pension data from multiple pay runs into a single file or sync operation, which is particularly useful for businesses that process frequent payrolls (e.g., weekly) but make pension contributions on a less frequent basis (e.g., monthly).
Proposed Functionality:
Combine Pay Runs for a Pension Provider:
Add an option to select and combine pension data from multiple individual pay runs that fall under the same Pension Provider.
This will generate a single, consolidated pension upload or sync file, rather than a separate file for each pay run.
Combine Pay Runs within a Date Range:
Add an option to include all pay runs that have been processed between a user-specified start and end date.
This will automatically gather all relevant pension data and combine it into a single file or sync.
Use Case: This feature is essential for scenarios such as:
Weekly Payroll, Monthly Pension or 2 Monthly payrolls (Salaried and Hourly Pay runs): A company runs payroll every week but only makes pension contributions and uploads pension data to the provider once a month. The new options would allow them to easily generate a single, combined file for their monthly pension submission, rather than having to handle four or more separate weekly files and combine manually.
Hello - We’re pleased to let you know that we can now produce a combined pension report in both PAPDIS and Aviva formats.
If you require other formats, these can be considered as part of a new enhancement request.
Please note that this release does not include integration with connected service pension providers.
This report is now available in reports pensions combined pension contributions. This is great that you get all contributions from different payrolls. However, the format on the report is not the format saved in the pension scheme it is a PAPDIS report which means I still have to manipulate the data to be able to upload to the pension scheme portal we use. Feels like a good idea badly implemented. Can this be looked at?