When a company decides to move to an HR system, it faces many offers with similar feature lists that differ in the details that actually matter: how leave and end-of-service are calculated, how flexible payroll is, and how easily data moves in and out. This guide helps you define what you need before speaking to any vendor, and assess offers with practical questions.

What does an HR system usually cover?

A human resources management system (HRMS) is made of modules you can enable in full or in part:

ModuleWhat it managesQuestion to ask the vendor
Employee recordsJob file, contract, documents, org chartAre there alerts for contract, Iqama and document expiry?
Time and attendanceBiometrics or mobile app, shifts, lateness, absence, overtimeCan records be reviewed and corrected before payroll?
LeaveTypes, balances, approval flowHow are leave types and balances set to the Labor Law and company policy?
PayrollAllowances, deductions, GOSI, end of serviceCan allowance rules be changed without code?
RecruitmentOpenings, applicants, interviewsDoes it connect to the careers page on your website?
PerformanceGoals, KPIs, review cyclesAre past reviews kept per employee?
Self-serviceEmployee requests, payslips, leave balanceDoes it work on mobile and in Arabic?

You do not have to switch everything on from day one. Many companies start with employee records, leave and payroll, then add attendance and appraisals.

Step one: write your requirements before asking for quotes

The most common mistake is to start with a demo before knowing what you are looking for. Write a page or two covering:

  • Headcount today and over the next two years, and how staff are spread across branches and sites.
  • Working patterns: fixed hours, shifts, field work.
  • Pay structure: approved allowances, commissions, advances, deductions.
  • Current systems it must integrate with, such as accounting.
  • Who will use it: HR only, or managers and employees too.

Selection criteria for companies in Saudi Arabia

1. Labor Law fit

Ask the vendor to show with examples how the system calculates items set by the Labor Law, including annual leave of not less than 21 days, rising to 30 days after five consecutive years with the employer (Article 109), the end-of-service award (Articles 84 and 85) and overtime pay (Article 107). Ask for a worked example for a sample employee instead of accepting "compliant with the law".

2. Social insurance and nationality

Contribution rates differ between Saudi and non-Saudi staff, and between existing contributors and new entrants under the new Social Insurance Law. Check that these groups can be configured, and confirm the rates on the GOSI website. See also payroll and GOSI.

3. Government platforms

The wage protection file is uploaded through the Compliance System on Mudad, and employment contracts are documented on Qiwa. Ask precisely: does the system produce reports that help your team with these steps, or does it claim a direct integration? If it claims integration, ask to see it working in the demo.

4. Flexibility without code

Policies change: a new allowance, an extra leave type, a different approval path for one branch. A good system lets your team make these changes in settings.

5. Data ownership and export

Ask where data is stored, who owns it, and how you get a full copy if you leave. Ask about permissions too: payroll data should be visible only to authorised users.

6. Support and training

Ask about support language and hours, who migrates data from Excel, and who trains your team.

Ready-made, custom, or inside an ERP?

  • Inside an ERP such as Odoo: a fit when accounting and inventory run on Odoo, keeping payroll and journal entries together. See Odoo for HR and Odoo services.
  • Custom system: a fit when your processes are specific and not covered by ready tools. See custom systems.
  • Ready HR product: a fit for standard processes. One example is Maham HR, a Maham Pro product under development, with a demo available on request.

Quick demo checklist

  1. Enter a sample employee with a real contract and allowances from your company.
  2. Run a month's pay that includes absence and overtime.
  3. Calculate the end-of-service award for a resignation after six years.
  4. Submit a leave request as an employee and approve it as a manager.
  5. Export employee data to a file.

If these steps are not easy in the demo, they will not be easier after go-live.

FAQ

How long does an HR system take to roll out?

It depends on the number of modules and the quality of your current data. Ask the vendor for a written, phased plan rather than a general figure.

Do I need an HR system with only a few employees?

Not always. If spreadsheets work for you without recurring errors, you can wait. Our article on when Excel stops being enough helps you judge the timing.

Next step

If you would like help writing requirements or comparing options, book a free 30-minute introductory session. Detailed analysis and an implementation roadmap are quoted separately; published packages are on the pricing page.