← All posts April 08, 2026

Ohio's reporting history — from decennial to biennial to "nothing required

A regulatory history most processors don’t know

Ohio is one of a small number of US states that does not currently require a recurring annual report for most business entities. This is unusual, and the history behind it explains some quirks in Ohio entity verification.

The relevant Ohio Revised Code chapters are 1701 (general corporations), 1705 (former LLC act, repealed 2022), and 1706 (the current Limited Liability Company Act, effective 2022).

The history, in brief:

  • Pre-1992: Ohio required a biennial corporate filing.
  • 1992: Ohio dropped the biennial filing in favor of a one-time formation requirement with no recurring report.
  • 1995-2014: Various proposals to reinstate a biennial or annual report — none passed.
  • 2022: Ohio enacted the new LLC Act (chapter 1706), which superseded the old chapter 1705. The new Act explicitly does not require recurring annual reports for LLCs.

The result, as of 2026, is that Ohio domestic corporations and LLCs have no required recurring filing with the Secretary of State after formation. The SOS record for an Ohio entity reflects whatever was on the formation document — and only that, unless the entity has voluntarily filed an amendment.

What this does to verification

A typical Ohio entity record on the SOS portal (bizimage.ohiosos.gov and businesssearch.ohiosos.gov) returns:

  • Entity name, charter number, type
  • Status (Active, Cancelled)
  • Date of formation
  • Statutory agent name and address
  • Original incorporator/organizer name and address (from the formation document)

What you do not get, in many cases: current officer list, current principal place of business, current ownership. A 1998-formed Ohio corporation that has filed no amendments has the same SOS record today that it had in 1998. The current CEO, current address, current capitalization — none of those are on the SOS unless somebody filed something voluntarily.

For commercial-finance verification, this is the gap. The SOS record can be 20 years stale and still show “Active.” Active here only means “the entity exists and has not been cancelled” — it does not mean “the entity filed something recently.” There is no biennial-report freshness check.

Why the entity might still be cancellable

Ohio retains the ability to cancel entities for two specific reasons:

  1. Failure to maintain a statutory agent. If the statutory agent resigns and the entity does not designate a replacement within 30 days, the SOS can cancel the entity. This catches a meaningful number of entities each year — the registered-agent service drops the account for non-payment, files the resignation, and the entity doesn’t notice.

  2. Failure to file a Statement of Continued Existence (corporations only). Ohio corporations (not LLCs) must file a Statement of Continued Existence every five years. Missing two consecutive five-year statements triggers administrative cancellation.

The Statement of Continued Existence is the closest Ohio comes to a recurring report. For corporations, the absence of a statement in the recent five-year window is a real cancellation risk. For LLCs, there is no equivalent — an Ohio LLC formed in 2010 with no amendments since is still Active and is in no danger of automatic cancellation.

The verification workaround

For Ohio entities, the SOS data alone is insufficient to verify current officers, current principal office, or current operating status. The workarounds:

  • Federal tax filings. An entity’s most recent federal return (990 for non-profits, 1120/1065/1120S for operating businesses) is filed with the IRS and not publicly accessible, but a credit applicant should be able to supply a current copy.
  • State tax filings. Ohio Commercial Activity Tax (CAT) registration is current for any entity with $150,000+ of taxable Ohio gross receipts. The Ohio Department of Taxation’s CAT lookup confirms whether the entity is currently registered.
  • State licensing. Most regulated Ohio businesses (contractors, trucking, financial services) have separate state licenses that are maintained on a current basis.
  • County-level UCC filings. Recent UCC filings against the entity indicate current operating activity.

The pattern: in Ohio, you have to triangulate “current operating status” from sources other than the SOS, because the SOS by itself only confirms “the entity has not been formally cancelled.”

The statutory-agent flag

The statutory-agent name and address is the most useful single piece of data on an Ohio SOS record because it is required to be current — the agent has to be a real person or registered service who consented to act and who has a real Ohio address. If the SOS record shows an old agent who is no longer at that address, the entity is at risk of administrative cancellation and may be unaware of it.

A specific pattern to watch: an Ohio entity with a statutory agent listed as an individual (rather than a registered-agent service) at an address that has changed hands (i.e., the individual moved away years ago). The entity is technically alive but service of process to that address bounces. Lending to such an entity creates a real notice-and-service problem if litigation arises.

What this means for you

For Ohio, the SOS record is a “does this entity exist” check, not a “is this entity currently operating” check. The Active flag is broad — it covers everything from a vibrant operating business to a 1995 paper entity that hasn’t filed anything since formation. To distinguish, you need a separate current data source.

A VerifySOS Ohio lookup pulls the SOS record and cross-references against Ohio Department of Taxation CAT registration, USDOT (for trucking entities), and OFAC. When the entity shows on tax or USDOT registration with a current-year filing, the packet flags it as “operating-current.” When it only shows on SOS, the packet flags it as “formation-only.” Developers get both flags on /api/v1/lookup.

Report a bug — straight to our team

See something broken or weird? Tell us. Your report submits directly to our team — no email client needed. Each report gets a unique ticket ID so we can track and respond.

v0.8-beta · 6d85e11