What this calculator does

Run this scenario in DocketMath using the Wage Backpay calculator.

DocketMath’s Wage & Backpay Calculator helps you estimate lost wages and backpay for an Arizona situation using a clear, repeatable method. The calculator is designed to translate your inputs—like pay rate, number of work hours, and the time window—into an estimated backpay amount.

In practical terms, it can help you model questions such as:

• “What amount of wages would my employer have owed for the period from March 1 to July 15, 2024?”
• “If I typically worked 40 hours/week at $22.50/hour, what does that imply for a 20-week backpay window?”
• “How do my results change if I enter gross pay vs. a net-adjusted assumption?”

Because this is a calculator, your result depends heavily on the inputs you choose. You’ll generally get the most useful estimate when your dates and wage figures reflect what actually happened (or what you’re claiming should have happened).

When to use it

Use the DocketMath wage-backpay calculator when you need a structured way to estimate wages owed for a defined time period in Arizona. Common use cases include:

• Documenting damages: You’re assembling a timeline and want a consistent way to compute claimed backpay.
• Estimating settlement ranges: You’re comparing “before/after” scenarios (different dates, different pay rates).
• Checking internal consistency: You have payroll records for part of the time and want to sanity-check a missing portion.
• Modeling intermittent work: You want to compute backpay based on an hours-per-week pattern rather than only an annual salary figure.

Tool link: If you haven’t already, open the calculator here: /tools/wage-backpay.

Arizona limitation framework (timing matters)

Arizona’s criminal statute of limitations framework you may encounter in filings can include different limitation periods depending on the “type” or exception applied. For a relevant timing anchor, Arizona law provides:

• 2 years under A.R.S. § 13-107(A) (with exception O2)
• 3 years under A.R.S. § 13-107 (with exception P3)

You provided the SOL details as:

• SOL Period: 2 years
• Statute: A.R.S. § 13-107(A)
• Source: https://www.findlaw.com/state/arizona-law/arizona-criminal-statute-of-limitations-laws.html?utm_source=openai
• Sub-rules:

  • A.R.S. § 13-107(A) — 2 years — exception O2
  • A.R.S. § 13-107 — 3 years — exception P3

How this affects your calculator inputs

The limitation period is a timing concept: it can determine which months you choose to include in your wage/backpay estimate. If you’re selecting a backpay window, you may decide to:

• include only the period within the applicable lookback, and/or
• run multiple scenarios (e.g., “2-year window” vs. “3-year window”) to compare totals.

When not to rely solely on the calculator

You may need extra care if:

• your pay changed during the period (raises, role changes, bonus structures),
• you’re including or excluding overtime,
• benefits or deductions are part of your model,
• you have irregular schedules (variable hours, layoffs, partial-week work).

In those cases, the calculator can still help, but you should break the time window into segments with different inputs (more on that below).

Step-by-step example

Below is a practical walkthrough using a hypothetical scenario in Arizona and showing how inputs change the output.

Scenario: missed wages for a defined period

• Your regular rate: $22.50/hour
• Typical schedule: 40 hours/week
• Backpay window: March 1, 2024 through July 15, 2024
• Assumption for estimating: you would have worked the same schedule each week

Step 1: Set the wage rate

Enter:

• Hourly wage: $22.50

If your situation involves salary instead of hourly pay, you can model it either:

• by converting salary to an hourly equivalent, or
• by using weekly earnings if you’re provided those figures.

Step 2: Set the time unit (hours or weeks)

Enter:

• Hours per week: 40

Then confirm whether the calculator expects:

• total hours = weeks × hours/week, or
• you provide total hours directly.

Step 3: Provide the date range

Enter:

• Start date: 2024-03-01
• End date: 2024-07-15

The tool will translate those dates into an estimated number of work periods (commonly using week-based math depending on configuration). If the calculator gives you options for how it counts partial weeks, choose the option that matches your schedule reality.

Step 4: Review the computed wage/backpay estimate

Your estimated gross backpay will reflect:

• hourly wage × estimated hours in the window

If the tool also supports components (like different segments), you can refine accuracy by splitting the period if anything changed.

Step 5: Run a second scenario for timing window comparison

Because the Arizona timing framework you provided references A.R.S. § 13-107(A) and A.R.S. § 13-107 exceptions, you might want to compare totals using:

• a 2-year back window vs.
• a 3-year back window

For example, if a filing date is 2024-08-01, a 2-year window begins around 2022-08-01, and a 3-year window begins around 2021-08-01. You’d then re-enter the start date while keeping the wage rate consistent (or adjusting it if your wage changed).

Common scenarios

Wage and backpay calculations rarely stay perfectly “flat” across months. Here are common Arizona-related patterns you can model in DocketMath without guessing blindly.

Scenario 1: Wage rate changed mid-period

Example:

• March–April: $20.00/hour
• May–July: $24.00/hour

How to model it:

• Split the date range into two segments:

  • Segment A: March 1–April 30 with $20.00/hour
  • Segment B: May 1–July 15 with $24.00/hour
• Sum the segment totals.

Checklist:

Scenario 2: Overtime or different weekly hours

If your work included overtime, your backpay estimate may change depending on whether you include:

• straight time only, or
• overtime multipliers (which can require separate rate inputs and rules)

How to model it:

• If the calculator supports overtime fields, enter:

  • regular hours/week
  • overtime hours/week (if known)
  • overtime rate or multiplier
• If overtime fields aren’t available in your run, you may need to estimate:

  • average weekly pay based on historical timesheets, then calculate using that blended figure.

Pitfall to avoid:

• Do not treat a schedule with 45 hours/week as if it were 40 hours/week “by default.”
• Do not apply an overtime rate to all hours unless that’s what the payroll history shows.

Scenario 3: Missing workdays and partial weeks

If the backpay window includes partial weeks, the calculation depends on how the tool counts them.

How to model it:

• Use week-based assumptions if your schedule is stable.
• If you have a pattern (e.g., Mon–Thu only), reflect that by:

  • converting to “hours per included workday,” then using realistic hours for partial weeks, or
  • providing “total hours” directly if the calculator allows it.

Checklist:

Scenario 4: Salary vs. hourly

If you’re paid salary, you’ll need an hourly equivalent or weekly equivalent.

How to model it:

• Convert salary to weekly earnings:

  • weekly amount = annual salary ÷ 52
• Then estimate hours back using weekly earnings, or enter weekly earnings directly if your calculator flow supports it.

Checklist:

Tips for accuracy

Getting a reliable estimate is mostly about clean inputs. Use the following practices when running DocketMath’s wage-backpay calculator.

Use segmented dates when anything changes

Whenever any of these changes during your backpay window, segment the calculation:

• hourly wage rate
• weekly hours (schedule changes)
• overtime structure or frequency
• job classification (if it changes pay rules)

Quick guide:

| If this changes… | Do this in the calculator | |

Related reading

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