How do you audit and correct employee PTO balances before switching to a new tracking system?

Freeze the rules before you touch the numbers

A balance is only meaningful relative to a policy, so the audit starts by writing down the rules as they were actually applied: accrual rate by employee class, when accrual started for each person, any waiting period, the cap, the carryover limit, and how sick time, vacation, and floating days were separated. You will often find that the written handbook says one thing and the spreadsheet did another for years. Decide which version is the truth going forward and note every place they differ. Related: Why does tracking employee PTO in a spreadsheet eventually break down for teams?

Pick a cutover date and freeze the old system as of that date. Everything before it gets reconciled in the audit; everything after it happens in the new system. Without a hard line, requests approved during the migration end up in both places or neither. Announce the date to the team so they know which system to use for a request that straddles it, and pause manual adjustments in the old file once the audit begins. Related: How can managers approve time-off requests fairly without leaving the team short?

Keep reading: Why does tracking employee PTO in a spreadsheet eventually break down for teams?, How do PTO accruals actually work and how should a small business set them up?, How can managers approve time-off requests fairly without leaving the team short?. See how LeaveLedgr helps you employee pto and leave balance tracking.

Rebuild each balance from its history

For each employee, reconstruct the balance from first principles: starting balance at hire or at the last verified point, plus accruals per pay period at the correct rate, minus every approved absence, plus or minus any documented adjustment, with caps and carryover rules applied at the right dates. Compare the rebuilt figure to what the old system shows. Small differences from rounding are normal; large ones point to a missed deduction, an accrual that did not stop during unpaid leave, or a cap that was never enforced. Related: How do PTO accruals actually work and how should a small business set them up?

Prioritize the employees where errors matter most: long-tenured people with large balances, anyone who changed from part time to full time, anyone who took an extended leave, and anyone in a state where balances must be paid out at separation. For a small company, rebuilding every balance is feasible in a few days. For a larger one, rebuild the high-risk group fully and spot-check the rest, then expand if the spot checks find problems. Related: Should a small business track sick time and vacation as separate leave balances?

Resolve discrepancies with employees, not at them

When the rebuilt balance differs from what the employee has been seeing, you have a choice. If the correct number is higher, correcting it is easy and welcome. If it is lower, an abrupt correction feels like a pay cut and can raise legal questions if the employee relied on the higher number. Many companies honor the displayed balance as of the cutover, absorb the difference, and fix the rule going forward. Others adjust downward with a clear explanation and a transition period. Either is defensible; silence is not.

Send each employee a statement showing the opening balance in the new system, the accrual rule that will apply, and a plain explanation of any adjustment. Ask for acknowledgment. This does three things: it catches errors you missed because employees remember absences you did not record, it creates a documented starting point that ends old disputes, and it builds the trust the new system will need. The audit is as much a communication project as a data project.

Load, verify, and run in parallel briefly

Load the opening balances as dated transactions with a note referencing the audit, not as silent starting numbers. Then verify the new system against the audit: run the first accrual and confirm every employee's balance moves by the expected amount, submit a test request and confirm the deduction, and check that caps and waiting periods trigger correctly. A short parallel run of one or two pay periods, where the old file is updated alongside the new system, catches configuration errors while they are still cheap.

After the parallel run, retire the old file for good and archive it read-only with the audit workpapers. Keep the reconstruction for each employee, the acknowledgment, and the configuration notes together, because the next audit or the next wage claim will start from them. A migration done this way is slower by a week or two and saves far more than that in disputes, and it gives you something the spreadsheet never had: a ledger where every balance can be explained line by line.