Why Alimony Child Support results differ in Arizona

The top 5 reasons results differ

If you’re running DocketMath’s “alimony-child-support” calculator in Arizona (US-AZ) and your results don’t match what you expected, the cause is usually not arithmetic—it’s the inputs and how the calculator applies jurisdiction-aware rules. In practice, even a small change in one input can shift the monthly outputs.

Here are the top 5 reasons your alimony and child support results may differ.

1. Different inputs about income and expenses

   • Child support is especially sensitive to the income numbers you provide, how frequently you’re paid, and what expenses you list as allowable deductions.
   • Alimony can also change based on the financial information entered for each spouse and the structured assumptions used by the calculator (even when it’s not framed as “court discretion,” the outcome still tracks the inputs).
   • Example of how results can diverge: entering gross vs. net income, or adjusting pre-tax deductions, may move the final figure noticeably.

2. Parenting time (custody schedule) assumptions

   • Child support calculations often depend on the assumed time share.
   • If one run assumes equal time while another assumes unequal time, the outputs can differ even with identical income inputs.

3. Recurring obligations vs. one-time items

   • Recurring payments and ongoing financial obligations are typically treated differently than one-time items.
   • If an obligation is recurring but entered as a one-time expense (or omitted entirely), results can shift because the model will “weight” that financial impact differently across time.

4. Rounding, caps, or minimum/maximum constraints

   • Even when the underlying framework is consistent, calculators can apply rounding conventions or caps/min/max limits internally.
   • That means two people using the same facts but different input formatting (or different rounding behavior) can see slightly different monthly numbers.

5. **Timing confusion (default rule timing vs. claim-specific timing)

   • Arizona has a general statute of limitations (SOL). The general/default period is 2 years under A.R.S. § 13-107(A).
   • Important: The provided jurisdiction data did not include any claim-type-specific sub-rule, so you should treat 2 years as the baseline only, not as an automatic rule for every possible scenario.
   • Note: SOL affects whether certain claims may be available; it generally does not change the amount calculation for alimony/child support based solely on the inputs you enter into the calculator.

How to isolate the variable

Treat this like debugging: change one thing at a time, and compare outputs.

• Run the calculator twice, changing only one variable per run

  • Example: keep income identical; change only the parenting-time input.
• Record the outputs for each run

  • Track: alimony result, child support result, and any combined total.
• Check input normalization

  • Confirm you’re using the same format across runs:

    • Monthly vs. annual figures
    • Gross vs. net income
    • Whether deductions are already reflected or need to be entered separately
• Validate schedule assumptions

  • If the parenting schedule changed between scenarios, that’s usually one of the first suspects for child support differences.
• Re-enter recurring vs. non-recurring items consistently

  • If an expense repeats each month, enter it the same way each time (and don’t mix recurring and one-time entries between runs).

Quick triage table (use it to speed up your comparison):

Next steps

1. Start from one “source-of-truth” input set

   • Use the same income basis, the same time-share schedule, and the same list of expenses/obligations in each run.
2. Run a controlled comparison

   • Change only one variable per run, and document the difference in alimony and child support outputs.
3. Confirm you’re using Arizona (US-AZ) correctly

   • DocketMath is intended to be jurisdiction-aware; choosing the wrong jurisdiction can create misleading discrepancies.
4. If timing matters, treat the general SOL as a baseline

   • For general SOL questions, use the 2-year baseline under A.R.S. § 13-107(A).
   • Do not assume a claim-specific exception unless you’ve confirmed it with the correct claim-type rules.
5. Discuss the “why” with your case team

   • Once you identify the variable driving the change, you can explain the discrepancy clearly (rather than debating the math).

Primary action: Run DocketMath here: /tools/alimony-child-support

Related reading

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