You give notice before the math feels solid
Resignations often start with a date, not a finished calculation. Someone gives two weeks, opens the payroll portal afterward, and realizes the balance they counted on is harder to price than expected. Vacation hours may look earned, but the cash value can depend on rules outside the pay stub. That gap matters when rent, insurance, or a move is already timed around the last check.
In practice, notice usually goes in before the payout math feels settled. Accrued time may be treated like wages in one state and handled more narrowly in another, while company policy can add its own limits. A small mistake here is not abstract. Even one unpaid week of PTO can leave the exit month short.
The expected payout may not be guaranteed
What looks payable on the screen can still fall apart once the exit is processed. A PTO balance is only an estimate until two separate tests hold up: state law has to support payment, and the employer’s written policy has to avoid cutting it back. In review, this is where many assumptions fail. Workers often count every accrued hour at their current rate, then learn some hours were front-loaded, some were not yet vested, or the company distinguishes vacation from general PTO.
That difference changes cash planning fast. A person expecting an extra $1,200 may end up with half that, or nothing, if the policy allows forfeiture and state law does not block it. Timing adds another constraint. Even when payout is required, payroll may need a full cycle to convert hours, remove deductions, and issue the amount. By the time that shows up, moving costs or a first insurance premium may already be due.
State rules change the answer before policy does
By the time someone reaches the handbook, the bigger filter may already be outside the company. State law often decides whether unused vacation is treated like earned pay, whether forfeiture language can stand, and whether a payout must be included with final wages or handled later. That means the same PTO balance can produce different outcomes for two employees doing the same job in different states. From a review standpoint, this is the first place the estimate stops being portable. A balance that looked reliable in one move or one prior job may not travel to the next resignation.
The practical risk is simple: policy can only matter inside the room state law leaves open. If state rules are strict, an employer may have less room to deny payment. If state rules are loose, the written policy starts carrying more weight, and that is where surprises show up. Someone planning around an extra week of pay can come up short not because payroll made a mistake, but because the legal baseline was weaker than expected. That shifts the job from guessing the number to checking which rules control it before the final budget is built.
Your handbook can narrow what you collect
Once state law leaves room for employer rules, the handbook starts doing real damage to rough estimates. In review, the weak spots are usually small and easy to miss: payout applies only to vacation, not PTO; accrued hours are capped at a carry limit; balances disappear if notice is not worked in full; payment is limited to what is earned through the last completed pay period. Each line trims the number a different way. Someone leaving mid-cycle may think 64 hours are payable, then find the policy recognizes only 48, or excludes the newest accrual entirely.
The harder part is that these limits often sit across more than one document. A handbook may give the general rule, a PTO policy may define accrual, and an offer letter or manager practice may say something looser that does not control payroll. That gap creates planning risk. If a worker is using the expected payout to cover a deposit, loan payment, or insurance premium, even a modest reduction matters. Before relying on the balance shown in the system, it is worth checking the exact policy language that governs resignation, notice, and the type of leave on the books.
The last paycheck may arrive later than expected
Even after the payout amount looks defensible, the cash can still miss the date a worker has in mind. Final-pay timing is usually driven by payroll mechanics as much as policy. Regular wages, unused vacation, commissions, expense reimbursements, and benefit deductions do not always clear in one run. A resignation submitted just after payroll closes can push part of the money into the next cycle, especially if HR has to confirm the last day worked or recalculate accrual through the exit date.
That delay matters because bills do not wait for payroll cleanup. Someone expecting one larger final check may instead receive base wages first and any PTO payout later, or get a paper check when direct deposit is turned off at separation. Taxes can add another surprise by reducing the net more sharply than expected if the payout is bundled with other earnings. By this stage, the useful question is no longer only how much is owed. It is when each piece is likely to land, and whether the gap between resignation and receipt creates a short-term cash problem.
Small policy details can shrink the estimate
Once timing is already uncertain, the estimate itself can keep slipping for smaller reasons than most people expect. In review, the biggest cuts often come from policy mechanics rather than a flat denial. Some employers pay only earned vacation, not flexible PTO. Some convert hours using base pay only, leaving out shift differentials or bonuses that had been folded into a worker’s rough math. Others stop accrual on the last day of the prior pay period, not the resignation date the employee had in mind. A balance can look stable in the system and still produce a lower cash number when payroll applies the actual rule set.
The practical effect is usually a series of small reductions, not one dramatic surprise. Rounding rules, carryover caps, negative balances from advanced leave, required deductions, or a policy that wipes out unused time after a missed notice condition can trim the payout faster than expected. None of those details looks large alone. Together, they can turn a planned cushion into a narrow margin. By this point, the useful estimate is no longer the portal balance multiplied by hourly rate. It is the amount that survives the fine print payroll will actually use.
Verify the payout before you rely on it
At this point, the estimate is only useful if it survives verification. The practical check is narrow: confirm which leave category is on the books, whether state rules protect payout, what policy applies at resignation, and when payroll expects the money to be issued. If any answer stays verbal, the number is still weak. A balance that looks safe in the portal can fail once payroll applies a different document or a different cutoff date.
What usually helps is getting the rule and timing pinned down before building the exit budget around it. Ask for the written policy, compare it with the state standard, and request the expected payout treatment from HR or payroll in writing. That will not guarantee a perfect result, but it changes the decision from hope to something closer to a working number.
