Zoho People Consultant in Nigeria

Staff files that payroll and pension can rely on

A Nigerian staff file carries more than a name, job title and start date. Payroll needs the employee's tax identification, the state they live in, their pension fund administrator and account details, bank information and, in many companies, the guarantor who vouched for them at hiring. When these sit in a cabinet or a spreadsheet, the payroll officer chases them every time someone joins or moves.

In Zoho People I structure the record around those needs:

• Identity and tax fields with a format check, so a missing or mistyped number is caught at onboarding, not at remittance.
• State of residence as a controlled list, because personal income tax on salaries is generally administered by the state where the employee lives. Confirm the exact rule for your staff with your tax advisor.
• Pension details naming the administrator the employee chose, kept current when someone transfers.
• Guarantor and reference documents stored as attachments with a status, visible only to HR.
• Contract type separating permanent staff, fixed-term hires, interns and workers supplied through an outsourcing agency, since each follows different rules.

Outsourced staff deserve a decision of their own. Some employers keep them in Zoho People for attendance and site access only, while the agency handles their pay. Writing that boundary down early avoids a later argument about whose records are correct.

Public holidays declared at short notice

Nigeria's federal government announces public holidays through official statements, and some of them, including the Islamic festivals, depend on the sighting of the moon, so the exact day may only be confirmed shortly before. States can also declare their own work-free days. A holiday calendar typed in once at the start of the year will be wrong more than once.

Zoho People lets HR maintain holiday calendars by location, which matters when staff in different states observe different days. I set up a routine rather than a calendar:

• One calendar per state or site group, with the federal holidays shared across all of them.
• A named person in HR who adds or moves a holiday when it is announced, and a short checklist for informing managers.
• A rule for staff already on approved leave over a newly declared holiday, agreed with HR and your advisor, then tested.
• Shift rosters for depots, plants and security staff who work through holidays, with the holiday premium your policy grants recorded as an attendance flag for payroll.

Leave types come from your handbook: annual, sick, maternity, paternity where your policy grants it, study, compassionate and unpaid. Entitlements under the labor law and your contracts should be confirmed by HR or legal counsel. I test each type against a handful of real employees, including a mid-year joiner and someone returning from extended leave, before balances go live.

Attendance when the power goes off

Attendance capture assumes a working device and a connection. In Nigerian offices, depots and plants, electricity can come from the grid, a generator or an inverter at different times of day, and the network can drop with it. An attendance design that ignores this produces missing punches, angry staff and overtime claims nobody can verify.

I plan the capture method by location:

• Head office staff check in on the web or the mobile app, with the office network or location used as the check where your policy allows it.
• Depots and plants use a biometric or card device that Zoho People supports, connected to backup power, and checked for whether it stores punches locally and uploads them later. Confirm the device model and integration method with the vendor before buying.
• Field sales and drivers check in on their phones, with a rule for visits where signal is absent.

Every location then needs a fallback. If punches are lost, the supervisor files a regularization request with a reason, and HR sees a weekly report of how often each site relies on it. A site that regularizes constantly has an equipment or discipline problem, and the report makes that visible instead of hiding it in payroll adjustments.

Overtime and lateness rules come from your policy. I configure what HR confirms and test them with real rosters, including night shifts that cross midnight.

Feeding the payroll that handles PAYE and pension

Zoho People records the HR inputs; it does not compute Nigerian salaries. Zoho Payroll is offered in some countries only, so check with Zoho whether a Nigerian edition exists for your account before planning around it. In practice, PAYE, pension contributions and other statutory deductions are calculated by a local payroll provider, an outsourced bureau or a package your finance team runs.

The design work is the handoff between the two. Each month Zoho People produces a package the provider can load:

• Joiners and leavers with effective dates, plus changes to grade, location or state of residence.
• Unpaid leave days and approved overtime, already signed off by supervisors.
• Allowance triggers your policy ties to attendance, such as shift or holiday work.
• Pension and bank detail changes, flagged so the provider updates its own records.

Before the first live month, we run the export against the previous payroll and explain every difference. After go-live, a cut-off date and a sign-off by HR keep late changes from slipping in. Salary amounts themselves can stay outside Zoho People if you prefer, which reduces the number of people who can see them.

The accounting side, where the payroll journal lands in the ledger, is covered on my Zoho Books Nigeria page.

Staff data under the NDPA, and when to look elsewhere

Employee records hold exactly the kind of personal data the Nigeria Data Protection Act addresses: identity numbers, bank details, health information and next of kin. Your legal advisor or data protection officer decides what the Act means for your company. I make the configuration able to follow their advice: field-level access so managers see their team's leave but not salaries or medical notes, exports restricted to named HR roles, retention rules for leavers, and a record of where the Zoho account is hosted. Confirm the data center region with Zoho in writing and pass the answer to your advisor.

Zoho People suits Nigerian companies with office, depot and field staff that want one record and self-service. I would suggest something different when:

• Payroll and HR must come from one local vendor because finance wants statutory remittance schedules generated in the same tool.
• Most workers are outsourced or casual, and the real need is a workforce or contractor management system.
• The company is weighing several Zoho apps at once, where People is one part of a wider decision covered on my Zoho One Nigeria page.

For the wider picture see Zoho in Nigeria, the Nigeria ERP consultant page and the Nigeria hub, which explains how I work remotely.