Tawasol Muqeem
Muqeem integration for SAP SuccessFactors
For organisations in Saudi Arabia running SAP SuccessFactors. The standard integration keeps records in step. Tawasol Muqeem raises the transaction itself.
Who it's for
Two conditions
You run SAP SuccessFactors with Visa and Permits Management in use, and it does not matter which partner implemented it. Your tenant stays the system of record and nothing in your implementation changes. You sponsor expatriate employees in Saudi Arabia, at a scale where Iqama and visa transactions are a recurring workload. Tawasol Muqeem runs on SAP Business Technology Platform (BTP), SAP's own platform for extending its products, beside your tenant rather than inside it. It is live at a KSA enterprise.
Tawasol Muqeem is listed on the SAP Store, and SAP publishes a partner solution page for it on sap.com.
What it does
Six things Tawasol Muqeem does
Raised where the record lives
An Exit Re-Entry Visa, a Final Exit or an Iqama renewal is requested from the employee's own record in SAP SuccessFactors. The transaction is recorded against that employee and against the person who raised it. There is no side system to keep in step and no tracking spreadsheet beside it.
The transactions it covers
Exit Re-Entry Visa: issue, cancel, extend and reprint. Final Exit Visa: issue and cancel, including Final Exit during probation. Iqama: renewal, issue and transfer. Visit Visa: extension. Each is a Muqeem interactive service, raised and tracked from SuccessFactors.
Muqeem's official interface
Each transaction is sent to Muqeem through the interface Muqeem publishes for the purpose, not by operating the portal's screens on a person's behalf. A change to those screens does not change how a transaction is sent. The response Muqeem returns is written back to the employee's record.
The fee posts to Finance
Each Muqeem service fee, whether a renewal or a visa charge, posts to SAP S/4HANA Finance with a reference to the transaction that caused it. No one keys a journal entry from a portal receipt. Finance can trace every government fee back to an employee, a transaction and a date.
Three reports, delivered
The Interactive Service Report, the Muqeem Report and the Visitor Report are delivered to email and to SAP SuccessFactors dashboards. Each shows what was raised, what Muqeem returned and what is still open, so a renewal that has not happened is visible before its date rather than after it.
Nothing changes in your tenant
Tawasol Muqeem runs on SAP BTP beside your SAP SuccessFactors tenant, not inside it. It reads the employee record and writes the transaction back. It adds nothing inside the tenant that an upgrade would have to carry, and it does not depend on which partner built your implementation.
One transaction
From the employee's record to Muqeem's response
Six steps sit between a request raised in SAP SuccessFactors and a response recorded against it. They run in this order, and none of them is done by hand.
Configuration
The transaction types, the legal entities and the account mapping are set once. Every transaction after that inherits them.
Collection
The employee's data is read from the SuccessFactors record. Nothing is re-keyed.
Transformation
The record is arranged into the form Muqeem expects for that transaction type.
Validation
Missing or inconsistent data is caught here, before anything reaches Muqeem.
Transmission
The transaction is sent to Muqeem through its official interface.
Response
Muqeem's response is written back to the employee's record, and the service fee posts to SAP S/4HANA Finance.
The record of the transaction stays with the employee's SAP SuccessFactors profile as the system of record, and its fee sits in SAP S/4HANA Finance with a reference back to it. When an auditor asks whether a renewal was done, the answer is in the system, not in an inbox.
Questions
Five things people ask first
SAP SuccessFactors already has a Muqeem integration. What does this add?
SAP SuccessFactors Visa and Permits Management keeps the employee's permit data in step with Muqeem and sends reminders before a date falls due. Tawasol Muqeem requires it and runs alongside it. What it adds is the transaction itself: the Exit Re-Entry Visa, Final Exit or Iqama renewal is raised, sent to Muqeem, tracked and costed from the same record.
We already have a script that works the Muqeem portal for us.
Tawasol Muqeem does not operate the portal's screens. It sends each transaction through the interface Muqeem publishes for the purpose, so a change to those screens does not change how a transaction is sent. Each transaction is recorded against the employee it concerns and the person who raised it, inside SAP SuccessFactors.
Is Tawasol Muqeem part of nábd Pay?
No. They are separate products and separate purchases. Payroll is what nábd Pay does, in Egypt only, and it does not touch Muqeem. Tawasol Muqeem raises Muqeem transactions in Saudi Arabia and does not run payroll. Neither is included with the other, and neither requires the other.
About nábd PayDo we need to have been a Raptors customer?
No. The condition is an SAP SuccessFactors tenant with Visa and Permits Management in use, whichever partner implemented it. Nothing in your implementation changes, because Tawasol Muqeem runs beside the tenant on SAP BTP rather than inside it. It is listed on the SAP Store as a standalone product.
What does the finance team get from it?
Every Muqeem service fee arrives in SAP S/4HANA Finance as a posting with a reference to the transaction, the employee and the date. No journal entry is keyed from a portal receipt, and each fee can be traced back to the request that caused it.
Tell us how a renewal reaches Muqeem today
A call with the team that built Tawasol Muqeem. Bring one transaction, from the request to the fee, and we walk through how it runs from the employee's record.