Common Settlement Allocator mistakes in Philippines

The top mistakes

Run this scenario in DocketMath using the Settlement Allocator calculator.

Using a Settlement Allocator in the Philippines with DocketMath can speed up drafting and internal review—but small input choices can materially change the allocation outcome. Below are the most common mistakes we see when teams use /tools/settlement-allocator under PH jurisdiction settings.

1) Mixing up “who gets paid” vs. “what the payment covers”

A frequent error is entering settlement amounts that already include costs, interest, or attorney’s fees, then also adding those items again as separate categories. The result: double-counting.

What this breaks

• The allocator output may allocate more to individuals than intended.
• Payment breakdown totals can stop matching the agreement figure.

Checkbox to prevent it

2) Using the wrong currency precision

Teams sometimes enter amounts in whole pesos when the agreement includes cents (or when internal calculations require rounding rules). Another variant: rounding per line item rather than once at the end.

Practical impact

• Rounding differences can create “leftover” cents that cause downstream reconciliation issues.

Quick check

3) Incorrectly allocating based on “equal shares” when the settlement uses ratios

If the agreement describes allocation by:

• percentage of claim,
• contract milestones, or
• damages categories,

…then selecting an equal-share approach in the allocator often produces a logically inconsistent distribution.

Outcome you’ll notice

• The output distribution doesn’t align with the settlement logic your signatories relied on.

Pitfall to watch

• Equal allocation feels “fair,” but when the settlement defines a formula (e.g., 70/30, or by category value), using equal shares can create an allocation that doesn’t match the instrument—even if the totals match.

4) Failing to separate categories (principal vs. interest vs. fees)

Settlements in the Philippines often reference multiple components (e.g., principal claim amount, accrued interest, and litigation-related expenses). If you enter one combined number into the allocator without mapping categories, the output can’t support a clean breakdown.

What you lose

• Audit trail clarity for internal review and reconciliation.

Checkbox to prevent it

5) Not reconciling the “Total to distribute” to the agreement’s payment section

Another classic error is using a “total damages” figure rather than the “total settlement amount” stated in the payment clause.

How outputs change

• If the agreement says “Settlement amount: PHP 5,000,000 inclusive of attorney’s fees,” but you input “damages only,” the allocator will allocate too little for what the agreement contemplates—or too much if you add fees separately.

Quick validation

6) Forgetting the Philippines jurisdiction setting (PH ruleset)

DocketMath’s PH jurisdiction awareness affects how the allocator interprets common settlement components and expected breakdown structure.

If the allocator is run under the wrong jurisdiction setting, the distribution can appear “reasonable” while still being structurally inconsistent with PH-oriented handling.

Checkbox to prevent it

7) Adding recipients with missing or zero shares/weights

Some teams list all potential recipients but leave weights blank or enter 0 by accident. Depending on the allocator logic, recipients can be excluded silently or distort proportional totals.

What you’ll see

• Fewer recipients than expected, or allocations that don’t sum correctly.

Recommended workflow

How to avoid them

You can reduce errors quickly by tightening the workflow around inputs, outputs, and reconciliation. Below is a practical checklist designed for DocketMath users preparing PH allocations.

Use a written checklist for inputs, document each source, and run a quick sensitivity check before finalizing the result. When two runs differ, compare inputs line by line and re-run with one variable changed at a time.

Step 1: Build your inputs from the settlement text

Use the settlement agreement’s payment section as the source of truth.

• Identify the Total settlement amount stated for distribution.
• Extract any component amounts (principal/interest/fees/costs) exactly as written.
• Capture allocation drivers:

  • percentages,
  • ratios,
  • or fixed category amounts.

If you want a fast starting point, run the tool early—but validate before finalizing.

• Use /tools/settlement-allocator: start with draft numbers, then iterate against the agreement figures.

Step 2: Validate totals before worrying about line-item aesthetics

In DocketMath, the most reliable quality signal is whether the breakdown totals reconcile.

Reconciliation checks

Step 3: Use consistent rounding strategy

Pick one strategy and keep it consistent:

• Round only at the end (preferred for reconciliation), or
• Round per line item (only if your agreement or internal policy requires it)

Then compare the difference between:

• “sum of rounded parts” and
• “rounded grand total”

If they don’t match, adjust your approach so the final output is agreement-ready.

Step 4: Treat formula-based settlements as formulas

If your settlement allocation method is defined in the document (for example, “allocated according to verified receipts,” “70%/30% split,” or “by category value”), set DocketMath inputs to mirror that method rather than defaulting to equal shares.

Quick rule

Step 5: Run a “what-if” sanity pass

After generating a result, run a minor controlled variation to test stability:

• change a single weight slightly (e.g., 30% → 31%),
• confirm only the expected recipient changes.

This helps catch mapping errors (like swapped categories or wrong recipients).

Step 6: Keep an internal “reason codes” note

For each category or recipient, record the reason the value exists (e.g., “principal portion per payment clause,” “interest per computation annex,” “fees included in total per paragraph 8.3”). DocketMath outputs become far easier to review when someone can trace every number.

Gentle reminder: DocketMath helps structure and calculate allocations, but it isn’t a substitute for reviewing the settlement agreement itself.

Related reading

• Settlement Allocator Guide for Alabama
• Settlement Allocator Guide for Arizona
• Settlement Allocator Guide for Colorado