Spreadsheet checks before running Alimony Child Support in Philippines

What the checker catches

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

Before you run any alimony/child support computation in the Philippines with DocketMath (calculator: alimony-child-support), a spreadsheet is often where errors hide—wrong dates, mismatched parties, incomplete income lines, or a calculation basis that doesn’t match your scenario. The spreadsheet checker is meant to catch these issues before you generate numbers that you may later need to redo.

Here are the most common problems it flags in PH (Philippines) runs:

1) Missing or inconsistent key fields

A solid calculation starts with a stable “case snapshot.” The checker looks for:

• Recipient vs. payer roles flipped, especially when spreadsheets reuse templates
• Child details incomplete, such as the number of children provided not matching the child rows included
• Date fields that can’t be reconciled, such as a start date for the support period that doesn’t line up with the inputs you’re using

2) Income inputs that don’t reconcile

Most spreadsheet mistakes come from input structure and consistency, not necessarily from the math logic. The checker checks for:

• Null or zero income components when other parts of the spreadsheet indicate income exists
• Duplicate income lines, such as the same income source entered twice
• Totals not matching components, for example:

  • monthly income total differs from the sum of monthly income items
  • component amounts exist, but the total cell wasn’t updated

3) Currency and unit mismatches

Philippines-oriented spreadsheets are frequently built from different sources (pay slips, HR summaries, bank records). The checker helps catch:

• Amounts entered as annual when the spreadsheet expects monthly, or vice versa
• Mixed units such as some lines entered in pesos while others are entered in thousands, or incorrect decimal placement

4) Scenario drift (spreadsheet no longer matches your intended setup)

Even if every number is correct, your spreadsheet might be using the wrong scenario switches. The checker verifies:

• Whether the spreadsheet indicates which category you’re computing for (i.e., the intended modeling purpose of the run)
• Whether the computation period aligns with the date inputs

Pitfall: One of the most costly spreadsheet errors is pairing a correct spreadsheet with an incorrect scenario toggle. The output may look reasonable, but be built on the wrong basis—so the checker is focused on preventing that mismatch.

5) Output readiness checks

If the calculator is about to run, your spreadsheet needs to be “ready” for calculation. The checker validates things like:

• Required fields exist (no blanks feeding critical parameters)
• Formulas reference the correct cells (no references to removed or renamed cells)
• Values are numeric where numeric computation is expected

Think of the checker as a data QA gate: it helps ensure the inputs you pass into DocketMath are internally consistent.

Gentle note: This guide is about input quality and spreadsheet hygiene—not legal advice. Treat outputs as computational estimates and confirm with appropriate professionals for case-specific guidance.

When to run it

Run the spreadsheet checker at the moments where errors are most likely to slip in—and where catching them early saves you time.

Run the checker before importing a spreadsheet into the Alimony Child Support workflow. It is especially helpful when you have multiple entries or when a teammate provided the inputs.

Recommended timeline (practical workflow)

• Before you paste or enter values for your PH scenario into DocketMath
  Catch blank fields, mismatched totals, and unit issues first.
• After you update income or dates
  Pay-slip-based inputs can change quarterly, and edits can silently break formulas.
• Right before you finalize any scenario comparison
  If you test multiple setups (for example, different income assumptions), check each variant.

Quick “trigger checklist”

Rerun the checker if any of these happen:

Why “right before” matters

Once DocketMath produces results, it’s easy to move into interpretation. If the spreadsheet inputs are off, correcting later usually costs more—especially when you’re running multiple scenarios.

Try the checker

You can run the DocketMath workflow directly from the tool. Start with the primary CTA:

• Try: /tools/alimony-child-support

To use it in a way that reduces errors, follow a spreadsheet-first approach:

Upload the spreadsheet, review the warnings, and then run the calculation once the inputs are clean: Try the checker.

Step-by-step (spreadsheet-first)

1. Prepare your spreadsheet inputs for the PH scenario you’re modeling:

   • Identify the payer and recipient roles in your sheet
   • Enter children count and relevant child details
   • Provide your income breakdown (or the closest approximation your spreadsheet already contains)
   • Ensure date inputs are consistent (especially the start date for the computation period)
2. Run the spreadsheet checker to validate:

   • Missing or blank fields
   • Unit/currency consistency
   • Totals vs. components consistency
   • Scenario alignment (the intended purpose and date window)
3. Only then run the alimony-child-support calculator in DocketMath:

   • Confirm outputs reflect the scenario you intended
   • If numbers seem unusually high/low, recheck inputs and units before “tuning” results randomly

What to watch for when inputs change (input → output behavior)

This is a practical sanity guide (not legal guidance):

Compact checklist before clicking “calculate”

Use this each time you run a new scenario:

If your spreadsheet passes these gates, DocketMath’s calculator inputs are much more likely to produce results you can trust for scenario comparison.

Related reading

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