<style>.reveal{opacity:1!important;transform:none!important}</style> Skip to content

Jordan statutory pack v3 is production-grade — GCC packs are in validation See coverage

Enterprise is a set of properties, not a feature

Enterprise isn't something you add — it's the deliberate set of properties that let one system serve large, regulated, multi-entity organisations without custom code per customer.

One system, every entity

These properties are what let a single deployment run payroll and HR for an entire group — across companies, branches, countries and currencies.

  • Configurable engine

    A builder-and-transaction split with a formula engine — a new allowance, deduction or country is configuration, not a code change.

  • Multi-everything

    Multi-tenant, multi-company, multi-branch, multi-country, multi-currency and multilingual — built for tens of thousands of employees.

  • Governance & audit

    Everything is a transaction, posted is immutable, and transaction-level permissions enforce who may create versus approve.

  • Money correctness

    Effective-dating, retroactive deltas, per-line logs and idempotency keys — provably right when the inputs change.

  • Layered security

    SSO/JWT, RBAC + ABAC scoped by tenant, branch and manager-chain, two personas and field-level PII encryption.

  • Built to last

    A modular monolith per product on its own PostgreSQL, schema-per-module, with CI-enforced boundaries — not microservice sprawl.

Standards we build against

Security and compliance are part of the architecture, not an afterthought.

  • ISO/IEC 27001:2022
  • SOC 2 (Trust Services Criteria)
  • OWASP Top 10
  • Database-per-tenant isolation
  • Customer-managed encryption keys
  • Immutable audit trail

Frequently asked questions

How many employees can it run?

The architecture is built to run payroll over tens of thousands of employees per tenant, with database-per-tenant isolation so one customer's scale never affects another's.

Do you need custom code per customer?

No — that's the point. New allowances, deductions, countries and approval routes are configuration on a shared engine. Custom code per customer is the anti-pattern this design avoids.

Why a modular monolith over microservices?

One deployable with enforced module boundaries gives you the seams of microservices without the operational sprawl. A module is extracted into a satellite service only under measured pressure.

Run payroll and HR for your whole group — on one governed platform.

Book a demo and see HRMSTONE run multi-country payroll, statutory filing and approvals — as SaaS, or on-premise for banks and government.