Zoho People Consultant in Egypt

Arabic policies, bilingual records and who checks the wording

HR in Egypt operates in Arabic. Employment contracts, internal work regulations, warning letters and leave forms are normally Arabic documents, and employees expect to see their own names written correctly. At the same time, a regional parent, a foreign shareholder or senior management may read reports in English. Zoho People can support both, but the bilingual design has to be explicit.

The engagement runs in English, so responsibilities are agreed at the start:

• I specify the structure: which fields hold Arabic names, which hold English, which templates are Arabic only and which carry both languages.
• Your bilingual HR staff or a local partner write the Arabic: policy text, leave type names, letter templates and self-service labels.
• Native speakers test the output: right-to-left layout in printed letters and PDFs, name order, mixed Arabic and English records, and searches by partial Arabic name.

Interface language support in Zoho People should be checked screen by screen for the parts your employees will use, including the mobile app, rather than assumed from a feature list. Where a screen is weak in Arabic, we decide whether staff can use it in English, whether a short Arabic guide closes the gap or whether it is a reason to reconsider.

Policies themselves come from your HR team and legal advisor. I turn their final text into rules, not the other way round.

Plant shifts, Ramadan hours and holidays that move

Attendance rules in an Egyptian manufacturer or contact center can be intricate: rotating shifts, night work, weekly rest days that differ by department, and shorter working hours during Ramadan. Official holidays add another variable, because the government sometimes moves a holiday to a different weekday, and religious holidays move with the Hijri calendar, so their exact dates are often fixed only days ahead.

I keep each pattern separate in Zoho People:

• Shift templates per workforce group, with weekly offs set at the group level instead of per employee.
• Ramadan variants prepared in advance and switched on by HR when the month begins.
• A holiday calendar routine, with a named HR owner who updates dates when an official announcement moves them, and a checklist for informing plant supervisors.
• Device integration for attendance machines at plant gates, checked with the device vendor for compatibility and for how punches are stored during network interruptions.
• Sign-off by the shift supervisor for forgotten punches and extra hours, before anything is sent to payroll.

Overtime definitions, pay for night and rest-day work, and the Ramadan timetable are matters for your HR advisor under Egyptian labor law and your work regulations. I configure what they confirm and test it with sample rosters from real shifts, including shifts that cross midnight and holidays that fall on a rest day.

Onboarding files and the documents employers ask for

Hiring in Egypt involves a familiar stack of paper: a copy of the national ID, educational certificates, a criminal record certificate where your policy asks for one, a military service status document for male employees, a medical check and, for some roles, professional syndicate membership. Social insurance registration also needs the right details at the start. When this is tracked on paper, joiners begin work with incomplete files and HR spends months chasing them.

In Zoho People I turn onboarding into a checklist with owners:

• HR tasks: documents collected, contract prepared in Arabic, details passed to whoever registers the employee for social insurance.
• IT tasks: email account, system access and equipment.
• Line manager tasks: induction, safety briefing on plant floors, probation objectives.
• Document status fields so HR sees which files are complete and which are still missing a certificate.

Which documents you must hold, and for how long, is for your HR advisor to confirm, and requirements differ for foreign employees who need work permits. I build the checklist from your confirmed list and restrict access to scanned documents to HR. Performance cycles follow the same pattern: probation review tasks at the end of the agreed period, then simple periodic appraisals in forms that supervisors on the plant floor can complete.

Social insurance and salary tax stay with payroll

Zoho People manages HR inputs; it does not calculate Egyptian payroll. Social insurance contributions, salary tax and related filings are normally handled by a local payroll package, an outsourced provider or the payroll module of your ERP. Zoho Payroll is offered only in certain countries, so ask Zoho or the partner whether anything is available for Egypt in your account before designing around it.

The value of Zoho People here is a clean, approved monthly package:

• Joiners and leavers with effective dates, so insurance registration and exit forms are prepared on time by whoever owns them.
• Changes in grade, department or contract type.
• Unpaid leave, sick leave and approved overtime, already signed off.
• Deductions your approved work regulations allow, recorded with the decision behind them.

The first live month runs alongside the old method and every difference is explained. After that, a cut-off date and an HR sign-off keep late changes out of the run. Salary figures can stay outside Zoho People if you want fewer people able to see them.

Where the payroll journal enters the ledger, and how electronic invoicing affects finance, is covered on my Zoho Books Egypt page. If you are weighing several Zoho apps at once, the Zoho One Egypt page discusses licensing for large workforces.

Personal data, group companies and when to choose differently

Staff records contain national ID numbers, health information and family details. Egypt has a personal data protection law, and your legal advisor should interpret what it means for your company, including any conditions on transferring data abroad. I make the setup able to follow that advice: access by role, exports limited to named people, retention rules for leavers, and a written answer from Zoho on which data center region hosts your account.

Groups with several companies, sometimes including a free zone entity, need an early decision on whether all of them share one Zoho People account, how employees who move between companies are handled and who administers each. I document that structure before data is loaded.

Zoho People fits Egyptian companies with office, sales and plant staff who need self-service and one reliable record. I would suggest something different when:

• The workforce is very large and mostly shift-based, where a dedicated time and attendance system may handle rosters better.
• HR and payroll must come from one Egyptian vendor with social insurance forms built in.
• Employees need a fully Arabic experience and testing shows gaps you cannot accept.

For the broader picture, see Zoho in Egypt, my Egypt ERP consultant page and the Egypt hub, which explains how remote engagements with Egyptian companies are run.