Spreadsheet checks before running Wage Backpay in Hawaii

What the checker catches

Run this scenario in DocketMath using the Wage Backpay calculator.

Running Wage Backpay in Hawaii with DocketMath is usually smooth—until a spreadsheet quietly breaks one of the math assumptions behind the calculator. The spreadsheet checks step is designed to catch those problems before you calculate anything, using jurisdiction-aware rules for US‑HI.

Common spreadsheet issues the checker flags

Use this checklist to understand what you’re validating:

• Date coverage problems

  • Missing start or end dates for the wage period.
  • End date earlier than start date (or “string” dates that sort incorrectly).

• Incorrect lookback window

  • The checker applies Hawaii’s general 5-year statute of limitations rule for the relevant wage backpay claim type using the general/default period.
  • HRS § 701-108(2)(d) is the rule it uses as the default source.
  • Important: No claim-type-specific sub-rule was found, so the checker does not try to infer a different window. It stays with the general 5 years.

• Row-level aggregation errors

  • Duplicate pay periods (same date range entered twice).
  • Gaps where a week/month exists but has blank hours.
  • Mixed units (hours entered as “days” in some rows).

• Rate inconsistencies

  • Different hourly rates for the same pay period without justification.
  • Overtime rows missing the overtime indicator/rate while still carrying extra hours.

• Blank or non-numeric wage components

  • “—” or empty strings in wage columns.
  • Text-formatted numbers (e.g., $1,200 in one row and 1200 in another).

• Partial overrides that distort totals

  • One column calculated by formula, another hard-coded.
  • A tax/fee column accidentally included in “wages due.”

• Overpayment sign errors

  • Credits entered as positive instead of negative (or vice versa), changing net backpay.

How the checker’s rules affect your output

DocketMath’s wage backpay output is only as reliable as the inputs that survive validation. After the checker runs, these outcomes change:

• Out-of-window time may be excluded (or flagged for review), changing which wage period rows are considered under the 5-year general SOL rule.
• Total gross wages may change if duplicate or missing pay periods are removed or marked.
• Overtime and rate math may adjust when the checker normalizes units and detects inconsistent rate patterns.

In short: the checker doesn’t just “validate”—it helps prevent totals that look precise but are based on flawed structure.

When to run it

Run the checker at two specific points in your workflow. This prevents rework and reduces the chance that a spreadsheet error propagates into your final Wage Backpay calculations.

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.

1) Before you calculate anything

Use DocketMath’s spreadsheet checks right after you prepare the worksheet and before you click through to Wage Backpay.

Do this when:

• You imported data from payroll exports (CSV/XLSX).
• You entered dates manually.
• You edited pay period rows after the fact.

2) After you update dates or pay periods

Re-run immediately if any of the following changed:

• The start date or end date of the wage period you’re analyzing.
• Any row that affects time-in-period coverage (e.g., adding one missing week).
• Any transformation to the dataset (merging tabs, renaming columns, recalculating hours).

The Hawaii rule the checker uses (US‑HI)

For this workflow, the checker uses the general/default SOL period of 5 years based on:

• HRS § 701-108(2)(d) (general rule).
  Source: https://codes.findlaw.com/hi/division-5-crimes-and-criminal-proceedings/hi-rev-st-sect-701-108/?utm_source=openai

Because no claim-type-specific sub-rule was found in the brief’s research context, the checker keeps the general 5-year default rather than attempting a more granular assumption.

Try the checker

Start the process here: /tools/wage-backpay.

A practical way to use it:

Upload the spreadsheet, review the warnings, and then run the calculation once the inputs are clean: Try the checker.

Capture the source for each input so another team member can verify the same result quickly.

Step-by-step setup checklist (fast)

Inputs the checker expects (typical spreadsheet shape)

While your exact columns may vary, the checker generally needs:

• Date range per pay period row
• Hours (and overtime hours if tracked separately)
• Pay rate (and overtime rate if applicable)
• Wage components representing gross wages due (so adjustments/taxes don’t get mixed in)

Output to look for before finalizing

After running, focus on three categories of results:

1. SOL window alignment

   • Whether rows fall within the 5-year general/default period under HRS § 701-108(2)(d).

2. Data quality warnings

   • Missing dates, non-numeric values, unit mismatches.

3. Normalization/cleanup notes

   • Deduplication, re-parsing of dates, correction of sign conventions.

Even if the checker doesn’t stop the calculation, treat warnings as a “must-fix” list when you want clean, defensible totals.

Related reading

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