Article

Enterprise HR Software Egypt: SIF Export, ERP & PTO Accrual

Running HR across 3 branches and two Gulf entities sounds manageable until payroll week. Here's what the architecture needs to handle — from SIF file generation to accrual logic and ERP sync.

Enterprise HR Software Egypt: SIF Export, ERP & PTO Accrual

A 300-person company with offices in Cairo, Dubai, and Riyadh runs three payroll cycles under three regulatory regimes — and somebody has to reconcile the attendance data before any of that starts. That's the problem most enterprise HR software never solves cleanly.

The Multi-Branch Attendance Problem Nobody Talks About

Branch managers usually own their own biometric terminals or mobile check-in apps. The data lives in silos until someone exports a spreadsheet on the last Thursday of the month and pastes it into a master file. By that point, two branches have employees who worked across locations the same week, one terminal was offline for 11 hours, and you're reconciling 400 rows manually.

What you actually need is a centralised attendance ledger that pulls from every node in near real time — not a nightly CSV dump. Each employee record carries a primary branch code, but punches can be posted to any branch and still resolve to the right cost centre. Without that, overtime calculations will consistently be wrong for field staff and travelling supervisors.

SIF File Export for UAE WPS: What the Format Requires

The UAE Wages Protection System mandates a Salary Information File (SIF) generated to Central Bank specifications before the transfer hits. The fields are precise: employer EIN, employee bank IBAN or card ID, net salary in AED to two decimal places, payment type code, and the salary month. One malformed row rejects the entire file at the bank.

Common failure points:

  • Employee IBAN stored without the two-character country prefix (AE not stripped)
  • Net salary figure not matching the bank transfer amount because a manual deduction was added after export
  • Payment type coded as SALARY for someone on a fixed-term contract who should be CONTRACT
  • File encoding sent as UTF-8 when the submitting bank expects ASCII

The fix is not a better export template — it's a locked payroll-to-SIF pipeline where net pay can't be edited after the file is generated. Any post-approval change forces a new cycle, not a manual override.

WPS in Saudi Arabia: Different Rules, Same Deadline Pressure

Saudi WPS via MUDAD operates on a similar principle but diverges in structure. The file references IQAMA numbers for expatriate workers, the salary period must be 30 days exactly (calendar month proration has to be explicit), and late submission triggers Ministry of Labour flags against the employer record. For companies with 100+ Saudi-based employees, even one flag can delay Iqama renewals across the whole workforce.

The practical implication: your HR system needs country-aware payroll rules, not a single payroll engine with a currency switcher bolted on. The accrual calendars, overtime multipliers, and file schemas diverge enough that trying to generalise them into one template creates silent errors.

Egypt Labour Law 12/2003 — and What's Changed

Egypt's foundational labour law hasn't been replaced wholesale, but ministerial decrees have layered significant amendments onto it over the past few years. The areas with the highest compliance exposure for a 100-500 person operation are:

  • Overtime caps and rates: Daily overtime beyond 2 hours requires written employee consent per Article 68, and the rate is 135% for daytime, 170% for night shift. Many systems still apply a flat 1.5× multiplier and miss the shift-type distinction.
  • Annual leave accrual: 21 days after less than 10 years of service, 30 days after. The accrual should be daily, not monthly-block, so mid-year leavers are calculated correctly.
  • Social insurance base: The variable component cap and minimum base have been adjusted by decree. If your system has a hardcoded EGP figure from 2021, your SI contributions are almost certainly understated now.

For a fuller breakdown of the recent statutory updates, the Egypt Labour Law compliance guide covers what HR managers need to audit before the next inspection cycle.

PTO Accrual Engines: The Logic That Has to Be Right

Most HR platforms offer leave management. Fewer have a proper accrual engine — meaning a system that calculates earned-but-not-yet-taken leave as a liability, with correct proration for joiners, leavers, and unpaid leave periods.

What a compliant accrual engine needs to handle:

  1. Daily accrual rate based on statutory entitlement ÷ working days in the year (not calendar days)
  2. Carry-forward cap — Egypt law limits carry-forward; excess should auto-expire or trigger encashment depending on company policy
  3. Unpaid leave freeze — accrual should pause during unpaid absence, not continue accumulating
  4. Backdated joiner correction — if a contract start date is corrected two months in, the system should recalculate the entitlement from day one, not from the correction date
  5. End-of-service encashment — the final accrued balance has to feed directly into the termination payslip with the correct daily rate

If your platform doesn't surface a real-time accrued-leave liability balance per employee, you're running blind on what you owe the workforce at any given moment.

ERP Integration: Where HR Data Goes After It Leaves the System

For companies already running on SAP, Oracle, Microsoft Dynamics, or even a mid-market ERP like Odoo, the HR system is not the final destination for payroll data — the ERP's general ledger is. Every payroll run needs to post journal entries: gross wages by department, employer-side SI, withholding tax, and net cash to the bank.

The integration points that break most often:

  • Cost centre mapping — HR assigns employees to branches, ERP uses a different GL cost centre hierarchy, and the two maps drift over time as branches get added
  • Currency conversion for multi-entity setups — payroll in EGP and AED needs to land in the consolidation ledger at a defined rate, and that rate has to be agreed between HR and finance before each run
  • Timing mismatch — HR closes payroll on the 25th, ERP period closes on the 30th, and provisional accruals posted between those dates create reconciliation work every month

The cleaner approach is an API-based integration where the HR platform pushes a structured payload (employee ID, GL account, debit/credit, amount, currency, period) and the ERP consumes it without manual mapping. That payload format should be agreed at implementation, not patched after the first reconciliation fight.

For teams evaluating how integration architecture decisions compound over time, the piece on ERP and CRM integration patterns in MENA is worth reading alongside this — the data-ownership questions are the same.

What to Actually Evaluate in an Enterprise HR Platform

Attendux was built specifically for the MENA multi-entity scenario — country-specific payroll rules, SIF/WPS export, and ERP sync aren't add-ons; they're in the core. But whatever platform you're assessing, the evaluation questions should be the same:

  • Does it generate a valid SIF file without manual post-processing?
  • Can it run parallel payrolls under different country rule-sets from one admin console?
  • Is the PTO accrual engine configurable to daily rates, or does it work in monthly blocks?
  • What does the ERP integration payload look like — fixed export or structured API?
  • When a labour law parameter changes (SI cap, overtime rate), who updates it and how fast?

The last question matters more than any feature list. A platform that relies on a client ticket to update a statutory rate is a compliance liability every time a ministerial decree lands.

The Setup That Actually Scales

Companies that handle multi-country payroll cleanly tend to have made one decision early: they picked a system that treats each jurisdiction as a first-class configuration, not a workaround. Egypt, UAE, and Saudi each get their own payroll calendar, their own statutory deduction rules, and their own file export format. The consolidation happens at the reporting layer, not by forcing everything through a single payroll template.

That decision is harder to reverse than it looks. If you're currently on a system that's stretched to cover MENA with one-size logic, the multi-branch HR engineering breakdown outlines what a migration actually involves before you commit to anything.

Ready to talk?

If you're running HR across multiple branches or entities and hitting the limits of your current setup — SIF errors, accrual gaps, ERP reconciliation every month — we're happy to walk through what the architecture should look like for your specific headcount and geography. Reach out to the ProgMine team and describe the problem; we'll tell you honestly whether it's a configuration fix or a platform decision.

Share this article

Want to talk?

Have a project in mind or questions about our services? Get in touch.

Contact us