A step-by-step approach to recording attendance accurately every day — and why spreadsheets quietly cost you money at payroll time.
Attendance is the foundation of payroll. If the record of who worked which days is wrong, everything downstream — pay, leave balances, overtime — is wrong too. Yet most small businesses still track attendance in a spreadsheet or a group chat, then re-type it at month-end. Here's a cleaner way, from what to capture each day to how it becomes a correct pay run.
A spreadsheet works fine for five people in one office. It breaks down the moment you have real-world complexity:
None of these are visible on any single day. They surface all at once at month-end, when a payslip is wrong and nobody can reconstruct why. The cost isn't just the correction — it's the trust you lose with the employee whose pay was short.
Good attendance data is specific. For each employee, each working day, capture:
Record it once, at the source, on the day it happens. Every time attendance is re-entered later, accuracy drops.
Vague attendance ("in" or "out") can't drive payroll. A small, consistent set of statuses can, because each one has a defined effect on the monthly pay calculation:
The distinction that matters most for money is paid vs unpaid. Only absent days, unpaid leave, and the unpaid half of a half-day should reduce a salary; everything else is a paid day. Getting this mapping right once — and applying it consistently — is what keeps payroll defensible. We break the tricky cases down in calculating late marks and half-days fairly.
Self-service removes the HR bottleneck and gives people ownership of their record. Employees mark entry and exit; managers only step in for exceptions. When someone checks in from their own phone with a timestamp (and, for field roles, a location), you also get a record that's far harder to fake than a name written into a shared sheet.
Instead of chasing every person, look at a live daily view and act only on the anomalies — who's absent, who's late, who's on half-day. On a 30-person team that's usually two or three names a day, not thirty.
Approve paid and unpaid leave in the same place, so monthly totals stay accurate without reconciling two systems. When a leave request is approved, the matching days should update on the attendance record automatically — so an approved leave can never quietly show up as an absent day at payroll time.
This is the payoff: at month-end, payroll should be calculated from the attendance and leave you already captured — not re-typed. We cover this in detail in From attendance to payroll.
Clean attendance isn't about the ordinary days — it's about having a rule ready for the awkward ones before they happen:
The reason you record all of this is a single, trustworthy monthly number per person: total working days, days present, paid leave, unpaid leave, and the resulting paid days. If that summary is generated from the same data employees marked each day, there's nothing to reconcile — the month simply adds up. If it's re-typed from a spreadsheet, every month is a fresh chance to introduce an error into someone's salary.
Broadly there are three methods: manual (a register or spreadsheet), biometric (a fingerprint or face device at a fixed location), and app-based check-in with a timestamp and optional GPS. Each suits a different kind of team — a single-office shop, a factory floor, or distributed field staff. We compare the trade-offs in biometric vs GPS vs manual attendance. Whichever you choose, the principle is the same: capture it once, at the source, in a form payroll can read directly.
The most reliable way is a single system where employees mark entry and exit each day with a status (present, absent, late or half-day), so records are captured once and flow directly into monthly payroll — instead of being re-typed from spreadsheets or chat messages.
Record the date, entry and exit time, a status such as present, absent, late or half-day, and any remarks. Track paid and unpaid leave separately so monthly summaries stay accurate for payroll.
Spreadsheets are edited by hand, so they drift out of date, get copied incorrectly between months, and have to be re-keyed into payroll — which introduces errors and wastes hours every month.
Only unpaid statuses reduce a salary: absent days, unpaid leave, and the unpaid half of a half-day. Present, late, work-from-home and approved paid leave all count as paid days. Keeping paid and unpaid clearly separated is what keeps the monthly pay calculation correct.
Decide in advance whether remote work is marked as WFH or Present, and tie leave approval to the attendance record so approved days update automatically. That way an employee on approved leave is never counted as absent at payroll time.
Merik gives every employee a dashboard to mark their own attendance and request leave, while HR gets a live company-wide view and a full monthly summary for each person. Approved WFH and leave update the attendance record automatically, corrections stay visible, and because attendance, leave and payroll share one dataset, the numbers you record each day flow straight into monthly pay — no spreadsheets, no re-keying. See the features or how it works in three steps.
Two guides on the systems most small businesses are moving away from: why the Excel sheet breaks and why the WhatsApp group fails.
A practical comparison of the three ways small businesses capture attendance today.
Seven failure modes, the headcount where each one bites, and what to use instead.
How connecting attendance and leave directly to payroll removes errors.