Spreadsheet checks before running Wage Backpay in Idaho

What the checker catches

Before you run Wage Backpay calculations in Idaho, DocketMath’s spreadsheet checker helps you catch the errors that most often cause wrong backpay totals—especially when the spreadsheet is missing dates, misreading units, or applying the wrong lookback window.

In Idaho, the default legal time window for claims is the general statute of limitations (SOL) period: 2 years, under Idaho Code § 19-403. The key point for your spreadsheet is this: use the general/default 2-year SOL period unless you have a claim type with a different limitation period. Your jurisdiction data indicates no claim-type-specific sub-rule was found, so the checker assumes the general SOL applies.

Here’s what the checker is designed to flag in a Wage Backpay spreadsheet:

• Missing or malformed dates

  • “Work performed on” dates are blank or not entered
  • Pay dates entered as inconsistent text (e.g., “01/15/24” stored differently by rows)
  • End date earlier than start date (a common copy/paste issue)
• SOL window mismatches

  • The lookback window is larger than 2 years
  • The lookback is anchored to the wrong reference date (for example, using “today” instead of the workflow’s case-relevant start date)
• Inconsistent pay frequency / period units

  • Weekly rows mixed with biweekly rows without normalizing to the same unit
  • Hourly wage entered as a whole number when the spreadsheet expects decimals (e.g., “15” vs “15.00”)
• Bad math structure

  • Hours and rate columns swapped
  • Overtime multipliers applied where they shouldn’t be
  • “Total earned” and “total paid” columns double-counting
• Row-level gaps

  • Days/weeks with zero entries that should have been populated
  • Duplicated date ranges that inflate totals
• Output sanity issues

  • Negative backpay results (often caused by reversed “paid vs. owed” logic)
  • Backpay totals that change dramatically after small edits (a sign formulas no longer reference the correct cells)

Idaho SOL anchor (what the checker uses)

The checker’s Idaho rule is the general/default SOL period: 2 years under Idaho Code § 19-403. Because your jurisdiction data specifies no claim-type-specific sub-rule found, the checker treats this 2-year window as the default lookback.

When to run it

Run the spreadsheet checker before you execute Wage Backpay, and again after any change that affects dates or calculation logic.

A practical sequence:

1. Populate core inputs

   • Work dates (start/end or date-by-date)
   • Pay rate and hours (including any premium/OT logic you’re using)
   • Paid amounts (if your sheet nets what was already paid)
2. Run the checker

   • Confirm the spreadsheet can be parsed
   • Confirm the SOL window aligns with the 2-year default for Idaho
3. Only then run Wage Backpay
4. Re-run after edits to:

   • The case reference date you’re using to define the calculation window
   • Any date column formatting changes (common after exporting from payroll systems)
   • Wage or hours column logic (formula edits can silently break totals)

Timing guidelines that typically prevent rework:

• Before first run: Catch structural errors and SOL logic problems early.
• After payroll import: Payroll exports often convert dates into strings while they still look correct.
• After template changes: If you copied or modified a sheet template, rerun immediately to detect column misalignment.

Try the checker

You can start the DocketMath Wage Backpay workflow from the calculator entry point:

• Primary CTA: /tools/wage-backpay

To get the most reliable results, make sure your spreadsheet aligns with the checker expectations:

• Dates

  • Use consistent formats across all rows (ideally true date values, not text)
  • Ensure “from” dates precede “to” dates
• Rates and hours

  • Enter wages as numeric values (e.g., 18.50, not $18.50)
  • Confirm hours are in the unit your sheet expects (commonly decimal hours)
• Paid vs. owed structure

  • Decide whether your spreadsheet is calculating:

    • Gross owed first, then comparing to paid later, or
    • Net backpay directly (paid subtracted at the row level)
  • The checker can catch inconsistencies, but it can’t determine your intended structure if column meanings are ambiguous.

What you’ll see after fixing issues

Once you correct the problems the checker flags, outputs should behave in predictable ways:

• **SOL-related fixes (anchoring/window length)

  • Backpay totals may drop because the checker removes periods outside the 2-year lookback under Idaho Code § 19-403.
• Date parsing fixes

  • Totals may shift because previously “incorrect” date interpretation can move rows in/out of the window.
• Math structure fixes

  • Grand totals should become stable when you edit a single row.
  • If totals still swing wildly, formulas likely reference the wrong cells/ranges.

A quick “spreadsheet health” checklist you can use each time:

Gentle note: This tool is for checking spreadsheet structure and window logic, not for providing legal advice. If anything doesn’t match your situation, consider verifying the inputs and assumptions with appropriate guidance.

Related reading

• Wage & Backpay Calculator Guide for Alabama
• Wage & Backpay Calculator Guide for Arizona
• Wage & Backpay Calculator Guide for Colorado