Inputs you need for Wage Backpay in Illinois
5 min read
Published April 15, 2026 • By DocketMath Team
Inputs you will need
Run this scenario in DocketMath using the Wage Backpay calculator.
To calculate wage backpay in Illinois (US-IL) with DocketMath, you’ll need inputs that line up with (1) what the employer should have paid you and (2) what you actually received, over an Illinois lookback period.
This guide is not legal advice—it’s a practical checklist for getting your numbers organized. Wage-backpay rules can depend on your exact facts and claim type, so consider confirming the right approach for your situation.
Core backpay inputs (minimum set)
Collect the baseline data first:
“Difference” inputs (to compute what’s owed vs. paid)
Next, enter the information needed to calculate the gap between entitlement and payment:
Optional inputs that improve accuracy
If you have these details, include them so the calculator can reflect the wage structure more precisely:
Illinois time-window input (default rule)
Your date range matters because Illinois applies a lookback period. In the jurisdiction data provided here, no claim-type-specific sub-rule was identified, so the default applies:
- General SOL period: 5 years
- General statute: 720 ILCS 5/3-6
Note: DocketMath’s wage backpay setup uses the 5-year general/default lookback where a more specific rule has not been identified for the claim type you’re modeling. If your situation falls under a special statutory scheme, the recoverable dates can change.
Where to find each input
You can usually pull most wage-backpay inputs from pay stubs, payroll portal exports, timesheets/punch logs, and employment documents (offer letter, handbook, pay plan).
| Input | Where to find it | What to capture |
|---|---|---|
| Pay period start/end dates | Pay stubs, payroll portal exports, employer remittance logs | Exact dates tied to each paycheck period |
| Wage type | Offer letter, employment agreement, handbook, payroll history | Hourly vs. salary vs. commission/piece |
| Hourly rate / salary amount | Offer letter, signed pay schedule, payroll system records | The rate(s) used for regular earnings |
| Regular hours worked | Time records, scheduling apps, timesheets, punch logs | Hours per pay period (or totals matching your date range) |
| Amount actually received | Pay stubs or direct deposit statements | Paid amounts for the wage categories relevant to backpay |
| Entitled amount (what should have been paid) | Your rate × eligible hours (plus any agreed components) | The computed “should have been paid” figures |
| Missed paychecks | Pay records and payroll confirmations | Dates and amounts of checks not issued |
| Partial payments | Pay stubs + bank statements (when needed) | Any amounts paid during the same dispute window |
| Overtime/differentials (if included) | Pay stubs showing earning codes, company payroll policy | The wage components to include/exclude and how they’re calculated |
Practical tip: If your payroll system lets you export CSV files, it’s often easiest to export:
- all pay periods within your target date range, and
- a parallel report of hours worked for those same periods,
so you don’t mismatch hours and payments.
Run it
After you’ve organized the inputs, you can run the calculation in DocketMath.
Enter the inputs in DocketMath and run the Wage Backpay calculation to generate a clean breakdown: Run the calculator.
When rules change, rerun the calculation with updated inputs and store the revision in the matter record.
Step-by-step in DocketMath (tool-focused)
- Open DocketMath → Wage Backpay:
/tools/wage-backpay - Enter your date range for the unpaid wages you want considered.
- Provide the wage structure:
- Choose your wage type (hourly/salary/commission or closest match)
- Enter the rate(s) and the hours worked for the relevant periods (or the totals, if you’re entering aggregate data)
- Enter what was actually paid:
- Add the amounts you received for the same periods (and wage categories, if prompted)
- Review how the time window is applied:
- With the default jurisdiction rule here, DocketMath uses the Illinois general/default 5-year lookback tied to 720 ILCS 5/3-6 when no claim-type-specific sub-rule was identified in the provided data.
How the outputs change when you change inputs
Understanding sensitivity helps you catch data-entry mistakes:
- Shorter date range: fewer pay periods → lower backpay total.
- Higher entitled rate or more hours: increases the gap between “owed” and “paid” → higher backpay.
- Including partial payments: reduces the difference calculation → lower backpay.
- Adding overtime/differentials correctly: can increase owed wages if those components are part of what you were entitled to during the period.
Quick self-check before you submit
Use this checklist to reduce avoidable errors:
Reminder: If your date range extends beyond the 5-year general/default window, the recoverable amounts may be limited. This checklist uses the provided default SOL approach tied to 720 ILCS 5/3-6, but it doesn’t confirm a full entitlement window for every possible claim type.