Settlement Allocator reference snapshot for Philippines
6 min read
Published April 15, 2026 • By DocketMath Team
Rule or statute summary
This “reference snapshot” shows how DocketMath’s Settlement Allocator can support a Philippines (PH)-focused allocation of settlement proceeds using jurisdiction-aware inputs and common claims/relief logic. It does not provide legal advice—treat it as a workbench for organizing settlement discussions, documentation, and internal calculations.
What the Settlement Allocator is designed to reflect (PH context)
In Philippine civil practice, settlement allocations often need to reflect the nature of the underlying claims and the relief categories typically pleaded and proven—e.g., actual damages, temperate damages (where applicable), moral damages, exemplary damages, attorney’s fees (when allowed by law or contract), and interest (when legally recoverable). The allocator can map settlement amounts into these buckets so that you can:
- track what the parties are effectively valuing (by claim category),
- document agreed valuation assumptions,
- reconcile the final settlement figure against your internally defined inputs.
Key allocation drivers for PH
The same overall settlement number can allocate differently depending on several common drivers:
Claim category mix
If the dispute is primarily about property loss, the settlement may logically emphasize actual damages. If it’s centered on non-pecuniary harm caused by wrongful conduct, the discussion may more naturally support moral (and in appropriate cases, exemplary) damages. If the case is framed as a contract dispute, damages and interest treatment can shift depending on the relief sought and agreed.Nature of entitlement to damages
Philippine civil law differentiates categories (actual vs moral vs exemplary) and recognizes that recovery depends on the circumstances and legal standards applicable to the cause of action.Interest treatment
Whether the settlement amount is described (and calculated) as including interest can significantly change the implied split between “principal-like” damages and “interest-like” amounts.
Pitfall: Allocating the entire settlement to a single bucket (e.g., “damages only”) can make later internal reporting, approvals, or documentation inconsistent with what the settlement agreement actually intends. Using multiple buckets helps align the allocator output with the settlement narrative.
Practical “bucket” approach (what to prepare)
To get stable and defensible allocator results, prepare:
- the agreed total settlement amount,
- a claim-category breakdown (even rough internal estimates),
- whether the settlement includes interest, and if so the basis you’re using,
- any agreed treatment of attorney’s fees,
- what the matter is best characterized as for allocation purposes (e.g., tort/quasi-delict vs contract), since it affects which damages categories are logically included.
Citations
The allocator’s jurisdiction-aware mapping is grounded in Philippine law concepts commonly referenced in settlement discussions (noting that settlement drafting can vary widely, and the final allocation should match the settlement agreement’s actual language and intent).
- **Civil Code (Republic Act No. 386)
- Articles 2199–2200: Actual damages / temperate damages (where applicable)
- Articles 2217–2220: Moral damages (and related standards)
- Article 2232: Exemplary damages in appropriate cases
- Articles 2208–2209: Attorney’s fees (when allowed) and interest-related rules that can affect damages recovery concepts
- Civil Code — legal interest concepts
- Article 2209 (commonly cited for indemnity/interest on damages/obligations where delay is relevant)
Because settlements can be structured in many ways, your allocator inputs should align with:
- the relief demanded in the complaint,
- the pleaded causes of action (contract vs tort/quasi-delict),
- and the settlement agreement’s text—especially any express designation of what the payment covers.
Sources and references (where additional precision may be needed)
- TODO: Verify the exact interplay of Civil Code articles for the specific cause of action described in your settlement scenario (contractual breach vs. quasi-delict vs. other).
- TODO: Confirm any Supreme Court guidance you rely on for interest computation methodology tied to the procedural posture (pre-judgment vs. post-judgment).
Use the calculator
Open DocketMath’s Settlement Allocator here: /tools/settlement-allocator.
Run the Settlement Allocator calculation in DocketMath, then save the output so it can be audited later: Open the calculator.
When rules change, rerun the calculation with updated inputs and store the revision in the matter record.
Suggested inputs (PH-aware)
Use these inputs to shape the output. The allocator typically redistributes the total settlement across buckets based on the categories you select.
Check the boxes that match your settlement intent:
Include amounts tied to receipts, invoices, repair costs, medical bills, property damage valuation, lost earnings, etc. Use only if your settlement narrative is aligned with a category recognized in circumstances where exact proof is difficult but liability is established. Select if the settlement is addressing non-pecuniary harm (you’ll need a fact basis consistent with Civil Code concepts). Select if the settlement is intended to reflect conduct warranting exemplary treatment. Include if the settlement contemplates attorney’s fees recoverable under Civil Code concepts or agreed by contract. Select if your settlement amount includes interest, and specify whether you’re treating interest as part of the damages value or as a distinct component.
How output changes when you adjust inputs
| Change you make in inputs | Likely effect on allocator output |
|---|---|
| Increase “Actual damages” share | Larger portion assigned to the pecuniary bucket; remaining categories shrink proportionally |
| Turn on “Moral damages” | Output increases the moral damages line item (assuming total is fixed) |
| Turn on “Interest” while leaving others constant | The allocator shifts money into an “Interest” bucket rather than forcing everything into principal-like damages |
| Add “Attorney’s fees” | More of the total is allocated to fees; the damages buckets reduce unless you also raise total settlement |
| Select fewer buckets | Output becomes more concentrated, which may or may not match your settlement drafting goals |
Output to review before finalizing settlement documents
After you run the calculator, review:
- Category totals: do they sum to the agreed total?
- Consistency with agreement language: does the settlement explicitly say what the money covers?
- Documentation alignment: if “actual damages” are included, do your files contain the supporting valuation basis (even if negotiated)?
- Interest basis: if you include interest, confirm your internal method (even for settlement purposes) is consistently described.
Warning: Settlement agreements sometimes include global releases and broad “inclusive” language. If the allocator buckets don’t match how the parties intended the payment to function (e.g., covering both damages and costs), downstream reconciliation can become difficult.
For best results, iterate:
- start with the categories most clearly supported by the pleadings or demand,
- run DocketMath,
- adjust only one input category at a time to see which bucket logic moves the largest amount.
Sources and references
Start with the primary authority for Philippines and confirm the effective date before relying on any output. If the rule has been amended, update the inputs and rerun the calculation.