Year-End Leave Carryover and Payroll Close for HR

The three questions that land on HR's desk every December

Year-end leave carryover is one of those topics that returns every year with the same scramble. Employees ask how many days they have left, managers want to postpone leave because January will be busy, and payroll wants the numbers settled before the books close. If balances live in a scattered spreadsheet, all three questions arrive at once, and the answers contradict each other.

This article walks through how to handle leave balances at year-end, what the carryover decision actually depends on, and which checks to run before closing payroll. The goal is to turn closing week from a crisis into a routine job you planned for.

Carryover is a policy decision, not an automatic outcome

First, a distinction. Annual leave entitlement is usually triggered by each employee's hire anniversary, while 31 December is just a reporting boundary. A rule like "all balances reset on 31 December" rarely matches reality, because each person's entitlement moves on their own calendar. We covered the underlying calculation in how automatic annual leave accrual works by seniority.

What happens to unused days, however, is not something HR can decide alone. In many jurisdictions annual leave cannot be waived, the employer is expected to make it possible to take, and unused leave can turn into a monetary claim when employment ends. The exact rules vary by country, so agree on the carryover policy together with your legal counsel or accountant. Questions the policy should answer:

• How long may unused days be carried over, and is there a cap?
• By what date must leave be planned, and by when must managers approve the plan?
• Are there internal rules on splitting leave into blocks?
• When an employee leaves, how will carried-over days be valued, and at what pay rate?

This is general guidance, not legal advice; take the exact figures and deadlines from your own advisor.

Before closing: take a balance inventory

You need a reliable snapshot of "where we are today" before touching anything. Build this view for each employee:

| Field | Why it matters | | --- | --- | | Hire date | Determines the anniversary and seniority tier | | Total days earned | Current-year and carried-over days should be visible separately | | Days used | Should come from approved requests, not manual entry | | Pending requests | Requests still in approval will change the balance | | Days remaining | The number you will carry over or schedule |

The most common discrepancy in this inventory is unapproved or wrongly dated requests. A request sitting in approval at the end of December makes the remaining balance wrong. That is why a stuck approval chain matters more at year-end than at any other time; how the chain keeps moving when a manager is away is covered in delegation and escalation in HR approvals.

Carry over or schedule? Three common approaches

Companies usually deal with year-end balances in one of three ways:

1. Planned usage in December. HR lists employees with high balances in October and works with managers to place leave in the final weeks. Less balance reaches the close, but this is hard in sectors where winter is busy, such as restaurants and retail.
2. Written carryover. Days up to a defined cap move into the new period, and the rest is planned separately. Leave for January to March is agreed with the manager in advance.
3. A mix. Planned usage is encouraged first, and what remains is carried over in writing. For most companies this is the most sustainable approach.

Whichever you choose, the rule must not live in one email or in a manager's memory. It belongs in a written policy that employees can read, and the system balance should reflect it the same way.

Reflecting carryover in the system

Carryover inevitably involves manual corrections to balances: days moved into the new period, days removed by policy, or a difference inherited from an old record. Three principles help:

• Write the reason. Instead of "+3 days", leave an explanation such as "2026 carryover, policy section 4".
• Don't let automatic accrual overwrite it. When the new entitlement opens on the anniversary, your correction must survive; otherwise you redo the same work every year.
• Keep the change in the audit log. Who changed whose balance, and when, must be answerable later. We explain why in why audit logs matter in property and HR management.

In HR-Tech, annual paid leave entitlement opens by itself on the hire anniversary, approved leave is deducted from the balance automatically, and manual corrections are preserved. A carryover correction therefore isn't wiped at the next automatic calculation, and the audit log shows which user changed what and when.

Payroll close: the leave-side checklist

Payroll intersects with leave at several points at year-end. Before you close the final payroll run, check:

• Paid versus unpaid leave. Unpaid days must reach payroll correctly. They don't draw from the annual leave balance; they are a separate category.
• Leave across period boundaries. Leave starting on 28 December and ending on 3 January spans two payroll periods; it must be clear which days belong to which period.
• Employees who left. Have unused leave days for people who left during the year been settled in their final pay? For the whole exit process, see digitizing offboarding in HR.
• Public holidays and weekends. Check on a few sample employees that day counting treats holidays and weekends consistently.
• Consistency with timesheets. Overtime and absence data sent to payroll must not contradict leave records. Nobody should appear both "on leave" and "at work" on the same day.

The payroll calculation itself belongs to your accountant or payroll software; the HR system's job is to feed it correct, traceable input. How that data can flow across is compared in webhook vs API integration options for HR-Tech, and payslip delivery is covered in digital payslip distribution.

A year-end calendar: plan backwards

Instead of squeezing the close into the last week of December, build a calendar backwards:

1. October: Take the balance inventory and identify employees with high balances.
2. November: Plan leave with managers and publish the carryover policy.
3. First half of December: Resolve pending requests; leave nothing waiting in the approval chain.
4. Second half of December: Enter manual corrections with reasons and run the payroll consistency check.
5. First week of January: Spot-check new-period balances and tell employees their numbers.

The calendar only works if the reports exist. Which metrics deserve attention is covered in our HR metrics guide; for company-specific views such as the distribution of remaining balances, the custom report builder helps.

If you want a calmer year-end, keeping leave balances, approvals and the audit trail in one system does half the work. You can explore HR-Tech's leave entitlement, approval flow and audit log on the HR-Tech product page, and if you'd like to talk through how to move your current leave tracking over, get in touch.