Why Alimony Child Support results differ in Idaho

The top 5 reasons results differ

When you run a DocketMath alimony-child-support calculation in Idaho (US-ID), different outputs usually come from repeatable factors—especially the inputs you don’t always realize you’re changing. Idaho’s mechanics are commonly fed by financial documents, expense schedules, and negotiated/assumed terms, so small differences can cascade into noticeably different totals.

Here are the top 5 reasons results differ:

1. **Income used (gross vs. net, and what counts as “income”)

   • Two people may report the same “pay amount,” but one dataset can include different categories such as bonuses, overtime, self-employment adjustments, or retirement/benefit deductions.
   • If the income definition shifts between runs, DocketMath will typically produce different support amounts.

2. Time period / payment schedule alignment

   • Alimony and child support often depend on timing—monthly vs. annualized, or adjustments that reflect changes in income over time.
   • If one run effectively treats numbers as annualized while another uses a monthly snapshot (or a different timing convention), the outputs can diverge.

3. Health insurance and childcare assumptions

   • Even when the core formula is driven by income, add-ons like health insurance and childcare can change the final figure.
   • Differences in whether these costs are entered, how they’re entered, or whether they’re treated as included vs. separately accounted for can alter results.

4. Credit, offset, or schedule variations

   • Parenting-time structure and how the worksheet applies credits/offsets can impact the computed obligation.
   • If the custody/visitation schedule differs between runs (or if the same schedule is implemented differently in the worksheet), the calculated output can change.

5. **A mismatch in “when” the calculation is measured (and why you may see SOL-driven discrepancies)

   • Idaho has a general 2-year statute of limitations (SOL): Idaho Code § 19-403.
   • The key point for this article: the provided jurisdiction data indicates this is the general/default period, and no claim-type-specific sub-rule was found in the data you provided. That means your timeline assumptions can affect what months are treated as within the calculation window—so two runs can look inconsistent even if the monthly formula components are similar.
   • Also, a difference in the months covered can create a different total even when the monthly inputs match.

Quick reference: Idaho limitations data used here

Note: This is general information about “why outputs differ” for auditing purposes—not legal advice.

How to isolate the variable

To pinpoint why two DocketMath runs differ, use a structured “change one thing at a time” approach. You’re looking to identify whether the discrepancy is coming from inputs, assumptions, or coverage/timing.

Use this checklist:

• Confirm the same pay period basis (monthly vs. annualized).

• Ensure the same categories are included/excluded (bonus/overtime/side income, etc.).

• Match health insurance cost amounts and whether they’re included in the run.

• Match childcare amounts and how any childcare is treated in the worksheet.

• If the worksheet inputs incorporate parenting time or custody credits, ensure both runs use the same schedule inputs.

• Make sure both runs are effectively calculating over the same time horizon and “months covered.”

• This is where Idaho’s general 2-year SOL under Idaho Code § 19-403 can matter for what’s being counted, especially since no claim-type-specific sub-rule was identified in the provided jurisdiction data.

• Compare monthly amounts first.

• Then compare totals across the coverage window.

• If the monthly results match but the totals differ, the “months covered” / timeline alignment is the likely driver.

Common pitfall: Comparing two totals without checking the “months covered” can make it look like the calculator logic changed when it’s actually a timeline mismatch.

If you want a fast diagnostic workflow:

1. Run two scenarios (Run A and Run B).
2. Swap one input category at a time (income → expenses → schedule → timing window).
3. Stop as soon as the outputs converge; the last change you made is usually the cause.

For a direct starting point, use: Alimony/Child Support Tool.

Next steps

If your DocketMath alimony-child-support results don’t line up with another party’s calculation, the best next step is to produce an input audit—not argue about which number is “right” without confirming the assumptions.

Practical path:

• Export or record your DocketMath inputs (income, expenses, any schedule/credit inputs, and the timing window).
• Request the other run’s input set and compare category-by-category.
• Re-run using your inputs but align the other party’s timeline window, then compare again:

  • If results track once the timeline matches, the discrepancy is likely coverage/timing, where Idaho’s general 2-year SOL under Idaho Code § 19-403 can influence what months are considered.
• If deadlines or SOL concerns feel unclear, treat this as a starting point for discussion and consider getting guidance tailored to your specific situation.

Gentle disclaimer: This is for understanding why calculator outputs differ and how to audit inputs. It’s not legal advice.

Primary CTA: /tools/alimony-child-support

Related reading

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