Why Alimony Child Support results differ in South Dakota
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 DocketMath’s alimony-child-support calculator for South Dakota (US-SD) and your results don’t match what you expected, the most common causes are input sensitivity and jurisdiction-aware timing assumptions. South Dakota uses a general 3-year statute of limitations (SOL) for many civil claims under SDCL 22-14-1. Also, no claim-type-specific sub-rule was found in the brief jurisdiction data—so this discussion uses the general/default 3-year SOL period. That matters because two “estimates” can look inconsistent even when the underlying math is being applied to different effective time windows.
Here are the top 5 reasons results differ in practice:
**Different time horizons (especially around deadlines)
- The general SOL period is 3 years under SDCL 22-14-1.
- If one estimate effectively “looks back” about 3 years (or assumes a different start/effective date), but another estimate uses a different timeline, the outputs can diverge—even if the dollar math looks similar in isolation.
Unaligned income inputs
- Small changes to monthly gross income, treatment of deductions/credits, or other income details can noticeably swing both child support and alimony results.
- DocketMath reflects those changes immediately because the calculation is downstream of the numbers you enter.
Child-related inputs that change the support calculus
- Number of children and parenting time/custody-related inputs can materially change the child support outcome.
- Even a seemingly minor difference (for example, a different parenting-time category) can create a noticeable gap.
Alimony characterization differences
- Different factual assumptions can change the alimony portion of the model (e.g., how needs/ability are estimated).
- Even without a specialized SOL sub-rule identified for this exact claim type, differences in the scenario assumptions can still drive large changes in outputs.
Rounding and order-of-operations effects
- Calculators may round intermediate steps differently.
- That can produce small differences (a few dollars) or larger differences depending on how values round and feed into later steps.
Pitfall to watch: Comparing two “estimates” that assume different effective starting dates or 3-year general SOL timing under SDCL 22-14-1 can make results appear mismatched, when the real issue is a timing/assumption mismatch.
How to isolate the variable
A practical approach is to treat DocketMath like a controlled experiment. The goal is to change one thing at a time and observe which part of the output moves.
- 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.
1) Lock the jurisdiction and start/effective date assumptions
Before comparing outcomes, write down exactly what you assumed:
- Jurisdiction: South Dakota (US-SD)
- Any effective/starting date used in the comparison (if applicable)
- Whether the other estimate implicitly treated the case as operating under the general 3-year SOL period from SDCL 22-14-1 (general/default; no claim-type-specific sub-rule was found in the brief data)
2) Re-run the calculator with everything the same except one category
Use a checklist and update only one input at a time in /tools/alimony-child-support.
For example:
3) Compare outputs by component, not just the final total
Look for where the change shows up:
- Child support monthly figure
- Alimony monthly figure
- Combined total
If only one component shifts, you’ve likely identified the driver.
4) Use a simple 2-run matrix
Run:
- Scenario A: your baseline inputs
- Scenario B: modify only one input category
Then compare which component moves and by how much. Repeat until you explain the divergence.
5) Run a quick SOL-aware sanity check
Because the general SOL is 3 years under SDCL 22-14-1, confirm you are not accidentally comparing:
- An estimate modeled with a 3-year general SOL window, vs.
- Another estimate using a different implied time window
Gentle reminder: This is an assumptions diagnosis, not legal advice. For case-specific timing questions, you’ll want to consult a qualified professional.
Next steps
Run DocketMath twice (Scenario A and Scenario B) and document:
- What you changed
- The exact change in output (child support vs alimony vs total)
If the mismatch is mostly income-related
- Re-check the monthly income values
- Confirm any deductions/credits and how they were handled in both estimates
If the mismatch is mostly child-related
- Verify number of children
- Verify parenting time allocation/custody-related input categories
If the mismatch seems time-related
- Confirm both estimates align with the general 3-year SOL period under SDCL 22-14-1 (general/default; no claim-type-specific sub-rule identified in the brief data)
Save your input set
- Keeping a copy of your inputs helps you reproduce the same run and avoids reintroducing multiple changes at once.
For a faster start, begin at /tools/alimony-child-support and then apply the controlled test above.