Spreadsheet checks before running Wage Backpay in Oklahoma

What the checker catches

Run this scenario in DocketMath using the Wage Backpay calculator.

Before you run Wage Backpay in Oklahoma (US-OK) with DocketMath, a spreadsheet pre-check can save time and prevent avoidable calculation drift. The spreadsheet-checker workflow is designed to flag the most common spreadsheet issues that cause backpay totals to diverge from the jurisdiction-aware logic DocketMath applies.

Here’s what the checker is built to surface for US-OK:

• Missing or mis-typed date fields

  • Pay periods entered as text (e.g., 01/05/24 saved as a string) instead of actual date values
  • Inconsistent formats across tabs (MM/DD vs DD/MM), which can silently reorder or misinterpret dates
• Wrong “start date” for the lookback window

  • Backpay spreadsheets often include an “earliest alleged violation” date
  • The checker helps ensure that this “earliest included” date aligns with how the calculation engine expects the timeline to be constructed
• Off-by-one period errors

  • Spreadsheets that accidentally exclude the first week/day—or include one extra—can shift totals significantly over longer timelines
• Payroll rate inconsistencies

  • Hourly rate vs overtime rate mismatches
  • Rate changes not mapped to the correct pay periods (for example, applying a later rate to earlier time)
• Duplicate or overlapping pay periods

  • Overlaps often happen when time ranges are copied down without validating boundaries
• Negative or blank values

  • Empty cells for hours, pay rate, or adjustments
  • Negative hours (commonly caused by sign convention problems)
• Junk rows from imports

  • “Grand total,” “subtotal,” or other summary lines included accidentally as if they were pay periods

Jurisdiction-aware rule the checker reinforces (Oklahoma)

In this checker context, DocketMath’s US-OK setup uses Oklahoma’s general/default statute of limitations (SOL) rule. The general/default SOL period is 1 year, tied to 22 O.S. § 152.

Important note: No claim-type-specific sub-rule was found for this checker context. The checker and calculator rely on the general/default 1-year period under 22 O.S. § 152 as the governing timeframe. (Source: https://www.findlaw.com/state/oklahoma-law/oklahoma-criminal-statute-of-limitations-laws.html)

Practical effect: if your spreadsheet includes pay periods older than the allowable window relative to your chosen reference date, the checker helps you identify where totals may include (or exclude) time that falls outside the 1-year general SOL window—without you having to guess which rows are driving the difference.

When to run it

Run the spreadsheet checker before you press “calculate” in DocketMath, and again after any edits that affect time ranges, dates, or pay rates.

A simple timing checklist:

• Before your first DocketMath run

  • Confirm all date fields are real date values (not text)
  • Confirm pay period start/end boundaries are consistent across the dataset
• After importing time/pay data

  • Watch for format conversions and duplicated rows that can appear during import/merge
• After adjusting the earliest included date

  • Changing the earliest included pay period can shift which amounts are treated as within vs outside the 1-year general SOL timeframe under 22 O.S. § 152
• After rate changes

  • Verify that hourly/overtime rate changes map to the correct date ranges (not just the correct labels)

Quick “inputs → outputs” mapping

Understanding what the checker validates makes it easier to interpret output changes:

Gentle disclaimer (non-legal advice)

This workflow is intended to reduce spreadsheet errors and help align inputs with DocketMath’s calculator expectations. It does not replace legal review of the underlying facts, claim classification, or how timelines are argued in a specific matter.

Try the checker

You can use DocketMath’s Wage Backpay in Oklahoma tool here: /tools/wage-backpay.

Before you run it, do these spreadsheet pre-flight checks:

Spreadsheet pre-flight checklist (fast)

What to expect when you run DocketMath

Once your spreadsheet passes the pre-check, DocketMath’s Wage Backpay run should produce totals that are easier to reconcile internally because:

• date ranges are consistent,
• pay period logic is clean,
• and the US-OK 1-year general SOL assumption (per 22 O.S. § 152) is applied consistently within the calculator context.

If you notice unexpectedly low or high totals, start by re-checking the highest-impact items first—date boundaries, overlaps, and the earliest included date—since those commonly drive the largest swings.

Related reading

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