Four products. One governed platform.
Start with one product or run all four. Each keeps its own data, and together they share one sign-in, one approval engine and one audit trail on the Stoneme platform.
Four products. One governed platform.
Start with one product or run all four. Each keeps its own data, and together they share one sign-in, one approval engine and one audit trail on the Stoneme platform.
Payroll
Multi-country salary calculation, statutory math and bank files — retroactive and off-cycle by design.
Explore Payroll
Time & Attendance
Schedules, attendance and leave that feed payroll — with GCC weekends and holiday calendars.
Explore Time & Attendance
HR
The canonical employee record, org structure and the hire-to-onboard loop.
Explore HR
Stoneme platform
The shared core: identity, the transaction and workflow engine, documents, country packs and audit.
Explore Stoneme platform
Every payroll & HR domain, in one platform
From salary calculation to end of service, every domain is a governed module on the same approval engine and the same audit trail.
Separately deployable. Deeply integrated.
The products are independent enough to adopt one at a time, and integrated enough to behave as a single system — because they share a core instead of duplicating it.
One identity, everywhere
A single SSO/JWT identity with RBAC + ABAC scoped by tenant, branch and manager-chain — the same person, the same permissions, across every product.
One transaction engine
Every change rides the same submit → approve → post → reflect lifecycle, so approvals and posting behave identically whether it's a raise, a roster or a hire.
One audit trail
An append-only history spans the whole estate — who did what, when and what it changed, in payroll, time and HR alike.
Shared country packs
Statutory rules, calendars and currency precision are configured once and resolved everywhere — add a jurisdiction as data, not a fork.
Frequently asked questions
Can I buy just one product?
Yes. Each product is independently deployable with its own database. Start with Payroll, add Time & Attendance and HR when you're ready — the shared Stoneme core means they integrate without a migration.
Is this microservices?
No. Each product is a modular monolith — one deployable with schema-per-module boundaries enforced in CI. A module is peeled into its own service only under measured pressure, never by default.
How do the products share data?
Through service contracts, never each other's tables. HR owns the canonical employee directory; Payroll and Time read it through a typed interface, so the seam stays clean if a product is ever extracted.
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.