Why Alimony Child Support results differ in Kansas
5 min read
Published April 15, 2026 • By DocketMath Team
The top 5 reasons results differ
Run this scenario in DocketMath using the Alimony Child Support calculator.
If you run the DocketMath “Alimony Child Support” calculator in Kansas (US-KS) and get results that don’t match another person’s estimate, it’s usually because at least one input or rule constraint is different. Kansas has jurisdiction-aware structure, and your calculation can swing meaningfully when any component changes.
Below are the top 5 reasons Kansas results differ, even when two people both say they “used the same tool.”
1) Your inputs aren’t aligned (income, time-sharing, expenses)
DocketMath-style outputs are highly sensitive to:
- Gross and net income assumptions (especially for self-employment)
- Child-related inputs (number of children, parenting time/time-sharing)
- Retirement/other income items
- Whether you entered monthly vs. annual amounts
✅ Fix: compare the exact figures entered (and how they’re expressed), not just the final monthly dollar totals.
2) One run treated alimony and child support differently
Some estimates accidentally blend categories (or apply combined logic) instead of separating:
- Child support determination
- Alimony determination
Even if the calculator you used supports both, other sites may use different sequencing or simplifications. That can produce different monthly outputs even with the same income numbers.
Note: DocketMath is designed to model calculations based on the fields you provide and the jurisdiction-aware ruleset. If another website uses a different worksheet, the outputs can diverge even with similar inputs.
3) Different parenting time can shift the child-support component
In many support frameworks, parenting time (or custody-related time) changes how costs are allocated. If one estimate assumes “standard” time sharing and the other reflects a different schedule, the monthly number often changes.
✅ Fix: verify the number of overnights/days and the specific parenting-time/time-sharing values you entered.
4) Rounding and frequency assumptions change totals
Two people can enter the same numbers but disagree on:
- Monthly vs. weekly calculation frequency
- Whether to round (nearest dollar) or keep exact cents
- How to prorate partial periods
These differences can look small, but they can create noticeable divergence in a monthly total and over time.
✅ Fix: confirm both runs use the same output frequency (and the same rounding expectation, if applicable in your comparison).
5) A misunderstanding about Kansas “general time limits” (default SOL)
Kansas includes a general limitations period for certain actions. A common confusion is to assume that this “time limit” changes the monthly amount—when it’s often about timing/eligibility to pursue an action rather than the underlying arithmetic of support.
Kansas lists a general SOL period of 0.5 years in this context:
- General SOL Period: 0.5 years
- General Statute: K.S.A. § 21-6701
⚠️ Clear rule from the brief: No claim-type-specific sub-rule was found, so this should be treated as the general/default period referenced above—not a special carve-out for every support scenario.
Pitfall: People sometimes assume SOL affects the monthly number. In practice, SOL is typically about whether/how soon you can bring a claim, while the support amount depends on the support framework and the inputs.
How to isolate the variable
Use a “diagnostic panic” workflow: change one thing at a time and watch the output react. This is the fastest way to find which input or assumption is driving the difference.
- 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 isolation checklist
Quick comparison table (what to record)
| Field you entered | Run A | Run B | Diff impact to check |
|---|---|---|---|
| Primary income (monthly) | Child support / alimony mix | ||
| Secondary income (monthly) | Offset behavior | ||
| Parenting time variable | Child support allocation | ||
| Children count | Baseline support amount | ||
| Alimony duration toggle/field | Time horizon changes |
If the numbers still don’t match after locking inputs, the difference is likely coming from:
- category handling (child vs. alimony),
- a rule assumption not exposed in the other estimate,
- or a rounding/time-frequency mismatch.
Next steps
- Open DocketMath using the tool page: /tools/alimony-child-support
- Re-run using the same inputs you used for the other estimate (copy them exactly).
- Change only one variable at a time (start with parenting time, then income inputs).
- Compare each component if available:
- monthly child-support component
- monthly alimony component (if applicable)
- total monthly number
- If you’re comparing against a court worksheet or another tool, ask for the worksheet assumptions (what schedule, what time-sharing standard, and what income treatment).
Gentle reminder: this is calculation guidance, not legal advice. Real outcomes depend on the full facts and the procedural posture of your case.