New year debt collection deadlines in Tennessee

Direct answer

In Tennessee, the “new year” debt-collection deadline question usually turns on whether a creditor can still file a lawsuit before the applicable statute of limitations expires—primarily under Tenn. Code Ann. § 28-3-104 (primary source in this packet).

From the verified packet inputs, common timing periods that often show up in collections disputes include:

• 6 years for many contract/debt-related claims (for example, breach of oral or written contract, and debt on a promissory note)
• 3 years for common-law fraud/deceit (and fraud generally, in the verified set)

Just as important as the length of time is the start date (when the clock begins). In DocketMath’s statute-of-limitations model, you may also need to consider discovery/timing assumptions and tolling inputs included in the verified setup (for example, the verified dataset includes a discovery-related maximum window concept and mental incapacity tolling).

What you need to know

Tennessee debt-collection “deadlines” are not one single fixed date for every debt. Instead, you typically:

1. Match the creditor’s likely claim theory to the correct limitations bucket, and then
2. Identify the trigger/start date the other side would argue starts the clock.

Common limitations buckets (from the verified facts packet)

Below are the periods reflected in the verified packet’s claim-type mapping:

“New year” logic that can change outcomes

Two factors often decide whether a January filing is timely:

• Which period applies (for example, 6 years vs. 3 years), and
• When the clock starts (which can differ from “date of signing” depending on the asserted theory and the packet’s modeled discovery/tolling assumptions).

Step-by-step

Use DocketMath to estimate a Tennessee filing deadline from the verified statute-of-limitations inputs.

1) Identify which claim bucket best matches the dispute

In collections settings, common matches from the verified set include:

• Loan document / promissory note → 6 years
• Signed agreement / written contract → 6 years
• Verbal agreement / oral contract → 6 years
• Claims that sound like misrepresentation or deception (as pleaded/argued) → 3 years for fraud/deceit in the verified set

If fraud is part of the theory, don’t assume the contract period automatically applies.

2) Choose the trigger/start date you’ll test

DocketMath’s calculator workflow is built around supplying a start/trigger date. In this packet’s verified setup, the model also contemplates discovery and tolling-style inputs (for example, mental incapacity tolling: true and a discovery maximum window concept).

If you don’t know what trigger the opposing side will argue, run multiple DocketMath runs using different plausible start dates, then compare the resulting deadline to your “new year” reference date.

3) Run the calculation in DocketMath

• Go to the calculator: /tools/statute-of-limitations
• Select Tennessee (US-TN)
• Use the statute-of-limitations mode and enter:

  • the claim bucket (so the tool applies the packet’s period mapping), and
  • the start date/trigger date you’re testing.

4) Convert the output into a “new year” risk check

Once you have the estimated deadline date from the tool, compare it to your target date (for example, January 1 of the year you care about, or a specific “filing by” date).

A practical rule of thumb:

• If the estimated limitations deadline has already passed as of the “new year” date, the risk is that a later suit could be time-barred (subject to whatever start-date/tolling arguments apply).

5) If the creditor might plead a different theory, rerun with the new bucket

Collectors sometimes pursue multiple theories. If the pleadings could plausibly involve fraud instead of (or in addition to) a contract/debt theory, rerun the calculator using the 3-year fraud/deceit period bucket from the verified set and compare results.

Key statutes and citations

This guide relies on the statutes included in the verified and allowed authority lists—especially the primary limitations statute shown below.

• Tenn. Code Ann. § 28-3-104 (primary citation in this packet)
  Primary source URL: https://law.justia.com/codes/tennessee/2021/title-28/chapter-3/part-1/section-28-3-104/

• Tenn. Code Ann. § 28-3-105 (companion provision within the same limitations chapter; included in allowed citations)
  Source URL (allowed): https://law.justia.com/codes/tennessee/2021/title-28/chapter-3/part-1/section-28-3-105/

• Tenn. Code Ann. § 28-3-106 (companion provision; included in allowed source URLs)
  Source URL (allowed): https://law.justia.com/codes/tennessee/2021/title-28/chapter-3/part-1/section-28-3-106/

• Tenn. Code Ann. § 28-3-109 (additional timing rules within the same chapter; included in allowed citations)
  Source URL (allowed): https://law.justia.com/codes/tennessee/title-28/chapter-3/part-1/section-28-3-109/

• Tenn. Code Ann. § 29-26-116 (medical/professional claims timing; included in allowed citations)
  Source URL (allowed): https://law.justia.com/codes/tennessee/title-29/chapter-26/part-1/section-29-26-116/

• Tenn. Code Ann. § 47-2-725 (UCC sale-of-goods limitations; included in allowed citations)
  Source URL (allowed): https://law.justia.com/codes/tennessee/title-47/chapter-2/part-7/section-47-2-725/

Common pitfalls

• Picking the wrong claim bucket

  • If the dispute is characterized as fraud/deceit rather than a contract/debt claim, the verified packet mapping reflects a shorter 3-year period for fraud/deceit categories.

• Assuming “any new contact” resets the clock

  • Statute-of-limitations analysis is typically about the time to file a lawsuit under the applicable limitations period and the clock’s start trigger—not about whether collection attempts were made in the new year.

• Using the wrong start/trigger date in the tool

  • Even with the correct period length, using the wrong trigger date can move the estimated deadline significantly. When uncertain, run scenarios with different plausible triggers.

• Forgetting tolling/discovery assumptions that the tool model accounts for

  • The verified dataset includes mental incapacity tolling: true and a discovery-based maximum window concept in the modeled framework. If those inputs are relevant, make sure they’re represented in your DocketMath run.

• Overgeneralizing “one Tennessee SOL fits all”

  • Tennessee has multiple timing provisions and categories. For collections disputes, the most important first step is aligning the dispute to the packet’s claim-type mapping.

Run the numbers

Below is a practical DocketMath checklist that reflects how your inputs change the output under this packet’s verified framework.

1. Open DocketMath: /tools/statute-of-limitations
2. Select jurisdiction: Tennessee (US-TN)
3. Select claim type/bucket (based on the verified set):

   • Contract/debt categories → 6 years
   • Fraud/deceit categories → 3 years
4. Enter the start/trigger date you want to test

   • If you’re unsure, do multiple runs and document which start dates you used.
5. Apply relevant packet-model toggles/assumptions

   • The verified setup includes mental incapacity tolling: true
   • The verified dataset includes discovery/timing max window concepts in the model framework
6. Compare the computed deadline to your “new year” date

   • If the estimated deadline is before the new year reference date, the suit risk is higher for that theory (still subject to factual and legal disputes about triggers/tolling).

If you tell me the rough claim type (contract vs. promissory note vs. fraud/deceit) and the dates you have (contract date, last payment date, and/or incident date), I can help you structure the DocketMath runs—without giving legal advice.

Related reading

• Statute of limitations in United States (Federal): how to estimate the deadline — Full how-to guide with jurisdiction-specific rules
• Why statute of limitations results differ in United States (Federal) — Troubleshooting when results differ
• [Statute of limitations reference snapshot for United States (Federal)](/blog