USE CASE
Payroll inputs
Payroll runs on spreadsheets pulled from three different places. Deriving it from approved attendance removes both the assembly work and the errors it produces.
Where wrong pay comes from
Payroll accuracy is downstream of attendance accuracy, and most payroll errors are attendance errors wearing a different hat. A missed punch becomes an unaccounted absence; an unfiled regularisation becomes a loss-of-pay day; a half-day counted under the wrong convention becomes a deduction the employee did not expect.
The damage is disproportionate. A wrong deduction discovered on pay day is a trust problem before it is an arithmetic problem, and the correction costs more in goodwill than the amount involved. Meanwhile the ops lead spends the last week of every month assembling inputs from sources that disagree with each other.
How inputs get derived
- 01
Approved sessions are the base
Hours that a manager has already reviewed become the attendance input, so payroll is not the first time anyone looks at the month.
- 02
Leave and shift rules apply automatically
Leave types, balances, weekly offs, holidays and auto-lunch are configured once and applied consistently, rather than interpreted afresh each cycle.
- 03
Employees see their own unaccounted days
Before the cycle locks, the person can regularise a genuine mistake — which is far cheaper than contesting a deduction afterwards.
- 04
Sensitive fields stay protected
Pay and bank data are encrypted and access-logged, so the people who can see compensation are a deliberately short and auditable list.
What changes
- One attendance input instead of three spreadsheets that need reconciling.
- Loss-of-pay and attendance percentages derived from approved records, with your policy conventions applied consistently.
- Fewer wrongful deductions, because the employee saw the gap before payroll locked.
- An append-only access trail over sensitive pay data.
What this does not do
Workclave does not run payroll. It does not compute salary structures, PF, TDS or generate payslips, and it does not file returns. It produces the attendance, leave and overtime inputs your payroll system or provider consumes — exported as CSV or read through the API. If you are looking to replace a payroll suite, this is not that.
Payroll inputs — common questions
Which payroll systems does this work with?
Any that accepts a file or an API read. There is no direct connector yet — approved-session exports are shaped to drop into a payroll run without reshaping by hand, and the roadmap covers direct connectors.
How are loss-of-pay days calculated?
From approved sessions and leave records, using the divisor convention your policy specifies. The convention matters more than the arithmetic — the same two absent days deduct different amounts under a 30-day and a 22-working-day divisor.
Can employees see their attendance before payroll runs?
Yes, and that is the point. Visibility plus a regularisation window that closes before the cycle locks is what turns a would-be grievance into a correction.
Comparing payroll inputs tools?
A 20-person team pays ₹3,980/mo on Workclave. Side by side with:
Related
Votre équipe travaille. Commencez à comprendre comment.
Rejoignez les équipes qui suivent des sessions, pas seulement des heures. Gratuit jusqu’à 3 utilisateurs — sans carte bancaire, sans minimum, sans engagement.