When is the last paycheck legally due — and what does being late cost? 258 rows covering all 51 jurisdictions (50 states + DC), each row carrying its statute citation and the date it was verified: 2026-10-26.
Free sample: exactly 3 complete states — California, Texas, Washington — full rows, no email required.
For every jurisdiction, the table states the deadline for a worker’s final paycheck in three situations, the penalty that applies when the deadline is missed, and the rule for paying out accrued, unused vacation. It is the dataset behind deadline logic in payroll and HR products: give it a state and a separation type, and it returns the due rule, the penalty mode, and the citation to check it against.
| Rule | Rows | Notes |
|---|---|---|
| Due when dismissed | 51 | Every jurisdiction. |
| Due when laid off | 51 | Every jurisdiction. |
| Due when an employee quits | 51 | Every jurisdiction. |
| Waiting-time penalty | 51 | Plus a separate quit penalty in 3 states (Missouri, New Mexico, Utah). |
| Accrued-vacation payout | 51 | Required, employer-policy, or law-is-silent, per state. |
| Total | 258 | 51 jurisdictions: 50 states + DC. |
Citations: statute citation text on 258 of 258 rows (100%). One honest limit: this table’s source dataset carries the statute section on every row but no citation URLs, so citation_url is empty on all 258 rows and no URL was invented. Look a row up by its statute section.
| Field | What it holds |
|---|---|
jurisdiction_code | Two-letter state code; DC for the District of Columbia. |
jurisdiction_name | Full jurisdiction name. |
rule_id | Which rule the row states. |
rule_statement | The rule in plain words. |
value | The typed value of the rule (a deadline type, penalty mode, payout code, band, or threshold text — the kind varies by rule). |
value_unit | What kind of value value holds. |
value_days | Day count for day-count deadline types; empty otherwise. |
effective_from / effective_to | ISO dates the stated rule takes effect or stops applying, where the source states one unambiguously. |
citation_text | The statute or code citation for the row. |
citation_url | Source link for the row, where the source dataset carries one. |
last_verified | Date the row was verified against its source. Release 2026.10: 2026-10-26 on every row. |
change_type | initial in this release; later releases use new / amended / repealed in the diff feed. |
Deadline values are typed codes (immediate, next_payday, cal_days, and nine more), penalty values are typed modes, and vacation values are one of required / policy / silent — so a product can branch on the value and display the plain-language statement. The full code lists ship in the data dictionary inside the package.
$550
One-time payment, per table. The complete current release in CSV + JSON, with data dictionary, changelog, and license.
$490/year
Per table, per year. The file, plus a change alert when a law changes — old rule to new rule — sent at signing, and a quarterly re-verification stamp.
$790/year
The Feed for both tables under one subscription. Buying both Feeds separately would be $980/year.
Redistribution, OEM, and VAR rights are not included in any offer above. Those rights are available on request — ask us at help@doogex.com.
Full text: the license page.
Every row was verified against the statute or agency publication named in its citation fields, and every row carries a last_verified date. Release 2026.10 was verified on 2026-10-26. The full method is on the How We Verify page.
CSV and JSON, same rows, same schema, in one package with a data dictionary, a changelog, and the license text.
The license covers one named product, or one organization’s internal work. Using the same table in a second product or for a second organization takes a further license. Redistribution and VAR rights are separate — ask us.
File buyers receive the release they bought. Feed subscribers receive a change alert when a law changes — old rule to new rule, with citation and effective date — sent at signing, plus a refreshed file and a quarterly re-verification stamp. Corrections are different from changes: a corrected cell is re-issued to every licensee of record, File and Feed alike.
No. These tables are reference data. Verify any cell against the cited primary source before relying on it, and take legal questions to a licensed attorney.