A payroll you can audit

What it is

Payroll software that can show its working. Every contribution line PEOPLE computes carries the rate it used, the instrument that sets that rate, the date the rate took effect and a flag saying whether the figure has been reconciled against a real payroll. You can read all of it on the statutory schedules page before talking to anybody.

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. This is the failure mode that makes payroll software dangerous: a zero looks like an answer, reconciles like an answer, and is discovered when somebody is underpaid. PEOPLE stops instead.

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, effective-dated and append-only. A payroll request may say a day count and one-off lines and nothing else. The test is whether a value could also be true next month: if it could, it belongs in the record. This closes the path by which a payroll request quietly restates a salary.

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 rather than columns. A country pack takes wage bases, employee facts, a statutory month and a year-to-date ledger, and returns explained contribution lines. Two earlier builds of this product died from breaking that rule, which is why it is enforced by tooling that fails the build rather than by 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 rather than a rough edge:

• Login UI. Better Auth sessions and database-enforced organization access are implemented. The web client does not yet expose sign-up, sign-in or organization selection.
• 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, and they currently refuse rather than emit — because the identity data they need is not modelled yet, and a filing with a wrong reference number is worse than no filing. There is also no single Malaysian bank file format: each bank publishes its own, and we hold one as verified.
• Most rate data is cited but not reconciled. Sourced with provenance, 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 —hello@flightworkly.com
• A figure on the schedules page that disagrees with its source —tell us, and we will fix the rule data rather than the page
• An integration against the API —write first, because the contract is stable and the deployment is not