Three days becomes twenty minutes
The inputs are already approved — attendance, leave, overtime, expenses. Klok computes the run, applies PF, ESI, PT, LWF and TDS, and shows you only the exceptions worth your attention. Payslips, the bank file and the registers come out of the same run.
Payroll, and the paperwork after it
The Run Itself
Payable days from the attendance register, salary structures by grade, arrears and mid-month joiners handled by the engine rather than by hand.
Salary Structures & Pay Heads
Earnings, deductions and employer contributions configured per grade, with formulas you can read and check before you trust them.
Statutory Computation
PF with pension split and ceiling, ESI with its wage limit, state-wise PT, LWF in the months your state deducts it, and TDS across the year.
Payslips & Form 16 Inputs
Generated from the approved run and shared to the employee — not rebuilt in a separate template afterwards.
Bank Transfer File
The payment file in your bank’s format, produced from the same run you approved.
Expenses & Reimbursements
Claims with the receipt read by AI, approved, and settled through payroll or separately. Travel and local conveyance included.
The three days are not computation
The arithmetic has never been the slow part. The time goes on gathering inputs — chasing attendance corrections, an unapproved claim, a revision somebody mentioned verbally, a leave application never filed.
Move the approvals into the month and the cut-off stops being a scramble. Everything that was going to be argued about has already been argued about, and the run itself takes minutes because it always did.
Statutory computed, not maintained
PF with the pension cap and admin charges, ESI with contribution-period stickiness, professional tax by the workplace state, LWF where it applies, and TDS that is regime-aware and recomputed across the year rather than month by month.
Rates are versioned with the date they take effect, so a change in October applies from October instead of retrospectively rewriting months you have already filed. Most statutory errors are not a misunderstanding of the law — they are last year's formula copied forward after a rate quietly changed.
Exceptions, not everything
Most of a payroll is unremarkable and should pass without a human looking at it. What deserves attention is the salary that moved oddly, the missing bank detail, the structure breaching the fifty-percent wages test, the incomplete statutory setup.
Reviewing thirty exceptions carefully is achievable. Reviewing three hundred employees carefully is not, and pretending otherwise is how errors get through.
Sealed, so corrections stay visible
Once approved, the period locks. A later change appears as a correction against a sealed period rather than quietly becoming the number that was always there — which is what keeps the payslip, the register and the return agreeing with each other afterwards.
Review, approve, pay
Inputs arrive approved
Attendance, leave, overtime and claims are already signed off during the month. Payroll day starts with data, not with chasing.
Only exceptions surface
Klok flags what looks wrong — a salary that moved oddly, a missing bank detail, a statutory threshold crossed — instead of asking you to re-check everyone.
Approve and it seals
Once approved, the run is locked and the artefacts are generated. Later changes are visible as changes, which is what an auditor wants to see.
Payroll questions we actually get
Can I trust the statutory numbers?
The rates and thresholds are held as versioned configuration with effective dates, and every computed figure can be traced back to the inputs that produced it. Klok does the arithmetic and produces the artefacts — filing, and responsibility for what you file, stays with you and your advisor.
We pay some staff on attendance and some on fixed salary.
Both work in the same run. A grade can be paid on payable days from the register, or a fixed monthly amount, with overtime and deductions applied per policy.
What happens when someone joins mid-month?
Proration is computed from the joining date, including for a mid-month increment, so the first salary does not need a manual adjustment.
Can I correct a run after approving it?
You can, and the correction is recorded as one. Nothing is silently edited after approval, because a payroll register that can be quietly changed is not evidence of anything.
How do arrears from a backdated increment work?
The period the arrears are about is tracked separately from the period they are paid in — the distinction most year-end reconciliations get wrong, and the reason a settled payslip is never reissued.
Can we pay some staff piece-rate or by production?
Variable pay is handled as rules rather than manual adjustments, and incentives are treated as wages for statutory purposes while penalties sit after. Getting that order wrong understates contributions.
Does it handle mid-month joiners and leavers?
Pro-rating is applied by rule, including the divisor question that quietly changes what a day of loss-of-pay costs. That divisor is a policy decision, not an arithmetic one.
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.
Take payroll day back
Run it once alongside your existing process and compare the two. That is what the free trial is for.