Field notes · Saudi Arabia · 12 minute read
SuccessFactors meets Muqeem: a playbook for KSA visa and residency automation.
How a 2,500-employee Saudi operation moved visa renewals, transfers, and final exits out of spreadsheets and onto an audit-ready integration channel, and what we'd tell any KSA enterprise about to do the same.
The problem at scale
A Saudi food and beverage group, 2,500 employees, around 1,200 of them non-Saudi nationals. SuccessFactors live for three years: Employee Central, Recruiting, Onboarding, plus payroll on Employee Central Payroll. Across the residency lifecycle (visa issuance, Iqama transfer, final exit, annual renewal), they were running about 4,800 Muqeem transactions a year.
2,500
employees, 1,200 non-Saudi
~4,800
Muqeem filings a year
2 to 4
late renewals a quarter
2 days
to answer who is compliant
All of it on spreadsheets. A coordinator in HR maintained a tracker. Renewal windows were watched manually. Each filing was a separate visit to the Muqeem portal by a government relations officer. Status updates flowed back as PDFs that someone scanned and uploaded to the employee record. The audit trail lived in email and on someone's laptop.
Two consequences. First, late renewals: between two and four per quarter, usually catching a transfer or a remote site. Each late renewal carries a per-day fine and a reputational risk with the regulator. Second, the HR director could not answer "what is the current residency status of our workforce?" without two days of reconciliation.
The shape of the work was right for automation. The constraint was that Muqeem operations could not be replaced with custom integrations. The Saudi government requires filings to go through approved channels. The right path was a channel that already had Muqeem's approval, wired into SuccessFactors so the operations could be initiated and tracked from the system of record.
Why standard SuccessFactors doesn't reach Muqeem
SuccessFactors has rich employee data: Iqama numbers, sponsorship details, contract types, and visa expiry dates all sit on the Employee Central record. What standard SF does not have is an integration to the Muqeem portal itself. The portal is a Saudi government system; SAP does not ship a connector to it.
Three options have been tried over the years. Each fails in a distinct way.
Manual filing with a tracker
A coordinator keeps a spreadsheet and visits the portal for every filing. Works at low volume.
fails on audit at scaleRPA on the Muqeem portal
Bots log in as a human operator and click through filings. Works briefly, then breaks on every portal change.
not an approved channelCustom point-to-point build
An SI wires SuccessFactors to an unofficial Muqeem API surface.
compliance and maintenance riskThe right pattern is an approved Muqeem integration channel that already exists, wired into SuccessFactors through a connector designed to live inside the SF tenant. That is what Tawasol is, and what we shipped for this customer.
The integration architecture
Three systems, one approved channel between them. HR works inside the SuccessFactors record; Tawasol carries each request to Muqeem and writes the answer back as structured data.
Exhibit 2 · Integration flow
Every Muqeem filing returns to SuccessFactors as data, not a PDF.
HR works inside the SuccessFactors record. Tawasol carries each request through the approved Muqeem channel and writes the answer straight back as structured, queryable data.
SuccessFactors
HXM system of record
Tawasol
the integration bridge
Muqeem
Saudi govt residency authority
SuccessFactors
HXM system of record
Tawasol
the integration bridge
Muqeem
Saudi govt residency authority
What runs through the channel
Source: client integration records, FY ending 2025. About 4,800 Muqeem transactions per year across the four lifecycle events. [VERIFY]
The HR coordinator used to reconcile Iqama state by spreadsheet on Sunday mornings. Now she opens the SF employee record and the state is already there.
What Tawasol automates
The bulk of KSA residency activity is covered out of the box, each operation pre-built and triggered from inside the SuccessFactors employee record.
Triggered by a new non-Saudi hire
Visa issuance
Tawasol routes the filing through the approved Muqeem channel and tracks issuance to confirmation.
Triggered by an inter-entity transfer
Iqama transfer
Enforces Muqeem eligibility rules, files the request, tracks status, and updates the record on completion.
Triggered by a termination
Final exit
Files the exit, watches for the regulator's release, and clears the Iqama state on the SF record.
Triggered as Iqama expiry approaches
Residency renewal
Surfaced 60 days out, filed 30 days out by default, confirmed back to the record on completion.
What it doesn't automate (and shouldn't)
Some operations stay human-in-the-loop on purpose. Tawasol surfaces them; it does not file them automatically.
Exceptions
Mismatched documents, blocked transfers, and regulator queries route to a named HR owner.
48-hour SLABulk operations on contested attributes
Mass renewals run automatically. Mass exits are surfaced for explicit approval first.
needs approvalEdge regulator changes
When Muqeem issues a rule update, Tawasol pauses the affected flow and notifies the customer.
product team picks upThe compliance posture: what SAP Store certification actually means
Three certifications matter here, and each one carries a different weight.
the build
SAP architecture review
SAP's audit of the integration against their architecture standards. It confirms the connector is built correctly against the SF tenant.
the channel
SAP Store listed
The discovery surface and contractual model. SAP handles the commercial flow; support comes from Raptors.
the regulator
Muqeem approved channel
Filings through Tawasol go through Muqeem's authorised integration, not screen-scraping or unofficial APIs.
the one that mattersAll three together is the bar. Two of three is a different product.
Three pitfalls in cross-tenant SF and Muqeem deployments
Cumulative lessons across the deployments we have shipped.
Attribute mastery on day one
Iqama numbers, sponsorship details, and contract types must be authoritative on the SF record before go-live. Plan two weeks of attribute cleansing before cutover.
Legal entity structure
Multi-entity customers file under each entity's commercial registration. The SF legal-entity to Muqeem-registration mapping must be complete, or filings reach the wrong CR.
Renewal-window discipline
The default 30-day window is the Muqeem-recommended buffer, not the minimum. Compress it to 15 and you lose exception-triage margin. We have never shipped under 25.
Where to go next
If you run KSA payroll on SuccessFactors and the residency lifecycle is on your roadmap, or already in your backlog of audit findings, the conversation starts with two artefacts: your current Iqama tracker, in whatever form it lives, and your Muqeem filing volumes for the last 12 months. We can map them against a Tawasol deployment in 30 minutes.
See the Tawasol product page for the architecture and capability detail, or talk to our team directly.
Next step