What is an HRIS?

An HRIS brings employee data and HR processes together in one place: records, contracts, time, absence, payroll, recruitment. This guide explains what the term covers, how it differs from an HRMS or an HCM, and what changes in practice when you operate across France and Switzerland.

Definition: what is an HRIS?

The French equivalent is SIRH, for Système d’Information des Ressources Humaines. You will also come across HRIM or SIGRH in some markets; the distinctions are terminological rather than functional.

The key word in the definition is centralises. What defines an HRIS is not any single feature: it is that a piece of data entered once — a change of address, a new hire, a change in working rate — propagates to every process that depends on it, with no re-keying. A tool that handles leave beautifully but ignores the employee record is not an HRIS: it is a leave management tool.

This is also why the question “do we need an HRIS?” is rarely asked in those terms. It arrives in another form: three spreadsheets that no longer agree, a holiday balance nobody can recompute, an onboarding process that depends on one person being at their desk.

The five core modules of an HRIS

Scopes vary between vendors, but five building blocks structure almost every solution on the market.

Around these five sit cross-cutting functions that matter just as much: approval workflows, roles and permissions, employee self-service, notifications, and the APIs that connect the HRIS to the rest of your systems.

HRIS, HRMS, HCM, payroll software: the table that clarifies

The acronyms overlap heavily and vendors use them loosely. Here are the distinctions as they are generally understood.

Why not a spreadsheet? Why not the ERP?

The spreadsheet

Excel works remarkably well up to a point — often around twenty to thirty employees, sometimes more. What breaks it is almost never volume: it is concurrency. Several people edit the same file, several versions circulate, and nobody knows which one is authoritative.

Three structural limits follow. A spreadsheet does not keep history: change a salary and the previous value disappears, whereas employment law assumes you can establish what was true on a given date. It does not handle row-level access rights: who is allowed to see which salary? And it records nothing: in an audit, you cannot prove who changed what, or when.

The ERP

Many ERPs ship an HR module. It is usually adequate on administration and payroll, and noticeably weaker on what makes up the HR day-to-day: employee experience, approval workflows, internal mobility, recruitment. The question to ask your ERP vendor is not “do you have an HR module?” — the answer is yes — but “how many of your customers actually use it to manage absence day to day?”.

What an HRIS actually does for you

Vendor-stated benefits all sound alike. Here are the ones that hold up, and how to verify them in your own organisation.

Eliminate re-keying

The most immediate gain, and the easiest to measure. Count how many times the same piece of information — a new hire, a change in working rate — is entered today across your organisation. Three times is not unusual. Every re-entry is an opportunity for error.

Make your data defensible

A serious HRIS keeps effective-dated history and logs access. In a dispute, an inspection or an audit, the difference between “we believe that” and “here is the state of the record on 12 March, and who changed it” is considerable.

Shift administrative work to self-service

Leave requests, certificates, address changes account for a significant share of HR time. Moving them to self-service does not remove the work: it moves it to whoever holds the information.

Make steering possible

Without a single system of record, producing a reliable absenteeism rate takes days. With one, it is a screen. The real benefit is not the dashboard: it is that people start asking questions, because answering them no longer costs anything.

Types of HRIS: SaaS, on-premise, ASP

Three deployment models still coexist, even though one of them dominates the market today.

In practice, virtually every project launched today is SaaS. The real question is therefore no longer “which deployment model?” but “in which country does the SaaS host my data, and with which sub-processors?” — which brings us back to GDPR and the Swiss FADP.

Is there such a thing as a free HRIS?

Yes, and the distinction is worth stating clearly, because “free” covers three different realities.

• Free trials — full access for a limited period, usually two to thirty days. Useful for testing, not for operating.
• Permanent free tiers — typically capped at a small headcount and a single module. They work for a very small organisation, but the move to a paid tier tends to arrive at the least convenient moment: once your data is already in.
• Open source — the software is free, the project is not. Hosting, configuration, upgrades and regulatory compliance remain yours, and that is where most of the real cost sits.

One thing to check systematically before committing to a free offer: reversibility. A complete export of your data, history included, is the only guarantee that matters the day you move on.

HRIS in France and Switzerland: what international guides leave out

Most definitions available online are translations of Anglo-American content. They describe a generic HRIS that ignores what, in practice, decides whether a project succeeds on this side of the Atlantic.

Data protection: GDPR and the Swiss FADP

An HRIS processes personal data by nature, and often sensitive data — health, sickness absence, family situation. In France and across the European Union, the GDPR requires a legal basis, defined retention periods and sub-processors governed by Article 28. In Switzerland, the revised FADP, in force since September 2023, pursues the same goals with its own requirements.

Three questions to put to any vendor: where the data is hosted, who the sub-processors are, and which retention periods are configurable. We publish our answers on our Sub-processors and Data Governance & Security pages.

Payroll: two different worlds

France has the DSN, a unified monthly filing that structures the entire payroll calendar. Switzerland has AVS/AHV, LPP/BVG, LAA/UVG, withholding tax, and above all rules that vary from canton to canton. An HRIS designed for one of these two countries rarely transfers to the other without substantial rework.

Cross-border workers and multi-country

This is the most commonly underestimated case. An employee living in France and working in Geneva falls under social security, tax and remote-work rules that cannot be modelled by a “country” field on a record. If this applies to you, test it in the demo before anything else: it is where most solutions give way.

Languages and multi-entity

A company in French-speaking Switzerland routinely works in French, German and English. A growing SME opens a subsidiary before it has a structured HR function. Multi-entity and multilingual support are not comfort options: they are prerequisites worth checking early.

For a market overview on this side, see our HRIS Panorama France–Switzerland.

How to choose: seven questions to ask

1. Which processes must I cover within twelve months? Not within five years. A realistic scope avoids paying for modules that will never be switched on.
2. Who will enter the data day to day? If the answer is “HR”, the benefit will be limited. If it is “employees and managers”, usability becomes the deciding criterion.
3. What happens if we leave? Ask to see a real export, not a contractual promise. Reversibility is verified before signing, never after.
4. Where is the data, and with which sub-processors? Ask for the list in writing. A vendor who does not publish it is already telling you something.
5. Which local rules are covered natively? Swiss cantons, collective agreements, cross-border workers. “Configurable” often means “your problem”.
6. What is the total cost over three years? Licences, implementation, data migration, training, add-on modules, support. The advertised per-employee price tells only part of the story.
7. Who runs the project on our side? An HRIS project rarely fails on technology. It fails when nobody has the time to carry it internally.

Our comparisons put Illizeo side by side with the main solutions on the market.

What an HRIS costs

The dominant model is a per-employee, per-month subscription with volume tiers. Market spreads are considerable, and the ranges published online are unreliable because they compare different scopes.

What matters more than the headline price: the line items that do not appear on the first page of the quote.

• Implementation and data migration — often the first real expense, sometimes equivalent to a year of subscription.
• Add-on modules — check what is in the base package and what is billed separately.
• Interfaces — every connection to accounting, outsourced payroll or your directory has a cost.
• Support and upgrades — included, or optional?
• Commitment — minimum term, exit conditions, annual uplift.

Our pricing is public: see the Pricing page.

How an HRIS project unfolds

For an SME with a reasonable scope, allow six to sixteen weeks between signature and go-live. The stages are fairly stable from one project to the next.

1. Scoping — perimeter, entities, business rules, roles and permissions.
2. Data migration — the longest and most underestimated stage. The quality of your current data determines the duration.
3. Configuration — absence balances, approval workflows, document templates.
4. Testing — on real cases, including the awkward ones: irregular part-time, mid-month joiner, cross-border worker.
5. Go-live and adoption — training, internal communication, temporary dual entry if needed.

Frequently asked questions