Inputs you need for Interest in Philippines
5 min read
Published April 15, 2026 • By DocketMath Team
Inputs you will need
Run this scenario in DocketMath using the Interest calculator.
To calculate interest in the Philippines using DocketMath (the /tools/interest calculator), you’ll want to gather a few inputs upfront. Interest outcomes change dramatically depending on what you enter—especially the principal, start date, end date, and the rate framework you’re using.
Check off what you already know:
The unpaid sum you’re applying interest to (excluding or including other items depending on your scenario).
The applicable rate in percentage per year (example: 6% = 6.00).
Use simple interest unless your facts clearly point to compounding. DocketMath can handle common interest styles—choose the one that matches your documents.
The date from which interest begins accruing.
The date you want the interest computed through (often a payment date or a filing/cutoff date).
If the tool requests it, select the option aligned with your method. If it doesn’t, the calculator will apply its internal default.
Confirm the computation is in PHP so the output matches your records.
Pitfall: Entering a rate without confirming whether it’s per year (or mixing up monthly vs. annual) is one of the fastest ways to produce a wildly incorrect interest figure.
A jurisdiction-aware note for PH computations: Philippine interest outcomes can depend on whether interest is due by contract, court award, or law. This guide stays practical (and not legal advice), but make sure your rate and start date align with the basis used in your documents.
Where to find each input
Use the checklist below to locate each input in your own records. Where the “correct” value comes from depends on the document type—so treat this as a mapping of typical sources.
| Input | What to look for | Common document location |
|---|---|---|
| Principal amount (PHP) | The amount originally due (or the remaining unpaid balance) | Promissory note, loan agreement, invoice, statement of account, judgment dispositive portion |
| Interest rate | A stated interest rate (annual %, monthly %, or “as agreed”) | Contract clause (loan/credit terms), settlement agreement, court order/judgment terms |
| Rate basis / type | Whether interest accrues in a simple or compounded manner | Contract language (e.g., “interest on interest” or “compounded quarterly”), court award language |
| Start date | Date when interest begins | Contract: date of default; judgment: date of judicial demand or accrual date stated; settlement: effective date |
| End date | Date through which you want the computation | Payment receipt date, computation cutoff date in your filing materials, ledger “as of” date |
| Day-count convention | Any specified method | Court computation instructions; your internal policy notes; tool prompt |
| Currency | Ensure PHP peso amounts | Same documents as principal/rate; your accounting system export |
A few practical decision points to help you pick the right inputs:
- If the agreement states an interest rate and a triggering date (e.g., “upon default”), use the contract’s rate and the contract’s trigger as your start date.
- If this is court-related, the judgment/order language typically controls the rate framework and the period.
- If you’re working from a ledger or statement of account, the ledger might already show accrued interest—still, your DocketMath run should reflect the same start/end dates to avoid double-counting or mismatched periods.
Warning: Don’t mix “total amount due” figures with “principal” unless the document clearly says the total already excludes prior interest. If your principal already includes past interest, you could unintentionally compound beyond what your records support.
Run it
Once your inputs are ready, the process in DocketMath is straightforward. The goal is to run a computation you can reproduce and explain—especially around date ranges, rate units, and principal definition.
- Open the DocketMath Interest tool: /tools/interest
- Select your computation style (if asked):
- Simple vs. compounded
- Enter:
- **Principal (PHP)
- Interest rate (%) per year
- Start date
- End date
- Confirm the tool’s day-count convention only if prompted.
- Run the calculation and review:
- Total interest output
- Any breakdown provided (principal vs. interest)
Use this quick validation loop to reduce errors:
Example (replace with your actual values):
- Principal: PHP 1,000,000
- Rate: 6.00% per year
- Start date: 2024-01-15
- End date: 2024-04-15
- Interest type: Simple (unless your facts require compounding)
Sanity-check outputs (common-sense behavior):
- For simple interest, increasing the rate increases interest roughly proportionally.
- Extending the end date increases interest based on additional days.
- Changing principal scales the result linearly.
If you need multiple runs (often necessary), compute in segments:
- Run 1: Start → first cutoff (e.g., filing date)
- Run 2: Next period → payment date Keep each run’s inputs consistent so your results stay auditable.
Note: Small date changes can matter. Even a 10–15 day shift can materially affect the interest amount on large principals at rates like 6%–12% per year.
Related reading
- Interest rule lens: Maine — The rule in plain language and why it matters
- Common interest mistakes in Rhode Island — Common errors and how to avoid them
- Worked example: interest in Maine — Worked example with real statute citations