Spreadsheet checks before running Wage Backpay in Texas
5 min read
Published April 15, 2026 • By DocketMath Team
What the checker catches
Before you run a wage backpay calculation in Texas with DocketMath, make sure your spreadsheet isn’t quietly feeding the calculator inconsistent dates or mismatched duty/earning periods. DocketMath’s spreadsheet checker for wage backpay (US-TX) is built to validate the inputs that most often cause Texas backpay spreadsheets to undercount or overcount—especially when you’re using jurisdiction-aware limitations logic.
Common issues the checker flags (Texas-aware)
| Spreadsheet element | What the checker looks for | Typical downstream effect |
|---|---|---|
| Pay period date columns | Missing start/end dates, swapped ranges, or invalid ordering | Backpay runs for the wrong time window |
| Notice / cutoff date inputs | A cutoff that occurs before the first eligible period | Output shows $0 or an unexpectedly small number |
| Duty/earning hours columns | Negative values, blanks, non-numeric strings | Totals drift or fail validation |
| Wage rate inputs | Rate stored as text (e.g., “15.00/hr”), inconsistent units across rows | Hourly math breaks or gets applied inconsistently |
| Multiple rows per period | Duplicate periods or overlapping date ranges | Double-counting backpay |
| Summary vs line-level totals | Header totals that don’t match sum formulas | Calculator output conflicts with your spreadsheet totals |
| Jurisdiction tagging | US-TX rules not applied (or overwritten) | Wrong default limitations logic used |
Pitfall: A single “month” date typed as 01/02/2024 (mm/dd vs dd/mm confusion) can shift the limitations window by weeks—enough to materially change which pay periods are included.
Texas limitations logic used in the checker
For US-TX, DocketMath’s wage backpay checker uses the general/default limitations period when no claim-type-specific sub-rule is found in the jurisdiction data being applied. In other words, this setup treats the limitation window as the default rather than a narrow, claim-type override.
Here’s what the jurisdiction configuration uses:
- General SOL period:
0.0833333333 years - Interpretation approach: that value is the default limitations window used by the checker and calculator for this jurisdiction setup.
- Governing general statute (context): Texas Code of Criminal Procedure, Chapter 12
Source: https://statutes.capitol.texas.gov/Docs/CR/htm/CR.12.htm
Because the jurisdiction data notes “no claim-type-specific sub-rule was found,” the checker should apply this default period consistently. To keep your workflow reliable, the checker emphasizes date consistency first, and limitations-window inclusion second.
When to run it
Run the checker before you calculate wage backpay totals and after you finish editing date and rate data. If you’re iterating on your spreadsheet (common during reconciliation), use these checkpoints:
Run the checker before importing a spreadsheet into the Wage Backpay workflow. It is especially helpful when you have multiple entries or when a teammate provided the inputs.
Best times to run DocketMath’s spreadsheet checker
After importing payroll/export data
Example triggers:- You copied a CSV from a payroll system
- You merged two spreadsheets (pay history + schedule)
- You adjusted pay period boundaries
After changing any date field
- Pay period start/end dates
- Any cutoff/notice date you’ve encoded
- Any “as of” date used to limit the calculation
Before exporting values to the wage-backpay calculator
- If you plan to normalize hours, normalize wage rates, or convert formats, do it first—then run the checker.
- This helps ensure the calculator is seeing validated inputs rather than broken or ambiguously formatted fields.
A quick “green light” checklist
Use these checkpoints in order:
If any item fails, rerun the checker after you fix the underlying row/field. Don’t proceed to the calculator while the checker still reports validation issues.
Gentle note: This is a tooling/workflow check, not legal advice. If you’re unsure which dates or rules apply to your situation, consider confirming the setup with a qualified professional.
Try the checker
You can start the workflow from the primary call-to-action:
- Primary CTA: /tools/wage-backpay
Upload the spreadsheet, review the warnings, and then run the calculation once the inputs are clean: Try the checker.
Input expectations (what changes outputs)
To get reliable results, keep these core fields aligned between your spreadsheet and the calculator inputs:
Pay period start & end
- If you shift these dates forward/backward, included periods change.
- If start/end ordering is reversed, the checker typically flags the row or blocks inclusion.
**Hours (or earning quantities)
- Output scales directly with total validated hours included in the calculation window.
- Non-numeric cells (like “8 hrs”) can become zeros or fail parsing, which will change totals.
Wage rate
- Output uses the rate to convert hours into wage amounts.
- Mixed units across rows (some hourly, some daily) will distort totals even if dates look correct.
**Default limitations window behavior (Texas)
- With “no claim-type-specific sub-rule found,” the checker applies the general/default period for US-TX using:
- General SOL period:
0.0833333333 years
- Practically, that means the checker uses your validated date inputs to determine which pay periods fall within the default inclusion logic.
What you should look for in results
After running the checker, review:
Row-level validation messages
Fix these first. The checker should tell you which rows/fields are malformed, contradictory, or outside expected ranges.Period coverage summary
Confirm the checker’s “included time window” aligns with the timeline you intended before you trust the dollar output.Consistency checks between line totals and summary totals
If the calculator’s subtotal doesn’t match your spreadsheet sum, it often indicates at least one column is mis-typed (text vs number), mis-scaled (unit mismatch), or missing.
If everything passes validation, proceed to the wage backpay calculation using the same jurisdiction setting (US-TX).