All-in-one HR platform · v2.0
14-day free trial · No credit cardhello@HrMagix.com
A correction to an attendance record raised against a specific day with a reason attached and routed for approval. The original capture is kept alongside the correction rather than replaced, because a ledger that can be overwritten is not evidence of anything.
Regularisation requests arrive daily and peak in the days before attendance cut-off, when employees fix missed punches, forgotten check-outs or on-duty days at client sites. The manager approves or rejects each one, and HR clears pending requests before payroll runs.
Example: an employee who spent the day at a client office shows as absent because they never punched in. They raise an on-duty regularisation, the manager approves it, and the day stops counting as LOP.
The common mistake is allowing unlimited regularisations, which turns the biometric record into a formality. Many companies cap the number per month and require a reason for each. In HRMagix, regularisation requests go through the attendance module to the manager for approval.
A correction to an attendance record raised against a specific day, with a reason, routed for approval.
No. The original capture is kept alongside the correction.
A ledger that can be overwritten is not evidence of anything.
Yes, it is routed for approval.
Yes, a reason is attached.
Yes, through self-service; applying is not approving.
If the day was worked, correcting attendance removes the basis for the unpaid day.
In Attendance & Shifts.
14-day free trial · Full access to all 12 modules · Zero implementation fee · Cancel anytime