Judgment Interest Calculator Guide for Tennessee

What this calculator does

Run this scenario in DocketMath using the Interest calculator.

DocketMath’s Judgment Interest Calculator for Tennessee (US‑TN) helps you estimate interest that may accrue on a judgment based on the dates and principal you enter. The goal is to give you a reproducible number you can sanity-check, not to replace a court’s final judgment math.

At a high level, the calculator is built around one Tennessee statute for the general post-judgment interest framework:

• General post-judgment interest “default” period: 1 year
• Statutory cite (default framework): Tennessee Code Annotated § 40‑35‑111(e)(2)

  • Source: https://law.justia.com/codes/tennessee/title-40/chapter-35/part-1/section-40-35-111/

What you can calculate with DocketMath (typical inputs)

Use the tool here: /tools/interest

Most judgment interest workflows require you to provide some combination of:

• Principal amount (the judgment amount subject to interest)
• Start date (often tied to judgment entry or another legally relevant date)
• End date (date of payment, payoff estimate, or calculation date)
• Any partial payments (optional, if you’re modeling reductions over time)

What you get back (typical outputs)

Depending on how the calculator is configured in DocketMath, the output commonly includes:

• Estimated accrued interest
• Estimated total due (principal + interest)
• Day-count based breakdown (or an equivalent computation model)
• Assumptions summary (what the calculator assumed about dates and inputs)

Why this matters

Small date differences can materially change totals. For example, moving an end date by even 30 days changes the day-count portion of an interest estimate and can swing a payoff number enough to affect payment planning, settlement discussions, and internal reconciliation.

When to use it

Use DocketMath’s judgment interest calculator when you need an estimate for a Tennessee judgment and you want transparent, repeatable math tied to the calculator inputs.

Best-fit use cases

• Estimating payoff amounts before payment is made (e.g., “What might this be as of March 15, 2026?”)
• Reviewing settlement posture where interest accrual is a central term
• Preparing internal demand/reconciliation worksheets to align principal and interest totals
• Modeling partial payments to see how the estimated accrued interest changes

Timing scenarios where you should pay close attention to dates

Interest calculations are date-sensitive. Make sure your selected dates match your workflow:

• After judgment entry: Use the date your process treats as the interest “start” date.
• Before final payoff: Use the date you want to estimate through (today, next business day, date of planned wire transfer).
• With installments: If you’re simulating a partial payment on a specific date, ensure that later periods use the reduced principal (if your model supports that).

Step-by-step example

Below is a practical walk-through using DocketMath. The example uses a general default approach tied to the statute framework noted above.

Example inputs (Tennessee)

Assume:

• Principal (judgment amount): $25,000
• Start date: January 1, 2025
• End date (calculation date): January 1, 2026
• Claim type: not specified (so we use the general/default period framework)

Because the general/default period identified is 1 year, the example spans exactly that year.

Step 1: Open the calculator

Go to /tools/interest and select the Tennessee jurisdiction context (US‑TN) if the interface prompts you.

Step 2: Enter the principal

• Enter $25,000 as the principal subject to interest.

Checklist:

Step 3: Enter the dates

• Set Start date: 01/01/2025
• Set End date: 01/01/2026

Checklist:

Step 4: Confirm the computation uses the general default framework

This is where the key legal framework shows up in your mental model: Tennessee Code Annotated § 40‑35‑111(e)(2) is the identified default period framework with a 1-year reference.

Checklist:

Step 5: Review outputs and assumptions

After you run the calculation, capture:

• Estimated interest
• Estimated total due
• Assumptions summary (if the tool shows it)

Step 6: Use the estimate for your decision

Now you can use the result in one of these ways:

• Compare it with a proposed settlement number
• Check whether a demand includes interest consistent with the dates you’re using
• Build a payment plan based on “total due through X date”

Common scenarios

Real-world judgment interest situations usually differ by timing, payments, and how you define the “through date.” Here are common Tennessee scenarios you can model in DocketMath—along with the specific inputs that typically change the output.

Scenario A: Full amount payoff on a single date

Story: You plan to pay the full principal on a specific payoff date.

Typical inputs:

• Principal: full judgment amount
• Start date: your interest trigger date
• End date: payoff date

What changes the output:

Scenario B: Partial payment reduces the outstanding principal

Story: A partial payment is made, reducing principal for later accrual.

Typical inputs:

• Principal: original amount
• Add one or more partial payment dates/amounts (if supported by the calculator)
• End date: final payoff estimate

What changes the output:

Scenario C: Calculation “as of today”

Story: You need an estimate for an ongoing matter.

Typical inputs:

• Start date: interest trigger date
• End date: today’s date
• Principal: unpaid balance

What changes the output:

Scenario D: More than one year of accrual modeling

Story: The payoff doesn’t occur within the initial year window you might be focused on.

Typical inputs:

• Principal: unpaid balance
• Start date: interest trigger date
• End date: later date beyond the first year

How to think about it under the provided framework:

• The identified reference is a general/default period with a 1-year figure under Tennessee Code Annotated § 40‑35‑111(e)(2).
• If your math extends beyond one year, the calculator will still apply its computation model; you should verify that model matches the legal treatment you intend to reflect.

Scenario E: Disputes about which date starts accrual

Story: The parties disagree about the interest trigger date (e.g., judgment entry vs another date).

Practical approach:

• Run two versions:

  • Version 1: start date = earlier asserted trigger
  • Version 2: start date = later asserted trigger
• Compare the difference in estimated interest.

Checklist:

Tips for accuracy

You’ll get the best estimate from DocketMath if you treat inputs like ledger entries: precise, consistent, and documented.

Use consistent principal definitions

Decide what principal number you are using and keep it consistent across runs.

• Full principal vs unpaid balance
• Adjusted principal after partial payments (if modeled)
• Avoid mixing “judgment amount” with “amount demanded” unless that’s truly what your estimate should accrue on

Use dates that match your workflow

Interest math is only as accurate as your selected dates.

• Start date: align to your operational interest trigger
• End date: use a single “through” date for comparisons
• If you’re comparing scenarios, keep end date constant

Run “delta checks” to verify changes make sense

A quick reasonableness check catches data entry errors:

• If you increase the end date by 30 days, the interest estimate should generally move in the same direction.
• If it doesn’t, double-check:

  • date format
  • swapped start/end dates
  • principal entered as dollars vs cents

Keep your assumptions explicit

DocketMath can help you standardize assumptions, but you still need to track them:

• The default framework reference: **Tennessee Code Annotated § 40‑35‑111(e)(2) (general/default period of 1 year)
• You are using the general/default approach because no claim-type-specific sub-rule was found in the provided context.

Source reminder: https://law.just

Related reading

• Interest rule lens: Maine
• Common interest mistakes in Rhode Island — Common mistakes
• Worked example: interest in Maine — Worked example