Why Settlement Allocator results differ in Philippines

The top 5 reasons results differ

When you run DocketMath’s Settlement Allocator for Philippines (PH) scenarios, differences usually come from how the allocator interprets jurisdiction-aware rules and how your inputs map to those rules. Below are the most common causes—diagnosed by symptom patterns you can reproduce.

1) Claim type mapping doesn’t match your document labels

Settlement Allocator depends on structured inputs (e.g., categories like damages, fees/costs, interest, attorney fees, other). If your case uses nonstandard labels (or you entered amounts under the wrong category), outputs shift because the PH rule set allocates differently per bucket.

Output symptom: amounts move disproportionately into “interest” or “costs” compared to your expectations.

2) Interest is modeled with different start/end anchors

Even when the total settlement figure looks consistent, changing the interest start date and/or cutoff/end date alters what portion the allocator assigns to interest vs principal-like components.

Output symptom: two runs produce the same total settlement but different distributions across components.

3) Partial settlement vs full settlement flags are inconsistent

If one run assumes a partial settlement (e.g., settlement covers only a subset of claims) and another assumes a global/full settlement, the allocator will reweight remaining claim components.

Output symptom: “missing” claim categories in one run; the other run spreads across all entered categories.

4) Tax/withholding and “net vs gross” interpretation differs

Allocator results vary when amounts are entered as gross settlement totals versus net amounts after deductions. For PH workflows, ensure your input convention is consistent; otherwise, the tool reallocates the same headline number across components differently to reconcile totals.

Output symptom: one output effectively “shrinks” certain categories while “inflating” others to make totals balance.

5) Currency/rounding and payment schedule granularity

Rounding rules and payment schedule modeling (single lump sum vs multiple tranches) can change allocation because the allocator reconciles totals at the component level using the specified granularity.

Output symptom: small rounding differences become noticeable—especially when you have many line items (e.g., 10+ claim components).

How to isolate the variable

Use a structured “single-change” approach. The goal: change one input at a time, re-run DocketMath, and observe which component(s) move.

1. Lock the totals

   • Keep the overall settlement total identical across runs.
   • Ensure currency and rounding settings remain the same.

2. Run a baseline

   • Use your most complete dataset (all claim categories + dates + flags).
   • Save the output snapshot.

3. **Change one dimension per iteration (recommended order)

   • First: claim category mapping
   • Second: interest start date
   • Third: interest cutoff/end date
   • Fourth: net vs gross convention / deduction flags
   • Fifth: payment schedule (lump sum vs tranches) and rounding

4. Compare deltas component-by-component

   • If only interest changes → the variable is date anchoring.
   • If multiple buckets shift but total stays constant → the variable is mapping, net/gross, or reconciliation logic.
   • If outcomes differ mainly by small cents → rounding/payment schedule granularity.

Here’s a quick troubleshooting matrix:

To speed up diagnosis, start from the same run setup each time and modify a single field.

If you want to reproduce quickly, use the tool directly: DocketMath Settlement Allocator.

Next steps

1. Confirm your input conventions

   • Are amounts entered as gross or net?
   • Are claims entered as partial coverage or full/global coverage?

2. Standardize claim categories

   • Align your labels to the allocator’s expected structure (damages, interest, costs/fees, other).

3. Validate the interest timeline

   • Check both the interest start date and cutoff/end date for the PH scenario you’re modeling.
   • Ensure the dates reflect the settlement’s practical allocation window.

4. Re-run with “controlled changes”

   • Do at least 3 iterations:

     • baseline
     • change claim mapping
     • change interest cutoff/end date (keep everything else fixed)

5. Document the winning configuration

   • Once you find the setting set that matches your internal expectations, store the exact input values for repeatability.

Gentle note: This is not legal advice—just practical guidance for debugging allocator behavior. If your inputs mirror your underlying documents, the remaining differences are usually explainable by the specific allocator assumptions you’re toggling.

Related reading

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