Resources
How-to · The Kaleidoscope MCP Playbook

How to Screen for Item 4.02 Non-Reliance 8-Ks with AI

When a company tells the market its previously issued financial statements can no longer be relied on, it files an 8-K under Item 4.02. It's one of the highest-signal disclosures in the entire SEC taxonomy — and one of the easiest to screen for, once your AI client can query filings directly.

Why Item 4.02 matters

An Item 4.02 filing means the company — or its auditor — concluded that issued financials contain an error material enough that investors shouldn't rely on them. Restatements follow. So, often, do auditor changes, delayed filings, credit consequences, and litigation. For different desks it's a different alarm:

  • Accounting and audit teams read it as restatement risk materializing — and a map of which issues (revenue recognition, leases, controls) are surfacing across a sector.
  • Short sellers and distressed investors read it as an event catalyst with a well-studied drift.
  • Lawyers read it as the start of a disclosure record that will be picked apart later.

The related codes are worth knowing as a family: 4.01 (auditor change — often the precursor), 4.02 (non-reliance), and nearby distress signals like 2.06 (material impairment) and 1.03 (bankruptcy).

The old way

EDGAR full-text search will find the filings, but then the work starts: opening each 8-K, extracting the issue, checking whether a restatement followed, cross-referencing the auditor situation, and repeating weekly. It's exactly the kind of structured-but-tedious work that made this screening a specialist's job.

The prompt

With the Kaleidoscope SEC server connected to Claude, ChatGPT, or any MCP client, the screen is one sentence:

"Which companies filed non-reliance 8-Ks (Item 4.02) in the last quarter? For each, summarize the stated issue and note any auditor change, each fact cited."

Under the hood, the assistant composes the tools for you: screen_companies with eightk_item_in=['4.02'] to pull the universe, then get_sentences or semantic_search to retrieve the actual disclosure language, then get_company_profile for context on each name. Every line comes back cited to an accession number you can open.

Variations that earn their keep

  • The precursor screen: "Show companies that changed auditors (Item 4.01) in the last 90 days but haven't filed a 4.02" — the watchlist before the event.
  • The sector cut: "Item 4.02 filings in software (SIC 7372) over the past year — what accounting issues keep recurring?"
  • The full distress family: "Companies filing any of Items 1.03, 2.06, 4.01, or 4.02 in the last quarter, ranked by 8-K density" — one call, the whole red-flag taxonomy.
  • The language pull: "Show me the exact non-reliance language from this filing" — for the memo, verbatim and cited.

Why cited matters here more than anywhere

Non-reliance work ends up in front of committees, clients, and sometimes courts. A summary you can't trace is a liability. Because every answer carries its source filing, the verification step is one click — you're quoting the 8-K, not an AI's paraphrase of it. That's the difference between a screening shortcut and a professional workflow. (More for audit and advisory teams in MCP for accounting firms, and for deal and disclosure lawyers in MCP for law firms.)

Back to all Resources MCP for accounting firms

See it on your own questions

Request a demo and we'll show you cited, point-in-time answers from SEC & SEDAR filings — running in your own AI client.