HR software that treats Arabic as a first language, not a setting
Most HR systems are built in one language and translated afterwards. You can tell within a minute: the layout does not mirror, the dates read backwards, and somewhere there is a screen that quietly stays in English because nobody got to it.
HR Master is built the other way round. The direction of the page and the shape of the type are decided before anything renders, in both languages, on every screen. A team that works in Arabic and English is not running a translated product — it is running the same product twice, correctly.
The rest follows from one decision: there is a single employee record, and every module reads it. Attendance does not keep its own list of people. Payroll does not keep a second one. That is what makes a leave approval turn into a payroll line without anyone retyping a name.
What we hold to
One record, always
Every module reads the same employee row. A second copy of your people is a bug, not a feature.
Both languages, every screen
Arabic gets its own type metrics and its own direction, rendered on the server. Never a flag that flips a stylesheet.
Say what it does, not what it evokes
Concrete claims, checkable ones. No certifications we do not hold and no connectors we cannot support.
Your data leaves whenever you want
Every table exports in either language. Keeping customers by making export painful is not a strategy.
See whether it fits how you actually work
The fastest way to judge it is against your own departments, grades and leave rules.