HR Compliance in Egypt: Payroll, Leave & Biometric Setup

Most payroll errors in Egyptian companies don't come from bad intentions. They come from a single ambiguity: the difference between basic salary and total compensation when calculating overtime. Get that wrong once and you've underpaid every hour of extra work your team logged this month — and exposed the company to a Labour Court claim.

Overtime Under Egyptian Labour Law: The Number That Matters

Law No. 12 of 2003 sets overtime at 1.35× the hourly rate for daytime extra hours and 1.7× for night shifts (roughly 7 PM–7 AM). The trap is the denominator. The hourly rate is calculated on basic salary only, not allowances, commissions, or in-kind benefits — unless your employment contract explicitly includes them.

A concrete example: an employee earns EGP 8,000 basic + EGP 2,000 transport allowance. Their statutory overtime base is EGP 8,000, giving a daily rate of roughly EGP 267 (÷ 30) and an hourly rate of EGP 33.3 (÷ 8). One Saturday at 1.35× costs EGP 44.95 per hour — not EGP 62.50, which is what you'd get if you mistakenly used total pay.

Monthly hours cap: standard working time is 8 hours/day, 48 hours/week. Overtime cannot legally exceed 2 hours per day without mutual written agreement.

Leave Policy Templates That Hold Up

Egyptian law mandates a minimum of 21 days of annual leave after one year of service, rising to 30 days after 10 years (or if the employee is over 50). Beyond the legal floor, most HR headaches come from undocumented policies. A lean but enforceable template covers:

• Accrual method: monthly (1.75 days/month at 21-day entitlement) or lump-sum at the anniversary date
• Carry-over cap: Egyptian law allows employees to accumulate up to three years of unused leave before they must take it — define your company's cap explicitly or you'll face a large payout liability
• Sick leave: up to 180 days per year under the Social Insurance Law, on a sliding pay scale (100% for first 90 days if insured)
• Unpaid leave: a written request + written approval, both timestamped
• Public holidays: Egypt currently recognises 13 official public holidays; overlap with annual leave must be stated explicitly

Keep templates in the employment contract, not only in an HR manual. Courts look at the signed document first.

Attendance Geo-Fencing: Configuration That Actually Works

Geo-fencing — restricting clock-in to a defined GPS radius — sounds simple until you deploy it in Cairo. A few hard-won lessons:

• Set the radius to at least 150 metres for urban offices. GPS drift in dense city blocks routinely runs 50–80 m, and a 100 m fence blocks legitimate punches.
• Allow an override workflow for field teams and client sites, with manager approval logged automatically.
• Log every failed attempt with timestamp and coordinates — this audit trail matters if you ever dispute a termination for attendance.
• Re-calibrate the fence if your office moves or you add a satellite location. A fence pinned to the old address silently fails from day one.

For multi-branch operations across Cairo, Alexandria, or Gulf subsidiaries, each branch should have its own fence polygon rather than a shared radius. See how multi-branch HR setups differ from single-office deployments if you're managing more than two locations.

Biometric Attendance Device Buyer Guide for MENA

The market is full of devices at wildly different price points. Here's what actually separates adequate from problematic:

Face Recognition

• IR vs. visible light: Infrared sensors work in direct sunlight — critical for any location with exterior access in Egypt. Visible-light cameras wash out between 10 AM and 3 PM.
• Liveness detection: Without it, a printed photo can punch someone in. Check vendor spec sheets for "anti-spoofing" or "3D face liveness."
• Template storage: On-device storage (typically 10,000–50,000 faces) is more reliable than cloud-only devices in areas with intermittent connectivity.
• SDK openness: If the device can only sync to the vendor's proprietary platform, you're locked in forever. Prefer devices with an open HTTP API or WSDL integration.

Fingerprint

• Optical sensors degrade with dry or calloused hands — common in construction and manufacturing. Capacitive sensors handle this better but cost more.
• Specify FAR (False Acceptance Rate) ≤ 0.0001% in your procurement brief.

General Checklist Before Purchase

1. Can it export to CSV or connect via REST API to your payroll system?
2. Does it store a local backup if internet drops?
3. What's the warranty and local service centre location in Egypt?
4. Is the firmware update path documented and free?

Payroll Reconciliation: A 10-Step Monthly Checklist

Reconciliation is where overtime errors, missed deductions, and ghost employees surface — if you're looking. Run through this before approving any payroll run:

1. Confirm headcount against active contracts (look for leavers still on payroll)
2. Pull raw attendance data and verify against approved timesheets
3. Calculate overtime per employee using basic salary only (see above)
4. Apply social insurance deductions: 11% employee, 18.75% employer on the insurable wage
5. Check income tax brackets against the latest Finance Ministry tables (updated periodically)
6. Reconcile any mid-month hires or terminations for partial-month proration
7. Match approved leave requests against deducted leave balances
8. Verify loan or advance repayments against the outstanding balance ledger
9. Cross-check net pay totals against last month ± known changes (a variance >5% without a business reason is a red flag)
10. Get dual approval (HR + Finance) and timestamp the sign-off before bank transfer

Where HR Software Fits Into This

Manual spreadsheets can handle steps 1–3 for a team of 20. At 60+ employees, the error rate climbs faster than the team does. Attendux — ProgMine's HR and attendance product — automates the overtime formula, feeds approved timesheets directly into payroll calculation, and flags reconciliation anomalies before you approve the run. The attendance module includes geo-fence configuration and supports most major biometric devices via API, which removes the manual export step that's responsible for a surprising share of payroll errors.

If your broader tech stack — ERP, CRM, finance tools — needs to talk to your HR system, that's worth a separate conversation about integration architecture. Custom software builds in Egypt sometimes make sense when off-the-shelf connectors don't cover your specific workflows.

One Practical Starting Point

Before evaluating any HR software, audit your current payroll for three months and answer: how many overtime hours were calculated on total pay instead of basic pay? How many leave balances don't match your attendance records? The gap between those numbers and zero is your compliance exposure — and the clearest argument for building a proper system before an inspector or a Labour Court case makes it urgent.

For a deeper look at what the latest Attendux feature updates cover — including flexible hour tracking and WPS export — that article walks through the specifics.

Ready to talk?

If you're working through payroll compliance, biometric procurement, or attendance policy for a team in Egypt or the wider MENA region, we're happy to compare notes. Reach out through ProgMine's contact page and describe your setup — company size, locations, current tools — and we'll come to the conversation with something useful rather than a generic demo script.