Payroll · Pay Run
Run payroll from attendance you can audit.
Payroll is fragile when paid days are retyped and statutory calculations cannot be traced to the cycle.
This is a capability inside Lightning Pharos, not a separate product.
Open a pay cycle from approved attendance and leave.
01 · What ships
The complete working surface.
Statutory Indian payroll driven by attendance you can audit.
- 01
Earnings and deductions structured per employee, with a pay register per cycle
- 02
Paid days derived from real attendance and approved leave, not typed in at month end
- 03
Confirmed EPF, ESI, and professional-tax tables applied to the cycle
- 04
Approval, finance posting, and settlement states
- 05
Payslips per employee for the period
02 · Connected work
One action. One history. More than one team.
Pharos keeps the source action and the records it affects on one inspectable event path.
- 01 / 03
Source action
Open a pay cycle from approved attendance and leave.
- 02 / 03
Governed event
Earnings, deductions and statutory amounts resolve per employee.
- 03 / 03
Connected result
The pay register, settlement state and payslips remain tied to the cycle.
03 · What it needs
Ready inside every Pharos workspace.
No additional module is required before this capability can be switched on.
04 · Where it stops
The boundary is part of the product.
Monthly TDS and ECR are not supported. There is no Form 16, 24Q, gratuity, bonus, LWF, reimbursements, loans, advances, arrears, or external payroll connector.
Bring your exact workflow to a walkthrough and we will show where Pharos fits and where it does not.