Enterprise HR Software Egypt: SIF, ERP & Labour Law
Most HR setups that work at 80 employees start cracking at 200. Here's what breaks first — attendance aggregation, SIF export, PTO accrual — and how to fix it before auditors or employees notice.
A company reaches 180 employees across three branches — Cairo, Alexandria, and a Gulf subsidiary — and the payroll manager is spending every Wednesday night manually reconciling attendance exports from two different biometric vendors into a single spreadsheet before Thursday's payroll run. That is not a productivity problem. That is an architecture problem, and it compounds every month.
Where Multi-Branch Attendance Actually Breaks
Single-location HR software is not the same product as multi-branch HR software, even when the vendor says otherwise. The gap shows up in a few specific places:
- Device aggregation: Each branch runs its own fingerprint or face-recognition device. If the software has no central polling engine, someone is manually exporting CSV files and importing them. That's where missing punches happen.
- Shift policies per branch: Your Alexandria warehouse runs a split shift; your Cairo office runs flex hours. A system with one global shift policy will miscalculate overtime for at least one site.
- Approval chains: Branch managers should approve their own team's leave and exceptions before it hits central HR. Without a hierarchical approval model, everything lands in one queue and central HR becomes a bottleneck.
The fix is not more spreadsheets. It's a system where each branch feeds a single data layer — with device polling running every 15 minutes — and branch-level rules are configurable without touching the core setup.
SIF File Export for UAE and WPS Payroll for Saudi
If your company has a UAE entity, the Central Bank of UAE requires a Salary Information File (SIF) in a specific XML schema before wages can be processed through the Wages Protection System. Saudi Arabia runs its own WPS implementation with different field requirements — notably the IBAN format, employer ID structure, and payment date tolerances.
What this means practically:
- Your HR software needs to hold country-level payroll configurations, not just a single payroll export template.
- The SIF must include the correct establishment ID, employee Emirates ID or Iqama number, and the exact net salary after all deductions — in that schema, in that order.
- A rejected SIF file means delayed salaries. Banks in the UAE return SIF errors within 24 hours, but correcting and resubmitting can push payment past the contractual salary date, which triggers a WPS violation flag.
Companies running Gulf payrolls through Egypt-only HR software typically handle SIF generation outside the system — in Excel or a one-off script — which creates version drift every time a field format changes. Country-specific export modules that stay in sync with WPS schema updates are not a luxury feature at this scale; they're operational infrastructure.
Egypt Labour Law 12/2003: What the 2023 Updates Changed
Labour Law 12/2003 has been amended incrementally, and the updates most relevant to HR software configuration are:
- Overtime caps and rates: The law specifies 1.35× the hourly rate for overtime on regular days and higher multipliers for rest days and official holidays. If your overtime engine uses a flat 1.5× across the board, you are either overpaying or underpaying — either creates liability.
- Annual leave accrual: Employees with under 10 years of service accrue 21 days per year; over 10 years, 30 days. HR systems that run a single accrual policy regardless of tenure are quietly miscalculating leave balances for long-tenured staff.
- Notice period and end-of-service: Calculation depends on contract type and length of service. Fixed-term and indefinite contracts have different termination settlement rules that need to be encoded, not approximated.
The practical exposure here is not usually an audit — it's an employee dispute at the moment of resignation or termination. At that point, a miscalculated leave balance or an incorrect severance figure becomes a Ministry of Manpower complaint. HR software that holds the law's logic internally, rather than leaving it to the payroll manager's memory, is the operational buffer.
PTO Accrual Engines: The Detail That Causes the Most Disputes
PTO accrual sounds simple until you have to configure it. The decisions that matter:
- Accrual frequency: Monthly, bi-weekly, or per-pay-period. Each produces a different balance at any given point in the year, which affects how you approve or reject a leave request in February.
- Carry-over rules: Egypt law limits carry-over (unused leave lapses if not taken within a defined period). Gulf entities may have different rules per jurisdiction. One global carry-over policy breaks compliance in at least one country.
- Proration on hire and exit: An employee who joins in mid-March should accrue a partial balance for March. An employee who exits in mid-October should receive only the leave days accrued to that date. If the system rounds to the nearest full month in either direction, it's wrong for someone.
- Balance visibility: Employees who can see their real-time accrued balance make fewer HR inquiries. That alone saves a mid-sized HR team 3-4 hours per week.
For a detailed look at how leave policy setup interacts with biometric attendance in Egyptian SME contexts, this setup guide covers the configuration sequence that tends to cause the fewest errors at go-live.
ERP Integration: What Actually Needs to Connect
HR software sitting in a silo from your ERP means someone is re-entering data. The integrations that deliver the most value at the 100-500 employee range:
- Payroll → GL posting: Payroll entries should post directly to the general ledger with cost-centre coding, not be re-keyed by the finance team. The error rate on manual re-entry in a 300-person payroll is not zero.
- Headcount → budget modules: When HR approves a hire, the ERP budget module should update the approved headcount and flag if the department is over-headcount. Keeping these two systems in sync manually delays reporting by days.
- Project allocation → attendance: For companies billing by project, attendance data needs to map to project codes. This is especially relevant in engineering, consulting, and construction firms operating across MENA sites.
The integration pattern matters as much as the connection itself. REST API integrations with field-level mapping are maintainable. File-based FTP exports that run nightly are fragile and create data that's always 24 hours stale. If you're evaluating ERP integration options more broadly, the integration patterns guide for MENA systems explains the tradeoffs between event-driven and batch approaches.
When to Build vs. When to Configure
Most 100-500 employee companies in Egypt and the Gulf do not need custom-built HR software. They need a configurable specialist product that handles MENA-specific compliance natively. The build-vs-buy decision only shifts toward custom development when the HR workflow is so industry-specific — say, a staffing agency managing thousands of contractors across jurisdictions — that no commercial product's configuration layer can accommodate it. For everyone else, the ROI of a well-configured specialist product is better than a 14-month build cycle. The build-vs-buy framework for MENA gives a structured way to run that analysis.
What Attendux Handles in This Stack
Attendux is built specifically for the Egypt and Gulf operational context — multi-branch attendance aggregation, SIF and WPS export per country, Labour Law 12/2003-compliant overtime and leave accrual, and ERP integration via REST API. It's not a generic global HR product configured for MENA as an afterthought; the compliance logic is in the product, not in a consultant's setup document.
Companies that have moved their multi-branch setup onto Attendux typically report reducing payroll close time from 18 days to 3, mostly because the manual reconciliation step disappears when device polling and branch approval chains work automatically.
The Practical Checklist Before You Migrate
If you're evaluating a move from your current system — or from spreadsheets — these are the questions that reveal whether a product is genuinely built for your context:
- Can it generate a compliant SIF file for UAE and a WPS file for Saudi from the same payroll run?
- Does the overtime engine support multiple multipliers per day type, or just a single rate?
- Can leave accrual rules be set differently per employee group, with tenure-based step-ups?
- Does the branch structure support independent approval chains, or does everything route to a single HR inbox?
- What is the ERP integration method — API with real-time sync, or nightly file export?
- How does the vendor handle schema updates when UAE or Saudi WPS requirements change?
The last question matters more than most buyers expect. WPS schemas are updated periodically by the respective central banks, and a vendor who handles that update transparently — pushing a schema version update to your account — is a fundamentally different operational partner than one who notifies you to re-export a template manually.
Ready to talk?
If you're running HR across multiple branches or multiple countries and the current setup requires too much manual intervention to close payroll, we're happy to walk through what a migration would actually look like for your headcount and entity structure. No generic demo — a conversation about your specific configuration requirements. Reach out to the ProgMine team and we'll set up a working session.
Want to talk?
Have a project in mind or questions about our services? Get in touch.