What it reads

One XBRL concept for one company — every value it has reported for that tag, across all its filings — and keeps the newest periods.

Tag is the concept name as the SEC stores it. Common ones:

• RevenueFromContractWithCustomerExcludingAssessedTax — revenue for most modern filers
• NetIncomeLoss — net income
• Assets, Liabilities, StockholdersEquity

⚠ There is no universal revenue tag. Filers choose which concept to report under, and it changes between eras and industries. A company that reports revenue under a different tag returns 404, which this recipe reports as not reported under that tag rather than as an error — try another tag rather than assuming the company filed nothing.

⚠ USD only. The response groups values by unit; this recipe reads units.USD and ignores the rest, so a foreign-currency filer will look empty. That is a real limit, not a bug, and the card says which units were present.

⛔ One period, one figure: the SEC's. A 10-Q reports the quarter AND the year to date under the same end date, and a later filing repeats earlier periods as comparatives under its own fiscal label. This keeps only the fact the SEC aligned to a single period (it carries a frame: CY2026Q2 a quarter, CY2025 a year); where a year and a quarter end the same day, the year is kept. Each row is labelled by the filing that FIRST reported the period. Until 2026-10-08 this recipe read the response one level too shallow and stored nothing at all, and had it read it, it would have stored every second and third quarter as its year to date (Apple's FY2026 Q3 as $364.4B; the quarter was $109.4B).

A figure that is no period's own is corrected. If a stored figure is not any filing's figure for that single period (a year to date kept under a quarter's date), a refresh replaces it with the period's own figure and label, and the card counts it. A figure some filing reported for that period is left alone, so a restatement still never overwrites history.

⚠ Both 10-K and 10-Q rows are kept, and they are not comparable. A 10-K value is usually a full year and a 10-Q a single quarter; the form column tells you which. Do not sum a column that mixes them.

⚠ Restatements exist. A later filing can report a different value for a period already stored. One period of one concept for one company is ONE row, and the first value observed is the one kept — refreshing never overwrites history and never adds a second row for a period you already have. Delete the datapoint if you want it re-read.

⛔ That rule is enforced by the store, not by this recipe, and it did not used to be. The recipe reads back what it already holds and skips those periods, but that read is capped at 200 rows — so a company with a long history compared itself against a fraction of itself, and every refresh past that point added the same periods again. The row id is now derived from the company, the concept and the period, so a period you already have is recognised however long the history is. The read-back stays as a shortcut; it is no longer what keeps the numbers right.

⚠ This reports what was filed. It is not advice, a score, or a recommendation, and nothing here values a company.