Tawakkalna Still Shows Your Old Sponsor After a Qiwa Transfer? Here Is the Real Fix (2026)

Your new employer pushed the transfer through Qiwa. You confirmed it. The status says complete. And yet you open Tawakkalna Services (the app most people still call Tawakkalna) and it cheerfully shows the old sponsor. Worse, some of the services you rely on are greyed out or throwing errors, so it feels like you are locked out of your own life.

Here is the short answer before we go deep. Tawakkalna does not hold its own copy of your sponsor. It pulls that information from your residency (iqama) record through the government identity backbone. If the app shows the old sponsor in 2026, it is almost always one of three things: the transfer is not as finished as you think, the new iqama record has not propagated yet, or your app session is showing cached data and simply needs a fresh Nafath login. Most cases resolve on their own within roughly a day once the underlying record is truly updated.

This guide walks through how the data actually flows, how to tell which of the three causes is yours, the realistic fixes for each, and how long each one takes. It also gives you a worked example of a typical stuck transfer, a clear diagnosis decision table, and a ready-to-use list of exactly what to have in hand before you call a helpline so you are routed fast. Throughout, treat every timeline as indicative, not guaranteed - the official channels to confirm your specific case are Absher, the Ministry of Human Resources and Social Development (MHRSD) on 19911, and the Ministry of Interior helpline 989.

To fix a sync problem you have to understand what is talking to what. In 2026 the Saudi digital-government stack is tightly integrated, but each platform plays a very specific role:

• Qiwa (MHRSD) is the labour platform. This is where the employer-employee relationship and the work permit live, and where a sponsorship transfer (naqal kafala) is initiated and approved.
• Absher (Ministry of Interior) is the residency platform. Your iqama record - including the official sponsor name printed on the iqama - is held here. When a labour transfer is finalised, the change has to be reflected on the residency side before it is the legal source of truth.
• Nafath is the national digital-identity and login layer. When you log into Tawakkalna, you are authenticating through Nafath, which verifies you against the same central identity records.
• Tawakkalna Services (SDAIA) is the citizen and resident super-app. It is largely a display and access layer. It reads your civil and residency data and unlocks services based on what that data says. It does not independently decide who your sponsor is.

So the chain is: Qiwa approves the transfer, the residency record on the Absher/MOI side is updated and a new iqama is issued, and only then does Tawakkalna - reading through Nafath - have a new sponsor to show you. Tawakkalna is the last link in the chain, not the first. That single fact explains almost every "my app is wrong" complaint after a transfer.

It helps to picture each platform as a separate department in the same building rather than one big computer. The labour department (Qiwa) signs off on the new employment relationship. The residency department (Absher/MOI) is the one that actually re-stamps your iqama with the new sponsor and is the legal record everyone else trusts. The identity desk (Nafath) checks who you are every time you walk up to a counter. And Tawakkalna is the lobby screen that simply mirrors whatever the residency department has on file. When the lobby screen is wrong, the question is never "how do I edit the lobby screen" - it is "which department upstream has not finished its part."

Because the names blur together, here is each platform mapped to its owner, its role, and where in the chain it sits. Keeping this straight is the difference between fixing the right thing and refreshing the wrong app for days. Treat it as orientation; confirm anything specific to your case directly with the relevant authority.

The practical rule that falls out of this table: a sponsor problem is almost always solved on the Qiwa or Absher side, not inside Tawakkalna. Tawakkalna can only show you what Absher already holds. If you remember nothing else, remember that the app is a mirror, and you cannot fix a reflection by polishing the mirror.

People expect these systems to update in real time because they are all part of "the same government." In practice the platforms are separate systems that exchange data on their own rhythm. A few realistic reasons your Tawakkalna lags behind:

• The transfer is approved in Qiwa but not finalised on the residency side. Labour approval and the issuance of a new iqama reflecting the new sponsor are not the same moment. Until the residency record flips, the legal sponsor is still the old one - and so is the app.
• Propagation delay. Even after the residency record updates, downstream apps refresh on a cycle rather than instantly. Civil-status changes commonly appear in Tawakkalna after a synchronisation window that is often within a day, but can vary.
• Cached session. Your app may be showing data captured at your last login. A new Nafath login forces it to re-read fresh data.
• An outstanding step on the employer side. If the new employer has not completed everything required to finalise the relationship, or there is an unresolved flag (for example a wage-protection or eligibility check), the record can sit in limbo.

It is worth naming the most common false assumption directly, because it sends people down the wrong path: people treat the green "completed" status in Qiwa as the finish line for everything. It is the finish line for the labour approval, not necessarily for the residency record. Those are two distinct milestones, and the gap between them is exactly where most "my app is stuck" cases live. A transfer can be genuinely, correctly approved in Qiwa while the new iqama has not yet been issued or printed, and during that gap Tawakkalna is not broken - it is faithfully showing the old sponsor because the old sponsor is, for the moment, still the legal one.

If you want to understand the upstream transfer mechanics in detail, our iqama transfer (naqal kafala) guide walks through every stage, and our piece on a Qiwa transfer rejected by the employer covers what happens when approval never actually lands.

Before you change anything, find out the truth of your record. Tawakkalna is the symptom, not the diagnosis. The authoritative place to check is your residency record itself.

• Open Absher and look at your iqama / digital ID details. Check the sponsor name field. If Absher shows the new sponsor, the record has updated and your problem is almost certainly a stale Tawakkalna session - jump to the re-login fix.
• If Absher still shows the old sponsor, the residency record has not flipped yet. Tawakkalna is correctly reflecting reality; the fix is upstream, not in the app.
• Check the transfer status in Qiwa or via MHRSD. Confirm the request shows as completed, not merely submitted or pending. If you cannot get into Absher to verify, our guide on checking iqama status without Absher shows alternative lookups.

This one comparison - what Absher says versus what Tawakkalna says - tells you whether you have an app problem or a record problem. They have completely different fixes. Do the comparison in this order every time: Qiwa status first (is the transfer actually completed?), then Absher (has the sponsor flipped on the legal record?), then Tawakkalna last (does the mirror match?). Reading them out of order is how people end up convinced the app is broken when the real blocker is a transfer that never finalised, or convinced the transfer failed when in fact only the app is lagging.

Use this table to convert what your three screens are showing into a clear next action. Read across the row that matches your situation. Every fix referenced here is detailed in the sections that follow, and every timeline is indicative and varies.

The pattern to internalise: when Absher is right and the app is wrong, the fix is fast and app-side. When Absher is wrong, the fix is slow and record-side. Diagnosing which row you are in before you act saves you days of refreshing an app that was never the problem.

Abstract steps are easier to follow with a concrete walk-through, so here is a representative scenario built entirely from the mechanics described in this guide. The names and exact days are illustrative; your own case will differ, and you should confirm the specifics on your own screens.

Imagine a worker whose new employer initiated the transfer in Qiwa, and the worker confirmed it. A few days later Qiwa shows the transfer as completed. The worker opens Tawakkalna expecting the new company name and instead sees the old sponsor, with one or two services greyed out. Panic sets in, and the instinct is to reinstall the app or ask the employer to "do the transfer again." Both of those are the wrong moves.

The correct first move is to diagnose, not to act. The worker opens Absher and checks the sponsor name on the iqama record. In this scenario, Absher still shows the old sponsor. That single observation reframes everything: the app is not broken, the residency record has simply not flipped yet, most likely because the new iqama still needs to be issued or a final step on the employer side is outstanding. There is nothing to fix inside Tawakkalna, because Tawakkalna is correctly mirroring a record that is, for now, still the old one.

So the worker takes a screenshot of the Absher record, notes the date, and contacts the new employer's HR or government-relations person with a precise question: is the transfer fully finalised on your side, and has the new iqama issuance been actioned? The employer checks their Qiwa establishment account, finds a pending finalisation step, and completes it. A day or so later, Absher flips to the new sponsor. Now - and only now - the worker does a clean Nafath re-login on Tawakkalna, force-closes and reopens the app, and the new sponsor appears with services restored.

The lesson the example is designed to teach: the worker who diagnoses first reaches the fix in two clean steps and avoids creating a duplicate-request conflict. The worker who panics and resubmits the transfer or reinstalls the app repeatedly typically adds days, because none of those actions touch the part of the chain that was actually behind. Same problem, very different timelines, decided entirely by whether you checked Absher before you acted.

If Absher already shows the new sponsor but Tawakkalna does not, you are looking at cached data. This is the easiest case and the one we see most often. Work through these in order:

• Fully log out of Tawakkalna, then log back in. Authentication runs through Nafath, which re-reads your identity record on login.
• Force-close the app (do not just minimise it) and reopen it, so it is not serving a screen it rendered earlier.
• Update the app from the store. An outdated build can mishandle refreshed data.
• Clear the app cache in your phone settings if a re-login alone does not do it, then log in again.
• Confirm your registered mobile number is current so you actually receive the OTP - login fails silently for many people purely because the SIM or number changed.

Do these in the order listed rather than jumping straight to the most drastic. A simple log-out and log-in solves a large share of cases on its own, because it forces a fresh Nafath read. Force-closing and updating handle the next slice. Clearing the cache is the heavier hammer and is rarely needed first, though it is harmless. The mobile-number check is the quiet one people skip: if your OTP never arrives, you may conclude the login failed when in fact you simply never completed it, and no amount of re-reading the record can help until you can actually authenticate.

If a clean re-login still shows the old sponsor while Absher shows the new one, give it the synchronisation window (often within about a day) and try once more before escalating. Persistent mismatch after that is worth reporting to Tawakkalna support directly.

If Absher shows the new sponsor but the apps simply have not caught up, the honest answer is that waiting is part of the fix. The systems reconcile on their own schedule. A reasonable expectation is that the change appears after the next sync window - often within a day - though this varies and there is no published guarantee.

While you wait, do not panic-submit duplicate requests or repeatedly re-initiate anything in Qiwa - duplicate or conflicting requests can slow things down. Instead:

• Keep a screenshot of your Absher record showing the new sponsor, in case you need to prove status to a service provider in the meantime.
• Note the date the residency record changed, so you can measure the lag accurately if you later need to escalate.
• Re-check once per day rather than once per hour. Constant logins do not speed up a server-side cycle.

It helps to set the right expectation with yourself and with anyone depending on you, such as a landlord or a bank that keys off your active sponsor. The change is coming because the legal record is already correct; you are waiting on plumbing, not on a decision. That distinction matters psychologically and practically: there is no application to chase and no officer to persuade during this window, only a sync cycle to let run. The screenshot of the correct Absher record is your bridge - if a service provider needs proof of your current status before the app catches up, the Absher record is the authoritative document, not the lagging app.

If your iqama is also near its expiry, do not let the transfer noise distract you from renewal - a lapsed iqama causes far bigger problems than a lagging app. See our complete iqama renewal guide to keep that on track.

If Absher itself still shows the old sponsor, the residency record has not been updated, and that is the real blocker. A few things to check and do:

• Verify your Absher account is active and fully registered. A half-set-up or unverified account can show stale data and block the very services you need. If you are not sure yours is complete, our Absher registration guide walks through getting it fully activated.
• Look for any pending action on your side in Absher or Qiwa - an unconfirmed step, an unread notification, or a required acknowledgement can hold the whole chain.
• Check whether a new iqama needs to be issued or printed. In some transfers the record only finalises once the new iqama is produced; until then the old sponsor legitimately remains.

The most overlooked item on that list is the new-iqama step. People assume the sponsor name on the residency record updates the instant labour approval lands, but in some transfers the record only carries the new sponsor once the new iqama is actually issued or printed. If that step is outstanding, Absher will keep showing the old sponsor and there is nothing wrong - the chain is simply waiting on a document. This is precisely why it can be the employer, not you, who has to act, because the issuance step often sits on the establishment side.

Absher is the source of truth on the residency side, so getting it right there is what eventually pushes the correct data down to Tawakkalna. If Absher is clean and current but the app is wrong, you are back to Fix A or Fix B. If Absher is wrong, the problem is upstream and you need the employer or MHRSD.

A surprising share of "stuck" transfers are stuck because the new employer has not completed their final steps. Qiwa approval is not always the finish line - the establishment may still need to complete formalities that trigger the residency-side update. The employee often cannot do this part at all.

Contact your new employer's government-relations or HR person and ask them, specifically, to confirm the transfer is fully finalised on their side and that any new iqama issuance has been actioned. Vague reassurance is not enough; ask them to check the actual status in their Qiwa establishment account. A useful way to frame the request is to ask three concrete questions rather than a general "is it done?": does the transfer show as completed in your establishment Qiwa account, has the new iqama been issued or printed, and is there any outstanding fee or eligibility flag on the establishment side holding it. Specific questions get specific answers, and they make it far harder for an employer to fob you off with a reassuring non-answer.

If the employer is unresponsive, dragging their feet, or the request was actually rejected rather than completed, that is a different problem with its own path - read our guide on a Qiwa transfer rejected by the employer. And if you are being pressured or left in limbo in a way that risks an absconding (huroob) flag, understand your exposure first with our huroob status check and removal guide before anything escalates.

When the record is genuinely stuck - Absher still wrong, employer claims it is done, and days have passed - it is time to escalate rather than keep refreshing. Use the channel that matches the layer that is broken:

• MHRSD / Qiwa issues (labour relationship, transfer not finalising): contact MHRSD on 19911. This is the right line for transfer and work-permit problems.
• Residency / iqama record issues (Absher showing the wrong sponsor): the Ministry of Interior line is 989.
• Tawakkalna app behaviour (record is correct everywhere but the app is wrong): use Tawakkalna's in-app support.

When you call, have your iqama number, the transfer request reference, and the date your record last changed ready. Describe the mismatch precisely: "Absher shows X, Tawakkalna shows Y, transfer in Qiwa shows completed on [date]." Precise descriptions get routed faster than "my app is broken." Phone numbers and processes can change - confirm the current contact details inside the official apps when you call.

Calling the right line first matters more than it sounds. If your real problem is on the residency record, calling the labour line (19911) will often just bounce you, and vice versa. Match the line to the broken layer using the diagnosis table above: if Absher is wrong, that is a residency matter for 989; if the transfer itself will not finalise in Qiwa, that is a labour matter for 19911; if every record is correct and only the app misbehaves, that is a Tawakkalna in-app support matter. One well-aimed call beats three misrouted ones.

Escalation calls go faster when you arrive prepared. Whichever line you use, having the exact facts to hand means the agent can find your record immediately instead of asking you to call back. This table lists what to gather and why each item matters. None of it is sensitive to share with the official channel itself, but keep it private otherwise.

The single most useful thing on that list is the pair of screenshots showing the mismatch side by side. "Absher shows the new sponsor, Tawakkalna shows the old one, transfer completed on this date" is a precise, routable description. "My app is broken" is not. Precision is what gets your call sent to the team that can actually fix your layer.

Use this as a triage table. Every duration is indicative and varies; confirm your own case with Absher, MHRSD (19911), or MOI (989).

The pattern to remember: fast fixes are app-side, slow fixes are record-side. Diagnosing which side you are on (Section 5) saves you days of refreshing an app that was never the problem. The two cheapest accelerators cost nothing: check Absher before you assume the app is broken, and ask the employer the three specific questions before you assume they have finished. Most of the avoidable delay in these cases comes from skipping those two free steps.

In the rush to unlock services, people often do things that delay the very fix they want:

• Re-submitting the transfer. A completed transfer does not need re-doing; a duplicate can create a conflict. If you fear it failed, verify status first, do not resubmit.
• Reinstalling the app expecting a sponsor change. A reinstall clears the cache (useful) but it cannot conjure data the central record does not yet hold.
• Assuming Qiwa approval equals a new iqama. They are separate milestones. Approval is necessary but not always sufficient.
• Ignoring iqama expiry during the chaos. A transfer does not renew your iqama and does not reset its expiry date. Track both separately.
• Calling the wrong helpline. Phoning the labour line about a residency-record problem (or the reverse) usually just gets you bounced. Match the line to the broken layer first.
• Letting a payment or fee question stall everything. If you want to sanity-check transfer and residency costs, our Saudi iqama cost calculator gives you a realistic figure, and the overstay fine calculator shows the cost of letting status lapse while you wait.

Notice the thread running through every one of these: they are all attempts to act before diagnosing. Resubmitting, reinstalling, assuming, and misdialing all skip the one step that actually tells you where the problem is. The discipline of checking Qiwa, then Absher, then Tawakkalna in that order is what keeps you from making any of these errors, because once you know which screen disagrees with which, the right action is obvious and the wrong actions become clearly pointless.

If you are reading this locked out of services after a transfer, the frustrating part is that the fix is rarely one big action - it is the right small action in the right system, in the right order. That is exactly the kind of paperwork chase Wathim handles so you do not have to.

We confirm where your record actually stands, identify whether the blocker is app-side, residency-side, or employer-side, push the employer or the right ministry channel to finalise it, and keep checking until Tawakkalna shows the correct sponsor and your services unlock. We treat this as a problem to be closed, not a ticket to be opened. In practice that means we run the same diagnosis you would, but we know which screen to trust, which question to ask the employer, and which helpline maps to which broken layer - so you do not lose days to misrouted calls or duplicate requests.

Because transfer issues often sit next to work-permit and identity matters, our work permit service and national ID service cover the surrounding paperwork too. And if the transfer turns out to have collapsed entirely and you need to plan an exit instead, read our final exit visa guide so you know every option before you decide. If your situation also involves a visit visa caught in the same status mess, our note on a visit visa you cannot extend due to insurance may save you a second headache.