EXA27
— Send data to a third party —
Pension Contribution Privacy
Monthly payroll-to-pension files leak the salary book — Polymonial wraps each row so the provider verifies math without seeing salaries.
The problem to solve
UK auto-enrolment + similar regimes worldwide require employers to file monthly contribution data with their pension provider — full salary, NI number, contribution rate, age, employment status. The provider needs the contribution math; they get the entire payroll for free. The data sits in the pension provider's systems for years, available to their actuarial teams, third-party administrators, and any breach.
The solution it enables
Polymonial schema-wraps the monthly file at the payroll system. Pension provider verifies contribution math (correct percentage, threshold met, age eligibility) over sealed records. Salaries + NI numbers stay inside payroll. Compliance unchanged; over-disclosure removed. Same spreadsheet/CSV/SFTP infrastructure, just sealed contents.
What it looks like
A 12,000-employee group pays monthly pension contributions to a workplace-pension provider via SFTP CSV. Today: full salary book lands on the provider's storage every month. After Polymonial: the payroll system seals each row; the provider's schema verifies contribution percentage on each sealed row. Salaries decrypt only on the provider's narrow tax-band-overrun audit query. Twelve thousand salary points stay inside payroll where they belong.
“The pension provider gets the contribution math. They don't get the salary book.”
Who’s this for you?
We have this problem.
Your organisation needs this for its own data, product or programme of work.
We deliver this for clients.
A consultancy, integrator, service provider, industry programme or technology vendor.