<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

The shared core every product runs on

Identity, the transaction and workflow engine, documents, country packs and audit — built once, used by Payroll, Time and HR alike so the estate behaves as one system.

Stoneme platform
Highlights

The shared core: identity, the transaction and workflow engine, documents, country packs and audit.

  1. 01Single sign-on with role- and attribute-based access
  2. 02Workflow & approval engine
  3. 03Documents, packs & notifications

Every screen ships in Arabic and English

Built once, shared by every product

Identity, workflow, approvals, country packs, documents and audit live in one core — so Payroll, Time & Attendance and HR behave as a single system.

  • Identity & access

    SSO/JWT identity with RBAC + ABAC, two personas (back-office and self-service) and field-level PII encryption.

  • Transaction & workflow engine

    The universal submit → approve → post → reflect engine, with two-axis status and effective-dating, that every domain plugs into.

  • Approval engine

    Ordered steps, committees, delegation, consultation and SLA escalation — segregation of duties expressed as configuration.

  • Country packs

    Versioned, effective-dated statutory, calendar and currency configuration shared across every product in the estate.

  • Documents & notifications

    Templated, bilingual document generation and a notification spine that the whole estate emits through.

  • Audit & permissions

    An append-only audit trail and a capability matrix with a permissions epoch, so access changes propagate instantly and provably.

Frequently asked questions

Is Stoneme sold on its own?

Stoneme is the platform layer the products run on rather than a standalone app. You adopt it implicitly with any product; its capabilities — identity, workflow, audit — are shared by all of them.

What is the transaction engine?

A single lifecycle — submit, approve, post, reflect — that every domain change rides. A new change type is a payload, an optional template and a reflector; there's no new lifecycle code.

How do permission changes take effect?

The capability set is cached against a permissions epoch that bumps on any change and is surfaced as a response header, so clients refetch and access updates immediately.

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.