Will staff in Damascus lower your Nitaqat ratio, or can they count as Saudization? Neither. From 15 April 2026 the ratio is calculated from Qiwa contracts, and a Syrian payroll is not one of them.

The question HR leads bring is about Nitaqat and employees outside Saudi Arabia. They want capacity in Damascus and a safe band at home. The ministry’s own remote-work service does not answer it. The worker must be a Saudi national, registered with social insurance as a remote worker, aged 18 to 60. A person employed in Syria fails the nationality line before age or insurance is even discussed.

Remotya’s recommendation is two ledgers, not one blended headcount. Saudi contracts stay on Qiwa, documented, so the Saudis who should count do count. Staff in Damascus are employed by our Syrian entity. You direct the work. We handle the contract, payroll, compliance, workspace and IT. The line is HR services. They are not a substitute for a Saudi hire, and they are not a penalty against one.

Nitaqat counts Qiwa contracts from 15 April 2026

Put a date on the board note. From 15 April 2026, Nitaqat Saudization rates are calculated from employment contracts documented on Qiwa. Documenting a Saudi employee’s contract is required for that employee to count.

Read the second sentence alone. A Saudi employee who is real, paid and in the building can still be invisible to the ratio if the contract is not on Qiwa. The calculation follows the file, not the org chart in the slide.

A developer on Remotya’s payroll in Damascus never enters that file. There is no Qiwa contract, because there is no Saudi employment. Typing the name into a spreadsheet beside your Riyadh team does not add a Saudi. It does not remove one either. The ratio cannot see a contract that was never a Saudi contract.

HR leads say the fear in one line. If the Syria team grows, the Saudi percentage falls. It falls when the denominator is a headcount you invented, mixing Kingdom employees with people who work for a Syrian employer. Nitaqat does not use that denominator. It uses documented contracts on Qiwa. Growth in Damascus does not dilute a ratio that never included Damascus.

If the Saudi percentage looks wrong, open Qiwa before you open a map. The miss is often an undocumented Saudi contract, not a hire in Syria. From 15 April 2026 that miss matters, because the rate is calculated from the documented file. A missing upload in Riyadh moves the band. A salary paid in Damascus does not.

The ministry stated the change in its own news: documenting the contract is what makes the Saudi employee count. Send that page to whoever still builds the ratio from a payroll export. MHRSD on electronic documentation of employment contracts is the source for the 15 April 2026 switch.

The remote-work service is for Saudis aged 18 to 60

MHRSD runs a remote-work contract service. The English name is where the mix-up starts. Remote does not mean anywhere, and it does not mean any nationality. The worker must be a Saudi national, registered with social insurance as a remote worker, aged 18 to 60.

Each condition is a gate. Nationality is Saudi. Registration is social insurance, and it is registration as a remote worker, not some nearby category you hope is close enough. Age is 18 to 60. A Saudi hire outside that age band is outside the service. A Syrian national is outside it at 30 with a laptop, and at 45 with a decade of Gulf experience. The years abroad do not convert the nationality test.

That service is how a Saudi employee can work remotely and remain inside the Saudi system. It is the opposite of a door for parking a Damascus team on your commercial registration. People reach for it because the product name sounds like the thing they want to buy. The ministry wrote the eligibility in one place. Nationality is the first test. The remote-work contract service says so on the service page itself.

So the plan to register Syria staff as remote workers and protect Nitaqat does not have a door. Remotya will not pretend one exists. We employ those people in Syria, under our entity. Your Qiwa file stays a Saudi file. If you also employ Saudis who work remotely inside the Kingdom, that is the service’s actual subject. It belongs to your Saudi HR process. It is not a Syrian contract with a new label on the folder.

Age is the condition founders skip. A Saudi remote worker at 17 is out. A Saudi remote worker at 61 is out. The band in the ministry text is 18 to 60. Do not round it, and do not borrow it for a non-Saudi. The number is an eligibility rule for one service, not a general definition of remote work.

A yellow or red band restricts Saudi visas

A yellow or red Nitaqat band restricts new work visas and renewals of existing ones. The pain sits inside the Saudi visa system. New visas. Renewals of visas you already hold. A person who never applied for a Saudi work visa is not the person that sentence constrains.

A hire in Damascus does not repair a yellow band or a red one. If you cannot renew a visa for a technician in Dammam, employing an engineer in Syria does not restore that renewal. The restriction is on the visas. The fix for the band is the Qiwa file: document the Saudi contracts so the employees who should count are in the calculation. From 15 April 2026 an undocumented Saudi contract is a Saudi the ratio cannot see. A weak file is how companies slide into the bands that block visas.

We say this because the shortcut is attractive. A founder in the yellow band looks at Damascus as a way to keep shipping while Saudi visas are stuck. Keep shipping if the work belongs there. Do not tell the board the foreign team will lift the band. It will not. The band is a Saudi documentation and hiring problem. The Syria team can still be the right capacity decision. It is a bad visa strategy.

Keep two ledgers. Ledger one is Saudi nationals on Qiwa. That ledger is your Nitaqat problem, owned by whoever runs Saudi HR. Ledger two is staff in Syria, legally employed by Remotya’s Syrian entity, paid on a local payroll, directed by you. Mixing the ledgers is how a board pack reports a number the ministry will not confirm.

The visa consequence is set out in a Q1 2026 note on Saudi employment law: a yellow or red Nitaqat band restricts new work visas and renewals of existing ones. Use the ministry for the calculation rule. Use that note for what the band does to visas. Neither source turns a Damascus payroll into a Saudi contract.

Keep Damascus off the Saudization slide

Hire in Damascus when the role fits a Syrian contract and you do not want a local branch. Do not hire in Damascus to decorate a Nitaqat ratio. The ratio will ignore the hire. You will have built a story your auditor cannot sign.

What we recommend is plain. Keep hiring Saudis, and document every Saudi contract on Qiwa, for the band you need in the Kingdom. Use Remotya when the role can sit in Syria under our entity. You direct the work. The employment, the payroll and the labour-law contract stay with us. Payroll accuracy on our run is 99.5%. We do not publish a fee. Commercial terms follow a discovery call.

Two neighbouring worries belong in other pages. If the question is whether the 1 July 2025 sanctions change blocks the hire itself, read what changed in Syria sanctions. If the question is who the employer is once you are directing the work, the model is an employer of record. Saudization is not either of those pages. It is Qiwa, Saudi nationals, and a band that can stop a visa.

This is general information, not legal advice.

Book a discovery call if you want the Syria ledger run as employment, payroll and compliance, while your Saudi HR keeps Qiwa as a Saudi file. We will say which people sit on which contract. We will not move a Damascus name onto your Saudization slide.

Sources

Questions readers ask

Do employees in Damascus count in Nitaqat?

No. From 15 April 2026, Nitaqat Saudization rates are calculated from employment contracts documented on Qiwa. A Syrian payroll is not a Qiwa contract, so it does not enter the ratio.

Can I register a Syrian hire on the remote-work service?

No. MHRSD's remote-work contract service requires a Saudi national, registered with social insurance as a remote worker, aged 18 to 60. A Syrian national employed in Damascus is outside that service.

What does a yellow or red Nitaqat band restrict?

A yellow or red Nitaqat band restricts new work visas and renewals of existing ones. A Damascus hire does not lift that restriction. Documenting Saudi contracts on Qiwa is what lets those employees count.

Will a Syria team lower my Saudi percentage?

Only if you mix two ledgers. Nitaqat uses documented Qiwa contracts. Staff employed by a Syrian entity are not in that denominator. An undocumented Saudi contract can hurt the ratio. A Damascus payroll does not.

Is this legal advice on Saudization?

No. This is general information, not legal advice. Your Saudi HR file and the ministry's Qiwa record are the ones that decide the band.