Why Alimony Child Support results differ in Indiana
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 Indiana (US-IN) and get different results than another run (or another tool), it’s usually because of input variation, not “mystery math.” Indiana-aware calculators can diverge when the assumptions and included items that turn your inputs into monthly numbers aren’t aligned.
Here are the top 5 reasons you’ll see different results:
Different definitions of income
- Even for the same jurisdiction, calculators may treat income items differently (for example: overtime, bonuses, education-related income, or pass-through benefits).
- Changing what you label as “gross” vs “net” (or how the tool converts between them) can move the output a lot.
Different child-related inputs
- The number of children and the ages (or the entered guideline category) can change the support output.
- If your workflow includes custody/time shares (even informally), small changes there can materially alter results.
Different alimony modeling choices
- DocketMath computes using its calculator logic, but other workflows may differ by:
- duration assumptions (how long support lasts),
- “type” or scenario assumptions, or
- which parts of income are treated as available for alimony versus support.
- If those inputs don’t match, the monthly combined result can change.
Unequal expense treatment
- Some tools rely mostly on income inputs only.
- Others approximate or directly account for expenses (such as health insurance premiums, childcare, or extraordinary costs) through additional categories/inputs.
- If one calculator includes an item and the other doesn’t (or uses different amounts), outputs will differ.
**Timing assumptions (and enforcement horizon)
- When you compare temporary vs final numbers, or scenarios with different “start dates,” timing can affect what’s included in each comparison.
- Also, disputes can become stale over time. In Indiana, the general statute of limitations (SOL) baseline is 5 years under Indiana Code § 35-41-4-2.
- The provided jurisdiction data does not identify a claim-type-specific sub-rule, so treat this as the general/default baseline rather than a guarantee for every claim type.
Practical note: DocketMath outputs reflect the inputs you choose and the tool’s ruleset. If two runs use different income definitions, child/custody parameters, expense inclusions, or duration assumptions, the results will differ—even if the numbers look close.
How to isolate the variable
To diagnose why two Indiana runs don’t match, do a controlled comparison: change one input at a time, and keep everything else identical. That makes it obvious which assumption causes the pivot.
Start with a baseline run
- Use Indiana (US-IN) consistently.
- Use a single, consistent “income basis” across runs (for example, both runs use the same gross-to-net assumption).
Lock the categories that usually drive the largest changes Keep these fixed while you test:
- monthly income numbers,
- number of children and their age/category inputs,
- any health insurance / childcare / expense inputs you use (if your workflow includes them),
- custody/time-share inputs (if used in your process),
- alimony duration/type assumptions (if your workflow includes them).
Change only one variable per run Run a sequence where each new run changes just one item. Common single-variable tests:
- switch income definition (gross vs net),
- change one expense line item (e.g., health insurance premium amount),
- change custody/time-share inputs slightly (if applicable),
- change the number of children or age/category group.
Record the delta For each change, write down:
- the difference in monthly support output,
- the difference in monthly alimony output (if applicable),
- whether one component moves while the other stays stable.
That pattern usually tells you which input the model is weighting most.
**Sanity-check against the Indiana SOL baseline (only for timing/retroactive questions) If your scenario involves delayed assertions, retroactive concepts, or arrears timing, remember the general SOL baseline is 5 years under Ind. Code § 35-41-4-2.
- Because no claim-type-specific sub-rule was identified in the provided jurisdiction data, treat this as the general/default baseline.
If you want to reproduce your test, use the calculator here: /tools/alimony-child-support.
Next steps
Use your isolate-test results to standardize your inputs:
- Reconcile your income definitions: Confirm whether each run uses the same gross/net framing and the same income inclusions (bonuses/overtime/other items).
- Match expense inclusions: Decide whether your scenario includes health insurance and childcare as explicit inputs, and keep those amounts consistent across runs.
- Document the exact input set: Save the DocketMath input list (or screenshot) for each run so you can compare changes line-by-line.
- Run a 5–10 variant test: Change one category per run to find the “pivot input” that causes the biggest jump in output.
- Be careful when comparing across tools: Don’t compare results from different models unless they share the same income basis, child/custody parameters, expense treatment, and duration assumptions.
Disclaimer: This is a practical troubleshooting guide, not legal advice. For advice about a specific case’s inputs, timing, or enforceability, consult a qualified Indiana family-law professional.