Software that has to be right.
We build business systems for Cambodia — payroll, invoicing, automation — where every rule they enforce traces back to the document it came from.
{
"instrument": "nssf.contribution",
"basis": "gross_monthly",
"employer_rate": 0.0000,
"employee_rate": 0.0000,
"ceiling_khr": 0,
"effective": "[placeholder]",
"authority": "449/2017 LV/PrK"
}
Figures are placeholderA payroll run producing real figures
The rules, compiled.
Most software is allowed to be approximately right.
Payroll isn't. Tax isn't. An invoice submitted to the GDT isn't. When being slightly wrong means a penalty, a re-filing or an inspection, “it mostly works” stops being an acceptable answer — and the way you build has to change to match.
Recorded once, every place it lands
A rate, a threshold, a deadline — recorded once from the document it came from, then read by everything that depends on it. When it changes, it changes in one place, and everything downstream follows.
Built and running
Not prototypes. Each has real users and a production database behind it.
IustumHR
Cambodian payroll compliance — NSSF, Tax on Salary, GDT filing, shift scheduling and leave balances, with NBC exchange rates fetched daily.
02 — FinanceIustumBill
Utility metering and invoicing for rental properties — meter rounds, anomaly review, batch generation with a rent-cycle guard, and delivery by email or Telegram.
03 — PropertySokhom Residence
A trilingual property site with enquiry routing, and honest attendance records for the staff.
Four more, shipped
Feast · Mission Control · Workout tracker · internal tooling. Range matters when you're hiring someone to build something that doesn't exist yet.
Who you are changes the answer
Three doors, same company behind them.
Small business
Payroll and invoicing that already know the rules, priced for a business that doesn't have a finance team yet.
Enterprise
Multi-entity deployments, audit trails, tenant isolation, and integration with the systems you already run.
Government
We've worked inside Cambodia's government digitisation programme, and we build to the documentation and accountability standards institutions require.
What needs building?
Pick the closest, or tell us it's none of these.
A system built from your rules, not adapted to them.
Instruments implemented
An instrument is the legal document a rule comes from — a law, a prakas, a sub-decree. Every rule the payroll engine applies is written down somewhere official, and that document is its instrument.
Provisional list, not yet verified. Every entry is checked against its primary document — not against a summary — before this grid goes live.
Every claim carries its source
The discipline that makes the software right is the same one that governs what we say about it.
NSSF occupational-risk contributions, calculated at the current rate against the statutory wage ceiling.
- Authority
- Prakas 449/2017 LV/PrK
- In force from
- [Awaiting primary-source check]
- Also governed by
- Sub-Decree 144 (wage floor and ceiling)
- Last reviewed
- [Awaiting primary-source check]
- Enforced in
- IustumHR payroll engine