nábd Pay · payroll engine
MENA payroll, native to your SuccessFactors tenant.
A payroll engine purpose-built for SuccessFactors customers operating in Egypt, Saudi Arabia, and the Gulf. Egyptian and Saudi labour law modelled at the core. Live OData integration with Employee Central. Designed to deploy in weeks and run for years.
Who nábd Pay is for
SuccessFactors customers running payroll in MENA.
You are running SuccessFactors. Your headquarters is in Egypt, KSA, the UAE, or you operate across the Gulf and Levant. You need payroll that understands local labour law without being adapted from a global product. You want it to live inside your SuccessFactors world — same tenant, same identity, same employee record.
That is what nábd Pay is.
The product
Egyptian and Saudi labour law, modelled at the core.
Every cycle gated before it runs. Approved through finance with the variance and break-down they need. Read back through analytics that explain the month, not just the total.
Readiness
Approval
Analytics
Readiness
Approval
Analytics
Captured from production at 1440 × 900. No mock data.
Capabilities
A payroll engine modelled around how MENA actually pays.
Egyptian labour law modelled at the core
Wage tax bands, social insurance, leave structures, end-of-service indemnity, overtime treatment — native, not configured.
Saudi labour law modelled at the core
GOSI, wage protection (WPS), Saudisation tracking, end-of-service benefit calculations — native to KSA law.
Multi-currency, multi-entity
Multiple legal entities in one tenant. Live exchange rate integration. Currency conversion is a first-class concern, not an afterthought.
Reactive pay element model
Pay elements declared as a dependency graph. Change one input, downstream calculations recompute automatically. No black-box payroll runs.
Retro and arrears built in
Late corrections, mid-period changes, retroactive adjustments — handled cleanly, not as exceptions.
Live OData with Employee Central
Master data flows in real time. New hires, transfers, terminations reflected without manual sync.
Bank file generation
Local bank formats for Egypt and KSA. WPS-compliant for Saudi. Direct hand-off to your treasury team.
Auditable, scored, governed
Every payroll run produces a structured audit trail. Errors flag pre-run, not post-run.
Architecture
Reads from Core. Writes back to the source.
nábd Pay reads employee master data, organisational structure, time data, and compensation information from nábd Core — the shared data layer underneath the suite. Core syncs in real time from your SuccessFactors tenant and other authoritative sources, so Pay always reads against the current picture without a direct integration of its own to maintain.
Payroll results — earnings, deductions, taxes, net pay — write back through Pay's own integration to a structured payroll posting record accessible from SuccessFactors. No separate identity store, no parallel master data, no reconciliation gap.
See the suite architectureChoosing the right fit
SAP ECP and nábd Pay solve different problems.
Every SuccessFactors customer asks this question. Here is how to answer it honestly — describing the buyer each is right for, not by ranking one above the other.
SAP Employee Central Payroll
SAP standard
Multi-country global operations standardising on SAP's enterprise payroll platform.
- Operations across multiple regions, not focused on a single geography
- 5,000+ employees with complex multi-jurisdiction payroll
- Deep multi-currency, multi-language global tax engines required
- Long-horizon enterprise architecture investment
- Already running global SAP standardisation programmes
nábd Pay
MENA-native
SuccessFactors customers whose operations centre on MENA, deploying payroll in weeks.
- MENA-focused operations: Egypt, KSA, Gulf states, Levant
- Smaller and mid-market — typically up to 5,000 MENA employees
- MENA currencies and tax structures modelled natively
- Want to deploy in weeks, not a multi-quarter programme
- Want to extend an existing SuccessFactors tenant without a global change initiative
Raptors implements both. If ECP is the right answer for your situation, our SuccessFactors practice delivers it. If nábd Pay fits, the same team ships it. The recommendation is independent of the product we own.
Pilot reference
Raptors runs payroll on nábd Pay.
We are the pilot tenant. Our payroll runs on Pay, reading from a Core instance synced from our SuccessFactors and S/4HANA Public Cloud systems. Additional reference customers slot here as they go live.
[VERIFY: confirm pilot customer naming and any published outcome metrics before publish.]
Next step
Payroll modelled for the region. Live in weeks.
A 45-minute demo with the team that built Pay. We show you the engine running against your own scenarios.