Spreadsheet checks before running Wage Backpay in North Dakota

What the checker catches

Before you run Wage Backpay calculations in North Dakota (US-ND) with DocketMath, a spreadsheet-style review can prevent the most common “garbage in / garbage out” issues. The Spreadsheet checker for the wage-backpay calculator focuses on practical validation steps that tend to matter for ND wage backpay workflows—especially when you’re reconciling time records, pay rates, and pay periods.

Run the checker as a pre-flight checklist. It catches mismatches that usually show up as incorrect totals, missing dates, or inconsistent pay assumptions.

High-value validations the checker flags

• Date continuity problems

  • Missing pay-period dates or gaps between pay_period_start and pay_period_end
  • Overlapping periods (two rows covering the same dates)
  • Rows where the “worked” date range falls outside the “pay” date range

• Pay-rate inconsistencies

  • Mixed formats (e.g., $15.50 in one row and 15,50 in another)
  • Hourly vs. salary assumptions in the same dataset
  • Sudden pay-rate changes without an effective date (e.g., rate jumps on the first day of a period but no change date is recorded)

• Hours and arithmetic integrity

  • Negative or zero hours where hours should be positive
  • “Worked hours” that don’t reconcile with hours * rate totals you later sum
  • Rounding drift (for example, rounding hours to 1 decimal but storing monetary totals to cents without a consistent rule)

• Duplicate or missing identifiers

  • Duplicate employees across rows without a differentiator (shift-level vs. summary-level)
  • Missing employee IDs or names that map to the wrong rate table

• Overtime and premium fields left blank

  • If your spreadsheet includes an overtime_hours column, the checker ensures it’s not empty while regular_hours is populated (or vice versa)
  • It also checks for nonsensical combinations like overtime hours exceeding total hours

Output behavior (what changes when checks fail)

DocketMath’s wage backpay output is only as consistent as the inputs you feed it. When the checker detects issues, you’ll typically see one of these patterns:

• Backpay totals drop or spike after you correct pay rates or hours.
• The number of calculated rows changes when duplicates or missing identifiers are resolved.
• Totals become stable across reruns once you fix date overlap/gaps and rounding rules.

Use the checker’s findings to correct the spreadsheet first, then rerun DocketMath to confirm the updated totals match your corrected understanding of the underlying records.

Gentle note: While this tool helps validate spreadsheet structure and common input problems, it isn’t a substitute for reviewing your underlying timekeeping and pay documentation.

When to run it

You don’t want to “discover” input problems after you’ve already produced figures for a claim narrative, settlement discussion, or draft demand. Instead, treat the spreadsheet checker as a gate before any backpay run.

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 the checker

• Right after you import or copy data

  • Typical moment: after exporting time records and pay rates into your wage-backpay spreadsheet format.

• After every structural change

  • Example: you add overtime columns, split one pay period into two, or change how you represent wage-rate changes.

• Before you lock a calculation version

  • If you’re going to snapshot outputs for “Version A / Version B,” run the checker first so both versions are comparable.

• After any manual edits

  • If someone updates a rate effective date, edits hours, or adjusts rounding, the checker should be rerun immediately.

Quick run checklist (fast and practical)

Before each DocketMath run, verify these items are clean:

Try the checker

If you’re ready to run the spreadsheet checks and then calculate wage backpay, start with DocketMath’s workflow for ND using the dedicated tool.

Primary CTA: Run Wage Backpay in DocketMath

When you get to the DocketMath wage backpay input steps, use this practical approach:

Inputs to review (and how they affect outputs)

Use these as your “focus fields” while interpreting checker warnings:

One recommended workflow

1. Load your spreadsheet data into the worksheet format your workflow uses.
2. Run the spreadsheet checker to fix structural issues first (dates, duplicates, formats).
3. Rerun DocketMath Wage Backpay and compare totals against your previous run.
4. Only after totals stabilize, start refining higher-level narrative inputs (e.g., scope of work categories).

The goal is straightforward: make your data reliable enough that the math reflects the wage backpay theory you’re applying—without silent spreadsheet errors.

Related reading

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