Picking an accrual method that doesn't match the policy document
When employees dispute their leave balances, the cause is rarely a bug. Your leave management software is usually doing exactly what it was told, and it was told the wrong thing during setup. Start with the accrual method, because every balance is built on it.
Most platforms offer three or four methods. Your contracts, handbook and local law assume one of them, often without saying so. If your policy reads "25 days per year" and nobody specifies how those days are earned, the implementer picks a default. That default is frequently front-loading.
| Method | How the balance builds | Where it goes wrong |
|---|---|---|
| Front-loaded (lump sum) | Full entitlement credited on the year start or hire date | Leavers have taken more than they've earned; recovering the overpayment may be restricted locally |
| Monthly accrual | 1/12 of the entitlement each month | Rounding on partial months; mid-month hires get a full or zero month |
| Per pay period | Credited with each payroll run | Breaks when pay frequency changes, for example weekly to monthly |
| Per hour worked | A ratio of leave hours per hour worked | Depends on clean timesheet data; overtime may or may not count |
Setting to check: the accrual frequency, the rounding rule (nearest half day, two decimals, or none), and whether accrual posts at the start or end of each period.
Question for the vendor: "Can different employee groups use different accrual methods within the same leave type, and can you show me the calculation trail for one employee's balance?"
Looking to streamline vendor RFP selection?
Access pre-negotiated tier discounts through our independent institutional network.
Starting accrual on the wrong date for new joiners
Start dates cause more disputes than anything else in the first year. Take a hypothetical company on a calendar-year policy with 20 days a year. Someone joins on 1 April, so a pro-rated balance is 15 days. If the tool front-loads on hire date without pro-rating, it shows 20, the employee books 20, and HR finds out at year-end.
Probation rules make this worse. Some employers block leave during probation but still accrue it. Others delay accrual altogether. Local rules differ widely. Many EU countries treat annual leave as accruing from the start of employment. Some Indian state shops and establishments acts set a minimum service period before earned leave can be taken. Several Gulf labor laws tie leave eligibility to completed service. A setting that's fine for your Dubai team may be non-compliant for your Dublin team, so confirm each country with local counsel.
- Check whether "accrue from" and "eligible to book from" are separate fields. They should be.
- Check how a hire on the 15th is handled: half a month, a full month, or nothing.
- Check that rehires don't inherit an old balance by accident.
Question for the vendor: "Can probation block booking without blocking accrual, and can that rule differ by country entity?"
Applying carry-over caps on the wrong date or not at all
Carry-over rules look simple: "up to five days carry into next year and expire on 31 March." In practice, three settings must agree: the reset date (calendar year, fiscal year or employee anniversary), the cap, and the expiry date for carried days. If one is wrong, balances jump on reset day.
The most common mistake is applying the cap to the total balance instead of to unused current-year entitlement. The second is carried days that never expire because nobody switched the expiry rule on.
Law matters here too. In the EU, the statutory minimum annual leave under the Working Time Directive generally can't simply be forfeited if the employer never gave the employee a real chance to take it. Some US states, California among them, prohibit use-it-or-lose-it policies. Other jurisdictions allow caps or require excess days to be paid out. One carry-over rule for every country will be wrong somewhere.
Setting to check: whether statutory and contractual leave can sit in separate buckets with different carry-over rules. That's the cleanest way to cap extra days without touching the statutory minimum.
Question for the vendor: "Show me a test employee's balance the day before and the day after year-end reset, including carried days and their expiry."
Pro-rating part-time staff in days instead of hours
Day-based balances work until days are different lengths. Take a hypothetical 40-person company where full-timers get 25 days of 7.5 hours, or 187.5 hours. A part-timer working 22.5 hours a week is 0.6 FTE and should get about 112.5 hours. If that person works three 7.5-hour days, 15 days is correct. If they work five 4.5-hour mornings, 15 "days" covers only 67.5 hours of absence, and they're short-changed.
For most companies with mixed schedules, hour-based tracking is the better choice because it handles uneven patterns without manual adjustments. The trade-off is that employees grasp days more easily, so pick a tool that shows hours and days side by side.
Watch mid-year pattern changes as well. A move from full-time to part-time should split the entitlement at the effective date, not recalculate the whole year. Irregular-hours and term-time workers need their own handling. The UK, for example, has a percentage-based accrual method for irregular-hours and part-year workers, and most tools support it only if you configure it deliberately.
Question for the vendor: "When a contract changes from 1.0 to 0.6 FTE on 1 July, what happens to the balance, and can I see the split?"
Looking to streamline vendor RFP selection?
Access pre-negotiated tier discounts through our independent institutional network.
Running one public holiday calendar for a multi-country workforce
A single company-wide holiday calendar is the quickest way to misstate balances for distributed teams. Public holidays vary by country and often within one: German states, Spain's autonomous communities, Canadian provinces, Australian states and Indian states all differ. Islamic holidays such as Eid move each year and are often confirmed only days in advance. Substitute-day rules for holidays falling on a weekend also differ.
These gaps hit balances directly. If a regional holiday is missing, an employee who books that week has an extra day deducted. Part-timers raise another question: do holidays count only on their working days, or are they pro-rated? Practice varies, and the tool must apply your chosen rule every time.
- Assign holiday calendars by work location, not legal entity. A remote employee in Bavaria employed by a Berlin entity needs the Bavarian calendar.
- Confirm who maintains each country and region's calendar: the vendor, a data feed, or your HR team.
- Decide how late-confirmed dates are handled, and make sure booked leave recalculates.
Question for the vendor: "Do you supply regional holiday calendars for every location we operate in? When a date changes, do existing bookings recalculate automatically?"
Lumping statutory absence types into one leave bucket
Annual leave is only one balance. Sick, parental, bereavement and study leave each carry their own rules, entitlements and payroll treatment, and often statutory pay. Log a sick day as annual leave, or the reverse, and both the balance and the payslip are wrong.
This is where basic PTO tracking software and full absence management software part ways. A PTO tool counts days off. An absence tool also tracks patterns, return-to-work steps, documents such as medical certificates, and pay rules for each absence type. If you have staff in countries with statutory sick pay or tiered sick-leave pay, you'll probably need the second kind.
Setting to check: each leave type should have its own entitlement, accrual and carry-over settings and its own payroll mapping. Confirm that one type can't draw from another's balance without approval.
Cost driver: standalone leave tools typically run about $1–4 per employee per month. Leave modules bundled into HRIS suites such as BambooHR, Personio, HiBob, Factorial, Zoho People or Keka generally sit inside packages of roughly $5–12 per employee per month. These are typical 2026 market ranges that vary by contract and region, so confirm pricing with vendors.
Migrating opening balances and changing policies without effective dates
Go-live is when spreadsheet errors get locked into the new system. Teams often import one "balance as of today" figure without splitting it into current-year entitlement, carried days and time taken. The first year-end reset then applies carry-over caps to the wrong numbers.
Policy changes cause the same trouble later. Say you raise entitlement from 20 to 22 days in July and the tool applies the new rule from 1 January. Everyone gains a day they shouldn't have. The opposite mistake is applying it only to new hires when the policy meant everyone.
- Import balances by component: entitlement, carried, taken, booked-future, adjustments.
- Reconcile 10–15 employees by hand before go-live, choosing edge cases: part-timers, recent joiners, people on long leave, and staff in different countries.
- Use effective-dated policy versions for every change. Never edit the live policy.
- Keep a manual-adjustment log with a reason code and the approver's name.
Question for the vendor: "Are policy versions effective-dated, and can you show an audit trail of every balance change for one employee?"
Ignoring the payroll link and the liability on termination
Leave balances become money when someone leaves. Many jurisdictions require accrued, unused annual leave to be paid out on termination; India's earned leave encashment rules, Gulf end-of-service settlements and payout rules in many EU countries are examples. Elsewhere, payout depends on the contract or state law. If the balance is wrong, the final payment is wrong, and that's the error most likely to become a formal dispute.
Accrued leave liability in your accounts works the same way. Finance needs balances that match payroll, not a separate figure in the HR tool.
| Check before go-live | What good looks like |
|---|---|
| Leave-to-payroll sync | Unpaid leave and statutory pay flow to payroll each period without re-keying |
| Negative balances | Capped or blocked by policy, with a clear deduction rule on exit |
| Termination calculation | Accrual stops on the leaving date and pro-rates correctly |
| Liability report | Balance in hours or days and in value, by entity and currency |
Question for the vendor: "Which payroll providers do you integrate with in each of our countries, is the sync two-way, and who owns fixing sync errors?"
Before you sign, give each shortlisted vendor three test employees: a mid-year part-time joiner, a carry-over case and a multi-country holiday case. Ask them to run all three through a year-end reset in a sandbox. A vendor that can't will probably be fixing it after go-live, at your cost. Have payout and carry-over rules for each country reviewed by local employment counsel before you finalize them.