After the payroll, the pension round
The pay run is done. Now each client's pension contributions need to go to their provider. Some clients use NEST, some The People's Pension, some Smart Pension, a few have insurer schemes with their own portals. Your payroll software produces a file or connects directly for some; for others, an administrator logs into a portal and uploads.
Some uploads fail with an error about a missing field. Some are accepted but the payment collection fails. Some are simply forgotten in a busy week. You find out when a provider writes to the client about missing contributions, and the client forwards it to you, unhappy.
Why pension submissions slip
The pension step comes after the pay run, when the pressure is off and attention has moved to the next client. Each provider works differently, and errors are reported in their portal, not in your payroll software. Employees who opt out, rejoin or change their contribution rate create mismatches that providers reject.
There is rarely one list of 'pension submissions due and done' across the bureau. Each administrator tracks their own, in their own way.
What failed uploads cost
Late contributions can lead to warnings from providers and, if unresolved, to the regulator, and your client will look to you for why. Fixing failed submissions weeks later means reconstructing what went wrong. Employees who notice missing contributions on their pension statement raise it with the client, and the trust you built on getting pay right is dented by the step after it.
| Failure | Where it shows up | Usually noticed |
|---|---|---|
| File rejected on upload | Provider portal | If someone checks |
| Records rejected for data errors | Provider portal, per member | Often late |
| Payment collection failed | Provider notice to employer | When the client forwards it |
| Submission not made | Nowhere | When the provider chases |
How we build pension submission tracking
- For each client, we record which provider and scheme they use, the submission route (direct from payroll software, file upload or portal entry) and the due dates.
- After each pay run, a submission task is created per client, with the contribution totals read from your payroll software.
- Where your payroll software or the provider offers an API or status report, we read acceptance and payment status automatically. Where they do not, the administrator marks the stage done and uploads the provider's confirmation.
- Before a file goes, we check it for common rejection causes, such as missing National Insurance numbers, invalid dates or members with changed rates, and flag them to fix first.
- A bureau-wide list shows every submission due, done, rejected or waiting on payment, sorted by how close it is to the provider's deadline.
- Rejections and failed collections create a task for the administrator responsible for that client, with the provider's message attached.
The duties around pension contributions sit with the employer and their provider's rules. The tracker helps your bureau do the part you have agreed to do, and shows where each submission stands.
Pensions finished, not just started
Every run ends with a pension submission that is confirmed, not assumed. Rejections are fixed in days instead of weeks. The provider's letters stop being the way you find out. And managers can see across the bureau which clients' pensions are complete for the period and which are not.
Is this happening in your bureau?
- Clients forward you letters from pension providers about missing contributions.
- Each administrator tracks pension uploads their own way.
- Rejections are found in provider portals weeks later.
- You use several providers, each with its own portal and format.
- Nobody can say which clients' pensions are complete this month.