Spreadsheet checks before running interest in Florida

Spreadsheet interest in Florida tends to fail in the same handful of ways: wrong dates, wrong balances, or the wrong statute rate. A quick spreadsheet check before you run interest can save a lot of backtracking—and make your final DocketMath run much easier to defend.

Below is a practical checklist-style guide to sanity‑checking a spreadsheet before you calculate statutory interest for Florida (US‑FL) using the DocketMath interest calculator.

What the checker catches

Think of the “checker” as a short pre‑flight routine you run on any spreadsheet you plan to feed into DocketMath. You can do it manually, or formalize it in a separate “Check” tab.

Here’s what it should catch, especially for Florida interest:

1. Date problems (the most common failure mode)

Florida interest is sensitive to dates because:

• The statutory rate changes over time.
• Prejudgment vs. post‑judgment interest may start on different dates.
• Partial payments apply on specific days.

Your checker should verify:

• Flag anything where:

  • End date < Start date
  • Dates are in the future (if that doesn’t make sense for your matter)

• Check for text dates like "1/2/24" vs. 2024-01-02 being interpreted differently (month/day vs. day/month).

• Every payment row should have:

  • A posted date (when interest should stop accruing on that amount)
  • A clear link to the balance it is reducing (e.g., invoice ID or judgment ID)

• For continuous interest, confirm:

  • The start date for interest
  • The end date for interest

• Then check whether you’ve:

  • Intentionally broken the period into sub‑ranges (for rate changes or payments), or
  • Accidentally skipped days or duplicated ranges.

2. Balance and sign issues

Florida interest is usually calculated on a principal amount that changes over time with payments, fees, and sometimes costs. Your checker should make sure:

• One column for:

  • Principal (the amount that earns interest)

• Separate columns for:

  • Fees
  • Costs
  • Attorney’s fees

• If your jurisdictional theory is that some of those also accrue interest, you’ll want explicit columns so you can include or exclude them in DocketMath with a clear record. (That’s legal‑strategy territory—document the choice; don’t guess.)

• Credits/payments should be negative or in a separate “Payment” column.

• Debits/additions should be positive.

• Your checker can flag:

  • Any row where both “Debit” and “Payment” are non‑zero
  • Any row where a “Payment” is positive

• Add a running balance column.

• Check for:

  • Sudden jumps that don’t match the row’s amount
  • Negative balances where they don’t belong

• A simple check formula:

  • Balance_t = Balance_(t‑1) + Debits_t – Payments_t

3. Florida‑specific rate alignment

You don’t need to hard‑code the Florida statutory rates if you’re using DocketMath; it will pull the correct US‑FL quarterly rates for you. But your spreadsheet still needs to align to how those rates change.

Your checker should focus on structure, not the numeric rate:

• Florida’s statutory rate typically changes quarterly.

• If you’re pre‑aggregating interest in the spreadsheet (e.g., per year or per quarter), make sure:

  • Your date ranges line up with actual quarter boundaries, or
  • You clearly note that DocketMath is the source of truth and your spreadsheet totals are only estimates.

• Don’t mix:

  • “Simple interest at statutory rate” and
  • “Contract rate interest”

• If you must track both:

  • Use separate columns, and
  • Label which rows are intended for Florida statutory interest (US‑FL) vs. something else.

4. Column mapping for DocketMath

DocketMath’s interest calculator works best when each input column has a clear meaning. Your checker should ensure:

• Example useful columns:

  • Event date (judgment date, invoice date, etc.)
  • Interest start date (if different)
  • Amount (principal)
  • Payment amount
  • Payment date
  • Category (e.g., “principal”, “cost”, “fee”)

• Avoid multi‑use columns like “Amount (principal or fee or payment)” with notes in comments.

• Use controlled values:

  • Category: principal, cost, fee, payment

• This makes it easier to:

  • Filter what should earn interest
  • Map columns into DocketMath consistently

• If your file covers multiple states or matters:

  • Add a Jurisdiction column and use US-FL for Florida rows.

• That makes it explicit which rows should be run under Florida’s statutory rules.

5. Check totals and reconciliation

Before you hit run on interest:

• Sum of principal balances should match:

  • Judgment amount
  • Invoice totals
  • Settlement spreadsheet

• If they don’t, your checker should flag the discrepancy.

• Decide the “as of” date for your interest run.

• Confirm:

  • All payments up to that date are included.
  • No payments after that date are included.

• Make a copy of the tab you’re about to use.

• Name it with the as‑of date, e.g., Interest Input – 2026-02-02.

• This gives you a defensible record if you later re‑run in DocketMath.

When to run it

You don’t need a full check on every edit. Instead, run the checker at specific milestones in your workflow.

Run the checker before importing a spreadsheet into the Interest workflow. It is especially helpful when you have multiple entries or when a teammate provided the inputs.

Recommended checkpoints

Use this list as a lightweight policy for your team:

• When you first pull data from:

  • Case management systems
  • Accounting ledgers
  • Opposing counsel’s spreadsheet

• Run the checker to normalize dates, signs, and columns before anyone starts modeling scenarios.

• Any time you’re about to:

  • Upload or map columns into DocketMath’s interest calculator
  • Export a result you’ll share with a client, court, or opposing counsel

• This is where you catch mismatches between your spreadsheet structure and the Florida statutory logic you’re relying on.

• If someone decides:

  • To include or exclude certain fees from interest
  • To change the interest start date (e.g., from breach date to judgment date)

• Run the checker again to ensure:

  • The columns still match the new theory
  • You’ve documented the change somewhere outside the numbers

• A quick check ensures:

  • The structure is obvious
  • Another person can run the same DocketMath calculation and get the same result

Try the checker

You can implement a simple, Florida‑ready checker directly in your spreadsheet:

1. Create a “Check” tab

   • Pull in key columns using references (e.g., ='Data'!A:A).
   • Add formulas that:

     • Flag invalid dates (=IF(OR(A2="",A2>TODAY(),A2<DATE(1900,1,1)),"Check date",""))
     • Flag sign issues (=IF(AND(Payment>0,Debit>0),"Check signs",""))
     • Confirm running balance logic.

2. Add summary indicators

   • At the top of the “Check” tab, create fields like:

     • Date issues count
     • Sign issues count
     • Balance anomalies count
   • Use COUNTIF or COUNTIFS to tally flags:

     • =COUNTIF(FlagRange,"Check*")

3. Document your Florida assumptions

   • On the same tab, include a small notes box:

     • Jurisdiction: US-FL
     • Interest basis: Florida statutory interest (simple) via DocketMath
     • As‑of date
   • This clarifies that:

     • The spreadsheet is an input container.
     • DocketMath is the calculator applying Florida’s quarterly rates.

4. Map into DocketMath

   • When you’re satisfied the checker is clear:

     • Use the cleaned columns (dates, principal, payments) as your inputs to the DocketMath interest tool.
   • Keep:

     • The original data tab
     • The “Check” tab
     • The DocketMath output
   • Together, they form a

Related reading

• Interest rule lens: Maine

• Spreadsheet checks before running deadlines in California

• Common interest mistakes in Rhode Island

• Why we started the DocketMath blog