Pay & Benefits
Your PTO Balance Looks Wrong: Reconcile Accrual, Carryover, and Recorded Absences
Reconcile a disputed PTO balance across two payroll cutoffs, scheduled accruals, canceled leave and future reservations. A completed ledger and unsent correction request keep explained timing differences separate from an unresolved deduction.
Rebuild your PTO balance from a dated opening balance, then add earned credits and subtract the absences actually charged. Compare the same leave bank at the same effective date before requesting a correction. A paystub and an HR portal can disagree because they captured different moments; a difference that remains after aligning those moments needs a transaction-level explanation.
This guide from LandOffer.ai uses primary documentation checked October 27, 2026 and an entirely fictional employee record. It organizes an existing employee’s balance inquiry, rather than comparing job offers or calculating final pay. No employer account was accessed, payroll corrected, or message sent. The example’s accrual rate and posting rules are invented assumptions, not a statement of anyone’s legal entitlement.

Establish what each number represents
Save the balance label, units, effective date and capture date beside each number. “Available,” “earned,” “projected,” and “remaining” need definitions from your employer’s plan or administrator. A balance that reserves future approved leave will differ from a historical earned balance even when neither has an error. Do not assume that every system uses these labels consistently.
The Namely support explanation identifies a specific timing cause: payroll may be submitted before a scheduled accrual reaches the HRIS balance. It recommends comparing the plan’s accrual frequency with the payroll calendar and processing dates. This supports investigating timing; it does not establish that every mismatch will disappear at the next payday.
Ask which bank you are comparing. Vacation, combined PTO, sick leave, floating holidays and compensatory time can have separate balances and rules. A transaction charged to the wrong bank needs a classification review, not an extra credit entered without explanation. Keep a bank identifier on each ledger line, particularly if the portal presents a combined dashboard total.
Use hours throughout the reconciliation unless the administrator specifies another unit. In the example below, one workday equals eight scheduled hours. That is an explicit example assumption. An employee with a different schedule should use the hours applicable to the recorded absence, rather than multiplying every calendar day by eight. Keep displayed rounding separate from transaction precision, so a rounded screen value does not become a new adjustment in your ledger.
Collect the plan and transaction evidence
Start from the most recent opening balance that both sides accept. Obtain the applicable plan version and its effective date, then request the transaction history through the date under review. A screenshot shows a result; the history explains the credits, deductions and adjustments producing it. Preserve the original history before annotating a working copy.
For accrual, identify whether credits are based on elapsed service, eligible hours, completed pay periods or another written basis. Record the rate and when it becomes effective. A promotion, work-schedule change or service anniversary may be relevant only if the applicable plan changes the rate at that event. Do not apply a higher rate retroactively without a written basis.
For carryover, record the closing prior-year balance, the opening new-year entry and any separate adjustment. Do not add a carryover amount again if it is already included in the opening balance. An unexplained January reduction should remain a disputed transaction until its basis is resolved, rather than becoming an assumed lawful expiration in your spreadsheet.
The legal context matters here. The Department of Labor’s FLSA explanation says that the FLSA does not require vacation pay for time not worked and describes those benefits as a matter of agreement. That federal statement does not resolve state requirements. California’s vacation guidance, for example, distinguishes an accrual cap from forfeiture of earned vacation: its rules do not permit an ordinary use-it-or-lose-it forfeiture. The same California guidance applies its vacation rules to the combined PTO arrangements it describes; a separate sick-leave bank needs its own analysis. Do not turn a handbook entry into a conclusion about its enforceability.
For absences, match dates, hours, bank and transaction identifier against the approved request and any cancellation. Approval to take time off and a posted deduction are different events. A canceled request may still need a reversal; a pending future request may affect a projected figure without appearing in the historical ledger. Ask how the specific view treats each status.
Completed example: reconcile two payroll cutoffs
Fictional employee Mina is checking a combined PTO bank in October 2026. Her employer’s hypothetical plan credits four hours on October 15 and October 31. Payroll snapshots are taken October 12 and October 26. The closing September balance is 32 hours, already including all earlier carryover. There is no new carryover, cap event, rate change or rounding adjustment in this example.
Mina took eight hours on October 9. A separate October 23 four-hour request was canceled before the absence; nevertheless, a four-hour deduction appears in the downloaded history. She also has eight hours approved for November 6. The example’s portal reserves that future request when calculating “available,” while the paystub shows only posted earned and used hours at its snapshot date.
Here is the completed transaction reconstruction. A negative amount records a deduction. Its sign does not establish that the absence should have been charged.
| Effective event | Posted movement | Running posted balance |
|---|---|---|
| September 30 accepted closing balance | Opening 32 hours | 32 hours |
| October 9 leave taken | −8 hours | 24 hours |
| October 12 payroll snapshot | No movement | 24 hours |
| October 15 accrual | +4 hours | 28 hours |
| October 23 canceled request, still deducted | −4 hours | 24 hours |
| October 26 payroll snapshot | No movement | 24 hours |
| October 31 scheduled accrual | +4 hours | 28 hours |
The first comparison is a timing difference. The October 12 snapshot contains 24 hours. Immediately after the October 15 credit, the posted balance is 28. The intervening credit explains their four-hour difference. Mina therefore leaves this item out of her correction request. This conclusion depends on the supplied transaction dates and the stated snapshot definition.
The second snapshot also shows 24 hours, but that identical number has a different explanation. Starting at 24 on October 12, add four on October 15 and subtract the disputed four on October 23. The October 26 result returns to 24. Two identical paystub figures can make it feel as though nothing changed. Here they conceal a credit and the disputed deduction. Mina retains the canceled request and asks the administrator to explain why it was charged.
The portal’s October 31 posted balance is 28. Its hypothetical “available” figure is 20 because it also reserves eight hours for November 6. Comparing that 20 with the October 26 paystub’s 24 creates an apparent four-hour shortfall. Bridge the views explicitly: 24 plus the October 31 credit, minus eight reserved future hours, equals 20. The bridge explains the display comparison while leaving the canceled-request deduction unresolved.
If the administrator accepts that the canceled absence should not have been charged, a four-hour reversal would bring the October 31 posted balance to 32 and the available balance to 24. These are conditional correction targets. The article has not established that a real employer accepted a correction, nor that Mina can take additional leave without approval. Her next booking decision remains subject to the employer’s process.
The completed reconciliation thus separates three conclusions: the first difference is explained by timing; the second display difference is explained by timing plus a future reservation; the October 23 deduction still requires review. A single net difference cannot substitute for that separation. It could be zero even while two offsetting errors remain.

Turn the discrepancy into a focused correction request
Mina’s second completed asset is an unsent request based on that ledger. It names the disputed entry and preserves the already explained differences, so the administrator can investigate one question without receiving her full personal calendar.
Subject: Review October 23 PTO deduction — October balance reconciliation
Hi Payroll Team,
Please review the four-hour PTO deduction dated October 23, reference PTO-1023. My four-hour request for that date was canceled on October 21, and I did not take that absence. The cancellation confirmation and the relevant transaction-history extract are attached to this sample packet.
I used the accepted September 30 balance of 32 hours, the eight hours taken October 9, and four-hour accruals on October 15 and 31. The current history gives an October 31 posted balance of 28 hours. If the October 23 deduction should be reversed, my calculation gives 32 posted hours. The portal separately reserves eight hours for November 6, so the corresponding available balance would be 24 hours.
I understand that the October 12 and October 26 paystub snapshots use earlier processing dates. I am requesting review of the October 23 deduction, rather than treating those snapshot differences as missing accruals.
Please confirm the entry’s basis or the correction reference, the effective date, and when each affected view should reflect the result. If another team owns this bank, please direct this request to that administrator.
Thank you, Mina
The sample packet contains three items: the September 30–October 31 ledger, the October 23 deduction extract, and the October 21 cancellation confirmation. It excludes unrelated appointments, medical details, family travel arrangements and other employees’ leave. Those exclusions do not mean withholding a relevant fact from an authorized reviewer; they keep the first inquiry tied to the identified entry. Use your employer’s approved private channel for any records it actually needs.
Mina also marks the proposed reversal as pending in her working file. She does not insert it into the original downloaded history or call the balance corrected because she sent a request. A factual response may identify an overlooked adjustment or explain a different plan rule. Revise the reconstruction when supported evidence changes an assumption, retaining the earlier version so the change is traceable.
Verify the outcome in both views
If a correction is approved, request its amount, sign, bank, reference and effective date. Then compare the revised transaction history with the same dated reconstruction. A response saying “fixed” without an identifiable movement may leave the next payroll comparison just as confusing. A later accrual can also make the total rise without correcting the disputed charge.
In Mina’s hypothetical follow-up, a four-hour reversal dated November 2 is entered with reference REV-1023. She preserves the October 31 history at 28 hours and adds the new reversal to obtain 32 posted hours as of November 2, assuming no intervening movement. She does not relabel the original October 31 screenshot as though it always showed 32. The available view would be 24 while the eight-hour reservation remains.
That follow-up is an authored completion scenario, not a promise about retroactive posting or how a particular system updates paystubs. If payroll instead corrects an earlier effective date, keep the stated date and explain which historical reports were regenerated. Ask whether the next snapshot or a separate corrected statement is the expected evidence. Do not assume old downloadable paystubs automatically change.
When the disagreement concerns a policy’s applicability or a potentially unlawful loss of earned leave, separate that issue from data-entry troubleshooting. Keep the disputed transaction, applicable policy version, work location and administrator response. Seek the appropriate state labor agency, representative or qualified adviser for the unresolved rights question; a mathematically balanced spreadsheet cannot decide it. Preserve any applicable review deadlines rather than assuming an internal inquiry suspends them.
For more practical workplace guides, return to LandOffer.ai. Begin with one dated balance and one transaction history, calculate the bridge to the other display, and send a focused inquiry only for the unexplained movement. Keep the request open until you can match the administrator’s explanation or correction to a dated transaction. An acknowledgement alone leaves Mina’s four-hour question unresolved.


