EXA38
— Onboard partners or customers —
HR Onboarding Fan-Out
One new-hire form fans out to 7 systems — Polymonial gives each system only the fields it needs.
The problem to solve
A new hire fills in one form. That form fans out to 4-7 systems — payroll (full salary + tax + NI), pension provider (salary + DOB), benefits (salary + dependents), IT (name + email + role), security (background-check level). Each system gets the full record because integration is 'send the whole thing'. One breach exposes everything.
The solution it enables
Onboarding form ships as a single sealed record. Each downstream system has its own schema: payroll gets salary + tax + NI; pension gets DOB + salary; IT gets name + email + role; benefits gets dependents. Schemas selectively decrypt. The full record exists nowhere outside HR.
What it looks like
A 4,500-employee group has 40 new hires/month. Each hire's onboarding form flows to 6 downstream systems via API integrations. Today: payroll gets the full record (overshoot for IT-related fields), IT gets the full record (overshoot for salary + tax), benefits gets the full record. Six replicated copies of every onboarding record exist. After Polymonial: HR seals the record once. Each downstream's schema unseals exactly what they need. Payroll schema unseals salary + tax + NI; IT schema unseals name + email + role; benefits schema unseals dependents. Six replicated copies become one sealed copy with six selective views.
“One onboarding form. Six downstream systems. Six selective views of one sealed record.”
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.