KayanHR is a regional HR and payroll platform, and regional is the interesting word: for a Saudi employer the decision usually turns less on features than on how the statutory side is handled and who is accountable when it changes. We test that before anyone signs, and we earn nothing different depending on the answer. It sits in our HR and payroll systems category alongside everything it is usually weighed against.
It fits organisations whose requirement is a dedicated HR and payroll platform rather than an HR module inside an ERP they have not bought yet. It fits employers with a mixed workforce across more than one country, where a single payroll engine that can carry several salary structures is worth more than depth in any one of them. It fits teams that want employee self-service and time capture to be part of the same system as the payroll run. And it fits where the statutory questions in section 3 can be settled in writing before contract.
We do not recommend it when the organisation is already committed to an ERP whose HR and payroll modules are in scope — running two systems that both think they own the employee record is a reconciliation problem you will pay for monthly. We do not recommend it where the statutory handling cannot be confirmed in writing, for the reason set out in section 3; that is a contracting condition, not a preference. And we are cautious where the real problem is process rather than software: a platform will not fix an approval chain nobody agrees on. In those cases we say so, and an impartial assessment is where that conversation starts.
We restrict this section to what KayanHR publishes. Its payroll module is headed multi-country payroll and describes automatically calculating accrued vacations, sick and owed time, embracing diverse salary structures and labor law regulations, building multiple tax profiles and social security rules, and handling all financial transactions. Its self-service module describes a portal that gives employees the ability to interact with each other and carry out their transactions. Its time and attendance module is an online punch clock that tracks employees time no matter where they are working. The company positions itself around making employee management easier and simpler for companies big or small. Read the payroll wording carefully: it is written in the language of many jurisdictions, and the vendor's own English product pages we reviewed name none of them — which is the subject of the next section.
The first limitation is the one section 3 sets out: the statutory handling that decides this purchase in Saudi Arabia is not something we found published, so it has to be established rather than assumed. The second is overlap — if an ERP is anywhere on your roadmap, its HR and payroll modules will overlap this platform, and deciding which system owns the employee record afterwards is much more expensive than deciding it now. The third is that a payroll engine built to be portable across jurisdictions carries configuration where a single-country product carries defaults, and configuration is where implementations run long. Budget for the configuration, not for the licence.
This is the section that decides the KayanHR question, and it is a section of questions rather than answers. GOSI contributions, Wage Protection System file submission and Nitaqat classification all have to work correctly from the first payroll run, and an error in any of them is visible to the employee and to the regulator in the same month. We looked for a published position: the vendor's own English product pages we reviewed name no jurisdiction at all, so we assert nothing about how this platform handles GOSI, WPS or Nitaqat, in either direction — not that it does, and not that it does not. What we do instead is put each obligation to the vendor in writing, with you, and require the answer in the contract rather than in a demonstration. Arabic-language documents and right-to-left output get tested rather than assumed, and VAT at 15% is settled wherever payroll touches the ledger. For a sector view, see IT services.
We publish no licence prices; they vary by headcount, module and agreement. What we build with you is the three-year picture — subscription, implementation, the configuration work the statutory answers turn out to require, migration of employee and historic payroll data, integration to finance and to time capture, training, and the internal capacity you will divert. On an HR platform the data migration is usually underestimated, because employee history is messier than anyone remembers until it is exported.
The comparisons we publish are at independent software comparisons. The deciding factors here are usually the statutory position, whether an ERP is already on the roadmap, how many countries the payroll has to cover, and whether the organisation wants HR and payroll in one system or is willing to run two and reconcile. If an ERP is coming anyway, the honest comparison is against its own HR and payroll modules — Oracle NetSuite ERP is a common version of that question in this market.
We start from your workforce rather than from a feature list: headcount and its shape, how many countries and contract types, what the payroll calendar has to survive, and which approvals actually exist versus which are described. Candidates are scored against criteria agreed with you before any vendor conversation, and the scoring is written down so your own people can challenge it.
We inventory every interface the platform will have to carry — the finance ledger, time capture devices, banking for salary transfer, and whatever holds the employee record today — decide which survive and which retire, and design the integration layer before configuration begins. The finance interface is the one that decides whether month-end is calm.
Training is planned by role and by process rather than by module, and it starts before cutover. Payroll is judged on its first live run and forgiven for nothing, so that run happens in parallel with the old process and with our people on call.
We publish no percentages and no counters on this page. What we will say about outcomes is structural: the HR implementations that go well are the ones where the statutory answers were in the contract before configuration started and where the first payroll ran in parallel rather than as a cutover. Ask us for references in your sector and we will arrange direct conversations.
We do not quote a standard duration. The timeline is set by headcount and contract variety, how clean the employee data is, the number of interfaces, and how much configuration the statutory answers turn out to require. We size it during the assessment with the assumptions written down so you can challenge them.
Subscription, implementation and configuration, employee and historic payroll data migration, integration to finance and time capture, training, and the internal time you divert. We model it with your figures rather than publishing a range, because a range not built on your workforce is a guess wearing a number.
We do not answer this generically, and on this platform we are being deliberately careful: we found no published vendor position on GOSI, WPS or Nitaqat handling, so we neither confirm nor deny it. We put each obligation to the vendor in writing with you, require the answer as a contractual term, and verify the configuration against it before the first live payroll rather than after.
Typically another regional HR and payroll platform, a global one with a local partner, and — where an ERP is already on the roadmap — that ERP's own HR and payroll modules. The evaluation and its scoring are part of the deliverable, so you can see what was considered and why it lost.
Usually yes, and the interfaces that matter are the finance ledger, time capture and banking. The question is which of them is standard, which is a project, and who maintains each when something upstream changes. We audit that dependency chain as part of the assessment.
There are none, and the heading deserves a straight answer rather than a filled one. We publish no counters, no project totals and no percentages, because an advisor's numbers cannot be checked by the reader who most needs to check them. What we will state about our own work is checkable: we take no vendor commission, we do not bid for the implementations we scope, we score candidates against criteria agreed with you before any demonstration, and we hand over the written evaluation whether or not you engage us further.
We name clients only with their consent, and in direct conversations rather than on a product page. References from Saudi employers of comparable size and workforce shape are available on request.
Every engagement ends in a written, evidenced recommendation: the workforce analysis, the statutory questions and the vendor's written answers to them, the integration map and the cost model. The deliverable is yours regardless of who implements, and it is the thing worth judging us on.
We do not publish testimonial quotes on this page. Speak to our references directly; an unmediated conversation with an HR director who has been through a payroll cutover tells you more than a curated pull-quote ever will.
We publish no partner claims on this platform. We hold no reseller position and no vendor designation, and we list technical partnerships only where they are contractual — none of which binds the advice given here. That is a deliberate position rather than a gap: an advisor whose recommendation is backed by a vendor relationship is not giving you the same thing, and on a purchase that turns on the vendor's own statutory answers it would be the worst possible place to have one.
Continue with our HR and payroll systems category, our consulting services, or IT services if that is your sector.
If KayanHR is on your shortlist, or a partner has already quoted you for it, book an evaluation before you negotiate. You will leave with a fit verdict, the statutory questions written out ready to put to the vendor as contractual terms, an integration map and a cost model. Request a demo or ask for an impartial assessment.
Unlimited support included.
One-on-one onboarding sessions.
Training videos, webinars, & demos.