Localization
Localization is five axes, not a translation file
A user in Riyadh can read English, see Hijri dates, format in SAR, on Riyadh time, under KSA rules — all at once. HRMSTONE models each axis separately and resolves it per user.
Enterprise localization
Five locale axes — resolved independently
Localization isn't "translate the buttons." A user in Riyadh can read English, see Hijri dates, format in SAR, on Riyadh time, under KSA rules — all at once. HRMSTONE models each axis separately and resolves it per user.
One user · Riyadh
Five axes, resolved independently
- UI languageEnglish / العربية
- Formatting regionSAR grouping
- CalendarHijri (Umm al-Qura)
- TimezoneAsia/Riyadh
- Data jurisdictionKSA country pack
Per-user preferences
Each person chooses their language, calendar, timezone, digits and theme — and their own payslip renders that way.
Hijri ⇄ Gregorian
Switch calendars as a reversible display conversion over a UTC instant; dual-display and legal-output locks supported.
Currency-correct money
JOD, KWD, BHD and OMR carry 3 decimals — a Money type uses currency-driven precision so payroll never silently rounds wrong.
Digit shaping
Eastern-Arabic ٠١٢٣ or Western 0123, per context — Arabic UI often keeps Western digits for money and IDs.
True RTL mirroring
Full layout mirroring via CSS logical properties, mirrored directional icons and bidi-isolated mixed content.
Bilingual documents
Letters, payslips and notifications render in the recipient's locale — Arabic + English side-by-side where required.
Beyond translation
Built bilingual, not retrofitted
Arabic isn't a skin over an English app — RTL, Hijri, digit shaping and currency precision are first-class, per user.
Per-user preferences
Each person picks their language, calendar, timezone, digits and theme — and their own payslip renders that way.
Hijri ⇄ Gregorian
Switch calendars as a reversible display conversion over a UTC instant, with dual-display and legal-output locks.
Currency-correct money
A Money type uses currency-driven precision, so three-decimal currencies like JOD and KWD never round wrong.
Digit shaping
Eastern-Arabic or Western digits per context — Arabic UI often keeps Western digits for money and IDs.
True RTL mirroring
Full layout mirroring via CSS logical properties, mirrored directional icons and bidi-isolated mixed content.
Bilingual documents
Letters, payslips and notifications render in the recipient's locale — Arabic and English together where required.
Frequently asked questions
Why separate the axes?
Because real users mix them. Reading English while needing Hijri dates and SAR formatting is normal in the GCC. Collapsing locale into one setting forces a wrong compromise; modelling each axis lets every user be exactly right.
Is the Arabic experience first-class?
Yes. The app mirrors fully in RTL via logical properties, shapes digits per context, and renders documents bilingually — Arabic is a primary language, not a translation layer.
How are dates stored?
As UTC instants. Calendar and timezone are display conversions resolved per user, so a single underlying value renders correctly as Hijri or Gregorian, in any timezone.
Get started
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.
- Statutory-accurate, MENA & GCC
- SaaS or on-prem, your keys
- Arabic & English, Hijri & RTL