Payroll data, defended in depth
Security claims should be architecture, not adjectives. Here is exactly how your data is protected — and the honest edges of it.
Encrypted in transit
Every connection between your devices and the cloud runs over TLS. No plaintext, ever.
Isolated per business
Every API request is scoped to your business — server-side, on every endpoint. Tenant isolation is the first check, not an afterthought.
Authenticated properly
OAuth token-based sessions; approvals re-verify passwords server-side; sensitive actions can require step-up authentication.
Permissions enforced twice
The app hides what your role cannot see; the server refuses what your role cannot do — the same tree, checked in both places.
An unbendable audit trail
Who changed what, when, and who approved it — recorded where it cannot be quietly edited.
SINs masked
A social insurance number appears in full only where the law requires it — on the filing and the employee's own slip — and as its last digits everywhere else.
Reverse, never edit
A posted pay run is corrected by reversal and a revised run. Nothing is edited or deleted, so the history always explains the money.
Unknown is not zero
A balance or amount that cannot be worked out is shown as unknown — never as a confident $0 that someone acts on.
Permissions that hold
Hiding a button is not access control. Who can prepare a pay run, who can approve it and who can post it are permissions checked twice: the interface hides what a role cannot see, and the server refuses what a role cannot do. The server is the authority.
Where the data lives
SeroPayroll runs on Microsoft Azure, on the same platform as SeroBooks and SeroPOS, with every request scoped to the business that made it. Card details for your subscription go to Stripe and never reach our systems.
We publish capabilities rather than badges. Formal compliance certifications will be announced when they are audited, never before.