Why Wage Backpay results differ in Maryland

The top 5 reasons results differ

Run this scenario in DocketMath using the Wage Backpay calculator.

Wage backpay calculations in Maryland can look “simple,” but DocketMath results may diverge for the same case because a few inputs and Maryland rules change the outcome. In Maryland, the default general statute of limitations (SOL) period is 3 years under Md. Code, Cts. & Jud. Proc. § 5-106. No claim-type-specific SOL sub-rule was identified for this general comparison—so the 3-year window is the starting point for comparing results.

Below are the five most common reasons DocketMath outputs don’t match across runs, analysts, or versions of a spreadsheet.

1. Whether the SOL “lookback window” is applied

   • If one run limits backpay to wages earned within the 3 years before the relevant filing/reference date (as used in your workflow) and another run includes older wages, totals will differ.
   • Maryland’s starting point for this constraint is Md. Code, Cts. & Jud. Proc. § 5-106.

2. Different definitions of the “backpay period”

   • Common variations include:

     • start date = termination date vs. start date tied to another event (e.g., wrongful action date)
     • end date = mitigation end date vs. stop at reinstatement or settlement date
   • Even small date changes (a few weeks) can materially affect totals because they shift which pay periods are counted.

3. Pay frequency and annualization assumptions

   • DocketMath may calculate using a specific pay cadence (weekly, biweekly, semimonthly).
   • If hourly wages are treated like a weekly/hourly rate in one run but annualized (or vice versa) in another—especially with different assumptions about hours per period—outputs can shift.

4. **Mitigation assumptions (or omission)

   • If mitigation earnings are included in one run and excluded in another, net backpay changes.
   • Likewise, different treatment of partial income (e.g., reduced hours) changes the “net wages” arithmetic.

5. Earnings/compensation inputs not aligned

   • Backpay math can diverge when one analysis includes different compensation components (e.g., commissions, shift differentials, bonuses) or uses different measures (gross vs. net).
   • Ensure both runs use the same compensation components and the same units (hourly vs. per-pay-period totals).

Practical takeaway: In Maryland, comparisons are often won or lost on whether the calculation applies the 3-year SOL constraint from § 5-106 to the wage period. If the SOL handling differs, two runs can disagree even when everything else is the same.

How to isolate the variable

To pinpoint what’s driving differences, use a controlled comparison method with DocketMath.

1. Lock the SOL window

   • Choose the same filing/reference date in both runs.
   • Confirm the wage period is restricted to the 3-year general SOL for this comparison (Maryland: § 5-106).
   • Because no claim-type-specific sub-rule was identified here, treat 3 years as the consistent baseline for this diagnostic.

2. Standardize backpay start and stop dates

   • Ensure both runs use the same:

     • start date (e.g., termination or wrongful action date—whichever your workflow specifies)
     • end date (e.g., mitigation end date, reinstatement date, or settlement date)
   • If you don’t know which dates each run used, reconcile them first before comparing totals.

3. Normalize wage inputs

   • Convert inputs into a consistent structure:

     • hourly rate + hours per week/per pay period, or
     • salary rate + consistent schedule
   • Verify pay frequency assumptions match (weekly vs. biweekly can create period boundary differences).

4. Match mitigation treatment

   • Include the same mitigation earnings line items (same dates and amounts).
   • If one run sets mitigation to zero, the resulting net backpay difference is expected—not necessarily a calculation error.

5. Compare by period, not only totals

   • When DocketMath output differs, review:

     • gross wage totals by pay period (or date segment)
     • mitigation earnings by pay period
     • net backpay by pay period
   • The segment that changes will usually reveal whether the mismatch is due to SOL filtering, backpay period boundaries, or mitigation handling.

If you need a consistent Maryland-focused calculation starting point, use: /tools/wage-backpay.

Next steps

1. Change only one variable at a time

   • First: modify only the SOL window handling.
   • Second: modify only pay frequency assumptions.
   • Third: modify only mitigation inputs.
   • Fourth: modify only compensation components (what’s included/excluded).

2. Create a run-by-run input checklist

   • For each run, record:

     • filing/reference date used for the 3-year lookback (per § 5-106)
     • backpay start and end dates
     • hourly/salary inputs and pay frequency
     • mitigation earnings entries (dates and amounts)
     • included compensation components and whether values are gross or net

3. Run a quick “inside vs. outside” SOL sanity check

   • Make a short timeline (even a basic table) showing which pay periods fall within vs. outside the 3-year window.
   • Large swings typically map directly to periods being excluded or included.

4. Verify workflow/version consistency

   • If one calculation workflow applies SOL filtering and another doesn’t (or uses different date rules), you’ll get mismatched results even when the underlying facts are the same.
   • Align the SOL and period boundaries first before drawing conclusions.

Gentle note: This is a diagnostic approach to explain calculation differences. It’s not legal advice.

Related reading

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