Cross-module workflow
Hire to Payroll
An employee record moves through onboarding, compensation setup, and attendance tracking to an attendance-adjusted, maker-checker-governed payroll run.
- 01
Trigger
- 02
Work
- 03
Govern
- 04
Outcome
What it is
Hire to Payroll is Vercentlabs ERP's real, cited sequence connecting HR & Payroll and Accounting — attendance-adjusted pay is calculated in one transaction and a run cannot be approved by the person who prepared it, with a manual accounting-batch reference for finance to reconcile against.
Execution sequence
- Steps
- 07
- Modules
- 02
- Approvals
- 02
The real sequence, step by step
The runbook shows trigger, participants, each module handoff, approvals, automated actions, exceptions, visibility and business value in one continuous operating document.
Trigger
An employee record is created as part of onboarding.
Participants
HR manager/admin · Line manager · Payroll preparer · Payroll approver (a different person than the preparer)
- Employee recordHR & Payroll
Workforce structure — department, designation, manager hierarchy, probation/confirmation dates — is set at onboarding.
- Compensation setupHR & Payroll
Salary components and jurisdiction-aware statutory components (PF, ESI, professional tax, TDS) are configured with effective-dated history.
- Attendance and leaveHR & Payroll
Per-day attendance status and overtime are tracked; leave balances deduct automatically on approval.
- Payroll runHR & Payroll
A run moves through draft → calculated → pending_approval → approved → posted, with attendance-adjusted gross-pay calculated in one transaction.
- ApprovalHR & Payroll
A run cannot be approved by the person who prepared it — a different approver is required, enforced structurally.
- PayslipHR & Payroll
A posted run generates the employee's payslip.
- Accounting referenceAccounting
A posted run carries a manual accounting-batch reference field for finance to reconcile against.
Approvals
- 01A payroll run cannot be approved by the person who prepared it.
- 02Leave requests cannot be approved by the person who submitted them.
Automated actions
- 01Attendance-adjusted gross-pay calculation runs in one transaction, not a manual spreadsheet formula.
- 02Leave balances update automatically on approval.
Exceptions & honest limits
- 01Posting to the general ledger is a manual accounting-batch reference field, not an automated journal-posting call — finance reconciles against the reference, it isn't posted on their behalf.
Visibility
- 01A dashboard showing active employees, employees on leave, new joiners, open payroll runs, and latest net pay.
Business value
- 01Payroll you can defend in an audit — attendance-driven pay calculation with hard-coded maker-checker control.
- 02An immutable event trail on every action, not a paper sign-off sheet.
Handoff map
Every module involved, in operating order.
The workflow is deliberately shown as a chain of responsibility rather than a bag of features.
Buyer questions
Questions buyers ask about this runbook
Direct answers about how the sequence behaves, where controls sit and what a real deployment should expect.
Does a posted payroll run 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; this is a real, stated limitation, not an oversight in the copy.
Can the same person prepare and approve a payroll run to move faster?
No — a payroll run cannot be approved by the person who prepared it. This is enforced in the permission model, not left as a policy someone could bypass under time pressure.
Is HR & Payroll accessible on a phone for managers approving leave on the go?
No — HR & Payroll is cataloged in the platform's module list but explicitly excluded from the enabled mobile modules, alongside Stock. Leave and payroll approval are browser workflows today.
Related runbooks