A payroll you can audit

What it is

Payroll software that can show its working. Every contribution line carries the rate it used, the instrument that sets that rate, the date it took effect, and whether it has been reconciled against a real payroll — all of it on the statutory schedules page.

It runs on the entity you already own. Malaysian statutory schemes — EPF, SOCSO, SKBBK, EIS, PCB, the HRD Corp levy and zakat — computed from the published schedules, for one company or several on one record.

Three decisions that shape everything else

No silent zero

A missing fact produces a blocker naming the employee and what is absent — never an amount of nothing. A zero looks like an answer, reconciles like an answer, and is discovered when somebody is underpaid.

The record is the system of record; a run states only what is true of that run

Who is employed, what is known about them, what they are standingly paid and what a previous provider paid are all stored, each with the date it became true, and nothing is ever overwritten. The test is whether a value could also be true next month: if it could, it belongs in the record.

The engine does not know which country it is in

The calculation engine contains no scheme name — no EPF, no SOCSO, no PCB — and stores contributions as rows, not columns. Two earlier builds of this product died from breaking that rule, so now a check fails the build instead of trusting convention.

Where the build actually is

Working, with tests: the calculation engine, the Malaysian country pack and its rule data, the HTTP contract and its generated clients, the web client's screens, and this site.

Not finished, and each of these is a real gap, not a rough edge:

• Login UI. Better Auth sessions and database-enforced organization access are implemented, and the web client serves sign-up, sign-in and organization selection. What is not finished is hosting: the app is not yet live at its hostname.
• Deployment. Neither the API nor the web client is hosted anywhere. This marketing site is the only deployed part.
• Statutory forms and bank files. Declared and specified, but they currently refuse: the identity data they need is not modelled yet, and a filing with a wrong reference number is worse than no filing.
• Most rate data is cited but not reconciled. Sourced with a source and a date, checked against published worked examples, and not yet compared against money a real person was paid — except EPF, which has been.

Talking to us

There is no sales team. Mail goes to the person building it, which is currently the fastest route for anything real.

• A walkthrough of a live run —coding@hazli.dev
• A figure on the schedules page that disagrees with its source —tell us, and we will fix the rule data, not the page
• An integration against the API —write first, because the contract is stable and the deployment is not