From clock-in to payroll without errors

Two days to payday. Someone downloads the clock-ins from the biometric clock, pastes them into a sheet and starts cross-checking them against leave requests that came by email and vacations written in a notebook. Absences show up on a holiday that was never loaded, a person who swapped shifts appears late all week, and a medical leave arrives after payroll has already been calculated. It’s fixed by hand, people get paid, and next month payslips have to be adjusted.

Almost none of those errors are calculation errors. They are process errors: data that arrives late, with no clear cut-off point and nobody confirming that the month is complete before calculating. This guide proposes a process with controls at each step, which you can apply even if you keep everything in spreadsheets.

Before you start: what this guide doesn’t cover

Payroll in Bolivia is regulated. Contributions, bonuses, benefits, deductions, withholdings such as RC-IVA, payment and filing deadlines, and any legal amount or percentage are deliberately left out of this guide. Legal parameters are set by your HR team or your labor advisor, who should also validate any change. Here we talk about process and control: how to make sure the data going into those calculations is correct.

The process in seven steps

1. Prepare the period calendar. Before the month starts, load working days and holidays (fixed ones, recurring ones and any declared during the year) and each person’s shifts. A missing holiday turns into absences for the whole staff.
2. Make sure clock-ins are complete. Review incomplete clock-ins daily or weekly: entries without an exit, exits without an entry, people with no mark on a working day. Fixing them at month-end, when nobody remembers, is where errors slip in.
3. Record incidents with supporting documents. Leave, vacations, permissions, shift swaps and time-off-in-lieu are recorded when they happen, with their supporting document and approval. What is agreed verbally doesn’t exist for payroll.
4. Generate the monthly summary. Per person: days worked, late arrivals, absences, leave, vacations and overtime according to the rules HR has defined.
5. Review, correct and confirm. Each department head reviews their team’s summary and HR confirms it. Every correction records who, when and why. Only the confirmed summary goes into payroll.
6. Calculate, review and approve payroll. Payroll is calculated from the confirmed summary, reviewed by someone other than the person who calculated it, and approved. Then the period is closed.
7. Reopen only in a controlled way. If a closed period must be corrected, it’s reopened with authorization, the reason is recorded, it’s corrected and closed again. No silently editing a file that has already been paid.

Controls by type of incident

Incident	Typical risk	Control
Holiday	Not loading it creates mass absences	Calendar loaded and reviewed before the period starts
Leave	Arrives after the calculation	Cut-off date for supporting documents and immediate recording
Vacations	Balances that don’t add up	Vacation ledger per person with opening balance, days taken and pending
Shift swap	False late arrivals	Swap recorded in advance, approved by the manager
Incomplete clock-in	Absence or lateness miscalculated	Periodic review and justification before the summary
Hire or exit during the month	Too many or too few days counted	Start or end date recorded before generating the summary

One simple control that catches most errors: the day reconciliation

Suppose a company with 40 people and a month with 22 working days according to its calendar. Expected person-days are 40 × 22 = 880.

The monthly summary must account for each of those days:

Concept	Person-days
Worked	830
Vacations	20
Leave	18
Absences	12
Total	880

If the total isn’t 880, there are unclassified or double-counted days. And look at the mix: if absences suddenly jump to 52, a holiday was very likely not loaded (40 people × 1 day = 40 absences nobody committed). This reconciliation takes minutes and is best done before confirming the summary, not after paying.

Monthly checklist

1. Period calendar with holidays and shifts loaded before the start.
2. Hires, exits and changes of position or department recorded with their date.
3. Incomplete clock-ins resolved and justified.
4. Leave, vacations and shift swaps recorded with support and approval.
5. Cut-off date communicated for the month’s incidents.
6. Monthly summary generated and person-day reconciliation done.
7. Summary reviewed by each manager and confirmed by HR.
8. Current payroll parameters validated by HR or the labor advisor.
9. Payroll calculated, reviewed by a second person and approved.
10. Period closed; any reopening with authorization and reason.

Indicators to track the process

Indicator	How it’s calculated	How to read it
Days to close payroll	Close date − last day of the period	If it grows, the bottleneck is usually the summary
Incomplete clock-ins	Unpaired clock-ins ÷ total clock-ins	High: device, location or habit problem
Summary corrections	Recorded corrections ÷ people	High: incidents arriving late or poorly defined shifts
Post-close adjustments	Corrected payslips ÷ payslips issued	Should trend to zero; each adjustment is an error that slipped through
Reopenings	Reopenings per period	More than one on a recurring basis means you close before reviewing
Pending vacation balance	Pending days per person	Balances growing unchecked are a liability and a risk

Common mistakes

• Calculating payroll from an unconfirmed summary and correcting on the fly.
• Having no cut-off date for leave and permissions.
• Loading holidays late or assuming the clock already knows them.
• Verbal shift swaps, which show up as late arrivals.
• One person calculates and approves, with no second review.
• Editing an already-paid period without reopening it or leaving a record.
• Copying legal parameters from an old payroll without HR or the advisor confirming they are still current.

If you want to automate it

This process works in spreadsheets, though it gets hard to sustain as headcount grows. A system like MKA can receive marks from the biometric clock, apply leave, vacations, holidays and shift swaps, and send only the confirmed monthly summary to payroll (see attendance).