Sponsorship Transfer (Naql Kafala) and What It Does to Payroll Continuity

A single sponsorship change can quietly disrupt weeks of payroll planning if HR and finance aren’t reading from the same file. Accounting Services KSA has walked enough clients through this to know that the biggest risk isn’t the transfer itself; it’s the payroll gap that opens up around it. This guide breaks down exactly how naql kafala payroll handling works, step by step, and where most teams lose control of the timeline.

What Is Naql Kafala, Exactly?

Naql Kafala refers to the transfer of an employee’s sponsorship from one employer to another within Saudi Arabia, typically processed through the Ministry of Human Resources and Social Development (Qiwa) and Absher platforms. It’s distinct from hiring a new employee from abroad, since the worker is already inside the country and simply moving employer of record.

For HR teams, the process feels administrative. For payroll teams, it’s anything but because the moment sponsorship shifts, so does the legal employer responsible for wages, GOSI contributions, and end-of-service liability.

Getting naql kafala payroll handling right isn’t just about avoiding fines it’s about making sure the employee’s salary, benefits, and end-of-service record survive the transfer without a break in continuity. That’s the piece most guides skip over.

The Naql Kafala Process, Step by Step

1. Mutual agreement stage: the releasing and receiving employers confirm terms, including any outstanding dues owed to the employee.
2. Platform submission: the transfer request is filed through Qiwa/Absher, along with contract and Iqama details.
3. Approval and Iqama update: once approved, the employee’s Iqama reflects the new sponsor.
4. GOSI re-registration: the employee must be re-registered under the new employer’s GOSI account.
5. Payroll system cutover: the receiving company activates the employee in its own payroll and benefits systems.

Each step in the naql kafala process has its own processing time, and delays at any single stage can push the payroll cutover later than either employer originally planned.

Companies that treat each step as a checklist item rather than a single administrative task tend to catch problems earlier. For example, confirming GOSI eligibility before submitting the platform request can prevent a rejected application that would otherwise delay the entire naql kafala payroll timeline by another cycle.

Why Payroll Continuity Breaks Down Mid-Transfer

Here’s the practical problem: payroll doesn’t pause just because a sponsorship is mid-transfer. Salaries are still due on schedule, and both employers have obligations that don’t automatically sync with the administrative approval timeline.

This is where naql kafala payroll issues tend to surface: an employee is technically still under the old sponsor’s GOSI record but already working under the new employer’s supervision, with neither system fully reflecting the reality on the ground. If this overlap isn’t managed deliberately, it creates gaps in wage protection system (WPS) reporting and can flag compliance issues with the Ministry.

The safest approach is to treat the transfer window as its own mini payroll cycle, with both employers checking in against the same timeline rather than assuming the other side has it covered. Teams that skip this coordination step are usually the ones that discover a naql kafala payroll gap only after WPS flags it, which is a much harder position to correct from.

Sponsorship Transfer Payroll: Who Pays During the Gap?

Sponsorship transfer payroll responsibility during the transition period is a question that catches many companies off guard. Generally, the releasing employer remains responsible for wages and dues up until the official transfer date, while the receiving employer’s obligation begins once the sponsorship officially moves.

The complication is that “official transfer date” isn’t always crystal clear in practice, especially when platform approvals lag behind the agreed start date between employer and employee. A written agreement specifying the exact cutover date protects both employers and the employee from disputes later.

Kafala Transfer Employee Rights and Employer Obligations

From the employee’s side, a kafala transfer employee situation comes with protections worth knowing. End-of-service benefits accrued under the previous employer don’t simply disappear; they’re typically settled as part of the release agreement, either paid out or, in some arrangements, carried forward by mutual consent between employers.

Employees moving through this process should confirm in writing how their accrued leave, end-of-service gratuity, and any pending reimbursements will be handled before the transfer date is finalized. Ambiguity here is one of the most common sources of post-transfer disputes.

It’s also worth noting that a kafala transfer employee retains the same labor law protections throughout the process; the transfer changes the sponsor of record, not the employee’s underlying rights under Saudi labor regulations. Employers who frame the transfer conversation around this fact tend to see smoother, less anxious handoffs from the employee’s side.

Naql Kafala Accounting: Recording the Transition Correctly

On the finance side, naql kafala accounting requires closing out the employee’s liability on the releasing employer’s books, including accrued leave and end-of-service provisions, while the receiving employer opens a fresh liability record starting from the transfer date.

Skipping this clean handoff is a common source of duplicated or understated end-of-service liability, especially when the same employee’s history isn’t clearly documented across both employers’ books. A short handover memo between the two finance teams, even informally, tends to prevent most of these errors.

Getting naql kafala accounting right also matters for audit purposes down the line, since auditors reviewing either employer’s payroll file will expect to see a clean break in liability rather than overlapping or missing records around the transfer date.

Practical Steps to Protect Payroll Continuity

• Confirm the exact cutover date in writing before submitting the transfer request
• Reconcile GOSI records the same week the Iqama updates
• Run a parallel payroll check during the first cycle after transfer to catch missed enrollments
• Keep a shared handover note between releasing and receiving HR/finance teams
• Document accrued leave and end-of-service calculations before the release is finalized

Following this sequence closely tends to prevent the wage protection system flags that catch companies off guard weeks after a transfer is technically complete. It also gives both employers a clear paper trail if the employee, the Ministry, or an auditor ever asks how the naql kafala payroll handoff was managed.

Smaller companies without a dedicated payroll function often find this the hardest part to manage internally, simply because the person handling HR paperwork isn’t always the same person tracking GOSI contributions and payroll cutoffs. Building a simple shared checklist between the two roles, even a one-page document, closes most of the gap that causes compliance issues later.

Bringing It All Together

Sponsorship transfers are routine in Saudi Arabia’s labor market, but the payroll side of naql kafala payroll management deserves more attention than it typically gets. A clean handoff between releasing and receiving employers protects the employee, avoids compliance flags, and keeps end-of-service liability accurate on both sides of the transfer. If your team needs a second set of eyes on a transfer that’s already in motion, Accounting Services KSA can help you close the gap before it becomes a bigger problem.

Frequently Asked Questions

How long does a naql kafala transfer typically take?

It varies by case, but platform approval combined with GOSI re-registration usually takes anywhere from a few days to a couple of weeks.

Who is responsible for the employee’s salary during the transfer period?

Generally, the releasing employer pays until the official transfer date, though this should always be confirmed in a written agreement.

Does end-of-service benefit reset after a sponsorship transfer?

Not automatically; it depends on the release agreement between employers, which should specify how accrued benefits are settled or carried forward.

Can a delayed GOSI update cause compliance issues?

Yes, a lag between the Iqama update and GOSI re-registration can create wage protection system mismatches that draw Ministry attention.

Should HR or finance lead the naql kafala process internally?

Both need to be involved from the start, since HR manages the administrative filing while finance manages the payroll and liability handoff. Treating naql kafala payroll coordination as a joint task from day one avoids most of the gaps described above.