Zoho People and Zoho Payroll: How Attendance Becomes a Payslip

Payroll disputes almost never come from a wrong formula. They come from a leave day counted differently in two systems, a joiner added in one place and not the other, or a shift that no policy actually described.

The directory is the integration

Both products read the same employee: the identifier, the joining date, the department, the reporting line, the location and the employment status. When that record exists once, a mid-month joiner appears in payroll automatically, an exit stops the salary without anyone remembering to say so, and a transfer between locations carries the tax consequence with it.

The most common estate mistake is treating payroll as a separate list maintained by finance. It works for a year, and it fails the first month someone leaves quietly.

Attendance, and the policies that make it unambiguous

Each of these is a configuration in Zoho People and a policy decision in the business. Where the two disagree, the software is nearly always following an older policy that nobody has revisited.

Leave, accrual and the balance nobody agrees on

Leave types in Zoho People carry their own accrual, carry-forward, encashment and approval behaviour. The questions worth settling explicitly are when accrual happens, whether it is pro-rated for joiners, what happens to unused balance at year end, and whether a negative balance is allowed at all. Every one of those has a defensible answer; problems come from having two answers in circulation.

The month-end lock

The single practice that removes most payroll disputes is a cut-off date after which attendance and leave for the period cannot be edited. Without it, an approval landing after the salary run creates a correction in the following month, and the payslip stops matching the attendance record it was built from. With it, the run has one version of the truth.

What Payroll adds on the statutory side

Salary structures are built from components with their own tax treatment, and statutory deductions and contributions follow the applicable rules for the location. What the product provides is the calculation and the reports; what it needs from the business is correct employee attributes — location, category, joining date and salary structure — because those are what the rules read.

Frequently asked questions

Can we run Payroll without People?

Yes, with inputs entered or imported each month. It works, and it moves the reconciliation burden onto the finance team every single cycle.

How are contractors handled?

Usually as a separate employment type with a different salary structure and no statutory components, kept in the same directory so headcount reporting stays whole.

What about employees across several locations?

Location on the employee record drives the holiday calendar and the statutory treatment, so a transfer is a field change rather than a new record.

Does timesheet data feed payroll?

Project timesheets in Zoho Projects answer a different question — profitability, not payable days. Keep them separate unless staff are genuinely paid by the hour.

Where to start

Take last month’s payroll and pick five employees at random. If you can trace each payable-day figure back to an approved attendance and leave record without opening a spreadsheet, the chain is working. If you cannot, that is where next month’s dispute will come from.

References

Topic inspiration: the HR and people coverage on the Zoho Blog. This article is Kelevo Software’s own analysis and wording, written from our implementation experience; no text has been reproduced from Zoho’s publications.