Final-paycheck deadlines are not one rule with fifty exceptions. They split three separate ways at once: how fast payment is due, which varies enormously by state; whether being fired or quitting changes that deadline, which it does in some states and not others; and whether accrued vacation must be paid out at all, which follows yet another grouping of states. A manual check that learned one state's answer from experience and reused it elsewhere gets exactly the state that differs wrong.
| Step | Common mistake checking it by hand | What this calculator does |
|---|---|---|
| Assuming one payment-speed rule applies everywhere | Applying California's same-day rule (or New York's next-payday rule) to every state, when the actual range runs from same-day (CA, CO, MA, NV) to a fixed number of days (TX, MT) to next-payday-only (NY, WA, IL). | Applies the specific rule for the state you select, with its own citation. |
| California's notice-dependent quit rule | Treating every voluntary quit in California the same way, missing that 72+ hours' notice moves the deadline to the last day worked while no notice leaves it at 3 calendar days. | Asks whether notice was given and applies the correct one of the two rules. |
| Minnesota's demand-triggered clock | Missing that Minnesota's fast 24-hour deadline only starts once the employee makes a written demand -- without one, the ordinary next-payday rule applies instead. | Asks whether a demand was made and applies the 24-hour clock only when it was. |
| Vacation/PTO payout requirement | Assuming the payout rule follows the same state grouping as the payment-speed rule, when it does not -- Texas and Nevada have fast payment deadlines but leave vacation payout to employer policy, while Illinois requires payout regardless of policy. | Reports the payout requirement for the selected state independently of its payment-speed rule. |
| Is anything I enter uploaded anywhere? | N/A | No. The calculator runs entirely in your browser; nothing you enter is sent to a server. |
The first row is the calculator's own shipped "load an example" scenario -- open the calculator and click it to see the same numbers.
| Scenario | Deadline | Vacation/PTO payout required? |
|---|---|---|
| California, voluntary quit, no 72-hour notice, separated Oct 1, 2026, 40 accrued hours at $28/hour | Sun, Oct 4, 2026 (3 calendar days after separation) | Yes -- $1,120.00 at the hours/rate entered |
| Same facts, but 72+ hours' notice given | Thu, Oct 1, 2026 (the day of separation) | Yes -- California requires it regardless of notice |
| New York, fired/laid off, separated Oct 1, 2026, next payday Oct 10, 2026 | Sat, Oct 10, 2026 (the next regularly scheduled payday) | No -- New York leaves it to employer policy |
Three days apart on payment speed, three days apart again once notice changes, and a payout answer that has nothing to do with either. A hand check that got the first row right by applying "3 days" has no way to know the second row is "same day" unless it separately remembered the notice carve-out, and no way to know the third row's payout answer without separately checking that New York's rule, unlike California's, leaves it to the employer.
No, and the range is wide. California, Colorado, Massachusetts, and Nevada require same-day or immediate payment for a firing or layoff. New York, Washington, and Illinois require only the next regularly scheduled payday -- no shorter statutory deadline at all. A manual check that learned the rule from experience in one state and applied it to an employee in another gets it wrong in either direction: too strict where the actual rule is looser, or too late where it is stricter.
Yes -- whether the employee gave at least 72 hours' notice before quitting, and this is the detail most likely to be missed by hand. An employee who gives 72+ hours' notice must be paid on their last day worked, the same as a firing. An employee who quits without that notice has 3 calendar days instead. Treating every voluntary quit in California the same way, regardless of notice, gets one of the two cases wrong.
Because the rule genuinely splits by state with no obvious pattern tied to the payment-deadline rule itself. California, Colorado, Massachusetts, Montana, and Illinois require accrued unused vacation to be paid out as wages, with no use-it-or-lose-it forfeiture. New York, Washington, Texas, Arizona, Nevada, and Minnesota leave it entirely to employer policy -- there is no state mandate either way. A manual check that assumes the payout answer follows the same state grouping as the payment-speed rule will get several states backwards, since the two rules do not track each other.
That the fast deadline is triggered by a written demand, not by the firing itself. Without a demand, a fired Minnesota employee's wages are due on the next regular payday, the same as most states. Once the employee makes a written demand for payment, the employer has only 24 hours from that demand. A check that applies the 24-hour clock to every Minnesota firing, or misses that the clock exists at all, gets the deadline wrong depending on which half it skipped.
No. This is a payment-timing and vacation-payout lookup, not a full wage-and-hour determination. It does not determine which state's law actually governs (usually the state where the work was performed, which can differ from where the employer is headquartered), does not model city or county ordinances that can be stricter than state law, and does not cover commissions, bonuses, or expense reimbursement rules.