Step-by-step

Run this scenario in DocketMath using the Wage Backpay calculator.

Below is a practical walkthrough for running Wage Backpay in DocketMath for New Mexico (US-NM). You’ll set jurisdiction-aware defaults using N.M. Stat. Ann. § 31-1-8, then review the calculator’s outputs and assumptions.

1) Open the Wage Backpay calculator

Use the primary call-to-action to launch the tool:

• /tools/wage-backpay

When the calculator loads, confirm the jurisdiction is set to New Mexico (US-NM). If it’s not, switch it before entering dates—because the tool’s SOL rules depend on jurisdiction.

2) Confirm the jurisdiction’s backpay window (statute of limitations)

For New Mexico, DocketMath should apply the general/default statute of limitations for this workflow:

• General SOL period: 2 years
• Authority: N.M. Stat. Ann. § 31-1-8
• No claim-type-specific sub-rule was found for this calculator flow, so the 2-year general period applies as the default.

What that means in practice: DocketMath will typically compute the payable backpay window so it does not reach earlier than the earliest date allowed under the 2-year SOL—measured relative to the anchor date the tool asks you to provide.

3) Provide the dates the tool needs

Enter the date fields that control the calculation window. While each implementation can vary slightly, wage backpay tools commonly include:

• Work start date (earliest date of unpaid wages you’re claiming)
• Work end date (latest date of unpaid wages)
• Anchor date (the date the limitation period is measured from—use exactly what DocketMath specifies on the screen)

How outputs change with dates

• If your work dates extend more than 2 years before the anchor date, DocketMath will generally limit the payable period to the most recent 2-year segment under § 31-1-8.
• If your unpaid period is fully inside that 2-year window, the SOL limit typically won’t reduce the period, and the calculation will more closely reflect the dates you entered.

Quick accuracy checklist:

4) Enter pay rate details

Next, input the wage information used to compute the underpayment and total backpay for the allowed period.

Common inputs include:

• Hourly rate (or agreed rate)
• Hours (sometimes as total hours, and sometimes as hours per week multiplied across the date range)
• Pay frequency (weekly/biweekly) if the tool asks
• Expected wage vs. paid wage (if supported)

How outputs change with rates

• A higher expected rate or higher hourly underpayment generally increases the total backpay, often in a roughly proportional way (subject to how the tool handles date segmentation).
• If you provide hours per week (or another time-based hours input), totals can change as the number of weeks/days within the SOL-limited window changes.
• If the tool supports multiple wage rates over time, the earlier vs. later rates can affect totals, depending on which portions of your period fall within the 2-year window.

5) Run the calculation and review the SOL impact

After entering dates and wage figures, run the calculation.

You should expect outputs that include:

• Calculated backpay amount for the allowed period (not necessarily your entire requested period)
• Compensable time totals (days/weeks/hours), depending on how DocketMath converts your date range
• Indications that the tool limited the window due to the SOL

What to look for (SOL sanity check)

• Confirm the tool’s backpay period begins no earlier than the earliest date permitted by the 2-year general SOL under N.M. Stat. Ann. § 31-1-8.
• If your requested period is longer than 2 years, the “allowed” result should reflect only the portion that falls within the last 2-year timeframe measured from the anchor date.

6) Use jurisdiction-aware defaults for consistency

DocketMath uses jurisdiction-aware rules for New Mexico based on your inputs. In this workflow, the key point is that the calculator uses the 2-year general SOL under § 31-1-8.

To keep results consistent while testing:

• Keep the anchor date constant while adjusting other inputs.
• Change one variable at a time (for example, adjust work end date only) so you can clearly see how totals respond.

7) Save or export your results (if available)

If the tool offers an export, screenshot, or share link, save it. Your record should include:

• Input dates (work start/end and anchor date)
• Wage inputs (rate(s), expected vs. paid, hours)
• The calculated allowed window
• The final backpay total

This is especially helpful if you later correct the hours, adjust the date range, or rerun using updated assumptions.

8) Double-check against your documents

Even a perfectly applied SOL limit can still be wrong if the underlying facts (dates/hours/rate inputs) are off.

Before relying on the number, cross-check what you entered against:

• Timesheets or schedules
• Pay stubs
• Employment records showing work dates/hours
• Any documentation explaining wage changes or pay disputes

Common pitfalls

These are common issues that can derail wage backpay calculations in DocketMath for New Mexico, particularly when the 2-year SOL under N.M. Stat. Ann. § 31-1-8 trims the window.

Pitfall checklist

SOL-specific confusion (New Mexico)

New Mexico’s general SOL for this workflow is 2 years under N.M. Stat. Ann. § 31-1-8. Because the brief doesn’t identify a claim-type-specific limitation period for this calculator flow, the tool should treat the 2-year general period as the default.

If your result seems unusually short, confirm first:

• whether your work start date is earlier than the tool’s earliest allowed date, and
• whether the tool is applying the 2-year window.

Try it

Ready to calculate? Use DocketMath’s Wage Backpay tool:

• /tools/wage-backpay

For a first run that’s easier to verify, try this order:

1. Set jurisdiction: US-NM.
2. Enter your work start date and work end date.
3. Enter the anchor date exactly as DocketMath requires it.
4. Add your wage inputs (hourly rate / expected vs. paid / hours).

Then verify that the allowed backpay window aligns with the 2-year general SOL under N.M. Stat. Ann. § 31-1-8.

Quick “sanity check” comparison

You can compare two runs to see how SOL limitation affects totals:

• Run A: original work dates
• Run B: move the work start date forward (but keep it within the 2-year window)

If DocketMath is applying SOL correctly, changes should mainly reflect the portion that comes in/out of the 2-year allowed timeframe.

Related reading

• Browse the blog

Step-by-step

• Select New Mexico in the Wage Backpay tool.
• Enter the trigger dates and any caps or rates.
• Run the calculation and save the output.

When rules change, rerun the calculation with updated inputs and store the revision in the matter record.

Common pitfalls

• missing a required input
• using a stale rate or rule
• ignoring calendar or holiday adjustments
• skipping documentation of assumptions

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

When rules change, rerun the calculation with updated inputs and store the revision in the matter record.

Try it

Open the Wage Backpay calculator and follow the steps above: Run the calculator.

If an assumption is uncertain, document it alongside the calculation so the result can be re-run later.

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

Related reading

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