Inputs you will need

To run interest for Singapore matters in DocketMath, you only need a small set of core inputs—but each one changes the output in important ways.

Use this as a working checklist:

• Jurisdiction: Singapore (SG)
• Principal amount
• Currency
• Interest type

  • Pre-judgment
  • Post-judgment
  • Contractual / agreed rate
• Interest rate

  • Statutory / court rate (if applicable)
  • Contractual rate (if applicable)
• Rate basis

  • Per annum (p.a.)
  • Per month / other period (if relevant)
• Interest period

  • Start date
  • End date (or “up to today”)
• Day-count / compounding assumptions

  • Simple vs compound interest
  • Compounding frequency (if compound)
• Payment / part-payment details (if any)

  • Dates of payments
  • Amount of each payment
  • How payments should be applied (interest first vs principal first, if relevant)
• Rounding / precision preferences (if you need to match a specific style)
• Scenario label or description (optional but helpful for documentation)

Below is how each of these interacts with the calculation, specifically for Singapore-focused work.

Where to find each input

This section focuses on practical sources and how each input affects the result. It’s written for lawyers, litigators, and legal ops teams working with Singapore matters.

Jurisdiction: Singapore (SG)

Where to find it

• Matter file / case management system
• Engagement letter or internal matter-opening form
• Court documents (writ, originating application, pleadings)

Why it matters

• Tells DocketMath to apply Singapore-specific defaults (e.g., typical court interest practices) rather than another jurisdiction’s.
• Helps you keep a clear audit trail when you later export or explain the calculation.

Principal amount

Where to find it

• Contract: principal sum, invoice total, or outstanding balance
• Pleadings: statement of claim, particulars of claim
• Judgment / order: “sum of…” in the dispositive section

How it affects the output

• This is the base on which interest is calculated.
• Any change in principal scales the interest linearly.

  • Double the principal → roughly double the interest (all else equal).

Currency

Where to find it

• Contract currency clause
• Invoices or statements of account
• Judgment wording (“SGD”, “USD”, etc.)

How it affects the output

• DocketMath will keep all calculations in the selected currency.
• If you mix currencies (e.g., contract in USD, judgment in SGD), you may need to:

  • Run separate interest calculations per currency, or
  • Confirm the conversion date and rate before calculating.

Interest type (pre‑judgment, post‑judgment, contractual)

Where to find it

• Contract clauses (interest on late payment, default interest)
• Judgment / order (pre‑judgment and/or post‑judgment interest wording)
• Applicable rules of court or statutes (for default or court rates)

How it affects the output

• Pre‑judgment interest

  • Usually runs from a date tied to breach, demand, or filing.
  • May be discretionary or at a specified rate.

• Post‑judgment interest

  • Runs from the date of judgment until payment.
  • Often at a court or statutory rate if not otherwise specified.

• Contractual interest

  • Follows the agreed rate and compounding terms (if any).
  • May override default court rates for pre‑judgment periods.

In DocketMath, you can model these as separate periods with different rates and start/end dates, then total them.

Interest rate

Where to find it

• Contract: “interest at X% per annum” or “default interest of X% p.a.”
• Judgment / order: “with interest thereon at X% per annum”
• Court / statutory materials: for default or court rates where no rate is specified

How it affects the output

• The rate is the main driver of the interest amount.
• Higher rate → proportionally higher interest, all else equal.
• Changing 5% p.a. to 6% p.a. increases the interest by 20% over the same period.

Rate basis (per annum vs other)

Where to find it

• Contract wording: “per annum”, “per month”, or “per day”
• Judgment wording: usually “per annum” if specified

How it affects the output

• Per annum (p.a.) is standard. DocketMath will interpret the rate as annual and prorate by days.
• If the contract uses per month or per day, you’ll either:

  • Enter that rate with the correct basis (if supported), or
  • Convert it to an equivalent annual rate for consistency.

Example (conceptual):

• 1% per month ≈ 12% per annum (simple, non-compounding view).

Interest period: start and end dates

Where to find it

• Contract:

  • From due date of invoice
  • From date of default or demand
• Pleadings:

  • From date of breach or cause of action
• Judgment / order:

  • “From the date of writ”
  • “From the date of judgment”
  • “Until payment in full”

How it affects the output

• Interest is time-based; the number of days is critical.
• Longer period → more interest; shorter period → less interest.
• DocketMath calculates based on actual calendar dates, so:

  • Moving the start date forward by one month reduces interest by roughly one month’s worth (at the given rate).
  • You can set the end date to a specific date or “today” when you run the calculation.

Day-count and compounding assumptions

Where to find it

• Contract:

  • “Simple interest” vs “compounded monthly/quarterly/annually”
  • Any explicit day-count convention (rare in many commercial contracts)
• Judgment / order:

  • Often silent; interest may be simple unless otherwise provided

How it affects the output

• Simple interest (common in court contexts):

  • Interest is calculated on the original principal only.
• Compound interest:

  • Interest is periodically added to principal; future interest is calculated on the increased amount.
  • Compounding frequency (monthly vs annually) can significantly increase total interest over long periods.

In DocketMath, you can:

• Choose simple vs compound.
• If compound, specify compounding frequency (e.g., monthly, quarterly, annually).

Over multi‑year periods, compounding at a given rate in Singapore disputes can materially change negotiation positions, so it’s worth modeling both if your contract is ambiguous or silent (with appropriate caveats).

Payments and part‑payments

Where to find it

• Bank statements
• Payment vouchers / receipts
• Settlement correspondence
• Ledger or account statements

How it affects the output

• Payments reduce the amount on which future interest is calculated.
• Key choices:

  • Application: Is payment applied to interest first, then principal, or directly to principal?
  • Timing: Exact payment date matters; interest stops accruing on the paid amount from that date.

In DocketMath, you can enter:

• Each payment’s date and amount.
• How to apply payments (depending on the calculator options and your matter’s rules).

This lets you reconstruct a running balance over time, which is especially useful for long‑running Singapore commercial disputes with staggered payments.

Rounding and precision

Where to find it

• Contract (if it specifies rounding rules)
• Internal firm or client policy (e.g., round to nearest cent)
• Court practice or precedent in similar matters

How it affects the output

• Rounding can create small differences between your figure and an opponent’s or the court’s.
• In DocketMath, you can usually:

  • Choose decimal places (e.g., 2 decimal places for cents).
  • Control whether intermediate steps or only final totals are rounded.

For Singapore matters where the exact cents can matter (e.g., interest over long periods at higher rates), aligning rounding rules with your expected audience (court, client, counterparty) helps avoid unnecessary disputes over “small” differences.

Scenario label or description

Where to find it

• Your own internal naming convention, for example:

  • “Scenario A – 5% simple pre‑judgment, 6% post‑judgment”
  • “Scenario B – contractual 8% compounded monthly”

How it affects the output

• Does not change the numbers, but:

  • Makes it much easier to compare scenarios.
  • Improves your documentation when you export or share the calculation.

This is especially helpful when you’re testing alternatives for negotiation or drafting purposes.

Run it

Once you’ve gathered your inputs, you’re ready to calculate.

1. Go to the DocketMath Singapore interest calculator:
   **/tools/interest
2. Confirm **Jurisdiction = Singapore (SG).
3. Enter:

   • Principal and currency
   • Interest type(s) and corresponding rate(s)
   • Rate basis (per annum or other, as applicable)
   • Interest period (start and end dates, or “up to today”)
   • Day-count and compounding settings
   • Any payments or part-payments
   • Rounding / precision preferences

Inputs you will need

Use this checklist to gather the core inputs before you run the Interest tool.

• principal or judgment amount
• interest type (pre- or post-judgment)
• rate and compounding method
• start date and end/as-of date
• payments or credits that reduce principal
• day-count convention

Where to find each input

Most inputs live in the case file, contracts, or docket entries. Dates usually come from the triggering event notice; rates and caps come from governing documents or statute; and amounts come from the ledger or judgment. Record the source for each value so the run is reproducible.

Run it

Enter the inputs in DocketMath and run the Interest calculation to generate a clean breakdown: Run the calculator.

If an assumption is uncertain, document it alongside the calculation so the result can be re-run later.

Capture the source for each input so another team member can verify the same result quickly.

Related reading

• Interest rule lens: Maine

• Inputs you need for deadlines in Australia

• Common interest mistakes in Rhode Island

• Why we started the DocketMath blog