Payroll That Reads Attendance and Leave Automatically

It is the twenty-sixth of the month. The accounts officer, Farida, has the salary sheet open and a list from the office of who was absent. The list says Mr Okafor took two days unpaid in the second week. The leave register, which sits in a different drawer, says three. The head of science remembers approving a half day for Ms Lindqvist that appears on neither. Farida has to choose which version to believe, and whatever she chooses, somebody will be at her door on payday.

None of this is a payroll problem in the arithmetic sense. The calculation is simple. The problem is that payroll is being fed by a copy of the truth rather than the truth itself, and copies drift.

Where the numbers actually come from

A teacher's monthly pay is usually built from a handful of inputs: the basic salary, fixed allowances, variable allowances such as extra duties, deductions for unpaid absence, loan instalments, and whatever statutory deductions apply where the school operates. Of these, the ones that change every month and cause disputes are the attendance-driven ones.

In most schools those inputs pass through at least two hands before they reach payroll:

• The teacher applies for leave, on paper or by message.
• A line manager approves it, sometimes verbally.
• The office records it in a register or spreadsheet.
• Someone compiles a monthly summary for accounts.
• Accounts keys the summary into the salary sheet.

Every handover is a chance for a day to be lost, doubled or reclassified. The fix is not more careful copying. It is removing the copying, so the deduction is calculated directly from the approved leave and the attendance record.

What "reads attendance" should mean in practice

When people say payroll should read attendance, they mean a few specific things:

1. Approved leave carries its type. Paid annual leave, sick leave and unpaid leave are recorded as different types when they are approved, not sorted out at month end.
2. Absence without approved leave is visible. A day marked absent with no matching leave is flagged for a decision, rather than silently deducted or silently ignored.
3. The deduction rule is set once. Whether an unpaid day is a thirtieth of the monthly salary, a share of working days, or something else, the rule is agreed and applied the same way to everyone it covers.
4. Late approvals are handled deliberately. Leave approved after payroll has closed lands in next month's run as an adjustment, with a note, rather than being forgotten.

With those four in place, the salary sheet stops being a document Farida assembles and becomes one she reviews.

Setting the rules before the first run

The technical part of connecting attendance to payroll is the easy part. The harder part is agreeing rules that were previously decided case by case. Before the first connected run, settle these with the principal and the bursar:

• Leave types and whether each is paid. Include the awkward ones: compassionate leave, study leave, leave during school holidays for staff on term-time contracts.
• The cut-off date. Pick a day, such as the twentieth, after which leave affects next month. Publish it to staff.
• How half days count. Decide once whether a half day is half a day's pay or something else.
• Who resolves unexplained absence. One named person, with a deadline, so the flag does not sit unresolved into payday.
• Statutory deductions. Tax, pension and social-security contributions differ by country and sometimes by region. Configure them to the rules that apply to your school and have a local adviser check them before you rely on the output.

Write these down. A one-page payroll policy that staff can read prevents more disputes than any system.

Running the month in a connected setup

Consider a school of sixty staff where leave is requested and approved in the same system that runs payroll. Month end then looks something like this:

1. Day 20: cut-off. Line managers clear any pending leave requests.
2. Day 21: the payroll officer opens the draft run. Unpaid leave and absences already appear as deductions against the right people.
3. Day 22: the exception list is reviewed: absences with no leave attached, staff who joined or left mid-month, changes to allowances.
4. Day 23: the bursar compares the total against last month and asks about any movement that is not explained.
5. Day 25: the run is approved, payslips are issued and the bank transfer is prepared.

The point of the exception list is that review time goes where it is needed. Fifty-five staff with ordinary months need no attention. Five need a decision.

Comparing the two approaches

Handling the disputes that still happen

Even with connected records, a teacher will occasionally say a deduction is wrong. The difference is what happens next. Instead of a search, the payroll officer opens the person's leave history for the month and shows the approved request, the date it was approved and the type it was approved as. If the type was wrong, the correction is made on the leave record and flows through as an adjustment, with the original kept for the audit trail.

Two habits help here. First, make sure staff can see their own leave balance and history before payday, so most disagreements surface while they are still cheap to fix. Second, never correct a deduction directly in the salary figure while leaving the leave record unchanged. That recreates exactly the drift you set out to remove.

Common mistakes

• Connecting the systems but keeping the paper register. Two sources of truth guarantee a third argument. Retire the old register on a fixed date.
• No cut-off. Without one, leave approved on the twenty-ninth either changes a run already sent to the bank or disappears.
• Treating every absence as unpaid. Unexplained absence should be a question, not an automatic deduction. Teachers forget to submit requests; that is a conversation, not a penalty.
• Assuming statutory settings are correct because they produce a number. Check deductions with a local adviser, especially after any change to the rules where you operate.

Where to go next

This post covers one link in the chain. The complete guide to school HR and payroll shows how personnel records, leave, loans and appraisals fit around it. In Scolvia, payroll reads the attendance and approved leave the institution already keeps, so unpaid leave comes from the register rather than from a list someone prepared. You can see how leave is requested and approved against balances on the staff and HR page.