Published

Filing deadlines

Startupsole LLC
Startupsole LLC
0

A comprehensive, open-source dataset providing highly accurate, machine-readable information on United States LLC formation fees, recurring annual reporting costs, and state compliance requirements ac...

Filing deadlines

This namespace is a typed normalization surface for one product question about an ordinary domestic LLC: when is the next recurring periodic report or statement due? It currently contains six jurisdictions; an owner-approved campaign is expanding the same contract and quality standard to all 51 jurisdictions.

Product contract

A consumer supplies a jurisdiction and the LLC formation date. The evaluation date (asOfDate) is a system input. A record yields exactly one outcome:

  • calculated: a verified next filing date or month window can be computed.
  • not_required: the authoritative record affirmatively says that an LLC periodic report is not required.
  • unavailable: the current data cannot support either conclusion or cannot produce the result from the permitted inputs.

unavailable is fail-closed. A missing record, null, an empty source list, or silence is never equivalent to not_required.

The only obligation in scope is the ordinary domestic LLC's recurring periodic_report, including an annual or biennial report or statement filed to keep the entity record current. Franchise tax, tax returns or payments, separate information filings, fees, amounts, thresholds, penalties, interest, status consequences, reinstatement, and dissolution are excluded.

Calculation contract

The public input set is fixed at state and formation_date. asOfDate is supplied by the consumer system and is not a third user question. A rule is executable only when those inputs are sufficient and every component has a typed value. Rules that depend on an assigned filing month, fiscal or tax year end, entity status, revenue, or another entity-specific fact yield unavailable.

Version 2 supports exact annual/biennial fixed dates, formation-anniversary dates, and formation-month windows. A missing cutoff timezone does not block a date-only result, and this namespace carries no time-of-day or filing-cutoff claim.

Projection and provenance

This namespace is a typed projection of entitysearch-state-data, not an independently maintained copy of state law. Each record carries resolvable JSON references for:

  • the authoritative state record and fact fields;
  • the official action link when a filing action exists;
  • the official source records shown to the user; and
  • the authoritative verification date.

The semantic validator resolves those references, requires identity and verification-date parity, and checks the supported due-phrase mapping. A projected value cannot be made fresher by editing this namespace. New portal research belongs in the authoritative namespace first; this namespace may then normalize the verified result.

Coverage status

The namespace contains Texas, New York, Delaware, Alabama, Maine, and Massachusetts. Five records are production-ready; Alabama is explicitly unavailable because the authoritative prose does not bind its no-report statement to an ordinary domestic LLC. The active coverage target is all 50 states plus the District of Columbia.

Coverage and answerability are separate. A jurisdiction counts as covered when it has a valid, source-bound record; only calculated and not_required are production-ready. A rule that the permitted inputs or current schema cannot express remains unavailable with an explicit blocker. It is never promoted to a definitive outcome merely to reach 51 records.

Until the campaign closes, consumers must continue to handle both missing records and unavailable explicitly. The current record count is published in the root coverage table.