Statute of Limitations for Account Stated / Open Account in Ohio

Overview

Run this scenario in DocketMath using the Statute Of Limitations calculator.

In Ohio, the statute of limitations (SOL) for an account stated or open account is generally handled using the general/default 0.5-year period under Ohio Rev. Code § 2901.13 (per the jurisdiction data provided).

Because this article is aimed at real-world timing questions—often arising in debt-collection disputes—a practical way to distinguish these labels is:

• Account stated: the parties are arguing that a balance was accepted/acknowledged as accurate (for example, by statement and lack of objection).
• Open account: the claim is based on an ongoing set of transactions (for example, invoices/charges) that remains unpaid.

Importantly, no claim-type-specific sub-rule was identified for these “account stated” / “open account” categories in the materials you provided. That means this guide uses the general/default period as the SOL baseline rather than a shorter or longer specialized deadline.

Limitation period

Based on the jurisdiction data, the general SOL period is 0.5 years under Ohio Rev. Code § 2901.13. Interpreted into a practical time window:

• General default SOL: **6 months (0.5 years)

This is a relatively short deadline compared with many other civil claim types, which is why the “start date” (accrual/event date) is often the hardest—and most important—part of the analysis.

Why the start date matters

SOL periods typically run from when the cause of action accrues (for example, when the debt becomes due, or when the alleged account-stating “statement/acceptance” occurs). While § 2901.13 provides the general timing framework, your case may hinge on what date you can actually support with documentation, such as:

• invoice due dates,
• the date of a final statement,
• written acknowledgements of the balance,
• communications that can be argued to trigger accrual under the chosen theory.

Practical input/output model (for DocketMath)

When you use DocketMath’s statute-of-limitations calculator, the output generally depends on two date inputs:

• Event/accrual date (when the claim is argued to have accrued—e.g., last transaction due date, last balance-statement acceptance date, or similar provable date)
• Filing date (when the lawsuit/complaint was filed), or you may use today’s date to estimate timing risk

Output you typically get: whether the filing is within or outside the 0.5-year (6-month) window.

Example timelines (illustrative)

Takeaway: even if the legal SOL rule is fixed at 6 months, shifting the provable event date by weeks can change the result.

Key exceptions

This guide focuses on the general/default 0.5-year period because no account-type-specific sub-rule was found for “account stated” or “open account” in the provided jurisdiction data. However, exceptions and adjustments can still affect results in Ohio cases.

Here are the most common categories to check when mapping your dates and evidence:

1) Tolling or pause events

Some circumstances may pause (toll) the SOL clock. In practice, these disputes depend heavily on the factual record and procedural history. If the plaintiff alleges facts that justify tolling, you’ll want to verify whether those facts actually support a legal basis to pause the timeline.

2) Acknowledgement that can change the “clock” (in argument)

In some disputes, communications may be argued to restart or affect accrual (for example, an acknowledgement of the debt balance). Even if the statute’s overall duration is still the general one, acknowledgement can impact what accrual date is defensible.

Practical framing: treat this as a litigation-risk and date-accrual issue, not a guaranteed “restart” under all circumstances.

3) Wrong claim framing / how courts characterize the cause of action

Even if a case is labeled “account stated” or “open account,” courts may look at the substance. If the court characterizes the claim differently, the parties may argue for a different limitation period.

Because your dataset indicates no claim-type-specific sub-rule was identified, the default 0.5-year period is your baseline—but classification arguments can still matter.

4) Evidence gaps that change the event date

With a short SOL, proof matters. Cases can flip outcomes depending on which date is provable, such as:

• itemized invoices or ledger entries,
• written statements and mailing dates,
• email/text letters acknowledging the balance,
• payment history and transaction logs.

Quick checklist for exception review

Use this checklist to gather the inputs that often determine the SOL outcome:

Statute citation

This guide’s general/default SOL baseline is based on:

• Ohio Rev. Code § 2901.13
  Source reference PDF: https://codes.ohio.gov/assets/laws/revised-code/authenticated/29/2901/2901.13/7-16-2015/2901.13-7-16-2015.pdf

Per the jurisdiction data provided, the general SOL period is 0.5 years, and no claim-type-specific sub-rule was found for “account stated” or “open account.” Therefore, this article uses the general/default period.

Use the calculator

Use DocketMath’s statute-of-limitations calculator to turn your dates into an easy within/outside the window result based on the 0.5-year default tied to Ohio Rev. Code § 2901.13.

Primary CTA: /tools/statute-of-limitations

What you’ll typically enter

To get a meaningful result, you generally need:

• Event/accrual date (the date the claim is argued to have accrued—e.g., due date or statement/acknowledgement date)
• Filing date (when the complaint was filed), or alternatively
• Today’s date (to estimate current SOL exposure)

How outputs change

Because the SOL period is short (6 months), small date differences can matter a lot:

• Moving the event/accrual date forward by 30–60 days can meaningfully change whether filing is within the deadline.
• Using a demand letter date instead of the provable accrual date can produce misleading results, because the SOL is often measured from when the claim accrues—not merely when a demand was sent.

Suggested workflow

1. Gather account records (invoices, statements, and correspondence).
2. Identify the most defensible event/accrual date supported by evidence.
3. Enter the event date and the filing date into DocketMath.
4. If the result is close, rerun using alternate plausible event dates supported by documentation, then compare outcomes.

(Not legal advice—use the tool to organize timelines and questions for an attorney or qualified legal professional.)

Related reading

• Choosing the right statute of limitations tool for Vermont — How to choose the right calculator
• Statute of limitations in Singapore: how to estimate the deadline — Full how-to guide with jurisdiction-specific rules
• Choosing the right statute of limitations tool for Connecticut — How to choose the right calculator