Why Wage Backpay results differ in Georgia

The top 5 reasons results differ

Run this scenario in DocketMath using the Wage Backpay calculator.

If you’re running Wage Backpay in Georgia (US-GA) with DocketMath, you may notice different results even when the underlying paycheck facts look similar. In practice, the differences almost always come from a small set of inputs and how they’re mapped to Georgia’s default timing rules.

Below are the top 5 reasons results differ, with the most common “diagnostic” signs to look for.

1. Wrong or inconsistent backpay start date

   • Backpay totals are extremely sensitive to the number of weeks/months included.
   • A single-day shift can change the weekly accrual count and alter the outcome.

2. **Dispute about the end date (work resumed vs. termination date)

   • Some models use the last day worked; others use the date backpay was effectively replaced by earnings.
   • If you input an end date that’s even a week off, results change.

3. Using a pay-period schedule that doesn’t match the payroll cadence

   • Weekly vs. biweekly vs. semimonthly pay frequency changes how wages are counted per period.
   • DocketMath’s wage-backpay calculation will reflect the cadence you select.

4. Overlapping offsets: mitigation earnings treated inconsistently

   • Backpay calculations often subtract “earnings during the period.”
   • When mitigation earnings are entered as a single lump sum vs. period-by-period, totals can diverge.

5. Timing assumptions tied to Georgia’s general SOL period

   • Georgia’s general statute of limitations period for most claims is 1 year under O.C.G.A. § 17-3-1.
   • Your outputs can differ if one run effectively limits the recoverable window to “last 1 year from the filing date,” while another includes earlier periods.
   • No claim-type-specific sub-rule was found for wage backpay in the provided jurisdiction data—so treat the 1-year period as the general/default period for SOL timing, not a specialized wage-backpay rule.

For a direct walkthrough and repeatable calculation inputs, start at /tools/wage-backpay .

How to isolate the variable

Use a repeatable “change one thing at a time” process in DocketMath. The goal is to identify exactly which input causes the delta.

• Freeze the jurisdiction and tool settings so both runs use the same rule set.
• Compare one input at a time (dates, rates, amounts) and re-run after each change.
• Review the breakdown to see which segment or assumption drives the difference.

Step-by-step diagnostic checklist (run in this order)

• Set the same backpay start date across both runs.

  • Set the same backpay end date across both runs.
  • Confirm both runs use the same pay schedule (weekly/biweekly/etc.).
  • Ensure the base wage rate is the same and entered in the same unit (hourly vs. salary converted to hourly/period).
  • Decide whether mitigation earnings are entered:

    • period-by-period, or
    • aggregated into one offset amount for the full window.
  • Verify whether the scenario is applying a Georgia general 1-year lookback under O.C.G.A. § 17-3-1 (General SOL Period: 1 years).
  • If one run uses a filing date and another doesn’t, that’s a prime cause of differences.

Quick “delta” method

1. Run A: current inputs.
2. Run B: change only one variable (e.g., end date).
3. Compare:

   • Total backpay difference
   • Effective number of pay periods included
   • Any reduced recoverable window caused by SOL timing

If the result changes dramatically after adjusting only the filing date or the SOL window, the discrepancy is timing-based rather than wage-based.

Friendly note (not legal advice): SOL timing and what counts as recoverable time can be fact-specific. This tool-based approach is best used to explain differences between scenarios, not to predict legal outcomes.

Next steps

To move from “different outputs” to “explainable output,” focus on documentation and input consistency.

1. Create an input audit table Use a simple comparison table for the two runs:

   Input	Run A	Run B	Why it matters
   Backpay start date			Controls number of included periods
   Backpay end date			Controls cutoff for included periods
   Pay frequency			Changes period-by-period wage totals
   Wage rate			Directly scales the wage component
   Mitigation/offsets			Subtracts during overlapping periods
   Filing date / SOL window logic			Can cap the recoverable period based on O.C.G.A. § 17-3-1

2. Confirm the SOL logic you’re applying Georgia’s general SOL is 1 year under O.C.G.A. § 17-3-1:

   • Outputs will differ if one calculation caps the recoverable window to 1 year and another includes earlier periods.
   • Because no wage-backpay-specific sub-rule was provided in the jurisdiction data, using only the general/default period is the consistent approach for comparisons.

3. Re-run the same scenario after normalization Once you align dates, cadence, offsets, and SOL logic, the results should converge closely. If they still diverge, the remaining mismatch is likely in wage unit conversion (hourly vs. converted salary), or how offsets map onto pay periods.

For the next hands-on iteration, use /tools/wage-backpay with your normalized inputs.

Related reading

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