Payroll check
Every finding shows the rule, the figures it compared and what to do. No score to trust. An AI summary is there if you want one.
What it checks
Flags a rise or fall of 25% or more, and names the cause: loss-of-pay days, one-off pay, a loan instalment or a change in gross.
Recomputes each with the rules for that month and flags a difference. This catches a run made before a rule change, such as the PF wage ceiling moving to ₹25,000 from September 2026.
No UAN for someone with PF, no ESIC number, no bank account or IFSC, and no work state for professional tax.
Two employees paid into one account is the usual sign of a duplicate or ghost employee.
Active employees with no payroll record, and people paid although their profile is not active.
Deductions as large as pay, more loss-of-pay days than working days, one-off pay as large as the salary, and no tax on a very high salary.
Example
Medium · illustrative example
Net pay fell from ₹45,000 to ₹27,000 (-₹18,000). Biggest driver: gross pay (-₹18,000). In detail: loss-of-pay days went from 0 to 9.
What to do: Confirm the cause is intended (a revision, leave, bonus or recovery) before finalising.
The figures above are an example, not a customer’s data.
No. It reads the processed month and reports findings. You decide what to fix and when to finalise.
No. Every finding, figure and reason comes from the rules, with or without AI. The AI summary is optional, off unless it is enabled, and asks for your consent each time.
Only the findings, with employee names replaced by labels such as Employee A. Bank details, PAN, UAN, email addresses and employee IDs are not sent.
Its answer is checked before you see it. If it contains a figure that was not in the findings, it is discarded and the rule-based summary is shown instead.
Not today. It checks PF, ESIC and professional tax against the rules. Income tax depends on each employee’s declarations, so it is checked only for large swings and for no tax on a very high salary.