Detect Filing Timeliness Deterioration With Claude and FMP MCP

By Pranjal Saxena·Oct 21, 2026·21 min read

Data in Action

When you monitor a company, changes in how long it takes to publish financial statements can help you decide which reports deserve closer attention. A longer reporting lag gives you a concrete question to investigate: what changed between the end of the fiscal period and the arrival of the filing?

This workflow uses Claude and Financial Modeling Prep's MCP server to turn SEC filing records into a repeatable timeliness screen. You retrieve a company's latest four original quarterly reports, Form 10-Q, and latest two original annual reports, Form 10-K. Claude matches each report to its fiscal period, calculates the calendar days to SEC acceptance, compares quarterly reports with quarterly reports and annual reports with annual reports, and identifies related notices of late filing. The output is a filing-by-filing record with accession links, lag changes and a rule-based classification you can use to prioritize follow-up across your coverage list.

Scilex Holding Company (SCLX) provides the worked example. At the October 15, 2026 cutoff, its FY2025 annual report took 10 days longer than the prior year's, and its Q1 FY2026 quarterly report took five days longer than the previous quarter's. Both followed NT notices, which companies submit when they do not expect to meet the original filing deadline. The screen classifies the sample as Deteriorating under the illustrative rules, even though the latest quarterly lag improved.

That result gives you a starting point for reading the filings and notices. It does not establish why reporting slowed or whether the company complied with SEC deadlines.

Key takeaways

Scilex's FY2025 10-K was accepted 100 days after year-end, compared with 90 days for FY2024. The 10-day increase is the largest same-form change in the sample.
The four 10-Q lags were 44, 45, 50 and 45 days. The slower Q1 FY2026 filing was followed by an improvement in Q2.
Two NT notices were associated with the selected reports: an NT 10-K for FY2025 and an NT 10-Q for Q1 FY2026.
Two of four comparisons were Slower. The latest 10-K was Slower, so the overall rule returned Deteriorating. All six selected filings matched their fiscal periods and passed the date checks.
FMP supplied notice metadata and links. Read the linked notices for the company's explanation; a longer lag alone does not establish its cause.

Building the filing timeliness screen

Scilex files on a calendar fiscal year, and between April and May 2026 it filed two NT notices followed by the reports they referred to. That makes it a useful test of how lags, notices and mapping rules work together. The analysis is a snapshot of the October 15 retrieval, not a continuously updated assessment.

Start with when the reports arrived, then investigate what changed. Reviewing material filing changes and regulatory risks can help you examine the disclosures behind a change in reporting lag.

Definitions and sample selection

Term	Meaning in this screen
Core filing	An original 10-Q or 10-K; amendments and NT notices are excluded
Acceptance date	Calendar date of acceptedDate, subject to the date-convention safeguard
Period end	Fiscal period end from the matched FMP income-statement record
Filing lag	Acceptance date minus period end, in calendar days
Same-form lag change	Current lag minus the previous selected lag for the same form
NT notice	Form 12b-25 submitted as NT 10-Q or NT 10-K

The screen searches every filing FMP returns for the symbol from January 1, 2025 to the cutoff, reading pages until one returns no data. “Latest” means the four original 10-Qs and two original 10-Ks with the most recent acceptance timestamps on or before the cutoff. After selection, the filings are ordered by period end, so a report submitted out of order still lands in its own fiscal period.

If two originals map to the same period, the affected rows require review. The four 10-Q periods must also be consecutive, allowing for the expected absence of Q4 because the annual report covers that quarter. This keeps filing dates and fiscal periods aligned rather than treating the submission date as the period being reported.

Mapping each filing to its period

The SEC-filings records used in this run did not contain a period-end field. Each core filing was matched to the FMP income-statement record whose acceptedDate was identical to the second: a quarterly record for a 10-Q and an annual record for a 10-K. Period end, fiscal year and period came from that matched record.

A filing with no exact match, or more than one, is Review Required. Date proximity, fiscal labels and dates embedded in document names are not substitutes. Exact matching makes the join reproducible, although matching two FMP datasets is not an independent verification of the underlying filing.

Acceptance dates and the timestamp safeguard

In this run, acceptedDate contained a date and time without a timezone. The timezone is therefore treated as an inference, not a documented FMP field convention. One historical record is consistent with Eastern time: Scilex's FY2023 10-K has acceptedDate 2024-03-11 17:57:25 and filingDate 2024-03-12. For the forms in this screen, the general EDGAR filing-date rule uses Eastern time and generally assigns submissions commencing after 5:30 p.m. to the next business day.

The screen uses the calendar date of acceptedDate, kept separate from filingDate. A core timestamp passes the conservative date safeguard only when:

Its date equals the date component of filingDate, or its time is after 17:30 and filingDate is the next business day, accounting for U.S. federal holidays.
Its time is between 05:00:00 and 19:59:59. Within that range, the calendar date remains the same if the timestamp is interpreted as Eastern time or UTC, including during standard time.

This safeguard protects the calendar-day calculation under those two interpretations; it does not establish FMP's timezone. A failed check produces “Review Required: date convention,” and no lag is calculated. All six displayed core timestamps pass.

Row direction and notice status

Same-form lag change	Direction
At least +3 days	Slower
−2 to +2 days	Stable
At most −3 days	Faster
Oldest selected filing of each form	Baseline
Either lag unavailable	Review Required

The three-day threshold is an illustrative screening rule, not an SEC deadline, an industry standard or a materiality test. Slower means the filing took at least three more calendar days than the previous selected filing of the same form. It does not mean the report was late.

An NT notice is associated with the first subsequent original report of the same form, provided that report's period end precedes the notice. This is a metadata-based screening association. Reading the notice is the next step when you need to confirm its stated period or explanation.

A notice with no subsequent report by the cutoff is listed as awaiting report, separately from the completed-filing comparisons. That pending state is not a mapping failure. If a later report exists but its period is incompatible or cannot be mapped unambiguously, the notice association requires review.

Each core row receives either “NT 10-Q identified,” “NT 10-K identified,” or “No NT identified (search complete).” An incomplete search can never support the last label. The cause field says “Company-stated reason not retrieved through FMP” when only metadata or a link was returned; it does not claim the reason is unknown.

Under Rule 12b-25, reports filed within the applicable 15-calendar-day period for a 10-K or five-calendar-day period for a 10-Q may be deemed timely if the rule's conditions are met. This screen does not determine filer status, original due dates or satisfaction of those conditions.

Overall classification and confidence

Apply the tests in this order:

Order	Test	Result if met
1	Any core row requires review, NT mapping is ambiguous, or the main search is incomplete	Review Required; stop
2	At least two Slower comparisons AND at least one of: latest 10-Q Slower; latest 10-K Slower; NT notice mapped to a core row	Deteriorating
3	At least two Faster comparisons, no Slower comparison and no mapped NT notice	Improving
4	No Slower comparison and no mapped NT notice	Stable
5	Any remaining combination	Mixed: deterioration signal present

For rule 2, the notice condition is an alternative to either latest-form condition: at least two Slower comparisons are always required. With four 10-Qs and two 10-Ks, there are four comparisons, three quarterly and one annual.

Confidence rates retrieval and rule application, not the company or the economic significance of the result. High requires six core filings, unique timestamp matches, passing date checks, a fully read main search window, and no ambiguous notice associations. Otherwise, confidence is Low and the relevant exception must be resolved. A pending notice remains visible even when it does not enter the completed-filing classification.

FMP inputs and Claude setup

The workflow uses the SEC Filings By Symbol API and Income Statement API. Use the connector's endpoint parameter to select the operation within each tool. The table shows the inputs for the Scilex example.

Connector tool and operation	REST path	Parameters used	Fields used
secFilings / search-by-symbol	/stable/sec-filings-search/symbol	SCLX; 2025-01-01 to 2026-10-15; limit 100; pages 0, 1, 2	formType, filingDate, acceptedDate, link, finalLink, cik
secFilings / search-by-symbol	/stable/sec-filings-search/symbol	SCLX; 2024-01-01 to 2024-12-31; limit 100; page 0; historical context only	formType, filingDate, acceptedDate, link
statements / income-statement	/stable/income-statement	SCLX; period quarter; limit 8	date, fiscalYear, period, filingDate, acceptedDate
statements / income-statement	/stable/income-statement	SCLX; period annual; limit 3	date, fiscalYear, period, filingDate, acceptedDate

In a raw log, tool names may carry a connector prefix such as mcp__FMP__secFilings. Accession numbers are derived from the returned SEC links. Lags, changes, notice associations and classifications are calculated by Claude, rather than returned FMP fields.

The Scilex data was retrieved on October 15, 2026, between 14:46:55 and 14:49:18 UTC. A fixed cutoff does not freeze a vendor dataset: later retrievals may reflect additions or corrections. Retain the returned records when checking the inputs supplied to an AI workflow.

To connect, follow the FMP MCP setup instructions. You need an active FMP API key and access to Claude's custom connector setup. In Settings, open Connectors, choose Add custom connector and enter this URL with your own key:

https://financialmodelingprep.com/mcp?apikey=YOUR_FMP_API_KEY

Start a new conversation after saving the connector. Run Prompt 1, inspect the accession links and mapping output, then run Prompt 2 in the same conversation.

Prompt 1 Retrieve and map the filings

Use the reusable prompt below to retrieve and organize the filings before calculating lags. The example tables contain the October 15, 2026 data snapshot; the prompts include safeguards for applying the workflow to subsequent searches.

Objective

For Scilex Holding Company (SCLX), retrieve SEC filing metadata through

the FMP MCP connector, select the core filings as of the analysis cutoff

2026-10-15, map each to its fiscal period, and identify NT notices.

Do not calculate lags or classifications in this step.

Data rules

- Use the FMP connector only.

- Call the secFilings tool, endpoint=search-by-symbol, symbol=SCLX,

from_date=2025-01-01, to_date=2026-10-15, limit=100, starting at

page=0. Request the next page until a page returns no data. If any

page fails, retry it once; if it still fails, report "NT search

incomplete" and stop.

- Core filings: the four original 10-Q and the two original 10-K

filings with the latest acceptedDate on or before the cutoff. Exclude

10-Q/A, 10-K/A, NT 10-Q, NT 10-K and every other form type from the

core sample. Order the core filings by period end.

- Period mapping: call the statements tool, endpoint=income-statement,

symbol=SCLX, once with period=quarter, limit=8 and once with

period=annual, limit=3. Match each 10-Q to the quarterly record and

each 10-K to the annual record whose acceptedDate equals the filing's

acceptedDate exactly. Take date (period end), fiscalYear and period

from that record. No match, or more than one, is Review Required. Do

not use date proximity, fiscal labels or file names.

- If two core filings map to the same period, or the 10-Q periods skip

a quarter other than Q4, mark the affected rows Review Required.

- NT mapping: map each NT 10-Q or NT 10-K in the window to the first

original report of the same form accepted after it. Keep the mapping

only if that report's period end is before the notice's acceptedDate.

A notice with no later report by the cutoff is "awaiting report",

a pending monitoring item rather than a mapping failure. If a later

report exists but its period is incompatible, missing or ambiguous,

mark "Review Required: NT mapping ambiguous". The first subsequent

report is a screening association, not confirmation of the period

identified in the notice text.

- Identify elapsed fiscal quarters with no original report in the

retrieved records by the cutoff. List them as not yet reported,

separately from the completed-filing sample. Do not infer lateness.

- Accession number: take it from the link field. Report acceptedDate

and filingDate exactly as returned.

- Also list any amendment or NT notice related to the core periods or

the window, with the reason it is excluded.

- Supplementary historical context: call secFilings,

endpoint=search-by-symbol, symbol=SCLX, from_date=2024-01-01,

to_date=2024-12-31, limit=100, page=0. Use this only to find the

NT 10-Q associated with the Q3 FY2024 10-Q accepted 2025-01-17.

Continue pages only if needed to find that notice. Log the pages

actually read; do not label this supplementary window complete

unless an empty page is reached. Do not add this notice to the

core sample's mapped-notice count.

- Never use web search or any non-FMP source.

Output

Table 1. Retrieval log

Columns: Item | Result

Rows: Retrieval date and time | Calls and parameters |

Records per page | Pages read | Window fully read |

Income-statement records returned | Retries

Table 2. Core filings

For readability, split the filing identity and period-mapping fields into

two tables keyed by fiscal period, retaining every field.

Columns: Form | Fiscal period | Period end | Accession |

acceptedDate (as returned) | filingDate | Matched income-statement record |

Mapping status

Table 3. Notices, exclusions and pending periods

Columns: Filing | Accession | acceptedDate (as returned) |

Related period | Treatment

After the tables, state in one sentence whether the window was fully

read and every core filing mapped. Do not interpret the figures.

Scilex filing records at the cutoff

The main search's earliest selected period end was December 31, 2024, so its notice search began January 1, 2025. With 100 records per page, page 0 ran from September 29, 2026 back to October 9, 2025; page 1 ran from October 9, 2025 back to January 3, 2025. Page 2 returned no data. The supplementary search found the historical 2024 notice on its first page. Its purpose was to supply that earlier comparison, so only the main window was searched to completion.

Table 1. Retrieval log

Item	Result
Retrieval date and time	October 15, 2026, 14:46:55-14:49:18 UTC
Main filing search	SCLX; January 1, 2025 to October 15, 2026; limit 100; pages 0-2
Main records per page	100, 100, 0
Main window fully read	Yes
Supplementary historical search	SCLX; calendar 2024; limit 100; page 0 returned 100 records
Income-statement records	8 quarterly; 3 annual
Retries	0

Table 2. Core filings and period mapping

Form	Fiscal period	Period end	Accession and SEC record	acceptedDate as returned
10-K	FY2024	2024-12-31	0000950170-25-047800	2025-03-31 16:30:46
10-Q	Q2 FY2025	2025-06-30	0000950170-25-108029	2025-08-13 16:09:50
10-Q	Q3 FY2025	2025-09-30	0001193125-25-283153	2025-11-14 16:33:18
10-K	FY2025	2025-12-31	0001193125-26-151455	2026-04-10 17:29:24
10-Q	Q1 FY2026	2026-03-31	0001193125-26-232857	2026-05-20 17:22:39
10-Q	Q2 FY2026	2026-06-30	0001193125-26-352464	2026-08-14 16:41:44

Fiscal period	filingDate, date component	Matched income-statement record	Mapping status
FY2024	2025-03-31	Annual FY2024	Exact timestamp match
Q2 FY2025	2025-08-13	Quarterly Q2 FY2025	Exact timestamp match
Q3 FY2025	2025-11-14	Quarterly Q3 FY2025	Exact timestamp match
FY2025	2026-04-10	Annual FY2025	Exact timestamp match
Q1 FY2026	2026-05-20	Quarterly Q1 FY2026	Exact timestamp match
Q2 FY2026	2026-08-14	Quarterly Q2 FY2026	Exact timestamp match

All six filings matched one income-statement record by exact timestamp. The selected 10-Q periods are Q2 FY2025, Q3 FY2025, Q1 FY2026 and Q2 FY2026. Only the expected Q4 is missing, and no two core filings share a period. The filingDate column above displays the date component; the excerpts below retain its returned midnight timestamp.

Table 3. Notices, exclusions and pending periods

Filing	Accession and SEC record	acceptedDate as returned	Related period	Treatment
NT 10-K	0001193125-26-135582	2026-04-01 06:03:28	FY2025	Mapped to 10-K accepted April 10, 2026
NT 10-Q	0001193125-26-226675	2026-05-15 16:06:21	Q1 FY2026	Mapped to 10-Q accepted May 20, 2026
10-K/A	0000950170-25-060302	2025-04-29 17:00:25	FY2024	Excluded: amendment
NT 10-Q	0001193125-24-258692	2024-11-14 16:36:50	Q3 FY2024	Historical context only; associated 10-Q accepted January 17, 2025 is outside the latest four
None	Not applicable	Not applicable	Q3 FY2026, ended September 30	No 10-Q or NT 10-Q identified by cutoff; outside completed-filing sample

No notice was awaiting a report in this sample. Q3 FY2026 had ended but had no report or NT notice identified at the cutoff; that alone is not evidence of a missed deadline.

Returned record excerpts

These excerpts show the filing metadata and income-statement fields needed to reproduce the period matches.

{"formType":"10-K","filingDate":"2025-03-31 00:00:00","acceptedDate":"2025-03-31 16:30:46","link":"https://www.sec.gov/Archives/edgar/data/1820190/000095017025047800/0000950170-25-047800-index.htm"}

{"formType":"10-Q","filingDate":"2025-08-13 00:00:00","acceptedDate":"2025-08-13 16:09:50","link":"https://www.sec.gov/Archives/edgar/data/1820190/000095017025108029/0000950170-25-108029-index.htm"}

{"formType":"10-Q","filingDate":"2025-11-14 00:00:00","acceptedDate":"2025-11-14 16:33:18","link":"https://www.sec.gov/Archives/edgar/data/1820190/000119312525283153/0001193125-25-283153-index.htm"}

{"formType":"NT 10-K","filingDate":"2026-04-01 00:00:00","acceptedDate":"2026-04-01 06:03:28","link":"https://www.sec.gov/Archives/edgar/data/1820190/000119312526135582/0001193125-26-135582-index.htm"}

{"formType":"10-K","filingDate":"2026-04-10 00:00:00","acceptedDate":"2026-04-10 17:29:24","link":"https://www.sec.gov/Archives/edgar/data/1820190/000119312526151455/0001193125-26-151455-index.htm"}

{"formType":"NT 10-Q","filingDate":"2026-05-15 00:00:00","acceptedDate":"2026-05-15 16:06:21","link":"https://www.sec.gov/Archives/edgar/data/1820190/000119312526226675/0001193125-26-226675-index.htm"}

{"formType":"10-Q","filingDate":"2026-05-20 00:00:00","acceptedDate":"2026-05-20 17:22:39","link":"https://www.sec.gov/Archives/edgar/data/1820190/000119312526232857/0001193125-26-232857-index.htm"}

{"formType":"10-Q","filingDate":"2026-08-14 00:00:00","acceptedDate":"2026-08-14 16:41:44","link":"https://www.sec.gov/Archives/edgar/data/1820190/000119312526352464/0001193125-26-352464-index.htm"}

{"date":"2024-12-31","period":"FY","fiscalYear":"2024","acceptedDate":"2025-03-31 16:30:46"}

{"date":"2025-06-30","period":"Q2","fiscalYear":"2025","acceptedDate":"2025-08-13 16:09:50"}

{"date":"2025-09-30","period":"Q3","fiscalYear":"2025","acceptedDate":"2025-11-14 16:33:18"}

{"date":"2025-12-31","period":"FY","fiscalYear":"2025","acceptedDate":"2026-04-10 17:29:24"}

{"date":"2026-03-31","period":"Q1","fiscalYear":"2026","acceptedDate":"2026-05-20 17:22:39"}

{"date":"2026-06-30","period":"Q2","fiscalYear":"2026","acceptedDate":"2026-08-14 16:41:44"}

The linked FY2025 NT 10-K and Q1 FY2026 NT 10-Q state that Scilex needed additional time to finalize its financial statements, including consolidation of Vivasor Holding Company. This is the company's explanation in the public notices. The FMP responses supplied metadata and links, so the prompt output records the reason as not retrieved through FMP.

Prompt 2 Calculate lags and apply the rules

Use all three tables from Prompt 1. Table 1 establishes search completeness, Table 2 supplies the core records, and Table 3 supplies notices, exclusions and pending periods. Prompt 2 makes no additional FMP calls.

Objective

Using only Tables 1, 2 and 3 from Prompt 1, measure the filing lag of each

core filing, compare it with the previous filing of the same form, and

classify the overall direction of SCLX's acceptance lags. This screen does

not determine SEC compliance, does not measure predictability, and does

not explain any delay.

Step 1. Acceptance date

Use the calendar date of acceptedDate exactly as returned. Eastern time is an inferred convention for this

sample, not a documented FMP timezone. Keep filingDate in its own column; compare its date component. The date passes only

if (a) it equals the date component of filingDate, or the time is after

17:30 and filingDate is the next business day, accounting for U.S.

federal holidays, and (b) the time is between 05:00:00 and 19:59:59.

Otherwise mark the row "Review Required: date convention" and calculate

no lag for it. Never substitute filingDate.

Step 2. Filing lag and same-form change

Filing lag = acceptance date - period end, in calendar days.

Lag change = filing lag - filing lag of the previous core filing of the

same form. Never compare a 10-Q with a 10-K.

Direction: Slower if change >= +3; Stable if -2 to +2; Faster if <= -3;

Baseline for the oldest filing of each form; Review Required if either

lag is missing. Do not call a Slower row "late".

Step 3. NT and cause status for each core row

- "NT 10-Q identified" or "NT 10-K identified" if a notice from Table 3

maps to the row.

- "No NT identified (search complete)" if Table 1 shows the window was

fully read and no notice maps to the row.

- "NT search incomplete" if the window was not fully read.

- Cause status: "Company-stated reason not retrieved through FMP" when a

notice maps but its text was not returned; "Company-stated reason

retrieved" only if the text was returned; "Not applicable" otherwise.

Step 4. Overall result, in this order

1. Any core row Review Required, ambiguous NT mapping, or NT search incomplete: Review

Required. Stop.

2. At least two Slower comparisons, and either the latest 10-Q or the

latest 10-K is Slower or at least one notice maps to a core row:

Deteriorating.

3. At least two Faster, no Slower and no mapped notice: Improving.

4. No Slower and no mapped notice: Stable.

5. Otherwise: Mixed: deterioration signal present.

The +/-3-day threshold is an illustrative screening rule, not an SEC

deadline or materiality standard.

Step 5. Confidence and data or mapping exceptions

High only if six core filings are selected, each is matched by exact

timestamp, each passes Step 1, the window was fully read, and every notice is either associated without ambiguity or clearly

listed as awaiting a report. An awaiting-report notice is not a mapping

exception and does not count as a notice mapped to a core row. If all conditions pass, Data or mapping exceptions = None identified.

Otherwise confidence is Low, Data or mapping exceptions = Yes, and the

overall result is Review Required. A Slower row, a notice, a Deteriorating result or a reason not

retrieved does not by itself constitute a data or mapping exception.

Step 6. Follow-up action

- Deteriorating or Mixed: read the slower filings and any mapped

notices, and apply the same rules to the next 10-Q and 10-K.

- Stable or Improving: keep the lags as a baseline for the next filing.

- Any awaiting-report notice: monitor for the report and read the notice;

do not interpret its absence from completed-filing comparisons as

evidence that reporting timeliness is stable.

- Review Required: resolve the named row or search issue and rerun

Prompt 1.

Output

Table 4. Filing lags and same-form direction

Columns: Form | Fiscal period | acceptedDate (as returned) |

Date used | Timestamp check | Filing lag (days) | Prior same-form lag |

Lag change (days) | Direction | NT status | Cause status

Rows ordered by period end. For readability, display Table 4 as a

calculation table and a separate NT/cause-status table, retaining all

requested fields. Use Table 2 for the full timestamps and repeat them

only if needed for a date exception.

Table 5. Same-form summary

Mapped notices | Latest direction

Table 6. Overall result

Columns: Item | Result

Rows: Slower comparisons | Stable comparisons | Faster comparisons |

Mapped notices | Latest 10-Q direction | Latest 10-K direction |

Notices awaiting a report | Periods not yet reported at cutoff |

Gate | Overall result | Deciding rule |

Confidence in data and rule application | Data or mapping exceptions |

Follow-up action

Finish with no more than three sentences. Do not use "late",

"non-compliant", "fraud", "misconduct" or "unpredictable".

Scilex lag calculations and direction

All six core acceptance timestamps pass the date check. Two of the four comparisons are Slower, and both slower filings followed an NT notice. Table 4 shows the calculations and associated notice statuses; Table 2 contains the full timestamps.

Table 4. Filing lags and same-form direction

Form	Fiscal period	Acceptance date used	Lag, days	Prior same-form lag	Change, days	Direction
10-K	FY2024	2025-03-31	90	Not applicable	Not applicable	Baseline
10-Q	Q2 FY2025	2025-08-13	44	Not applicable	Not applicable	Baseline
10-Q	Q3 FY2025	2025-11-14	45	44	+1	Stable
10-K	FY2025	2026-04-10	100	90	+10	Slower
10-Q	Q1 FY2026	2026-05-20	50	45	+5	Slower
10-Q	Q2 FY2026	2026-08-14	45	50	−5	Faster

Fiscal period	Date check	NT status	Cause status through FMP
FY2024	Passed	No NT identified; search complete	Not applicable
Q2 FY2025	Passed	No NT identified; search complete	Not applicable
Q3 FY2025	Passed	No NT identified; search complete	Not applicable
FY2025	Passed	NT 10-K identified	Company-stated reason not retrieved through FMP
Q1 FY2026	Passed	NT 10-Q identified	Company-stated reason not retrieved through FMP
Q2 FY2026	Passed	No NT identified; search complete	Not applicable

The FY2025 10-K's returned acceptance time was 17:29:24, and its acceptance-date component and filing-date component are both April 10, 2026. Its lag is 100 calendar days from December 31, 2025. The prior annual lag was 90 days, producing the 10-day increase.

Table 5. Same-form summary

Form	Filings	Comparisons	Faster	Stable	Slower	Mapped notices	Latest direction
10-Q	4	3	1	1	1	1	Faster
10-K	2	1	0	0	1	1	Slower

The quarterly sequence moved Stable, Slower, Faster, with the lag returning to 45 days in Q2 FY2026. The annual direction rests on a single comparison, FY2025 against FY2024.

Table 6. Overall result

Item	Result
Slower comparisons	2: FY2025 10-K and Q1 FY2026 10-Q
Stable comparisons	1: Q3 FY2025 10-Q
Faster comparisons	1: Q2 FY2026 10-Q
Mapped notices	2: FY2025 NT 10-K and Q1 FY2026 NT 10-Q
Latest 10-Q direction	Faster
Latest 10-K direction	Slower
Notices awaiting a report	None
Periods not yet reported at cutoff	Q3 FY2026, ended September 30, 2026
Data and mapping gate	Passed
Overall result	Deteriorating under the illustrative rules
Deciding rule	Two Slower comparisons; latest 10-K Slower; two notices mapped to core rows
Confidence in data and rule application	High: six exact matches, all core date checks passed, main window fully read, both notices mapped
Data or mapping exceptions	None identified
Follow-up action	Read the FY2025 10-K and Q1 FY2026 10-Q with their notices; add the next 10-Q and 10-K using the same rules

The classification is Deteriorating because two comparisons were Slower and the latest annual report was Slower. The Q2 FY2026 10-Q was five days faster than Q1. High confidence describes the inputs and application of the screening rules; it does not establish an adverse cause or remove the need for analyst follow-up.

Reading the filing timeliness results

The Deteriorating result comes from two filings in spring 2026. The FY2025 10-K took 100 days against 90 the year before, and the Q1 FY2026 10-Q took 50 days against 45. Scilex filed an NT notice before each. The following 10-Q returned to 45 days without an identified notice, so the record shows a slower stretch around year-end and the quarter after it, not a steady lengthening across all six filings.

Sample selection also shapes the finding. Outside the selected four-quarter sample, the Q3 FY2024 10-Q was accepted on January 17, 2025, 109 days after its quarter-end, following the historical NT 10-Q in Table 3. That report is inside the main retrieval window but outside the selected core sample. An earlier cutoff could have selected it and produced a different comparison sequence.

The sample contains completed filings only. A period whose report has not arrived cannot contribute a completed lag, so this method can miss an emerging delay. Keep pending notices and elapsed periods without reports visible alongside the classification. Sequential quarterly comparisons also do not control for seasonality, weekends and holidays, or changes in filer status that alter deadlines. The Q3-to-Q1 comparison crosses the annual reporting cycle.

The next research step is to read the slower filings with their notices and follow the company's explanation through the statements. Amendments stay outside the original-filing lag series. A 10-K/A belongs in a separate review of how revisions and restatements flow through financial data, rather than replacing the original acceptance date in this screen.

When to resolve an exception before interpreting the screen

Return Review Required instead of a trend classification when a core filing lacks a unique period match, fails the date safeguard, duplicates another selected period, or leaves an unexpected quarterly gap. An incomplete main search or an incompatible or ambiguous notice association also blocks classification.

A clearly identified notice awaiting a report is different: it is a pending monitoring item, not a failed join. Likewise, a Slower comparison or a company-stated reason not retrieved through FMP does not itself constitute a data exception. These distinctions keep input quality separate from the analyst's assessment of the reporting pattern.

Monitoring filing timeliness across a coverage list

To adapt the workflow, change the symbol, cutoff and search windows, then confirm that the income-statement limits reach every selected filing. Companies with different fiscal year-ends, missing quarters or altered reporting status may require a longer retrieval window or additional mapping review. Keep the classification thresholds consistent if you intend to compare results across companies or over time.

Store the underlying records with each run. A post-earnings data refresh can add newly observed reports to the research process, while a repeatable API workflow can retain retrieval times, detect new accessions and flag incomplete searches. Acceptance time identifies the filing event; the retrieval log records when the data was actually observed through FMP.

For Scilex, the next observation is the Q3 FY2026 10-Q and any notice preceding it. Add that evidence before deciding whether the spring slowdown was temporary or part of a broader reporting pattern.

Tags:Model Builds

About the Author

Pranjal Saxena

Financial APIs, Claude MCP, and AI-driven research workflows

Pranjal Saxena writes technical content focused on financial data APIs, Claude MCP workflows, AI-driven research systems, and Python-based market analysis. For FMP, his work centers on turning structured financial data into practical, workflow-driven content for developers, analysts, and fintech teams. He combines experience in data science, NLP, generative AI, and financial API workflows to show how APIs, automation, and AI-assisted systems can support modern financial research and analysis.

View all articles

Data in Action