Why Alimony Child Support results differ in New Mexico

The top 5 reasons results differ

If you run the DocketMath Alimony + Child Support calculator for New Mexico (US-NM), you may notice your numbers don’t match a prior estimate—sometimes even when the inputs look “close.” In New Mexico, these differences usually come from how key factors are captured (or missed) in the inputs and how the calculation window is framed.

Here are the top 5 reasons results differ:

1. Timing and “which period” you’re modeling

   • Support calculations can depend on the effective date you model (and whether you’re effectively treating amounts as current vs. retroactive).
   • Small date shifts can change the modeled monthly outcome—especially if the calculator reflects changes that occur over time.

2. Income classification: gross vs. net assumptions

   • Alimony/child support calculations require a consistent definition of “income.”
   • Reported wages, bonuses, overtime, self-employment income, and certain benefits can be treated differently depending on which income lines you include and how you categorize them.
   • So two runs can look similar to you, but still diverge because the income definition changed.

3. Child-related inputs that subtly change the output

   • “Number of children” is only the obvious part.
   • Parenting-time inputs (and sometimes how you model overnights/days or age-related support eligibility details) can materially affect the output.
   • If your parenting-time estimate is approximate (e.g., using a simplified weekly average instead of a more exact schedule), the result can drift.

4. Alimony-specific differences in duration or need framing

   • Alimony outputs are especially sensitive to the assumptions you enter about duration and the way “need/ability” is represented through your alimony inputs.
   • If one run effectively assumes a shorter or longer support term, the monthly number can change even if the income numbers match.

5. **The “stale vs. current” data issue (SOL-aware)

   • The jurisdiction data provided for New Mexico includes a general 2-year statute of limitations for certain actions under N.M. Stat. Ann. § 31-1-8.
   • Important clarity: the content uses this general/default 2-year SOL because no claim-type-specific sub-rule was found in the jurisdiction data provided.
   • Practical effect: if you’re comparing a model built from income or circumstances that are more than 24 months old, the results may not align with what a court would likely treat as the relevant, timely baseline.

How to isolate the variable

When results don’t match, don’t “average” the discrepancy—systematically isolate the input that changed. Here’s a practical way to do it with DocketMath.

• 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.

A repeatable 10–15 minute diagnostic checklist

1. Freeze everything except one input

   • Keep all other fields the same: income line item(s), parenting-time inputs, children count, and alimony term/duration framing.
2. Run a baseline and record outputs

   • Capture the total monthly support output.
   • If the calculator shows separate lines, record alimony vs. child support amounts too.
3. Change only one variable

   • For example, update income from last year to current year—then rerun.
4. Compare deltas

   • Note the difference in monthly amount.
5. Repeat until you find the largest swing

   • The input that produces the biggest change is your likely “driver.”

Use a simple comparison log (fast and clear)

SOL-aware sanity check (New Mexico)

Because the provided New Mexico jurisdiction rule is a general 2-year period under N.M. Stat. Ann. § 31-1-8:

• Assume it’s the general/default SOL (no claim-type-specific sub-rule was found in the provided data).
• Then check whether your inputs are “fresh” enough for the period you’re comparing:

  • If income data is older than 2 years, update it in DocketMath and rerun.
  • If the modeled date window is older than 2 years, confirm you’re modeling the same period you’re comparing against.

Next steps

To turn “different numbers” into “the reason,” do this in order:

1. Confirm input definitions match

   • Did both runs use the same income concept (e.g., wages only vs. wages + variable comp)?
   • Did both runs use the same parenting-time representation?
2. Update time-sensitive information

   • Replace outdated income values.
   • Align effective dates or the calculation window so comparisons are apples-to-apples.
3. Document your delta

   • Once you identify the driver (income vs. parenting time vs. alimony duration framing), write down exactly what changed and by how much the monthly output moved.
4. **Bring a short question list to a professional (if needed)

   • “Which income components are included in your approach?”
   • “How are variable payments handled?”
   • “How does parenting time affect the monthly outcome in this setup?”

If you want to reproduce the New Mexico diagnostic yourself, start with the calculator configured for US-NM here: /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