Every AI action is a proposal. Every proposal needs you.
The honest question about any payroll tool that uses AI is what happens when it gets something wrong. Here is how we answer it, and how you can check each answer in your own account rather than taking our word for it.
Nothing happens until you say so
The assistant does not write to your payroll. It prepares the change and brings it to you: raise Siti's salary to RM 4,200 from 1 September. You approve it or you don't. Bank details and payroll lock come to you every time, whatever else you have set up.
See for yourself. Ask it to change a salary. It arrives in your inbox, not in your records.
A record of who did what
Every approval, lock and edit is written down with the time, the person, and the value before and after. It is there when your auditor asks, and it reads like sentences rather than a database dump.
See for yourself. Open Audit and export a month as a spreadsheet.
Your accountant sees the payroll, not your people
Invite your accountant and they get what they need to file: payroll figures and reports. IC numbers, addresses and bank details are not in their account to open. You decide who is in your workspace, and nobody outside it can see your company at all.
See for yourself. Invite them, then look at what they can actually open.
The assistant can only do what you can do
It runs with your permissions, not its own. Ask it for something outside your role and it declines the same way the rest of the app would. Your staff do not have it at all.
See for yourself. Sign in as one of your employees. There is no assistant there.
Your provider key stays yours
If you bring your own AI key, it is encrypted before it is stored and it is never shown to the model. We keep the last four digits so you can tell which key is which.
See for yourself. Save a key, then reopen the page. Only the last four digits come back.
You can check where the numbers come from
EPF, SOCSO, EIS, PCB and HRDF come from rate tables that carry an effective date and a link to the authority that set them. When a rate changes, your runs change with it.
See for yourself. The table below is that data, read from the payroll engine itself.
Every rate carries its source and the date it took effect
This is the part most payroll tools ask you to take on faith. Ours is a table you can audit, read straight from the same rate tables the payroll run uses.
| Code | Instrument | Rate basis | Effective from | Authority |
|---|---|---|---|---|
| EPF | Employees Provident Fund | 11% employee, 13% employer | 2025-10-01 | Third Schedule, EPF Act 1991 (KWSP) |
| SOCSO | Social Security Organisation | Wage-banded schedule | 2024-10-01 | PERKESO Act 4 / Act 800 contribution schedule |
| EIS | Employment Insurance System | Wage-banded schedule | 2024-10-01 | PERKESO Act 4 / Act 800 contribution schedule |
| PCB | Monthly Tax Deduction | Computerised MTD | 2025-01-01 | LHDN computerised MTD specification (YA2025) |
| HRDF | HRD Corp levy | Headcount-banded | 2024-01-01 | HRD Corp levy calculation guideline |
Data usage
Your employee data, payroll records and salary information are used solely to run your payroll inside your own workspace. We do not train models on your data. When you use the built in AI tier, your queries go to the configured model provider under their API terms. If you need a zero egress configuration, bring your own keys under Advanced settings to keep all AI processing within your infrastructure. Verify the current terms of your chosen provider before relying on this for compliance.
PDPA posture
- Data is processed under your instructions, as a data processor.
- Tenant isolation means your data is never visible to another company.
- Audit logs provide the access records PDPA compliance requires.
- Encrypted at rest with AES-256-GCM, and in transit with TLS.