RoleAxis
AgentsHR and payrollLive

HR & Payroll Agent

Catches what is wrong in an employee's file, documents or payment details before a regulator, a bank or an unpaid employee makes it obvious.

The problem it addresses

An expired iqama turns up as a rejected transaction. A wrong bank detail turns up as an employee who was not paid. Both were knowable weeks earlier from data the business already had, and nobody had time to look.

Reports to
HR / payroll administrator
Reads
Employee files, Contracts, Document expiries

What changes for the team

  1. Renewals started in time

    documents expiring inside sixty days are raised while there is still room to act.

  2. A salary run that does not fail on the day

    employees with no bank account, no running contract or a zero wage are found before the run, not during it.

  3. Duplicated employee records surfaced

    two employees sharing one bank account is confirmed once by a person, rather than being noticed after a second payment.

  4. The end-of-service liability visible monthly and per employee, with its assumptions attached, instead of estimated once a year

It drafts. A person decides. Some things are never drafted.

What lands in your queue

  • A document expiry flag per document, with the date and days remaining
  • A payroll exception flag per employee, naming which of the four problems it is
  • An indicative end-of-service provision per employee, with its caveats attached
  • The observed Saudization ratio, as a number and nothing more

Under a person's approval

  • It cannot pay a salary, change a salary, or change an employee's bank details. These are blocked at the platform level for every agent: there is no draft, no approval path and no tool, because one wrong approval click is too small a gap between an agent and someone's salary.
  • Every finding waits for your payroll administrator, and they make each change in the HR system themselves.
  • It never sees a bank account number. Accounts are masked before they reach the agent, so a duplicate is found by fingerprint and reported as the last four digits.

It cannot

  • Pay a salary or change a salary
  • Change an employee's bank details
  • Claim compliance with any regulation
  • State an end-of-service figure as an entitlement

How approvals, owner sign-off and the blocked list work: security and control.

The skills, one check or draft each

Executes on approval means approving the draft writes to your system. Recommends means the approval records the decision and your team makes the change. Planned is not built.

  • Contract, iqama & permit expiryIqamas, visas and work permits expiring inside sixty days, or already expired, with the date and days remaining. Documents comfortably in date return nothing, so what you get is a renewal list rather than a roster. A field the connection cannot read is reported as unreadable, never as missing or expired.Recommends
  • Payroll-file validationThe four things that make a salary run fail: no bank account, an account shared with another employee, an active employee with no running contract, and a zero or negative wage. A shared account is presented as worth confirming once, never as fraud: it is legitimate within a family, and it is also what a duplicated record looks like. This validates the payroll data a run is built from, which is a narrower claim than validating a submitted WPS file.Recommends
  • End-of-service accrualsAn indicative provision per employee on the end-of-contract basis, with its assumptions attached every time: a resignation carries a different and lower statutory scale, the wage base is the contract's gross rather than the last wage including qualifying allowances, and unpaid leave is not deducted. No approval and no draft, on purpose: an approval record stating a person's figure would read as an entitlement, and this is not one.Recommends
  • GOSI contribution checkContributions recomputed from payroll and any shortfall named. Not built: payroll is not part of the accounting system's community edition, so a business may have no payslip data at all, and we have not verified that data's shape. The agent is forbidden from stating any contribution figure rather than estimating one from a contract wage.Planned
  • Nitaqat band alertA warning before a hire or an exit moves the band. Not built: the band thresholds depend on a business's sector and size against a government-set scale that no integration supplies. The ratio can be counted and is reported as a plain observation; the band is never named.Planned
One finding, start to finishExample

A work permit expiring in 25 days, two employees sharing one bank account, and an active employee with no running contract.

Agent draftedExecuted

No amount:

three data problems, each one enough to cost a fine or a failed payment

Decision
The payroll administrator starts the renewal, confirms the shared account is a family arrangement, and issues the missing contract
Result
Three recommendations recorded with their evidence; every change made by a person in the HR system

See what it finds in your data.

Free to start, no card. Which systems it can read is on the connectors page.

Start free