Separation of duties
Whoever prepares a rate change cannot approve it. Whoever reports a disciplinary case cannot decide it. Enforced in the server action, not hidden in the interface — and the refusal names the rule that stopped you.
Philippine HR, payroll, finance & loans
Payroll you can
defend line by line
Anyone can compute a payslip. An auditor asks where the figure came from, who approved it, and whether it could have been changed quietly. Every number here answers all three — years later.
No sign-up, no card. Read-only session in a sandbox company.
0
specification sections built against
0
automated tests, run before every deploy
0
permissions, every one enforced in code
The controls
Four rules that hold
when somebody is in a hurry
Statutory tables prove themselves
A version cannot go live without the official issuance, its SHA-256, a named professional's sign-off, and the agency's own worked examples reproducing to the centavo. A mistyped bracket is caught at review, not a quarter later by the agency.
One owner for every rate
Payroll, loans, accounting and reporting read rates through a resolver. None of them can author, default or override one. A test fails the build if a module reaches around it.
Records are added to, never edited
Correcting a past rate writes a correction and raises a retroactive event. A posted run is reversed, never recomputed in place. What was paid stays legible beside what should have been.
Provenance
One deduction, four steps to the circular
Not a report you generate. It is the shape of the records, so the chain exists whether or not anybody asks for it.
- 1Payslip line
SSS employee — ₱1,125.00 - 2Result snapshot
statutory version SSS 2026-01 - 3Endorsement
signed off — A. Bautista, CPA - 4Source issuance
SHA-256 f8a8530984d833dd…
Scope
Hiring through to the ledger
One system. No export step between departments, and no spreadsheet in the middle.
- Human resources
- 201 file, org structure, plantilla, movement, discipline
- Compensation
- Bitemporal rates, structures, mass change, guardrails
- Timekeeping
- Devices, schedules, timesheets, overtime, holidays
- Payroll
- Runs, 13th month, retroactive, final pay, payslips, reversal
- Statutory
- Agency masters, remittance, alphalist, 2316, annual tax
- Finance
- Chart of accounts, journals, posting, period close
- Loans
- Products, capacity checks, applications, amortisation
- Self-service
- Payslips, leave, change requests with cooling-off
- APPROVEPayroll run PR-2026-00002 approvedR. Cruz
- UPDATERate change CCR-00014 activatedM. Santos
- EXPORTAudit trail exported, 30 daysSystem Administrator
- REFUSEDSelf-approval — preparer is approverR. Cruz
An undocumented number is
not acceptable in payroll
A rate is correct only when its owner, version, effective date, approval and source can all be produced. This is built so they can.