Reference
Statutory schedules
Every law PEOPLE cites, with the date it takes effect and where we read it. Changes are added rather than edited, so the page is also the history.
Open the schedulesResources
What we publish, and why.
A payroll product that asks to be trusted has to be checkable. These are the places to check it.
Reference
API and MCP reference
One contract in Zod, generated outward to OpenAPI, a typed SDK and MCP tools. Build against the published document.
Read the referenceReference
Security
How the system is built, what it stores, and who can reach it. Written for the person your company will ask to sign this off.
Read the security pageChangelog
Amendment log
Every date on which a rate PEOPLE applies came into force, newest first, worked out from the rates themselves. A run from before a change is never touched by it.
Read the logEngineering
How it is built underneath
Why no scheme name appears in the calculation engine, why money is integer minor units and never a float, and why a year-to-date figure is derived from stored runs rather than accepted as a number.
Read the platform noteGuides
Employer guides
Practical walkthroughs for a Malaysian employer — a first run, a mid-year switch, and the statutory forms each one produces. Nothing published yet; this card says so rather than linking somewhere that does not answer it.
Not published yetTell us what you need
Check it before
you trust it.
Every rate PEOPLE applies names the instrument it came from and the date somebody read it.