Worked example: Wage Backpay in North Dakota

Example inputs

Below is a worked example showing how DocketMath calculates wage backpay for a claim in North Dakota (US-ND). This example focuses on the math workflow you can reproduce—inputs first, then the computed backpay and timing logic.

Scenario: hourly employee with an unpaid period

Assume a North Dakota employee was scheduled to work but did not receive wages during a defined “backpay window” due to an employer action that is later corrected.

Use these numbers (all amounts are in USD):

• Work status: hourly employee
• Wage rate: $20.00/hour
• Scheduled hours per week: 40
• Backpay start date: 2024-02-05
• Backpay end date: 2024-03-31
• Vacation / PTO credited toward backpay: $0.00
• Other earnings to offset (e.g., wages from a different job during the backpay window): $320.00 total
• Withholding / tax adjustment setting in DocketMath: On (calculator applies a standard net/tax handling approach)

Why these inputs matter

The backpay calculation typically combines:

1. Gross wages due for the backpay window
2. Offsets (like earnings from other work)
3. Optional adjustments (like tax/withholding handling, depending on the calculator settings)

In DocketMath, you’ll generally see those components reflected in the output breakdown.

Quick calendar sanity check (weeks covered)

From Feb 5, 2024 through Mar 31, 2024 spans:

• a partial week starting Feb 5
• full weeks in between
• a partial week ending Mar 31

Your exact day-count handling is done inside DocketMath using its date-to-worktime rules. You supply the start/end dates and DocketMath handles the proration.

Checkbox checklist for consistent results

Before you run any wage backpay math, confirm you have:

Example run

Run this scenario using DocketMath’s wage-backpay tool here: /tools/wage-backpay.

Run the Wage Backpay calculator using the example inputs above. Review the breakdown for intermediate steps (segments, adjustments, or rate changes) so you can see how each input moves the output. Save the result for reference and compare it to your actual scenario.

Inputs entered (as provided above)

• Hourly rate: $20.00
• Scheduled hours/week: 40
• Start date: 2024-02-05
• End date: 2024-03-31
• PTO credited: $0.00
• Other earnings (offset): $320.00
• Tax/withholding mode: On

What DocketMath calculates

DocketMath computes backpay in a structured way:

1. Gross wages due

   • Hourly rate × hours attributable to the backpay window (prorated by calendar)
2. Less offsets

   • Subtract other earnings you enter ($320.00 here)
3. Tax/withholding handling (if enabled)

   • Produces a net-like figure alongside a gross figure, depending on the calculator’s method

Example output (illustrative)

Because the precise number of compensable work-hours depends on DocketMath’s internal proration for the partial weeks, the output should be treated as the tool’s computed result for this date range.

A representative breakdown you would expect to see from DocketMath:

• Gross backpay: (tool-calculated)
• Less offsets (other earnings): $320.00
• Net backpay estimate: (tool-calculated, after withholding setting)

To make this concrete without guessing DocketMath’s proration, the key takeaway is how each input changes the final number:

• Changing the hourly rate scales the gross wages proportionally.
• Changing the hours/week scales the gross wages proportionally.
• Changing the start/end dates changes the number of work-hours attributed.
• Adding offset earnings reduces the wage portion dollar-for-dollar (as configured).

A practical way to verify your run

After you run, do a quick reconciliation:

• Does the gross backpay roughly equal:
  hourly rate × 40 hours/week × number of weeks covered, adjusted for partial weeks?
• Does the offset subtraction equal exactly what you entered: $320.00?
• If tax/withholding is enabled, does the net figure look materially lower than gross?

Sensitivity check

Sensitivity checks tell you where the biggest swings come from. For wage backpay, two inputs usually dominate: (1) time window and (2) hourly value.

1) Shift the start date by 7 days

Change:

• Start date from 2024-02-05 → 2024-02-12 Keep everything else the same.

Expected effect

• Fewer compensable work-hours in the window
• Gross backpay decreases
• Offset stays the same unless you re-enter offsets tied to the revised period
• Net backpay decreases accordingly

Use this to confirm that your run responds reasonably to the timeline you intend.

2) Increase scheduled hours/week by 5

Change:

• Hours/week: 40 → 45

Expected effect

• Gross backpay increases proportionally because:

  • hourly rate stays constant
  • hours tied to the time window increase by 12.5%

Rule of thumb for directionality

• A +12.5% change in hours/week typically yields a comparable +12.5% change in gross wages, then minus the same offsets.

3) Add an offset earnings amount

Change:

• Other earnings (offset): $320.00 → $1,200.00

Expected effect

• Net backpay drops significantly
• Gross backpay does not change (unless your workflow ties offsets to wage calculations)
• The difference between the two net outcomes is approximately the extra offset: +$880.00 offset reduction, subject to the calculator’s handling of net vs gross

4) Toggle tax/withholding mode

Change:

• Tax/withholding mode: On → Off

Expected effect

• Gross backpay stays the same
• “Net” estimate increases when withholding is disabled
• If your reporting needs a gross-only number, this toggle helps separate wage totals from take-home estimates

Summary table: what moves the result?

Related reading

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