Inputs you need for Payment Plan Math in Philippines
6 min read
Published April 15, 2026 • By DocketMath Team
Inputs you will need
Run this scenario in DocketMath using the Payment Plan Math calculator.
To run payment plan math in the Philippines with DocketMath (jurisdiction PH), you’ll want a complete set of inputs before you start. Missing even one number can change the payment schedule, totals, and “ballpark” affordability outputs.
Use this checklist as your pre-flight list:
- Example: ₱150,000 (the “base” amount)
- Example: ₱20,000 paid up front
- You can compute it, but DocketMath may accept either the remaining principal or the full principal + down payment inputs.
- Choose one:
Note: If you don’t have an interest/penalty figure, run two scenarios—“no interest” and “interest at your best available estimate.” The difference often dwarfs rounding choices, especially over longer timelines. (This is not legal advice—just practical modeling guidance for planning.)
Where to find each input
You can gather these inputs from documents and system records you likely already have. Below is a practical “where to look” map, plus what each input changes in the math.
| Input | Where to find it | What it changes in the math |
|---|---|---|
| Payment plan start date | Payment agreement, demand letter, settlement email, or your own payment calendar | Shifts installment due dates and the count of periods |
| Payment frequency | Your agreement terms (monthly, semi-monthly, weekly) or your planned cadence | Changes number of installments and period length |
| Principal / amount to be paid | Contract, settlement worksheet, statement of account, or invoice ledger | Sets the baseline total paid (and thus overall interest cost) |
| Down payment | Proof of payment receipt, agreement addendum, or bank transfer confirmation | Reduces principal and usually reduces total interest |
| Remaining principal after down payment | Your statement/ledger after the down payment, or computed value from your records | Determines what the plan amortizes going forward |
| Interest rate | Promissory note, loan document, or contract clause | Drives interest portion of each installment |
| Interest type (simple vs compound) | Loan terms or calculations clause | Determines how interest is computed across periods |
| Interest accrual convention | Loan terms or calculator basis inside the agreement | Affects interest even when APR looks the same |
| Penalty/fee assumptions | Default clause for late payments, schedule of charges, or addendum | Adds incremental costs after missed/late periods |
| Existing payments / credits | Receipts, ledger, amortization schedule, or bank statements | Affects remaining principal and period-by-period balances |
| Target duration or target payment | The agreement’s term (e.g., “pay within 12 months”) OR your affordability plan | Determines whether DocketMath solves for installment vs duration |
| Rounding rules | Your contract’s “amount per installment” wording or your accounting preference | Prevents mismatch between expected and posted amounts |
| Grace period | Clause specifying when late charges begin | Changes when penalties/interest hit after a missed payment |
A quick sanity tip: if you’re using bank records, verify whether amounts were applied to principal first or interest first. That single ordering choice can make your remaining balance diverge from the ledger even when totals “look” right.
Run it
With your inputs collected, you’re ready to run Payment Plan Math in DocketMath for PH.
Enter the inputs in DocketMath and run the Payment Plan Math calculation to generate a clean breakdown: Run the calculator.
Step 1: Select PH and configure the plan goal
In DocketMath → /tools/payment-plan-math, set:
- Jurisdiction: Philippines (PH)
- Plan goal:
- Solve for payment amount given a duration, or
- Solve for duration given a target payment
If you’re unsure which goal to use, match it to what your agreement states:
- Agreement says “pay ₱X monthly for Y months” → use the setup that aligns with payment per period and duration, then verify totals.
- Agreement says “pay within Y months” → use the setup that aligns with duration and computes the needed installment.
Step 2: Enter the financial inputs
Add the numeric data:
- **Principal (base amount)
- Down payment (if any)
- Interest rate (if any) and interest settings (simple vs compound)
- Payment frequency
- Start date
- Interest/penalty settings (if your scenario includes them)
For planning or “what-if” runs, keep assumptions consistent across scenarios:
- Same down payment
- Same interest type/convention
- Same rounding approach
Step 3: Add late/penalty modeling only if you have it
If you include penalty modeling:
- Set the penalty per missed payment or daily penalty
- Provide a grace period (days) if your terms specify one
This is where totals can jump quickly over longer timelines. Penalty-heavy scenarios are common in real-world schedules, even when the principal and interest are unchanged.
Step 4: Check the output components you should care about
Before you accept results, scan the key outputs that typically matter most:
- Monthly (or periodic) installment amount
- Total principal paid
- Total interest paid
- Total penalties/fees (if modeled)
- Total amount due over the plan
- Final payment adjustment (often needed due to rounding)
A simple validation method (no legal judgment required):
Warning: Don’t compare outputs from two runs if you accidentally changed interest compounding (simple vs compound) or accrual basis. Two scenarios that both say “12%” can produce meaningfully different totals.
Step 5: Save scenario sets (recommended)
If you’re uncertain about terms, run at least two scenarios:
- Scenario A: No penalty (or penalty set to zero), interest as specified (if you have it)
- Scenario B: Interest + penalty using your best estimate for late charges
Then compare the outputs to see which set matches the numbers you’re trying to replicate.
Reminder: This is planning math and scenario modeling, not legal advice. If you need to confirm enforceability of specific terms, consult a qualified professional.