Why Alimony Child Support results differ in Pennsylvania

The top 5 reasons results differ

If you run alimony and child support numbers through DocketMath for Pennsylvania (US-PA) and the result doesn’t match what you expected, the difference is usually driven by one of these five factors:

1. **Different assumptions about income (especially “support income”)

   • Even small changes to gross income, overtime, bonuses, or deductions can materially change the computed support obligation.
   • In DocketMath, the output typically moves when you adjust either parent’s income inputs or how recurring income is treated.

2. Timing and retroactivity assumptions

   • Many mismatches come from comparing a projected figure to an order that began on a different date.
   • For the timing-related framework referenced in your materials, Pennsylvania uses a general/default 2-year period under 42 Pa. Cons. Stat. § 5552.
   • Important: No claim-type-specific sub-rule was found in the provided data, so treat this 2-year period as the general baseline for the referenced period—not a claim-type-specific rule.

3. Custody/placement variables

   • Child support results are sensitive to placement (parenting time) inputs.
   • Even when income inputs are identical, changing the placement schedule can shift the final numbers.

4. Alimony type and input bundle mismatch

   • Alimony and child support calculations often require different input “bundles.”
   • If you reuse the same numbers for both categories without aligning them to the calculator’s required inputs (for example, duration assumptions or category-specific income treatment), the outputs can diverge.

5. Rounding, caps, and policy-mode differences

   • Two runs—either in different tools or different calculator settings—can differ due to rounding rules, minimum/maximum constraints, or how partial scenarios are handled (for example, low income or partial-month assumptions).
   • DocketMath helps here by making inputs explicit, so you can see which value is triggering the change.

How to isolate the variable

Use a short, practical “diagnostic pass” to identify what is changing the output in DocketMath. The goal is to avoid guessing and instead run controlled comparisons.

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

Step 1: Freeze everything except one input

Create a quick comparison table and change only one variable at a time:

Step 2: Run “paired” scenarios

Do at least two runs:

• Run A (baseline): your current best estimate
• Run B (one change): adjust only the single variable you suspect

Then compare:

• Total obligation (if shown)
• Alimony component (if shown separately)
• Child support component (if shown separately)
• Any intermediate metrics DocketMath displays (such as calculated support income)

Step 3: Anchor timing surprises to Pennsylvania’s general rule

If the mismatch appears tied to timing/period length, anchor your expectation to the general/default 2-year period under 42 Pa. Cons. Stat. § 5552. Since the provided data did not identify a claim-type-specific sub-rule, don’t swap in a different lookback period unless your specific case facts and sources clearly support it.

(This is informational only and not legal advice.)

Next steps

1. Open DocketMath and start with the primary calculation run

   • Use the DocketMath calculator here: **/tools/alimony-child-support

2. Create an “input audit list” before you re-run

   • Review these first:

     • Income inputs for both parents (including recurring vs. one-time amounts)
     • Placement/parenting-time inputs
     • Any effective date / order-start assumptions you enter
     • Alimony-related parameters you select or fill in

3. Record exactly what changed

   • Keep a simple change log, for example:

     • Effective date changed from X to Y
     • Placement schedule changed from S1 to S2
     • Parent B income changed from $A to $B

4. Determine whether the mismatch is “structure” or “numbers”

   • Structure mismatch: you’re feeding the wrong category of inputs into the model.
   • Numbers mismatch: the categories are correct, but income/placement/date assumptions differ.

If you’re trying to reconcile outcomes, input-level isolation is usually faster than re-arguing the overall calculation.

Related reading

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