Minutes, not days — and defensible afterwards
Inputs approved during the month, statutory computed on every run from versioned rates, and only exceptions surfaced for review. The artefacts come out of the run you approved.
Payroll & Compliance
The Run
Payable days from the register, salary structures by grade, arrears, mid-month joiners and increments handled by the engine.
Salary Structures & Pay Heads
Earnings, deductions and employer contributions per grade, with formulas you can read before you trust them.
Statutory Computation
PF with pension split and ceiling, ESI with its wage limit and period rule, state-wise PT, LWF in the right months, TDS across the year.
Payslips & Form 16 Inputs
Generated from the run and shared to the employee, not rebuilt in a separate template.
Bank Transfer File
In your bank’s format, from the same approved run.
Sealed Once Approved
Later changes are recorded as changes — which is what makes the register evidence.
The days go on inputs, not on the calculation
Ask a payroll team where the week went and it is never the arithmetic. It is chasing attendance corrections, unapproved claims, a salary revision somebody mentioned verbally, and a leave application that was never filed.
Klok approves inputs as the month runs. By the time the cut-off arrives, attendance is settled, claims are approved and revisions are recorded — so payroll day starts with data rather than with chasing. The computation itself takes minutes, because it always did.
Statutory computed, not typed
PF with the pension cap and admin charges, ESI with contribution-period stickiness, professional tax by the workplace state, labour welfare fund where it applies, TDS that is regime-aware and recomputed across the year rather than month by month.
Rates are versioned and dated, so a mid-year change applies from its effective date instead of retrospectively rewriting months that were already filed.
Only exceptions reach a human
A run surfaces what it cannot resolve: a missing punch, a negative balance, a structure that breaches the fifty-percent wages test, an employee whose statutory setup is incomplete. Everything else passes silently, which is the correct treatment for the ninety percent of a payroll that is unremarkable.
Once approved, the period seals. Later corrections appear as corrections.
Cut-off to credit
Inputs already approved
Attendance, leave, claims and revisions settled through the month rather than in the final week.
The run computes
Structures, pay heads and statutory applied from versioned, dated rates.
Exceptions surface
Only what cannot be resolved automatically is put in front of a person.
Approved and sealed
Payslips, bank file and statutory outputs generated from the same run, and the period locks.
Questions about payroll & statutory
Can we run payroll alongside our current process for a month?
That is exactly what we recommend during the trial. Compare both, then trust the software after it has agreed with you.
Is TDS handled properly?
It is regime-aware and computed across the year, with declarations and proofs held separately against the employee. Klok computes and produces; filing stays with you and your advisor.
What about employees paid a fixed monthly salary?
Fixed and attendance-linked grades run in the same payroll, with each treated under its own rules.
Can we run a parallel month before going live?
Yes, and we recommend it. Run your existing process and Klok on the same month and compare line by line. Cutting over without a parallel run is the decision teams regret most.
Does it file our returns for us?
It produces the filings — ECR, ESI, PT, 24Q, Form 16 — in the formats required, and a human at your end reviews and files. No Indian portal offers an e-filing API that would let anyone claim otherwise honestly.
What if we find an error after payroll is approved?
It is corrected as a documented adjustment in the next cycle rather than by editing a settled month. Rewriting history is how registers and filings stop agreeing with each other.
Can we switch this module off if we do not need it?
Yes. Modules are switched on per company and what is off is not billed. There is no bundle you have to buy through to reach the part you actually want.
Who can see this data inside our company?
Access follows the role you assign, and every company's data is isolated from every other company's by a boundary enforced in the software and covered by automated tests. Nobody at another company can reach yours.
See it on your own data
Fourteen days, no card, no consultant. Import your Excel and watch the first record draft itself.