Keeps: every run and its reasons
The run, each person’s lines, and the explanation of every change from last month.
Payroll deserves clear access controls and a traceable review.
Payroll deserves clear access controls and a traceable review. Pay is designed to keep sensitive records restricted to the roles you choose and require a named approver before any future payment or submission. These are design intentions, not certifications or live capabilities.
Product design preview · Pay has not shipped. All features, screens and prices are proposals.
Design intentions, not audited certifications.
Pay is a proposed product, not an available payroll service. These U.S. screens use fictional USD records. There is no app, beta or launch date yet. Supported states, tax calculations, filings and payment connections must be confirmed before launch. Join the waitlist to help shape the U.S. experience.
A payroll record holds what each person earns, their tax and their bank account. The design starts from what Pay should never do with it.
The run, each person’s lines, and the explanation of every change from last month.
Who prepared each run, who approved it, who changed a salary, and when.
Each return or contribution file stored beside the run it came from.
The payment file is released only after a named person approves the run.
Employees see their own payslips; payroll roles see the rest.
Nothing of yours is used to train anything, inside Centilio or out.
Design intentions, not audited certifications.
Compliance here means the right deduction for the right person, the right file on the right day, and a record that shows both. That is what Pay is designed to do, not a badge it holds.
Rules change. When a rate, a limit or a form changes, the change is designed to be dated, shown in the run it first affects and explained to the approver before the run is paid.
Who may prepare, approve or only read comes from Account, the same login and roles as every Centilio tool.
There is no second list of people to keep in step. When someone leaves and is removed in Account, they lose access to payroll at once; their own payslips stay reachable to them as the law and your policy require.
Every run records who prepared it, who approved it and what changed. On Business, maker and checker can be required, so no one person can both prepare and approve a run.
Design intentions, not audited certifications.
An assistant inside payroll must never know more than the person asking it. Celia is designed to stay inside that line.
When an employee asks Celia why their pay changed, it reads their payslip and the approved explanation, and nothing about anyone else. When a preparer asks about a run, it reads only what that role may read.
Celia drafts explanations and flags problems; it does not release payments, submit filings or change a salary. Everything it drafted is marked as such in the trail, with the person who accepted it.
Design intentions, not audited certifications.
Pay is designed to run on the platform that already serves the live Centilio tools.
Payroll records are designed to be encrypted in transit and at rest, inside your organisation’s space, with multi-factor sign-in and device rules from Account. We claim no certification for Pay: a product that is not built cannot hold one, and when there is something true and dated to say, it will be here.
Pay does not exist yet, so there is nothing running to secure or certify. This page is the design, and it will be rewritten with what is true and dated on the day Pay ships.
Only the roles you allow in Account: owner, payroll preparer, approver and accountant. Each employee sees only their own pay, and Celia is held to the same limits as the person asking.
No. No run is paid and no filing goes out until a named person approves it, and on Business the person who prepares a run cannot be the one who approves it.
No. Nothing of yours is used to train anything. Celia reads the run to serve you, inside your organisation’s space.
The exact fields, retention rules and access controls will be published before real payroll data is accepted. This preview contains only fictional people and amounts. Do not enter sensitive employee information here.
In your Centilio account, encrypted in transit and at rest, under roles you control and exportable at any time. Regional residency is proposed on Enterprise.
No, and we will not claim one for a product that is not built. When there is something true and dated to say, it will be on this page.
Pay is planned after Team and Ledger, with no launch date yet. Tell us your team size, work locations and the parts of payroll review that take too much time. Those needs will shape the U.S. experience.