Naarvin reads each employee's monthly pay from Jisr's Open API into its payroll register: basic pay, housing, transport, overtime, other allowances, deductions and net pay. Nothing is read until someone with payroll access switches the payroll register on, a month imported from a file is never overwritten, and Naarvin never writes to Jisr.
What does Naarvin read from Jisr?
Two things: the employee list, active and inactive, and each employee's monthly payables. Your ERP holds payroll as a few journal lines; Jisr holds it per person. The connection brings that per-person detail into Naarvin's payroll register, next to the books of the same company.
| Payroll register field | From Jisr |
|---|---|
| Employee code and name | The employee list: code and full name, in English or else Arabic |
| Department, nationality, joining and leaving dates | The employee list, where Jisr sends them |
| Basic pay, housing, transport, overtime, GOSI employee share | The earnings, additions and deductions breakdowns of the monthly payables, recognised by name |
| Other allowances | Whatever is left of the earnings and additions totals |
| Deductions and net pay | The deductions total and the net salary |
When a month comes without a breakdown that names basic pay, its earnings are shown as other allowances and the sync counts how many employee months that affected. Check those before you rely on basic pay.
Why is payroll off until someone switches it on?
Salaries are the most sensitive figures a finance team holds. A new Jisr connection reads nothing: the payroll register is a dataset someone switches on from the connection card, and only a person who manages connections and may see payroll detail for the connection's company can do it. The change is written to the audit log.
Once loaded, the lines are visible only to people with payroll detail access for that company. Sync statistics count lines, and warnings name months, never people.
Which months are read, and how often?
The first sync reads the last 12 months, starting for each employee from the month they joined. Later syncs read again from the month before the last sync, so a late correction in Jisr is picked up. Jisr gives pay one employee and one month per request, so a sync makes at most 5,000 such requests and reads the latest months first; when that limit cuts months off, the sync says which months it read, and earlier months keep what was loaded before.
Payroll changes once a month, so a daily or weekly schedule is usually enough. Schedules run in your time zone, and anyone allowed to sync can run one by hand.
What happens to months we imported from a file?
They stay. Each month the connection reads replaces only what this connection loaded before. A month someone imported as a payroll file, or that another connection loaded, is kept as it is, and the sync warns with the month. If you remove the connection, the months it loaded go with it.
Which company and currency does it use?
One Jisr organization, named by its slug, links to one company in Naarvin, often a company your ERP connection already loads. You enter the payroll currency, such as SAR, and it must match the company's currency. A group with several Jisr organizations connects each one separately.
You also choose Jisr's hosting: the API specification's server, api.jisr.net for sites on .jisr.net, or api.jisr.net.sa for sites on Jisr's local hosting.
What does the connection not do?
- It never writes to Jisr.
- It does not read employees' bank accounts or IBANs, leave balances, or Jisr's pay-run transactions.
- It reads nothing if Jisr refuses access to monthly payables. The sync then says so: ask Jisr to enable that part of its API for your organization, or import the register as a file.
- It brings no ledger. Payroll journals and balances still come from your ERP.
How do you connect Jisr?
- Create the key in JisrA Jisr admin generates an API key and secret for your organization, with access to the employee list and the employee monthly payables.
- Add the connectionEnter the organization slug (the name before .jisr.net in your Jisr address), the hosting, the payroll currency and, optionally, the company name and country, then the key and secret. They are encrypted when saved and never shown again.
- Link the companyLink the Jisr organization to its company in Naarvin. The currencies must match.
- Switch on the payroll registerFrom the connection card. This needs someone who manages connections and may see payroll detail for that company.
- Run the first sync and compare a monthCompare one month's totals with Jisr's own payroll report, and read the warnings before the register is used.
Questions people ask
Who in Naarvin can see salaries from Jisr?
Only people with payroll detail access for that company. Sync statistics count lines, and warnings name months, never people.
Will the connection overwrite a payroll month we imported from a file?
No. A month imported from a file, or loaded by another connection, is kept, and the sync warns with the month.
Why did a sync read fewer than 12 months?
Jisr gives pay one employee and month per request, and a sync makes at most 5,000 requests, latest months first. The sync says which months it read; earlier months keep what was loaded before.
Does Naarvin read bank account details from Jisr?
No. Bank accounts and IBANs are deliberately not read.
Official and primary sources, read on the date shown. Rules change: confirm with the authority or your adviser before you act.
- Jisr: Open API specification (servers and authentication) (read 9 October 2026)