Three different dates sit on every filing history row, and none agree

Every row in a filing history carries up to three dates. Most misreadings of a history come from treating them as one. That is the first fact below.

The rest follow from how the rows are made. A document arrives, an office stamps it, a clerk or a script indexes it. Later a reader opens a page that shows the index and, with luck, the image.

What to take away

Three dates on every row

The filing date is when the office received and accepted the document. It is the date the index shows by default.

The effective date is when the document says the change takes effect. It can be earlier, for a late filing that records something that already happened, or later, for a filing with a delayed effective date. It lives inside the document, and many indexes do not display it.

The indexed date is when the row appeared on the public page. Offices work through backlogs, and a document can be accepted on one day and searchable a week later. Nobody shows this date, but it explains why a filing you know was made is not yet visible.

When a history is read against a contract or a dispute, the effective date is usually the one that matters, and it is the one you have to open the document to find.

The row is not the document

An index row typically shows a document type, a date, and sometimes a page count. It was written by the office to classify the filing, not to describe it. "Amendment" tells you the founding document changed; it does not say what changed. "Statement of change" could be an agent, an address, or both. Reading the row and skipping the image is reading a label on a box.

The difference is clearest in a system that does both. The SEC's full-text search runs across the contents of filed documents, not their index labels. The two result types look different.

Most entity registers offer only the label. Where the office provides images, open them for any row that carries weight. Where it does not, the row is all you have. The note should say so.

Older rows may be thinner or missing

Registers went digital at different times, and the conversion was rarely complete.

Rows before the conversion date may show a type and date with no image or a single "historical filing" placeholder. Or they may be absent entirely, with the paper file still at the office. A history that starts abruptly in a given year usually shows the office's system date, not the company's birth.

The formation date on the entity page is generally reliable even when the early rows are not, because it was carried over as a field rather than as a document. So is the entity number, which survives the conversion for the same reason.

Rows come from paperwork, and paperwork lags life

A history records what was filed and when, not what happened and when. A company that changed its agent in March and filed in September has a September row. A company that never filed has no row. The gap between event and filing is invisible unless the document states an effective date.

This cuts both ways. A cluster of filings in one month can mean a busy month, or an overdue catch-up in which a year's changes were filed together. The document images distinguish the two; the index cannot.

Periodic reports are a rhythm, and the rhythm is set by the office

Each state sets the cadence of recurring reports for each entity type, and it differs. A history with a report every year and one with a report every other year can both be compliant.

Registers publish their own cadence: a national registrar states plainly when a company must file its annual accounts, and state offices publish the equivalent for their periodic reports. Find that statement for this entity type before reading a gap as a lapse. If a gap was a real lapse, the registration status field will usually have moved first.

Administrative rows are written by the office, not the company

Administrative dissolution, revocation, forfeiture, and similar rows record an action the office took, typically after notices went unanswered. Reinstatement records the company answering. Reading the pair together gives the length of the lapse and, through the reinstatement document, sometimes the reason. Neither row was authored by the company, which is why they carry more weight than the rows the company chose to file.

Foreign registrations are a partial view

A history on a state where the company is registered as a foreign entity begins at qualification and ends at withdrawal. It knows nothing of the home state's events.

Registering in each state where a business actually operates is the ordinary expectation set out in the Small Business Administration's guidance on launching a business. That is why one company routinely has several partial histories.

Two histories for one company in two states will disagree in length, content, and sometimes status, and both are right about their own office. The full story is at home; the state entity directories pillar explains how to find which state that is.

Rows are not deleted, but they are occasionally corrected

Registers are append-only in principle. In practice, an office that indexed a document against the wrong entity, or with the wrong type, will fix it, and the fix is rarely announced. A history you saved last year can differ from the one on the page today by a row that moved, not only by rows that were added.

The honest summary of a row

A row read fully supports one sentence: on this filing date the office accepted a document it classified as this type, which took effect on the date stated inside it and may or may not be viewable here.

Everything beyond that comes from opening the document. What a document does not say, the register does not know. Reading a whole history that way is what the filing history pillar sets out to teach.

A short discipline

Record the filing date from the index and the effective date from the document, and label each. Note whether the image was available.

If early history looks truncated, note the office's system date. Before calling any gap a lapse, note the report cadence the office states for this entity type. Four lines close most of the ways a history gets misread.

Common questions

The index and the document give different dates. Which do I write down?

Both, labeled. The filing date tells you when the office learned of it; the effective date tells you when it counted. A note carrying one unlabeled date is the thing that causes arguments later.

A filing I made last week is not showing. Has it been rejected?

Not necessarily. Acceptance and indexing are separate steps, and the second can trail the first. Check the receipt or confirmation the office gave you at submission, and give the index a few working days before treating silence as rejection.

Why does a document sometimes appear with no image?

Usually because it predates the office's imaging program, or because the office images only certain document types. Some offices will supply a copy of an unimaged document on request. Ask before concluding the document does not exist.

Can I rely on a history I downloaded a year ago?

For what the register showed you then, yes. For today, no. Corrections and reclassifications happen quietly, and periodic reports will have been filed since. Re-pull the history when it is going to carry weight in a decision.