Why Alimony Child Support results differ in Kentucky

The top 5 reasons results differ

Run this scenario in DocketMath using the Alimony Child Support calculator.

When you run an Alimony + Child Support calculation in Kentucky using DocketMath (jurisdiction-aware rules for US-KY), the numbers can come out noticeably different from what someone expected—even when people think they’re using the “same facts.” In Kentucky, the biggest drivers are usually how inputs map to the order, how time and deductions are treated, and which Kentucky defaults apply.

Below are the top 5 reasons results differ, with practical places to check. (This is general information—DocketMath results can’t replace legal advice.)

1. Income definition mismatch

   • Kentucky support outcomes are highly sensitive to what’s treated as “income” (for example, gross vs. net, bonuses, and how self-employment variability is handled).
   • If one run uses paystubs-style monthly income and the other uses annualized income, the monthly figures can shift.

2. Parenting time / obligation allocation

   • Child support calculations depend on the parenting schedule inputs you enter (for example, the number of overnights and the rough time split).
   • Even modest schedule changes can alter the baseline and therefore change results.

3. Deductions and special adjustments

   • Inputs related to health insurance, childcare, and other statutory adjustments can materially change the monthly amounts.
   • If an input is missing or effectively counted twice (for example, insurance is entered in one field but also included in another number you used as “total costs”), totals won’t match.

4. Alimony period and termination timing

   • Alimony outcomes vary based on the structure entered in the scenario (duration and termination assumptions).
   • A run that assumes a longer alimony period can “look” higher depending on how the tool distributes/expresses amounts over time, even if the income numbers are similar.

5. Timing assumptions and effective date

   • DocketMath outputs are driven by the time horizon implied by your entries (start/termination timing assumptions and the period you’re modeling).
   • Two scenarios using the same income levels can still produce different totals if the assumed start timing differs.

Important note on arrears timing (SOL): Kentucky has a general statute of limitations (SOL) of 5 years under KRS 500.020, and the period described there is the general/default period (no claim-type-specific sub-rule was found in the jurisdiction data you provided). This doesn’t automatically control your payment calculation, but it can affect what arrears period someone is trying to model.

How to isolate the variable

If your result “doesn’t match,” the fastest way to figure out why is to change one input lever at a time and compare the output deltas. In DocketMath, treat this like a controlled experiment.

Start with these steps in DocketMath:

• Freeze the facts: keep the same for both runs:

  • employment income figures (and the method—both annualized or both paystub-based),
  • parenting schedule/time split,
  • insurance and childcare inputs.
• Change only one lever per run, then record what moves:

  • parenting time,
  • insurance amount,
  • childcare amount,
  • alimony duration/termination assumption,
  • any income averaging setting (if present in your scenario inputs).

A simple comparison approach:

Rule of thumb:

• If child support changes but alimony does not, focus on parenting time and deductions/adjustments.
• If both change, start with income definition/averaging.
• If only alimony changes, revisit alimony duration/termination inputs.

If you want to recreate your scenario using the same Kentucky-aware workflow, begin here:

• Primary CTA: /tools/alimony-child-support

Next steps

1. Run a baseline where every input comes from the same source type (for example, both sides annualized from W-2 + documentation—avoid mixing annualized and monthly/paystub methods).
2. Do two “surgical” recalculations:

   • one that changes only parenting time,
   • another that changes only alimony duration/termination.
3. Check the adjustment fields tie to the story

   • Confirm the insurance and childcare fields reflect what you intend (and that you’re not entering a cost in more than one place).
4. Use timing carefully

   • If you’re modeling arrears or a specific period, align your assumed window with expectations around the general 5-year SOL in KRS 500.020 (general/default period).

Related reading

• Alimony & Child Support Estimator Guide for Alabama
• Alimony & Child Support Estimator Guide for Arizona
• Alimony & Child Support Estimator Guide for Colorado