Abstract background illustration for How to calculate interest in District of Columbia

How to calculate interest in District of Columbia

6 min read

Published June 4, 2026 • By DocketMath Team

Under review

missing_or_unverified_packet

Quick takeaways

  • In the District of Columbia, judgment interest is governed by D.C. Code §§ 28-3302 and 28-3303.
  • DocketMath’s interest calculator uses jurisdiction-aware defaults for the interest period and then applies the statutory interest mechanics keyed to the date(s) you enter.
  • DocketMath does not require claim-type-specific logic for DC under the general/default approach: the brief notes that no claim-type-specific sub-rule was found, so this guide treats the general/default period as the applicable framework.
  • Biggest drivers of different results: start date, end date, principal amount, and whether you’re calculating pre-judgment vs. post-judgment interest (DocketMath can model both depending on what you input).

Note: This post explains how to calculate interest mechanics using DocketMath and DC statutes. It’s written for workflow and calculation clarity, not legal advice.

Inputs you need

Before you open DocketMath’s interest tool at /tools/interest, gather these facts. If you’re missing one, the calculator may still run, but the output will reflect your assumptions.

Minimum inputs (for a DC interest run)

  • Jurisdiction: US-DC (District of Columbia)
  • Principal amount: the dollar amount the interest applies to
  • Interest start date: the date interest begins accruing in your scenario
  • Interest end date: the date you want to stop accruing interest (often judgment date, payment date, or a cutoff date)
  • Method/phase (if applicable in your workflow):
    • Post-judgment interest (commonly tied to the judgment date onward)
    • Pre-judgment interest (if your use case requires it and the statute supports it under your scenario)

Inputs that change the math materially

  • Compounding preference: if your scenario assumes simple vs. compounded interest, choose what DocketMath supports for the run you’re doing
  • Rate anchor details (if required by the tool UI):
    • Some statutory interest schemes depend on a benchmark rate or a defined schedule.
    • DocketMath’s jurisdiction rules will prompt you for what’s needed based on US-DC selection.

Quick checklist

  • Principal amount confirmed
  • Start date confirmed
  • End date confirmed
  • Correct phase (pre-judgment vs. post-judgment) selected for your scenario
  • US-DC jurisdiction selected in DocketMath

How the calculation works

DocketMath’s interest calculator for District of Columbia (US-DC) follows a jurisdiction-aware workflow grounded in D.C. Code §§ 28-3302 and 28-3303.

1) Select the DC rules in DocketMath

In the interest tool (/tools/interest):

  • Choose District of Columbia (US-DC).
  • Use the calculator’s DC-specific labels to enter:
    • Principal
    • Start date
    • End date

Because no claim-type-specific sub-rule was found for the “default period,” DocketMath’s DC setup should follow the general/default period approach tied to the statutory framework. Practically, that means you rely on:

  • the statutory framework for when interest begins accruing for your scenario, and
  • the statutory method for calculating accrued interest for the relevant date window.

2) Determine the accrual window (date math)

Next, DocketMath computes the duration between your interest start date and interest end date.

For transparency in your workflow, verify:

  • You’re using the correct legal milestone dates for interest to start and stop.
  • Your end date matches the point you want the interest total to reflect.

Even if the rate is correct, a shift in the accrual window can move the total meaningfully—especially for longer periods.

3) Apply DC’s statutory rate framework

DC judgment interest is statutory and is handled through D.C. Code §§ 28-3302 and 28-3303. In DocketMath, once the date window is determined, the calculator:

  • uses the rate logic embedded in the US-DC jurisdiction settings, and
  • applies that rate to the principal across the accrual period using the calculator’s configured interest math (for example, annualized rate applied across the fraction of a year, depending on the tool’s implementation).

Because statutory schemes can be sensitive to when the rate applies and how the statute defines the calculation period, DocketMath’s jurisdiction-aware rules help keep the rate mechanics aligned with DC’s statutory structure.

4) Output: interest total (and optionally breakdown)

Typical outputs you should expect from DocketMath include:

  • Total interest for the provided accrual period
  • Often a formatted breakdown or intermediate figures (such as days count or rate-applied period)

When iterating:

  • change one input at a time (usually dates first),
  • compare results to identify what drove the delta.

Common pitfalls

The issues below cause most “why does my number differ?” moments when calculating DC interest.

1) Using the wrong phase (pre-judgment vs. post-judgment)

DC’s interest rules depend heavily on the type of period you’re modeling. If you enter dates meant for post-judgment but label the run as pre-judgment (or vice versa), your accrual window will be wrong.

  • Confirm which milestone your start date represents
  • Confirm whether your end date is a judgment/payment cutoff used for that phase

2) Off-by-one errors in start/end dates

Interest calculations can be sensitive to day-count conventions. In longer runs, even a single day can affect totals.

Pitfall: Treating the start and end dates as “month-based” when the calculator expects exact dates can shift the days count and distort totals.

3) Assuming a claim-type-specific rule exists for DC

Your brief notes no claim-type-specific sub-rule was found for DC under the general/default approach. Don’t add extra sub-logic unless you have a clearly identified statutory trigger that changes the interest rule.

  • Use the general/default DC period framework unless you have a specific statutory basis

4) Changing too many variables at once

If you adjust rate settings, the start date, and the end date all in one run, it’s hard to troubleshoot.

Use a controlled approach:

  • Run 1 with your best estimate
  • Adjust start date
  • Adjust end date
  • Re-run and compare only the delta

5) Confusing “principal” with “amount already increased”

In some disputes, the amount you carry into an interest calculation may already include components beyond pure principal. DocketMath computes interest on the principal you enter, so make sure your principal input matches your intent.

Sources and references

Next steps

  1. Go to /tools/interest and set Jurisdiction: US-DC.
  2. Enter the principal amount and exact start/end dates that match your interest phase.
  3. Run one baseline calculation.
  4. Sanity-check by adjusting dates slightly:
    • Move the end date forward by 30 days and confirm interest changes in the expected direction.
  5. If results are unexpectedly high or low:
    • re-check phase selection,
    • re-check accrual window dates,
    • re-run with only one change at a time.

Related reading