People & Service module
HR-PAYROLL / MODULEHR & Payroll
Attendance-driven pay calculation with an immutable event trail and hard-coded separation of duties — no one approves their own leave or payroll run.
Attendance to Payroll
- 01
Track attendance
Per-day status and overtime are recorded through the period.
- 02
Apply leave
Approved leave automatically deducts from the employee's balance.
- 03
Calculate
Attendance-adjusted gross pay is calculated in one transaction, applying statutory components.
- 04
Approve
The run moves from calculated to pending_approval to approved — the preparer cannot approve their own run.
What it is
The Vercentlabs HR & Payroll module is a tenant- and company-scoped system of record for employee lifecycle, attendance and leave, and payroll processing, enforced through the same permission, audit, and separation-of-duties patterns as the rest of the platform.
Module atlas / operating conditions
Why HR & Payroll becomes difficult in fragments
Employee master data lives in spreadsheets
Basic employee records, reporting lines, and probation dates are tracked outside any system of record, with no single source of truth.
Manual leave-balance tracking
Leave balances are calculated by hand, and mistakes compound over a year of accrual and usage.
Error-prone attendance-to-pay math
Turning daily attendance into a correct payroll figure is manual and error-prone, especially with overtime.
No maker-checker on payroll or leave approval
The same person who prepares a payroll run, or requests leave, can also approve it — removing an important control.
Operating outcomes
What changes when HR & Payroll shares one system of record
One system of record for the workforce
Departments, designations, shifts, and manager hierarchy are structured, not scattered across spreadsheets.
Leave balances that update themselves
Balances deduct automatically on approval — no manual reconciliation.
Payroll calculated from real attendance
Gross pay is calculated in one transaction from attendance-adjusted data, not assembled by hand from multiple sources.
A payroll process you can defend in an audit
An immutable event trail and hard-coded separation of duties mean no one approves their own leave or payroll run.
Capability architecture
The module, decomposed by operating capability.
5 capability groups organised by the way the product works, not as a flat marketing feature wall.
Workforce structure
The organizational scaffolding employee records sit inside.
- 01Departments, designations, shifts
- 02Manager hierarchy
- 03Probation and confirmation dates
Attendance & leave
Daily attendance and leave, kept in sync automatically.
- 01Per-day status and overtime tracking
- 02Leave balances with automatic deduction on approval
Compensation & statutory setup
Pay structure and India-specific statutory compliance.
- 01Salary components with effective-dated history
- 02Jurisdiction-aware statutory components — PF/ESI/professional tax/TDS/gratuity/bonus
Payroll run processing
The governed run itself, from draft to posted.
- 01Draft-calculated-pending_approval-approved-posted lifecycle
- 02Attendance-adjusted gross-pay calculation in one transaction
- 03Self-approval blocked
Employee expenses
Expense records, exposed through the generic resource API.
- 01Employee expense tracking
Primary operating sequence
A transaction-level view of how work progresses through HR & Payroll.
See it work
Attendance to Payroll
The ordered process a real HR & Payroll workflow follows inside Vercentlabs.
Trigger
A payroll run is initiated for a pay period.
- Track attendance
Per-day status and overtime are recorded through the period.
- Apply leave
Approved leave automatically deducts from the employee's balance.
- Calculate
Attendance-adjusted gross pay is calculated in one transaction, applying statutory components.
- Approve
The run moves from calculated to pending_approval to approved — the preparer cannot approve their own run.
- Post
The approved run posts, with a manual accounting-batch reference for finance reconciliation.
Approvals
- 01Self-approval is blocked for both leave requests and payroll runs — hard-coded, not a policy document.
Automated actions
- 01Attendance-adjusted gross-pay calculation
- 02Automatic leave-balance deduction on approval
Connected modules in this workflow
Outcome
A posted payroll run with an immutable event trail and a manual accounting-batch reference ready for finance reconciliation.
Operational proof
HR & Payroll, documented as an operating system.
Capability architecture
5 groups
Grouped by how the module is actually structured.
Primary operating sequence
Attendance to Payroll
Rendered above as an ordered process rather than a feature collage.
Connected system
2 modules
Adjacent modules are linked through the operating model on this page.
Business outcome
One system of record for the workforce
Departments, designations, shifts, and manager hierarchy are structured, not scattered across spreadsheets.
Ready to see HR & Payroll running on your own data?
Book a DemoSystem map
HR & Payroll does not operate alone.
The handoffs below are part of the operating model, not decorative cross-sells.
A posted payroll run carries a manual accounting-batch reference field — a reference for reconciliation, not an automated GL-journal-posting call.
Output register
What HR & Payroll tells operators and managers
Active employees, on leave, new joiners, open payroll runs, latest net pay
Audience / HR managers, payroll preparers
Rule register
What the module can run on its own
Gross pay is calculated from real attendance data in one transaction, not assembled manually.
Balances deduct on approval without a manual reconciliation step.
Applies to both leave approval and payroll-run approval.
Control register
How HR & Payroll stays governed
Module-specific controls shown separately from the platform-wide security architecture.
HR and payroll actions are permissioned individually, not through one blanket HR role.
Prevents two people from processing the same payroll run simultaneously.
Every action is logged, and the preparer/approver split is enforced structurally.
What to plan before going live.
- 01
Department, designation, and shift structures are set up before employee data is migrated in.
- 02
Statutory components (PF/ESI/professional tax/TDS/gratuity/bonus) are configured per jurisdiction.
- 03
Leave policies and accrual rules are configured to match your actual policy before balances are migrated.
- 04
HR & Payroll is cataloged but explicitly excluded from the enabled mobile module list — no mobile access today.
Buyer questions
Questions teams ask about HR & Payroll
Can a payroll preparer approve their own run?
No — self-approval is blocked, hard-coded into the payroll-run lifecycle, not just documented as policy.
Does payroll posting automatically create a general-ledger journal entry?
No — a posted run carries a manual accounting-batch reference field for finance to reconcile against; there is no automated GL-journal-posting call found in the codebase today.
Is HR & Payroll accessible on mobile?
No — it's cataloged in the platform's module list but explicitly excluded from the enabled mobile modules, alongside Stock, as one of the two notable mobile-access gaps.