HR Software Egypt: Biometrics, Payroll & Leave Setup Guide
Most Egyptian SMBs lose hours every month to avoidable payroll errors — wrong overtime rates, missing leave balances, biometric devices that don't talk to their software. This guide covers the operational specifics.
Why Payroll Errors Keep Happening in Egyptian SMBs
Most Egyptian SMBs lose hours every month to avoidable payroll errors — wrong overtime rates, missing leave balances, biometric devices that don't talk to their software. This guide covers the operational specifics.
The root cause is almost never laziness. It is fragmentation: attendance data lives in one spreadsheet, leave requests in a WhatsApp group, and salary calculations in a third Excel file that only one person knows how to run. When those three sources disagree — and they will — someone spends a Thursday afternoon reconciling numbers instead of doing real work.
Fixing this starts with understanding the legal baseline, then picking hardware and software that actually fit together.
Overtime Calculation Under Egyptian Labour Law
Egypt's Labour Law No. 12 of 2003 sets specific multipliers for overtime. Getting these wrong exposes your company to back-pay claims and Ministry of Manpower inspections.
- Daytime overtime (beyond 8 hours/day): at least 135% of the basic hourly wage.
- Night-shift overtime (between 8 PM and 6 AM): at least 170% of the basic hourly wage.
- Friday (official rest day) overtime: at least 200% of the basic hourly wage, with a compensatory day off if the employee requests it.
- Public holidays: same 200% rule applies.
The hourly wage is calculated by dividing the monthly basic salary by 240 (30 days × 8 hours). Do not use the gross salary figure — allowances and commissions are excluded from the base unless your internal policy explicitly includes them.
Practically speaking, any HR software you evaluate must let you configure these multipliers per shift type, not just apply a flat overtime rate. Ask vendors to show you a sample payslip with mixed daytime and Friday overtime before you sign anything.
Leave Policy Templates That Hold Up
Egyptian law grants employees 21 days of annual leave after one year of service, rising to 30 days after ten years or after age 50. That is the legal floor. Your internal policy can be more generous, but it cannot go below those numbers.
A practical leave policy template for a Cairo-based company of 20–200 staff should cover:
- Accrual method: monthly accrual (1.75 days/month for the 21-day band) is easier to audit than annual front-loading.
- Carry-over cap: Egyptian law permits carrying over unused leave with employee consent. Set a cap — 10 days is common — to prevent large accrued liabilities on your balance sheet.
- Sick leave: law grants 90 days at full pay, 90 days at 75%, 90 days at 50% per illness cycle. Require a medical certificate from a certified physician for any absence beyond two consecutive days.
- Maternity leave: 90 days at full pay, available up to three times during employment.
- Unpaid leave: define the approval chain and the maximum duration before the employment relationship is considered abandoned.
Store signed acknowledgments of this policy in each employee's digital file. If a dispute reaches a labour court, paper trails matter more than intentions.
Attendance Geo-Fencing: Setup and Common Mistakes
Geo-fencing attendance means an employee's clock-in is only accepted when their phone's GPS location falls within a defined radius of the workplace. For companies with field teams — logistics, construction, retail — this replaces fixed biometric terminals without sacrificing accountability.
Typical configuration steps:
- Set the allowed radius at 100–150 metres for urban Cairo offices (GPS drift in dense areas can be 50–80 m).
- Define multiple zones if staff rotate between branches — Maadi HQ, Heliopolis branch, and a client site can each be a separate geo-fence.
- Enable tamper detection: the app should flag if the device's mock-location developer option is active.
- Log the raw GPS coordinates with each punch, not just a pass/fail flag — you will need the raw data if an employee disputes a missed clock-in.
The most common mistake is setting the radius too tight (under 50 m) in a basement office or underground facility where GPS signal is unreliable. Test the zone for three days before going live.
Biometric Attendance Device Buyer Guide for MENA
Face-recognition and fingerprint terminals vary enormously in price and reliability. Here is what to check before buying for a MENA office environment.
Environmental Factors
Egyptian summers push indoor temperatures above 35°C without consistent air conditioning in warehouses or factory floors. Confirm the device's operating temperature range — commercial-grade units typically run from 0°C to 45°C, but cheaper models throttle processing at 40°C, causing slow verification queues at shift start.
Liveness Detection
Basic face-recognition devices can be spoofed with a photo. Insist on 3D infrared liveness detection, particularly if your workforce handles cash or sensitive inventory. Devices with this feature cost 25–40% more but eliminate the most common fraud vector.
Offline Capacity
Internet outages are a real operational risk. Choose a device that stores at least 30 days of attendance logs locally and syncs automatically when the connection is restored. Minimum local capacity: 100,000 transaction records.
Integration Protocol
Ask whether the device exports via REST API, SDK, or only via a proprietary desktop application. Proprietary desktop apps create bottlenecks when your IT team is in a different city. API-first devices give HR software the ability to pull records in real time without manual intervention.
Recommended Brands Available in Egypt
- ZKTeco: Wide service network in Cairo and Alexandria; most models have Arabic UI.
- Hikvision DS-K1T671M: Strong liveness detection; popular in banking and retail.
- Suprema BioStation 3: Premium tier; best for 200+ employee sites that need high throughput.
Payroll Reconciliation Checklist
Run this checklist before every payroll approval, ideally by someone other than the person who built the payroll run.
- Attendance totals match the HR system export — check total hours, not just headcount.
- Overtime hours are categorised by type (daytime / night / Friday) and priced at the correct multiplier.
- New joiners have a confirmed start date and pro-rated salary, not a full month.
- Leavers have a final settlement calculation that includes accrued leave payout (Article 47, Labour Law No. 12/2003).
- Social insurance deductions match the latest Insurance Authority tables — rates changed in 2020 and again in 2023.
- Income tax brackets are applied to net taxable income after social insurance deduction, not gross salary.
- Allowances marked as non-taxable in contracts are excluded from the tax base.
- Bank transfer file totals match the payroll summary to the last piaster.
This eight-point check takes about 20 minutes on a well-structured system. If it takes longer, the problem is usually data format inconsistency between your attendance export and your payroll tool — a sign the two systems were never properly integrated.
Connecting the Pieces: What Integrated HR Software Should Do
A properly integrated HR platform eliminates the reconciliation bottleneck by making attendance, leave, and payroll speak the same language from day one. Attendux, built by ProgMine for the Egyptian and MENA market, handles biometric device sync, geo-fence clock-ins, leave accrual under Egyptian law, and payroll calculation in a single workflow — so the checklist above becomes an automated validation rather than a manual audit.
When evaluating any HR SaaS, verify that the vendor has pre-built the Egyptian social insurance tables, can configure the three overtime multipliers described earlier, and can ingest raw data from your existing biometric hardware via API — not just CSV uploads.
Implementation Timeline for a 50-Person Cairo Company
Realistic milestones for a full HR software rollout:
- Week 1–2: Data migration — employee master file, historical leave balances, open contracts.
- Week 3: Biometric device installation and API connection testing.
- Week 4: Parallel payroll run — process one month on both old and new systems and reconcile the difference.
- Week 5: Staff training on the mobile app for leave requests and clock-in.
- Week 6: Go live; keep old system in read-only mode for 60 days.
Skipping the parallel payroll run is the most common implementation shortcut — and the most expensive one when errors surface after go-live.
Ready to talk?
If you want to map these specifics to your company's headcount, shift patterns, and existing hardware, our team at ProgMine is available for a focused working session — no generic demos, just your data and your numbers. Get in touch through the contact page and we will schedule a call within one business day.
Want to talk?
Have a project in mind or questions about our services? Get in touch.