Attendance lock: exception and recovery register
Even a well-run attendance month throws up odd cases: a punch that was never captured, a leave approved on a call, a request to change a closed month. This register keeps each exception in one place with its cause, its effect on pay and the step taken to recover. The timekeeper opens the entry, the HR approver and payroll officer close it.
When to use it
Open a line the moment an entry cannot be explained by a punch, an approved leave or an approved overtime slip. Use it before the lock to stop gaps being filled by guess, and after the lock to record every change that arrives late. If the same type shows up more than twice in a month, treat it as a process problem and not as bad luck.
The template
The first table lists the usual exception types with a standard recovery step, so people do not invent one each time. The second table is the log you add to every time.
| Exception type | Typical cause | Business effect | Recovery step | Owner | Evidence to attach |
|---|---|---|---|---|---|
| Shift not recorded | Device down or punch missed | Pay may be cut for a day worked | Get a manager's written confirmation and mark attendance | Timekeeper | Manager note, shift roster |
| Approval missing | Leave agreed by phone only | Leave balance and pay wrong | Get a signed request, dated to the actual approval | HR approver | Leave approval |
| Retrospective change request | Employee or manager asks to alter a locked month | Salary already paid may be wrong | Raise a regularisation, approve it, pay in the next cycle | HR approver | Regularisation form |
| Overtime without slip | Work done on the floor, slip not raised | Cost not authorised | Approve late with a reason, or remove the hours | Payroll officer | Overtime authorisation |
| Duplicate or clashing entry | Two sources entered for one day | Double count of a paid day | Keep the entry with proof and strike the other | Timekeeper | Both entries |
| Leave beyond balance | Request approved without checking balance | Unplanned unpaid days | Convert the extra days as per your leave policy | HR approver | Leave balance sheet |
| Ref | Date found | Employee code | Exception | Amount at stake (₹) | Owner | Next check | Resolution evidence | Closed on |
|---|---|---|---|---|---|---|---|---|
How to fill it
- Ref: number in order, such as AL-2025-10-01, so a line can be quoted in a message.
- Date found: the date you noticed it, not the date it happened.
- Exception and Amount at stake: write the cause in plain words and an estimate of the pay affected.
- Next check: a date when someone will look again, so the line does not sit.
- Resolution evidence: a reference to the document that justified the fix, not "ok".
- Closed on: fill only when the evidence is attached and the HR approver has agreed.
Whether a late change needs a particular form, notice or record is set by labour law. Check the current rule on the official portal or with your CA before acting.
Example row
| Ref | Date found | Employee code | Exception | Amount at stake (₹) | Owner | Next check | Resolution evidence | Closed on |
|---|---|---|---|---|---|---|---|---|
| AL-10-03 | 28 Oct | EMP-031 | Retrospective change: 3 days marked absent in September, employee says he was on approved leave | 2,400 | HR approver | 4 Nov | Signed leave form dated 14 Sep, regularisation RG-07 | 5 Nov |
Review and sign-off
- The HR approver reviews every open line each week and closes those with proper evidence.
- The owner reads the register at month end: count of lines, rupee amount at stake, and the types that repeat.
- Escalate to the owner when a line stays open past the next payroll, or when a locked month needs changing for more than a few people.
Keeping it up to date
- Add a new exception type to the first table whenever a case does not fit one.
- Keep the register and its evidence for the period your CA or the law requires.
- Once a quarter, look at the most common type and fix its cause, for instance a faulty device or a late leave habit.