HR Software Egypt: Payroll, Biometrics & Leave Done Right
Most Egyptian SMBs hit the same three walls with HR software: overtime that doesn't match Labour Law 137, biometric devices that lose data at month-end, and leave policies nobody actually follows. Here's how to fix all three.
The Payroll Mistake That Shows Up on Month 2
You run payroll in month one and everything looks fine. Month two, a manager flags that two engineers worked through Eid and their overtime came out wrong. You dig in and realise your system calculated overtime at 1.25× for all extra hours — but Egyptian Labour Law 137/1981 (and its 2003 amendments) requires 1.35× for daytime overtime and 1.7× for night shifts and official holidays. The delta across a team of 40 is not trivial.
Getting overtime right is not a configuration checkbox. It requires the system to know shift type, whether the day falls on an official public holiday, and the employee's base wage structure. If your payroll tool can't distinguish those three variables, you will produce errors every month that compound into disputes.
Overtime Calculation Under Egyptian Labour Law — The Short Version
Article 70 of the Egyptian Labour Law sets the floor. Here's what a payroll system must handle correctly:
- Regular overtime (day hours): base hourly rate × 1.35
- Night overtime (between 7 pm and 7 am): base hourly rate × 1.7
- Official holidays and Fridays: base hourly rate × 2.0, minimum
- Maximum overtime: 2 hours per day, with employee consent; exceptions exist for specific industries
The base hourly rate itself has a trap: it's calculated on gross fixed wage divided by 200 working hours per month — not 176, not 160. Use the wrong denominator and every overtime figure is wrong before you even apply the multiplier.
For a deeper walk-through of how these rules interact with social insurance contributions, the payroll calculation guide for Egypt and MENA covers the full formula with worked examples.
Leave Policy Templates That Hold Up
Egyptian law sets a floor of 21 days annual leave after one year of service, rising to 30 days after ten years or after age 50. The common failure is building a leave policy that meets the legal minimum and nothing else — which means every exception (carry-over, sick leave conversion, unpaid leave for extended illness) becomes a one-off decision that HR handles manually and inconsistently.
A workable leave policy template for an Egyptian SMB should cover at minimum:
- Annual leave accrual rate (days per month, not lump sum at year-start)
- Maximum carry-over cap — 30 days is a sensible default; anything above requires a written agreement
- Sick leave: paid for the first 90 days (at varying rates per Labour Law), then social insurance takes over
- Emergency leave: up to 6 days per year, deducted from annual balance
- Unpaid leave approval process and effect on gratuity calculation
- Leave freeze periods for peak business cycles (write these in advance, not during Ramadan)
The policy document matters less than whether your system actually enforces it. If HR can override a leave rejection with no audit trail, the policy is decorative.
Attendance Geo-Fencing: Setup That Actually Works
Geo-fencing attendance — where an employee's check-in is only accepted if their phone GPS is within a defined radius of the workplace — works well in theory and badly when configured carelessly.
Common setup errors:
- Radius too tight (under 50 metres): GPS drift in dense Cairo streets causes legitimate check-ins to fail. 80–120 metres is a reasonable default for a single-building site.
- No offline fallback: If the employee's phone loses data signal in a basement or server room, the app should queue the check-in with a timestamp and sync when connectivity returns. Without this, you get missed punches that HR has to fix manually.
- Multi-site employees: Sales reps and field engineers visit client sites. The system needs to support multiple approved locations per employee, not a single fixed point.
- Spoofing: Some staff use GPS spoofing apps. A serious geo-fence implementation logs the device ID alongside location, making pattern anomalies visible to HR.
Geo-fencing works best as a complement to biometric devices in the main office — not a replacement for them.
Biometric Attendance Device Buyer Guide for MENA
Face recognition terminals have dropped in price sharply. A decent unit now costs between EGP 4,500 and EGP 12,000 depending on throughput and integration options. Here's what to evaluate before buying:
Recognition Speed and Queue Size
A device that takes 2 seconds per person at a 200-employee site creates a 6-minute queue at 8 am. Look for sub-0.5-second recognition and a database capacity of at least 5,000 faces, even if your team is 80 people today.
Connectivity and SDK
Ask specifically: does the device push attendance records via API (REST/JSON), or does it only export via USB or proprietary software? API push is non-negotiable if you want real-time sync to your HR system. Devices that require a nightly CSV export create a 24-hour lag in attendance data and a manual import step someone will eventually forget.
Offline Mode
Cairo office buildings have power fluctuations. The device must store locally and sync the backlog when connectivity is restored. Confirm the local storage capacity — some budget devices hold only 50,000 records, which a 300-person site fills in roughly 2 months.
Mask and Lighting Performance
Post-pandemic, requiring employees to remove masks for check-in is impractical. Test the device specifically under fluorescent office lighting and in lobby areas with direct sunlight — both conditions common in Egyptian office buildings. Ask the vendor for failure rate figures, not just marketing specs.
Warranty and Local Support
A device with no Cairo-based service agent means a 3–6 week wait for repairs on a faulty unit. Prioritise vendors with a local distributor who can replace a unit within 48 hours.
For a full comparison of device categories and integration patterns, the face recognition attendance systems guide for MENA HR goes deeper on vendor evaluation criteria.
Payroll Reconciliation Checklist Before You Run the Month
Run this before every payroll cycle, not after:
- Confirm attendance data is fully synced — no pending device imports, no open manual corrections older than 48 hours
- Verify all new hires this month have complete records: hire date, base salary, social insurance number, bank account
- Check that all approved overtime is tagged with correct shift type (day / night / holiday)
- Confirm all approved leave has been deducted from balances and cross-check against attendance records for consistency
- Run the variance report against last month: flag any employee whose gross changed by more than 15% without a documented reason
- Verify social insurance contributions match current salary brackets — brackets are updated periodically
- Confirm bank file format matches your bank's WPS spec before submission
Steps 1 and 5 alone will catch 80% of payroll errors before they become employee complaints.
How the System You Choose Shapes Every One of These Steps
The checklist above is straightforward. The question is whether you're doing it in four different spreadsheets and a WhatsApp thread, or in a single system where attendance, leave, overtime, and payroll are connected by design.
Attendux was built specifically for this operational context — Egyptian payroll rules, Arabic-language interfaces, biometric device integration, and multi-branch setups where each location has different shift patterns. The difference between a generic SaaS and something built for Egyptian Labour Law is exactly the kind of overtime denominator issue described above: a global tool won't know the 200-hour rule unless someone hardcoded it.
That said, the right system is the one your team will actually use. If your HR manager is running everything in Excel today, a system that requires three days of configuration training will sit unused. Prioritise the tool that solves your top two pain points first — usually overtime accuracy and leave tracking — and expand from there.
For multi-branch operations with ERP integration requirements, the multi-branch HR SaaS guide covering SIF export and ERP connections outlines the architecture decisions that determine whether your setup scales.
Ready to talk?
If you're evaluating HR software for an Egyptian or Gulf operation and want a straight conversation about what your specific setup needs — overtime structure, number of locations, biometric device compatibility, payroll bank format — reach out to the ProgMine team. No demo script, just a working session around your actual numbers.
Want to talk?
Have a project in mind or questions about our services? Get in touch.