People forget to punch. Phones die. The question isn't whether corrections happen — it's whether yours leave a trace.
Attendance regularisation is the process of correcting an attendance record that is wrong or missing, through a request that someone approves — rather than an edit someone makes. The distinction matters enormously at payroll time: an approved correction has a requester, an approver, a reason and a timestamp, so a disputed day can be reconstructed. A direct edit has none of those, and once it overwrites the original value, the evidence is gone.
In any team of thirty people, somebody will forget to check out this week. A phone will be dead at 9 a.m. Someone will go straight from home to a client site and remember at 11. If your process treats each of these as an incident requiring explanation to HR, two things happen: HR spends hours on trivia, and employees start not bothering to report problems at all. The register slowly diverges from reality, and nobody knows by how much.
The healthier framing: missed punches are expected, at a low but non-zero rate. Your job is to give them a fast, boring, traceable route back to correct — and to watch the rate, because a sudden rise is telling you something.
Most spreadsheet-based teams handle corrections by editing the cell. It takes four seconds and destroys the record. Compare what survives:
| Direct edit | The new value. That's it. No requester, no approver, no reason, no original value, no date of change. |
|---|---|
| Correction request | Original value, requested value, who asked, why, who approved, and when each of those happened. |
Now play out a dispute three months later. An employee says their March salary was short by a day. With a direct edit, you have one number and two opinions. With a correction request, you have a dated trail showing exactly what was changed, by whom, on what basis. The second conversation takes two minutes; the first can take a week and still end badly.
Never overwrite an attendance value. Add a correction on top of it and keep both.
Five steps, and no more:
Step 2 is the one teams get wrong most often. Routing corrections to HR turns HR into a bottleneck for information they do not have. The manager knows; HR only knows what the manager tells them.
Corrections need two dates:
What happens to a valid correction raised after the cut-off? It should be approved and applied to the next month's payroll as an adjustment, not squeezed into a run that has already been calculated. Re-opening a completed payroll to insert one day is how you end up with two versions of the same month and no idea which one was paid. State the rule in your attendance policy so the answer is known before the situation arises.
The obvious worry: what stops someone regularising every absence into a present day? Four controls, none of which require suspicion as a default posture:
If one person's correction rate is five times the team's, that is a conversation. If the whole team's rate jumped last month, that is a process or tooling problem — a confusing screen, a shift change, a site with no signal — and blaming individuals will not fix it.
Every correction changes payable days, and payable days drive pay. If corrections are approved after the salary is calculated, someone gets paid the wrong amount. If they are applied without a trail, you cannot explain the amount. If they are never applied at all, an employee is short-paid for a day they worked — which is the version that does the most damage to trust.
Handled properly, the chain stays clean: corrected attendance → recalculated monthly summary → payroll run → payslip, with each step traceable to the one before. That is the same chain described in connecting attendance to payroll, and corrections are the part of it most often left manual.
| What regularisation means | Correcting a missing or wrong attendance entry via an approved request rather than a direct edit |
|---|---|
| Typical request deadline | Within 3 working days of the affected date |
| Typical monthly cut-off | Around the 25th, after which attendance is frozen for payroll |
| Who should approve | The reporting manager — they know whether work happened; HR usually doesn't |
| Must be retained | Original value, requested change, reason, approver and timestamps |
| Late-but-valid corrections | Approve and apply as an adjustment in the next payroll run, don't reopen a completed one |
| Warning sign | A sudden rise in correction rate across the team — a process problem, not a people problem |
Attendance regularisation is the process of correcting an attendance record that is missing or wrong — a forgotten check-in, a missed check-out, or a day marked with the wrong status — through a request that a manager approves, rather than through a direct edit to the register.
A direct edit leaves only the new value. There is no record of what it was before, who changed it, when, or why. When an employee disputes a deduction months later, you have nothing to show them. An approved correction retains the original entry alongside the change and attributes it, so the day can be reconstructed exactly.
The employee's reporting manager. They have direct knowledge of whether the person was working on the day in question. Routing corrections to HR makes HR a bottleneck for information they do not have, and slows approvals to the point that employees stop raising them.
Three working days from the affected date is a common deadline. Recent memory is reliable, while corrections raised weeks later are reconstructions. Pair the deadline with a monthly cut-off, typically around the 25th, so the payroll run works from a stable set of attendance data.
Approve it and apply it as an adjustment in the next month's payroll rather than reopening a completed run. Reopening produces two versions of the same month and makes it unclear which one was actually paid. Write the rule into your attendance policy so it is decided in advance.
Require manager approval and a stated reason, and review a simple report of corrections per employee per month. Patterns become visible without anyone policing individual entries. If the whole team's rate rises at once, treat it as a process or tooling problem rather than a discipline issue.
Merik removes the largest category of wrong days rather than correcting them after the fact. Approving a work-from-home or leave request auto-stamps the attendance log for every date in the request — WFH becomes W, a half-day becomes H, and paid leave becomes OL — so the classic "approved leave recorded as absent" simply does not arise. Approved leave also blocks self check-in for that day, so the two records cannot contradict each other.
Where a day still needs changing, an admin edits it in the attendance grid. To be straight about the limits: Merik does not currently have the employee-raised, manager-approved correction request described above, and an admin edit replaces the previous value rather than keeping it alongside. If you need a correction trail for disputes, keep the requests in whatever system you already use for approvals until that lands.
The monthly summary recalculates from the corrected register, and that summary is exactly what the payroll run consumes, so no one re-counts payable days by hand after a correction lands. See the attendance and leave modules, the feature list, or how it works.
Every clause a working attendance policy needs, in plain language.
A clear, consistent rule set removes disputes and keeps payroll accurate.
Seven failure modes, the headcount where each one bites, and what to use instead.