Statute of Limitations for Account Stated / Open Account in Utah
6 min read
Published March 22, 2026 • By DocketMath Team
Overview
In Utah, creditors who sue to collect unpaid amounts often plead claims like “account stated” or “open account.” Those labels matter for litigation strategy, but they do not create unlimited time to file a lawsuit. Instead, Utah applies a general statute of limitations period to many contract-based debt collection actions.
For purposes of this page, the governing baseline is Utah’s general limitations framework. Based on the jurisdiction data provided, no claim-type-specific sub-rule was found for account stated or open account, so the default rule below applies as the general period.
You can use DocketMath’s Statute of Limitations Calculator to estimate dates tied to the relevant timeline events (such as when the account was last due or the last payment occurred, depending on what applies to your fact pattern).
Note: This page provides general information about Utah’s default statute of limitations for contract-type debt collection timing. It does not determine which specific cause of action a court would accept on any particular set of facts.
Limitation period
Utah’s general SOL period (default)
Utah’s general statute of limitations is 4 years under Utah Code § 76-1-302, as reflected in Utah Courts’ legal-help materials.
Because no claim-type-specific sub-rule was identified for account stated or open account in the provided jurisdiction data, you should treat this 4-year general period as the default SOL timeline for these types of account-based claims in Utah—subject to the exceptions below.
What “4 years” means in practice
The practical question is: when does the clock start? In most time-bar analyses, the clock starts from a triggering event tied to contract performance or default. Common triggering events include:
- Last date the debt was due under the agreement (often tied to an invoice/billing cycle or contractual maturity)
- Date of last payment or last acknowledgement that affects enforceability
- Date of breach if the claim is framed as breach of contract (account-based debts frequently end up treated as contract disputes)
Because Utah law and pleadings can vary by case and document trail, your timeline needs to be anchored to the best-supported date from your records.
Inputs you should collect before running the calculator
To use DocketMath effectively, gather:
- The date of the last payment (if any)
- The date of the last billing/due date you can document
- Any written acknowledgement of the debt (e.g., letters/emails/contracts) and its date
- The date you received a demand (sometimes relevant for context, but not always the SOL trigger)
Then run the calculator to see the estimated “latest filing” date based on the default period.
Key exceptions
Even when the default is 4 years, Utah law can change the outcome when certain legal events occur. The biggest SOL-impacting exceptions typically fall into these buckets:
1) Tolling (pauses) during certain legal situations
Some events can pause (“toll”) the statute of limitations. Tolling rules often depend on specific circumstances—such as procedural delays or particular legal disabilities. Without claim-specific sub-rules provided here, you should treat tolling as a case-specific analysis rather than something assumed automatically.
How to use this practically: if there was a pending related case, bankruptcy stay, or other legally significant barrier, your “clock” might not run uninterrupted.
2) Acknowledgement or new promise that revives enforceability
In many jurisdictions, a new promise to pay or clear acknowledgement can affect SOL timing by resetting or changing how limitations are computed. Utah courts generally require that the acknowledgement be sufficiently clear and tied to the debt.
How to use this practically: if you have correspondence that admits the debt (or makes a payment tied to an explicit agreement to pay), that evidence can matter to SOL calculations. The calculator can help you compare scenarios using different dates (e.g., last due date vs. last acknowledgement date).
3) Multiple obligations or installment structure
For accounts with installments (or multiple invoices), courts may treat each installment as having its own timing, depending on how the agreement and breach are pleaded.
How to use this practically: if your statement shows a series of charges rather than one matured amount, you may need to run calculations using different invoice due dates to see which portions are likely time-barred first.
Warning: Exceptions can significantly change the outcome. A small difference in the “start date” (for example, between last payment date and last due date) can shift the estimated end of the limitations period by months or even years.
Statute citation
Utah Code § 76-1-302 — sets forth Utah’s general statute of limitations framework, including the 4-year general period referenced in Utah Courts’ legal-help guidance: https://www.utcourts.gov/en/legal-help/legal-help/procedures/statute-limitation.html
Jurisdiction data used here:
- General SOL Period: 4 years
- General Statute: Utah Code § 76-1-302
- Claim-type-specific sub-rule: None identified in the provided jurisdiction data for account stated/open account; therefore, the default/general period applies.
Use the calculator
DocketMath’s statute-of-limitations calculator helps you convert timeline facts into an estimated latest filing date using Utah’s default 4-year general rule.
Primary CTA
Start here: **DocketMath Statute of Limitations Calculator
How to think about inputs (and how outputs change)
When you enter dates, the calculator effectively asks: “Four years from the chosen triggering date—what is the end of the allowable window?” Small input changes can produce different results.
Use these common scenarios as a guide:
Scenario A: Last due date is your anchor
- Input: the date the amount became due (or the last invoice due date)
- Output: “latest filing date” = last due date + 4 years (adjusted for any calculator-specific methodology)
Scenario B: Last payment/acknowledgement is your anchor
- Input: the date of the last payment or last qualifying acknowledgement
- Output: end date shifts forward if that date is later than the last due date
Scenario C: Multiple invoices
- Input: run the calculator for each invoice due date you have
- Output: see which invoices become time-barred earlier than others
Quick date checklist (before you hit calculate)
Once you run the calculator, treat the output as an estimate for scheduling and review, not a definitive courtroom ruling. If the other side argues a different triggering date or an exception applies, the relevant timeline can move.
Related reading
- Choosing the right statute of limitations tool for Vermont — Tool comparison
- Choosing the right statute of limitations tool for Connecticut — Tool comparison
