How to run Alimony Child Support in DocketMath for Kentucky

6 min read

Published April 15, 2026 • By DocketMath Team

This article is for informational purposes only and does not constitute legal advice. Laws change frequently — verify all citations with current official sources.

Step-by-step

This walkthrough shows how to run Alimony + Child Support calculations in DocketMath for Kentucky (US-KY) using jurisdiction-aware defaults. It’s designed to help you get consistent numbers quickly—without treating the tool’s output as legal advice.

Note: Kentucky’s general statute of limitations is 5 years under KRS 500.020. No alimony/child-support-specific sub-rule was identified here, so the default 5-year rule is the one reflected for SOL timing logic in this guide.

1) Open the correct DocketMath calculator

Go to the primary calculator page: **/tools/alimony-child-support
Confirm the jurisdiction selector is set to Kentucky (US-KY) (or set it if your interface requires selection).

2) Enter the parties and case timing inputs

Work through the input sections in order. Use dates carefully because SOL logic depends on them.

Recommended input set:

Filing date (or other relevant case start date you’re using for analysis)
Date of last payment (if you’re comparing arrears timing)
Current date (used to evaluate time windows)
Jurisdiction: US-KY (Kentucky rules)

How it affects outputs:

When SOL timing is enabled, DocketMath uses KRS 500.020’s 5-year general period to limit which months/periods are treated as potentially collectible for older arrears.
If you move the “current date” forward by 12 months, older portions may fall outside the lookback window and reduce the collectible amount.

3) Input child support facts

Enter the child-related inputs required by the calculator:

Number of children
Custody/placement arrangement (e.g., parenting time split or the calculator’s custody indicator)
Income figures for each parent as requested by the tool

Impact on results:

Changing the parenting-time indicator can change the portion allocated to each parent and therefore shift the computed child support obligation.
Updating income changes both the base computation and any downstream totals.

4) Input alimony facts

Next, provide alimony inputs, typically including:

Payor and recipient income inputs (as requested)
Requested/assessed period assumptions (if the calculator asks whether you’re modeling monthly alimony vs. a specific duration)
Any alimony-specific inputs the calculator collects

Impact on results:

Even small income changes can shift the modeled alimony amount.
If the calculator uses duration or termination assumptions, the total alimony over time changes even if the monthly amount stays similar.

5) Turn on (or verify) the SOL-related option

In DocketMath, there’s often a checkbox or toggle for “arrears timing / SOL window” logic. Verify it’s enabled if you’re modeling arrears collectible periods.

What Kentucky logic is used:

General SOL Period: 5 years
Statute cited: KRS 500.020
Important clarity: No claim-type-specific sub-rule was found for a separate SOL period for alimony vs. child support in this workflow, so the 5-year default is applied.

Warning: If you disable SOL logic, the calculator may show a full-period arrears total without limiting older months. That can significantly overstate collectible amounts when you’re actually modeling enforceability based on KRS 500.020.

6) Review the calculator outputs (and how to interpret them)

After entering inputs, DocketMath will typically generate:

Estimated monthly child support
Estimated alimony amount (monthly or periodic)
Arrears or total amounts over time (if you entered relevant dates and turned on SOL logic)
A breakdown by month/period (depending on the tool’s display)

Use this interpretation approach:

Monthly obligation numbers tell you the ongoing duty estimate under the inputs you provided.
Total arrears figures reflect both the monthly amounts and the time window the SOL toggle allows.

7) Adjust one variable at a time to sanity-check results

To verify you entered things correctly:

Change income first (e.g., adjust payor income by a small amount) and see if the monthly totals respond.
Then change parenting time (if supported) and confirm the child support component shifts.
Finally, change current date by 6–12 months and confirm SOL-limited arrears totals adjust.

This incremental testing helps catch common data entry errors faster than retyping everything.

8) Save or document your run

If your DocketMath workflow supports it:

Save the run name (e.g., “KY alimony+child support SOL window model”).
Export or copy the summary so you can compare runs later.

Practical checklist before you move on:

Common pitfalls

These are the issues that most often lead to confusing outputs when running alimony + child support calculations for Kentucky (US-KY) in DocketMath.

Forgetting that Kentucky SOL logic here uses a general 5-year rule

The workflow applies KRS 500.020 (5 years general SOL) because no claim-type-specific sub-rule was found for separate timing periods in this setup.
Result: older arrears months may be excluded from the collectible portion.

Mixing up “current date” and “last payment”

If you set “current date” to an earlier time than “last payment,” time windows can behave unexpectedly.
Fix: ensure “current date” is on/after “last payment” when you’re modeling arrears.

Using inconsistent income snapshots

Child support and alimony models are sensitive to income values.
Inconsistent income (e.g., using gross for one parent but net for the other, or different months/years) can distort both components.

Parenting-time entry mismatch

If the calculator uses a slider, code, or custody indicator, choosing the wrong placement label can shift child support estimates sharply.
Practical method: run two quick checks—one with the “higher time” label and one with the “lower time” label—to see which is directionally consistent with your case.

Assuming outputs are legal determinations

DocketMath provides calculation outputs based on the inputs you enter.
Courts and parties may use additional rules, deviations, or evidence not captured by a calculator interface.

Pitfall: You may see a large difference between “total arrears without SOL” and “total arrears with SOL.” That gap is often the SOL lookback window driven by KRS 500.020’s 5-year general period, not an arithmetic error.

Try it

Ready to run your first Kentucky scenario?

Open the calculator: **/tools/alimony-child-support
Set Kentucky (US-KY).
Enter:
- A reasonable filing date
- A last payment date (or the date you’re measuring from)
- current date
- child count and your parenting-time indicator
- income inputs for both sides
- alimony inputs requested by the tool
Turn on SOL logic to apply KRS 500.020’s 5-year general SOL period.

After the run:

Look for a month-by-month breakdown (if shown) and identify where SOL begins excluding older months.
Then do one quick adjustment:
- Increase current date by 12 months and re-run.
- Confirm whether collectible arrears decrease (typical SOL effect as older months move farther outside the 5-year window).

If you want a faster start, use a “small test” approach:

Enter only dates + SOL toggle + one income set first.
Add custody and alimony details after you confirm the tool is responding as expected.