How to calculate Alimony Child Support in Philippines

Quick takeaways

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

• In the Philippines, child support is governed primarily by the Family Code (especially Articles 194–208), while spousal support (alimony-like support) is treated under support obligations discussed in the same statutory framework (with the exact application depending on the parties’ legal relationship and circumstances).
• DocketMath’s alimony-child-support calculator helps you compute recommended amounts based on the inputs you provide—then it applies Philippines-specific, jurisdiction-aware rules to estimate obligations.
• For children, the key moving parts are usually: number of children, income figures (capacity), and any verified special circumstances you input (e.g., custody/physical care and recurring education/health needs).
• Courts generally expect support to be commensurate with need and capacity, so changing income inputs can shift results quickly.
• If you’re using the calculator for planning, build your numbers with documentation: pay slips, tax returns, and custody/expense evidence.

Inputs you need

Before you open DocketMath at /tools/alimony-child-support, gather these items. Missing fields usually make the output less reliable because the calculator needs enough data to map “need vs. capacity” for the PH context.

Use this intake checklist as your baseline for Alimony Child Support work in Philippines.

• jurisdiction selection
• key dates and triggering events
• amounts or rates
• any caps or overrides

If any of these inputs are uncertain, document the assumption before you run the tool.

A. Relationship + obligation type

(DocketMath uses jurisdiction-aware logic to decide which support “bucket” to compute.)

B. Children-related inputs (for child support)

C. Income + capacity inputs (for both)

You’ll typically need:

D. Duration and payment cadence

E. Verification notes (optional, but improves usefulness)

How the calculation works

DocketMath applies a Philippines-aware approach that separates child support from spousal support and then uses a structured “need and capacity” model.

DocketMath applies the Philippines rule set to the inputs, then runs the calculation in ordered steps. It validates the trigger date, applies rate or cap logic, and produces a breakdown you can audit. If you change any one variable, the tool recalculates the downstream outputs immediately.

1) Split the problem: child support vs. spousal support

When you select:

• Child support, the calculator estimates an obligation focusing on children’s needs and the payor’s capacity.
• Spousal support, it focuses on lawful entitlement concepts (including the general statutory framework on support) and the relative financial situations you enter.

This separation matters because the “what drives the number” differs.

2) Translate your inputs into “need” and “capacity”

DocketMath treats your income entries as a proxy for capacity. Then it incorporates either:

• A baseline child support component tied to the number of children and your custody input, and/or
• Any expense line items you entered (education, medical, transport).

Spousal support, by contrast, generally relies more heavily on:

• The support-recipient income (if you provide it), and
• The supportor capacity you input.

3) Apply statutory logic in jurisdiction-aware steps (PH rules)

Philippine law sets the principle that support obligations are tied to need and the ability to give. In practice, courts evaluate:

• The child’s needs (education, health, living requirements),
• The supportor’s financial capacity,
• The parties’ circumstances and custody setup.

DocketMath’s PH engine reflects these ideas by:

• Adjusting for the number of children,
• Adjusting for custody arrangement (when you provide it),
• Integrating your expense inputs where available,
• Scaling results when the supportor income changes.

4) Output the estimate and the drivers

After running the calculator, DocketMath shows:

• Estimated monthly child support
• Estimated monthly spousal support (if selected)
• A summary of which inputs had the biggest effect (typically: income and number of children)

You can use these outputs to run “what-if” scenarios (e.g., increased education expenses, or different income figures).

5) Example scenario (illustrative only)

Assume you enter:

• 2 children
• Primary care with the mother
• Supportor monthly income: PHP 80,000
• Child expenses included: PHP 18,000 (education + medical components included in your breakdown)
• Spousal support selected with recipient monthly income: PHP 25,000

DocketMath would likely produce:

• A child support output that reacts strongly to the PHP 80,000 capacity figure and the 2 children multiplier/adjuster, plus the documented expenses you added.
• A spousal support estimate that depends on the difference between supportor capacity and recipient income—so if you raise recipient income, the spousal support estimate usually drops.

Common pitfalls

• missing a required input
• using a stale rate or rule
• ignoring calendar or holiday adjustments
• skipping documentation of assumptions

Capture the source for each input so another team member can verify the same result quickly.

When rules change, rerun the calculation with updated inputs and store the revision in the matter record.

1) Using inconsistent income baselines

If you swap between gross and net values across runs, DocketMath will compute different “capacity” levels and you may misread the impact as a legal change rather than a data mismatch.

Checklist

2) Under-entering child-specific expenses

When you provide education/medical costs, the estimate can meaningfully increase—especially for recurring items.

Common omissions

3) Ignoring custody arrangement effects

If the calculator input says “primary care” but your actual facts are “shared care,” the output can be biased.

Quick fix

4) Overestimating what the calculator can “prove”

DocketMath estimates obligations from your inputs. In real proceedings, evidence matters—so your numbers should be traceable to documents.

5) Mixing spousal support and child support in one mental bucket

Many people compare one combined number to a prior discussion and assume it’s “all the same.” DocketMath keeps them separate—yet your narrative to others should also keep them separate.

Practical approach

Sources and references

These are the Philippines legal anchors that inform support principles used by jurisdiction-aware support calculators like DocketMath:

• Family Code of the Philippines (Executive Order No. 209), Book I, Title VIII (Support):

  • Articles 194–208 (support generally; includes principles of need and ability to give; covers different support relationships)
  • Article 195 (family support principles applicable to certain support contexts)
  • Articles 201–206 (duties, enforcement, and related mechanics of support obligations)
• Family Code of the Philippines provisions on the obligation to support (within the same Title/Book segment) and related procedural concepts.

Next steps

1. Open DocketMath’s tool here: /tools/alimony-child-support
2. Enter:

   • Number of children and custody arrangement
   • Supportor income (consistent basis: gross or net)
   • Child expense breakdown (education/medical first)
3. Run two scenarios:

   • Baseline (your current facts)
   • Adjusted (e.g., updated income or added verified medical costs)
4. Save your results by screenshot or notes so you can compare driver-by-driver changes.
5. Prepare documentation that matches your calculator inputs:

   • Income proof (pay slips, tax forms)
   • Receipts/invoices for education and medical costs
   • Evidence supporting custody arrangements (if available)

Related reading

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