How filed values are resolved
Every number on /financials is a value a company filed with the SEC, with the filing that reported it. When filings
disagree about a period, every value is kept with its filing. The rest of a financials answer is on
Filings and financials.
Default values
With assertions=latest (the default), each period serves the most recent value the company filed for it, as known
at known_at. accession, form, cik, and accepted_at name the filing that first reported that exact number.
A value with no field_states.value entry is served as filed: use it.
Later filings that change a value
When a later filing reports a different number for the same period, that number is served, attributed to its own
filing, and revises names the earlier value and its filing. A 10-Q can revise a prior fiscal year.
revises.kind | use |
|---|---|
revision | the filer now reports a different number: treat it as the current figure |
restatement | the filer's disclosed correction |
revises.context names, by accession, a non-reliance disclosure (8-K item 4.02) the company filed between the two
values' filings: read it to see which periods it covers.
Withheld values
A period whose filings disagree unresolved serves no value: value, accession, form, cik, and accepted_at are
null, and field_states names the reason:
| reason | what to do |
|---|---|
conflicting_assertions | compare the values in conflicting_assertions (oldest first, each with its filing), or request it again after the company's next filing |
unreliable | the only value filed is impossible for the item (a negative share count): there is no usable value for the period |
Each entry of conflicting_assertions has an assertion_state: conflicting (one side of the conflict) or rejected
(impossible for the item, so not used). When a later filing settles a conflict, the period serves that value again.
Values served with a caution
A value with field_states.value unverified, reason unconfirmed, is served: check it in the filing before summing,
comparing, or relying on it.
Every filed value
assertions= on /financials chooses what each period serves:
assertions | serves |
|---|---|
latest (default) | the current figure (default values) |
as_first_reported | the value in the first filing for the period known at known_at, unaffected by later filings. A first filing that reported two values is withheld |
all | the latest value plus assertions[]: every value filed for the period, oldest first, each with its relation |
view=continuity takes assertions=latest only (422 otherwise).
Relations
relation | use |
|---|---|
first | the filer's original figure |
repetition | the same number filed again: ignore it |
co_registrant_copy | the same value under another registrant's CIK: count it once |
revision | the filer's newer figure |
restatement | the filer's explicit correction: prefer it to the value it replaces |
conflicting | in conflict with another value: do not use it as the period's figure |
cleared | once in conflict, then reported again by a later filing (listed as repetition); the served value says whether it is the period's figure |
rejected | impossible for the item: never a value |
Reproducible reads
Each /financials answer echoes assertions. Pin known_at with saved results. A filing accepted before your
known_at can still arrive later and change an answer, so keep the values you saved rather than requesting them again.