Spreadsheet checks before running interest in North Carolina

What the checker catches

Run this scenario in DocketMath using the Interest calculator.

DocketMath’s spreadsheet-checker is designed to catch common reasons interest calculations go off the rails in North Carolina (US-NC)—especially when your workbook is doing more than one job (damages, dates, compounding, partial periods, or payments).

Because your interest model is only as reliable as its inputs, this checklist focuses on “sanity failures” you can spot before you click anything that applies interest.

High-frequency spreadsheet issues the checker flags

• Date order mistakes

  • Filing date vs. judgment date swapped
  • Start date after end date
  • Payment dates entered as text (so they don’t sort correctly)

• Silent unit errors

  • Using an annual interest rate as if it were a monthly rate (or vice versa)
  • Percent entered as “6” instead of “0.06”
  • Day counts based on 30/360 when your sheet assumes actual days

• Wrong “count window”

  • Accidentally including the period outside the relevant time window
  • Omitting a partial period after a payment date
  • Ending the count on the wrong day (e.g., using “through” date as exclusive)

• Payment application errors

  • Treating payments as additions rather than offsets
  • Posting payments to the wrong principal balance column
  • Applying a single payment to multiple rows (double counting)

• Row/column drift

  • Expanding one table but not the interest table (misaligned ranges)
  • Copy/paste formulas referencing the wrong column letter
  • VLOOKUP/XLOOKUP matching the wrong case/event key

Why the statute-driven time window matters (NC)

North Carolina uses a general 3-year statute of limitations period for many civil claims. In practice, your interest calculation often relies on a “count window” (the period you’re treating as relevant for accruing interest). That means your spreadsheet should be able to answer:

• What is the date range the model is using?
• Is the range consistent with a 3-year default timeframe when no claim-type-specific rule applies?

The “SAFE Child Act” is referenced by the North Carolina Department of Justice as part of the state’s supporting-victims-and-survivors framework for sexual assault. This is not legal advice, but it’s a useful reminder that North Carolina’s civil/tolling landscape can intersect with specific statutory frameworks—so the checker’s job is to ensure your spreadsheet is consistent, explicit about dates, and auditable before you calculate interest.

Source: https://www.ncdoj.gov/public-protection/supporting-victims-and-survivors-of-sexual-assault/

When to run it

The best time to run the checker is before you generate any interest results and before you freeze values or export numbers for submission. Think of it as a preflight step: your model can still be “wrong,” but you reduce the odds of a basic spreadsheet failure.

Here’s a practical sequence for running it with DocketMath:

Recommended run order (works well for interest spreadsheets)

1. Before formatting and exporting

   • Run the checker on the raw date and amount inputs.
   • Fix parsing issues (date formats, text-to-number conversions, mis-sorted columns).

2. Right after you set the interest parameters

   • Confirm the interest rate input is in the unit your formula expects (e.g., 0.08 vs 8).
   • Verify compounding settings (daily/annual/monthly) match your spreadsheet logic.

3. After adding payments

   • Payments are where many interest models break.
   • Run the checker after you import or paste payment rows.

4. After expanding or copying tables

   • When you add new rows (more events, more claims, more periods), re-run the checker.
   • Don’t assume the interest sheet references updated ranges automatically.

Quick “trigger list” for reruns

Re-run the checker if you change any of the following:

• Any date column (start, end, judgment, payment)
• Interest rate
• Principal balances
• Rows/events (add or remove claim/payment lines)
• Sheet tabs/ranges and then re-link formulas

Try the checker

Use DocketMath’s interest workflow to test your spreadsheet assumptions in a repeatable way. The goal is not to “make the numbers look right,” but to ensure the model is internally consistent and the date window is explicit.

Upload the spreadsheet, review the warnings, and then run the calculation once the inputs are clean: Try the checker.

Inputs to verify (minimum set)

Create or locate these inputs in your workbook:

• Start date (e.g., interest accrual start)
• End date (e.g., interest through date)
• Principal amount
• Interest rate (confirm whether it’s decimal or percent)
• Payment dates and amounts (if any)
• Day-count convention (if your sheet uses one)
• Window logic switch (if your sheet chooses a default vs special rule)

Output signals to watch for

DocketMath’s spreadsheet-checker should help you spot mismatches like these:

How outputs change when you fix inputs

After the checker helps you correct inputs, expect interest to shift in ways that match the underlying changes:

• Changing start/end dates changes total day count → interest moves proportionally.
• Fixing rate units often changes magnitude dramatically (commonly by a factor of 100 or 12).
• Repairing payment alignment changes when offsets apply → interest changes in a stepwise pattern.
• Adjusting day-count convention changes interest by a smaller but real amount (depending on date spread).

When you’re ready to run it, use DocketMath’s interest tool here: /tools/interest.

Simple “sanity checklist” you can do first

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