How to run Wage Backpay in DocketMath for Kentucky

Step-by-step

This guide explains how to run Wage Backpay using DocketMath for Kentucky (US-KY), using jurisdiction-aware rules so the calculation reflects Kentucky’s general timing rule.

1) Start the Kentucky Wage Backpay calculator

1. Open DocketMath’s Wage Backpay tool here: /tools/wage-backpay.
2. Ensure the jurisdiction is set to Kentucky (US-KY).
3. Select the calculator mode for Wage Backpay (the “wage-backpay” calculator).

If DocketMath shows a jurisdiction selector, choose US-KY—that selection controls the limitation window the tool applies.

2) Add your key dates

To compute backpay, DocketMath needs dates that determine what portion of wages falls within the limitations period.

Enter these inputs:

• Start date of wage period: the first date wages were allegedly unpaid (or underpaid).
• End date of wage period: the last date wages were allegedly unpaid (or underpaid).
• Claim date / filing date (or reference date): the date used to measure the lookback window.

How the Kentucky timing rule is applied

For Kentucky, DocketMath uses the general/default statute of limitations, because no claim-type-specific sub-rule was found for this configuration.

• General SOL Period: 5 years
• General Statute: KRS 500.020

Practically, that means DocketMath will count wage time within a 5-year window ending at your reference date (as supported by the tool’s Kentucky configuration based on KRS 500.020).

3) Input wage rate(s) and pay structure

Backpay is driven by how wages were supposed to be calculated. Depending on what DocketMath’s wage-backpay interface asks for, enter the wage inputs that match your pay records.

Common inputs include:

• Hourly wage (if hourly)
• Weekly/monthly salary (if salary)
• Overtime rate assumptions (only if the tool prompts for overtime inputs)
• Hours worked (if hourly and you’re quantifying by hours)

If wages vary over time (for example, raises, role changes, or schedule changes), use the most accurate structure the tool allows:

• If DocketMath supports multiple periods, enter each segment separately so totals reflect changes.
• If the tool supports only one continuous period, consolidate to a single blended rate/hours span (or use the closest matching structure available) so your numbers stay consistent.

4) Enter the amount “underpaid” or “owed” (if the tool supports it)

Some wage-backpay workflows are easier when you enter an underapayment amount rather than recomputing everything from scratch. If DocketMath offers an option like one of the following, choose the method that matches your records:

• Underpayment per pay period
• Wage difference
• Expected vs. paid

With that choice, DocketMath can typically produce:

• Backpay owed (based on the entered wage math)
• Limitations-adjusted backpay (the portion that falls within the Kentucky lookback period under KRS 500.020)

5) Review outputs and how they change with the inputs

After submitting your inputs, DocketMath will typically show results in two main buckets:

1. Total backpay across the entered wage period

   • Uses the wage math you provided (rates/hours/underapayment structure).

2. Backpay within the Kentucky 5-year limitation window

   • Applies the general 5-year lookback tied to KRS 500.020.
   • If your wage period begins more than 5 years before the claim/reference date, DocketMath will exclude the older portion from the limitations-adjusted total.

To see the effect, adjust one input at a time:

• Move the claim/reference date forward by 6–12 months → the included window shifts forward.
• Move the start date earlier → the total may increase, but the limitations-adjusted output may not change if the extra time falls outside the 5-year window.

6) Export or capture the calculation

Once you’re comfortable with the limitations-adjusted numbers:

• Use DocketMath’s output actions (copy results, save, or export—depending on what the interface provides).
• Keep a record of your final run with your Kentucky dates and rate/hour assumptions.
• If you later correct payroll details (for example, an updated end date or corrected wage rate), rerun and save a second version so you can track how totals changed.

Common pitfalls

The most common wage backpay mistakes are date-window problems and pay-structure mismatch. Use this checklist to catch issues early.

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

Date-window mistakes

Pay-structure mistakes

Data quality issues

Try it

Use this quick “sanity test” to confirm DocketMath’s Kentucky limitations logic behaves as you expect under KRS 500.020.

1. Choose your reference/claim date (the date you will use in the tool).
2. Enter a wage period that starts:

   • Less than 5 years before the reference date (example: 3.5 years earlier)
   • and ends on or before the reference date

Run the calculator and note:

• Total backpay
• Limitations-adjusted backpay

Now run the second test: 3. Change only the wage period start date to be:

• More than 5 years before the reference date (example: 6 years earlier)

1. Re-run and compare results.

Expected behavior:

• Total backpay: may increase, because the entered wage period includes more time.
• Limitations-adjusted backpay: should generally not increase for the additional time older than 5 years, because DocketMath applies the general 5-year lookback under KRS 500.020.

If the limitations-adjusted number increases when you move the start date earlier than 5 years, double-check:

• the reference date,
• whether the tool treats your end date/start date inclusively or exclusively for the window,
• whether your wage period boundaries match the tool’s expected date format.

To run the calculator, start here: /tools/wage-backpay.

Related reading

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