Inputs you need for Settlement Allocator in Philippines
5 min read
Published April 15, 2026 • By DocketMath Team
Inputs you will need
Before you run DocketMath’s Settlement Allocator (PH), gather the figures that let the calculator split a settlement across claims, parties, and (where applicable) documentable time periods. The allocator is only as accurate as the inputs you feed it—so collect items in a consistent format (amounts, dates, and who they relate to).
Use this checklist to confirm you have everything needed for the settlement-allocator tool:
The total settlement amount you intend to allocate (PHP), before internal distribution notes.
Each recipient/claimant (e.g., Plaintiff, Defendant’s insurers, co-claimants).
Include all recipients explicitly named in the settlement terms, not just the “main” parties.
Break down the settlement into agreed categories (e.g., damages, attorney’s fees reimbursement, costs/expenses, interest, nominal amounts).
Tip: If your agreement uses terms like “for damages” or “for costs,” those usually become your buckets.
Either:
For each claim/bucket, identify:
Keep labels consistent with your pleadings or settlement exhibits so you can reconcile output back to the agreement.
Examples: filing fees, expert fees, transportation, deposition transcript costs.
If your agreement says interest is computed in a particular way, reflect that basis label so your allocation presentation stays consistent.
DocketMath can help you reflect allocation accounting without making filings on your behalf.
Confirm whether amounts should be rounded to whole pesos or to cents (if you track cent-level agreements).
Consistency matters: decide your rounding approach once, then apply it to all related figures.
Note: The allocator does not replace your settlement agreement. If your settlement agreement specifies a distribution waterfall (e.g., costs first, then fees, then damages), encode those buckets and any ordering assumptions in your inputs so the outputs align with your contract logic. This is not legal advice—use it as a practical way to structure allocation math.
Where to find each input
Here’s a practical path to source each input, so you can compile everything in one pass:
**Settlement fund amount (gross)
- Pull from the settlement agreement’s “total settlement amount” line or the executed compromise agreement/record of compromise.
Parties list
- Use the caption of the case (complaint/petition) and the settlement signature block.
- Include all recipients explicitly named in the settlement terms.
Allocation buckets + per-bucket amounts/ratios
- Look for categories in the settlement document such as:
- “For damages…”
- “For attorney’s fees…”
- “For costs/expenses…”
- “Including interest…”
- If the agreement provides only one total but references categories, use your internal agreed distribution method to translate the total into buckets:
- amount-based if the agreement states fixed sums
- ratio-based if it states proportions or relative shares
Claim mapping
- Map each bucket back to the claim it supports using the labels from your pleadings:
- e.g., “breach of contract—damages,” “moral damages,” “exemplary damages,” “attorney’s fees,” “costs.”
- You don’t need to cite every legal element in the calculator—just keep mapping consistent so you can justify the breakdown internally.
Attorney’s fees
- Find the fee clause that states whether fees are:
- a fixed amount, or
- a percentage of the settlement, or
- a contractual rate with constraints.
- If fees are “subject to court approval” in the agreement, still enter the agreed handling approach so you can see the allocation presentation you intend to use.
Expenses/costs
- Use an exhibit, annex, or schedule of costs if present.
- If the agreement says “actual costs” without listing them, you can input your best estimate for allocation purposes, then rerun after final invoices.
Interest
- Locate the interest clause stating:
- whether interest is included,
- the basis (e.g., contract rate, statutory rate, or agreed rate),
- and the period.
- For allocation, you mainly need the start/end dates and an internal basis label.
Payment schedule
- Use settlement terms describing installments (e.g., “₱X payable within 10 days of signing”).
- Ensure each installment schedule entry sums to the gross settlement amount.
Tax handling preference
- Set your preference based on how your agreement and internal accounting treat taxes:
- excluded from fund (your settlement sum excludes tax), or
- included (your total includes tax treatment).
Run it
Once inputs are ready, go to DocketMath and run the Settlement Allocator here: /tools/settlement-allocator .
A typical workflow:
- Select Jurisdiction: Philippines (PH) in the allocator (if prompted).
- Enter:
- Settlement gross amount
- Parties/claimants
- Buckets (damages/fees/costs/interest) and amounts or ratios
- Claim mapping per bucket
- Choose optional settings:
- Payment schedule (lump sum vs installments)
- Rounding rules (whole pesos vs precision)
- Tax handling preference for allocation presentation
- Generate results and review:
- Allocation per party (PHP)
- Allocation per bucket (PHP)
- Installment breakdown (if you entered a schedule)
- Totals check (must reconcile to gross settlement amount)
Common ways the output changes when inputs change:
Switching from amount-based to ratio-based buckets
- Per-party results shift even if the gross stays the same.
Toggling “interest included vs excluded”
- Bucket totals reallocate, which can materially affect net amounts to claimants.
Adding attorney’s fees as a bucket
- DocketMath will treat that fee portion as part of the bucket structure. Ensure your bucket design matches what your agreement says about whether fees are taken from the settlement pool or handled “in addition” (encode that assumption using your inclusion preference and bucket design).
Pitfall: If your settlement agreement says “costs first, then fees, then damages,” but your bucket setup is entered as a simple percentage split with no ordering logic, the party-level output can conflict with the waterfall you need internally. Align buckets and assumptions before you treat results as final.
After you generate results, sanity-check these items:
