Why Alimony Child Support results differ in New York

The top 5 reasons results differ

Run this scenario in DocketMath using the Alimony Child Support calculator.

If you run the DocketMath Alimony Child Support calculator for New York (US-NY) and the results don’t match what someone else sees, the mismatch is usually due to a small set of inputs and timing assumptions. New York’s framework isn’t “one number for everyone”—even when the same worksheet is used, tiny differences can compound into meaningfully different outcomes.

Here are the top 5 reasons results differ in practice:

1. **Different income definitions (and how they’re entered)

   • Wages vs. self-employment, bonuses, overtime, commissions, and employer-paid benefits can be treated differently in calculations.
   • In DocketMath, the outcome is driven by the income figures you input—if they’re based on different pay periods or include different components, the result will shift.

2. Child support depends heavily on household and child details

   • Number of children, custody-time assumptions, and other household obligations can change the calculation inputs.
   • Even when the same two people are involved, different child-care arrangements or different reporting of “who provides what” can produce different outputs.

3. Spousal support (alimony) timing and duration assumptions

   • Results can change based on the length of the relationship and the effective start date used in the model inputs.
   • If one run uses one start date and another uses a different one (even by a few months), the output period weighting can diverge.

4. Lookback/arrears comparisons can create the impression of a “math error”

   • People sometimes compare a current-support figure to a back-support total (or vice versa). That creates a gap that looks like an error but is actually a comparison of different time horizons.
   • New York’s general statute limitation reference provided here is 5 years. The New York criminal procedure statute includes a general/default reference: N.Y. Crim. Proc. Law § 30.10(2)(c) (and this is a general/default period, not claim-type-specific based on the jurisdiction data provided).

     • In other words: treat this as a general limitation framework for “how far back” issues may be evaluated—not a claim-type-specific rule.

5. Credit for prior payments and treatment of one-time events

   • If another run assumes prior payments were handled differently (or excludes/includes one-time changes like a temporary job loss or one-off income adjustment), the totals you see won’t line up.
   • DocketMath can’t infer adjustments—your entered variables determine what the model computes.

Quick warning: Don’t compare a “monthly estimate” to a “total over time” number unless the time window matches. Many mismatches are unit/timing errors rather than true calculation differences.

How to isolate the variable

To pinpoint why two DocketMath runs differ in US-NY, isolate inputs in a controlled sequence. Use this checklist:

• Are you comparing monthly amounts, or totals across months/years?
• Use the same definition (e.g., “base pay only” vs. “base + bonus + overtime”).
• Keep pay-period timing consistent (weekly vs. biweekly vs. monthly).
• Same number of children.
• Same custody-time assumptions (or the custody driver your calculator uses).
• Repeat the calculation using the same effective start date used by the other run.
• Duplicate the original run with identical inputs.
• Change only one category at a time (income, custody/child count, alimony timing, or other obligations).
• Record the output difference after each change.

A practical diagnostic pattern:

• If changing income causes large swings → the mismatch is likely income definition/timing.
• If changing child inputs shifts the result more → it’s likely child-parameter driven.
• If things only differ when you change the start date/duration → timing and period alignment is the likely culprit.
• If numbers differ mainly when comparing totals vs. present estimates → it may be a “time window” issue; the provided general/default limitation reference is 5 years via N.Y. Crim. Proc. Law § 30.10(2)(c) (general/default, not claim-type-specific).

Gentle note: This guidance is for troubleshooting calculator assumptions and comparisons—not legal advice.

Next steps

1. Run a baseline DocketMath calculation using your best “single source” inputs.

   • Use consistent units (monthly vs. annual).
2. Create three sensitivity runs (only if you’re troubleshooting):

   • Run A: baseline
   • Run B: adjust income inputs slightly (e.g., include/exclude bonus)
   • Run C: adjust custody/child count assumptions (only if you’re unsure)
3. Compare outputs by component

   • Separate what changed: the child-support component vs. the alimony component.
4. Document the exact inputs you used

   • If you need to explain the difference to another party or a prep team, input transparency speeds up reconciliation.

If you want to reproduce your baseline exactly, use the same assumptions consistently.
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