Why Alimony Child Support results differ in Philippines

The top 5 reasons results differ

If you run DocketMath’s alimony-child-support calculator for the Philippines (PH) and your outputs don’t match another party’s (or an older estimate), the mismatch is usually explainable. Here are the top 5 causes we see most often—each one tied to a specific input or assumption.

1. **Different household facts (income + dependents)

   • Even when the “same” monthly support is being discussed, estimates can drift because one run assumes different income sources, different allowable deductions, or different dependent counts.

2. Child support vs. “alimony” labels getting mixed

   • In practice, people use “alimony” loosely when they actually mean support for children, spousal support, or a combination. If you enter child-related assumptions into a spousal slot (or vice versa), the calculator’s logic can produce a very different result.

3. Timing: arrears and ongoing support treated differently

   • Some scenarios include past-due months (arrears), while others compute only current ongoing support. Mixing these two approaches changes totals dramatically, especially for multi-month gaps.

4. Custody/parenting-time assumptions

   • Where custody arrangements are entered differently (e.g., who primarily provides day-to-day care), support computations can diverge because the effective “cost allocation” assumption changes.

5. Rule-set/jurisdiction awareness in the tool

   • DocketMath is jurisdiction-aware for PH. If a calculation was run with a mismatched jurisdiction code or with a configuration that doesn’t reflect PH logic, outputs won’t align—even if the numbers look close.

How to isolate the variable

Use a structured “diagnostic panic” workflow to pinpoint the exact input that drives the difference. Start by running the calculator once with your best-known facts, then change only one thing at a time. This keeps you from chasing “phantom differences” caused by multiple changes at once.

1. Confirm jurisdiction selection

   • Make sure the run is for Philippines (PH).
   • If you’re comparing with someone else, ask what jurisdiction code they used and whether they used DocketMath’s PH rules.

2. **Log your inputs (copy the setup)

   • Record these items from each run:

     • Reported monthly income for the paying parent
     • Reported monthly income for the receiving parent (if used in your run)
     • Number of children / dependent count
     • Custody or care arrangement inputs
     • Whether the output is ongoing only or includes arrears
   • Then compare run A vs run B line-by-line.

3. Flip one switch at a time

   • Create a small test matrix like this:

     • Change only dependent count (e.g., 1 child → 2 children)
     • Reset everything else to the original values
     • Note how the output changes
   • Repeat for custody assumptions, the arrears toggle, and any “support type” selector.

4. Use quick “delta” checks

   • If the other person’s result is consistently higher by a fixed pattern, it often signals a structural difference (like including arrears or using combined support assumptions).
   • If it changes erratically, it often signals category confusion (child vs spousal) or income mapping differences.

5. Use the calculator as a controlled experiment

   • Your goal is to make the inputs identical except for one variable.
   • Then the output delta tells you exactly what matters.

For convenience, you can rerun and compare in DocketMath via: Alimony/Child Support Calculator.

Gentle disclaimer: This is an estimation tool workflow, not legal advice. If you need a legally binding determination, consult a qualified professional for the specific facts and applicable rules.

Next steps

Once you’ve isolated the variable, take these practical actions to make your future results reliable and repeatable:

• Standardize your input definitions

  • Decide, for your own tracking, what “monthly income” means in your entries (gross vs net, whether bonuses are included, whether irregular income is averaged).

• Separate output types

  • Keep two separate records:

    • Ongoing monthly support estimate
    • Total arrears estimate (if you’re including past months)

• Document the scenario

  • Write down the scenario “statement,” e.g.:

    • “2 children, PH jurisdiction, ongoing only, custody assumed as ___, arrears excluded”

• Run a comparison checklist before finalizing

  • Use this before each calculation:

• Avoid a common pitfall

  • If you compare results that mix “ongoing” and “arrears,” you can falsely conclude the calculator is wrong. The tool may be consistent—your scenario comparison isn’t.

Finally, treat DocketMath outputs as scenario-based estimates rather than a guaranteed final figure. The practical win is repeatability: once your input framework is consistent, differences become easy to explain and defend internally.

Related reading

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