Final Paycheck Deadline in Minnesota
Minnesota's final-pay clock runs from a written demand. A terminated worker who demands payment in writing is paid within 24 hours in most cases; without a demand, the deadline is the regularly scheduled payday. A worker who quits is paid by the next payday — or the second payday if the next one is less than five days after the last day, up to 20 days out.
The Minnesota clocks
| Situation | Deadline |
|---|---|
| Terminated, written demand made | In most cases within 24 hours of the demand |
| Terminated, no demand | Regularly scheduled payday; in some circumstances 24 hours without a demand |
| Quit or resigned, next payday 5+ days after last day | Next regularly scheduled payday |
| Quit or resigned, next payday under 5 days after last day | Second payday, up to 20 days after the last day |
| Current employee | At least once every 31 days |
The written demand is the lever
The 24-hour rule runs from a written demand. A terminated worker who wants the fast clock should demand payment in writing — email counts if it is written and kept — stating the last workday, the wages owed, and the demand itself, and should keep a copy with a delivery record. The Department's guidance says "in most cases," which means the 24-hour rule has exceptions the pages opened do not enumerate; the demand still starts the fastest clock available, and the regularly scheduled payday remains the fallback deadline either way. Do not rely on an oral demand: the record is what the investigator works from.
Deductions, rate changes, and the quit arithmetic
Two companion rules travel with the final-pay clock. Deductions from pay generally require the employee's voluntary written authorization — an employer may not deduct its way out of the final check without it. And changes to pay rates or paydays require advance written notice — a rate cut announced with the final check is not an advance notice. Both are Labor Standards complaint topics alongside the timing claim.
The quit arithmetic deserves a worked example. A worker whose last day is Monday the 5th, with paydays on the 1st and 15th: the next payday is the 15th, ten days out, so the deadline is the 15th. A worker whose last day is the 13th, with the next payday on the 15th — two days out, under five — moves to the second payday, the 1st of the next month, subject to the 20-day maximum. Count from the last day worked, not from the notice date.
Filing the claim
Contact Labor Standards at 651-284-5075 or dli.laborstandards@state.mn.us. Intake is by phone and an investigator reaches out within two business days. Provide the employer's details, rates, hours, deductions, pay dates, the last workday, and the demand date. The court route is preserved alongside the agency route under Minn. Stat. 177.27 subd. 8, 181.171, and 181.101.
For the complaint process in full, see How to File a Wage Claim in Minnesota. For other states, see the Final Paycheck Laws by State directory. For the calendar date, use the Final Paycheck Deadline Calculator.
Source
Sources: Minnesota Department of Labor and Industry, Labor Standards and Wage Claim pages (24-hour demand rule, quit and resign timing, 20-day maximum, 31-day rule, deduction authorization, advance-notice rule, phone intake and two-business-day contact, court-route statutes), read 2026-11-01. Facts verified 2026-11-01. Open flags: the "in most cases" and "in some circumstances" qualifiers on the 24-hour rule are stated on the Department pages without an enumerated exception list, and no exception list is asserted here; no agency filing deadline is stated on the pages opened, and none is asserted — the rules above are pay deadlines.
This page explains how the process works and what the official rules say. It is general information, not legal advice. For a dispute about your specific situation, talk to Minnesota Labor Standards or a lawyer.
Keep Exploring
Use the Workflow Library to browse more guides, comparisons, and integration examples to continue your evaluation.
See the solutions, comparisons, and integration guides collected in one place.
Review grounded audit, compare, fix-plan, and report excerpts before you wire the API into anything.
Jump from the workflow page into the quickstart, endpoint guides, and full OpenAPI reference.