This audit covers six 8-Ks filed by INVO Fertility over the last twelve months; no 10-K, 10-Q, S-1, S-3, or DEF 14A filings were included in the dataset, which materially limits the depth of the review and should be flagged to your board. The single highest-severity signal is the Item 4.02 filing on June 2, 2026 (accession 0001493152-26-026772), which indicates non-reliance on previously issued financial statements — an item that outside risk desks universally treat as a Tier-1 flag. That 4.02 was filed contemporaneously (same morning, ten minutes apart) with an Item 2.02 earnings release (0001493152-26-026777), a sequencing choice sophisticated readers will notice and question. Separately, the April 29, 2026 Item 3.01 filing (0001493152-26-019593) signals a listing-standard deficiency, and its pairing with an Item 7.01 Reg FD disclosure in the same 8-K creates a 'buried' pattern our parser flagged in the buried_json field. The June 25, 2026 Item 1.01 (0001493152-26-030147) also carries a buried 2.01 completed-acquisition signal inside a material agreement item, which short-side readers will treat as under-labeled M&A disclosure. Overall posture is ELEVATED trending worsening within the window. Recommend the audit committee be walked through the 4.02 restatement scope and the 3.01 remediation plan before the next earnings call.
The combination of a Non-Reliance (4.02) filing, a listing deficiency (3.01), and two 8-Ks where item classification appears to under-label the underlying event puts your disclosure posture in the ELEVATED band. None of these signals is fatal in isolation, but the clustering within a roughly 60-day window is what outside readers will latch onto.
Trajectory: worsening — The 3.01 listing deficiency (April 29, 2026) was followed roughly five weeks later by the 4.02 non-reliance filing (June 2, 2026), and then by additional Reg FD and material agreement filings in June — the direction of travel within the window is toward more, not fewer, disclosure-sensitive events.
On June 2, 2026 you filed an 8-K carrying Item 4.02, which by definition indicates the company or its auditor has concluded previously issued financial statements should no longer be relied upon. This is the single most weighted item in most short-side disclosure taxonomies.
The Item 4.02 non-reliance 8-K (0001493152-26-026772) was filed at 08:30:27 on June 2, 2026, and an Item 2.02 results-of-operations 8-K (0001493152-26-026777) was filed at 08:40:33 the same morning. The sequencing means the restatement disclosure and the earnings release landed in the same pre-market window.
The April 29, 2026 8-K (0001493152-26-019593) carries Item 3.01, which reports notice of failure to satisfy a continued listing rule or standard. This is a named risk category in every short-side disclosure taxonomy and typically indicates minimum bid price, market cap, or stockholders' equity issues.
Our parser flagged (buried_json: {"7.01": ["3.01"]}) that the April 29, 2026 filing includes 3.01 content structurally nested under the 7.01 Reg FD section. The 3.01 is properly disclosed in filer_items, so this is a formatting observation rather than a failure-to-disclose finding, but the layout is atypical.
The June 25, 2026 8-K (0001493152-26-030147) is filed under Items 1.01 and 8.01, but our parser detected 2.01 (Completion of Acquisition or Disposition of Assets) language buried inside the 1.01 section and 3.01 language buried inside the 8.01 section (buried_json: {"1.01": ["2.01"], "8.01": ["3.01"]}). This may be a labeling choice, but under-labeling a completed acquisition as merely a material agreement is a recurring short-side flag.
You filed 7.01 Reg FD disclosures on April 29, 2026 (0001493152-26-019593) and June 16, 2026 (0001493152-26-028910). Two 7.01s in eight weeks is not unusual on its own, but combined with the 3.01 and 4.02 in the same window it contributes to a picture of elevated ad-hoc communication.
Item 2.02 results-of-operations 8-Ks were filed on June 2, 2026 (0001493152-26-026777) and June 22, 2026 (0001493152-26-029517). Two 2.02s in a 20-day window is unusual for a single reporting entity and suggests either a period-catch-up or a preliminary-then-final results cadence.
The following questions an analyst is most likely to raise on the next earnings call, with framing suggestions. Each is rooted in a specific filing in the audit window.
The Item 4.02 non-reliance filing sits squarely within audit committee territory and should be documented with a clear record of who identified the issue, when, and how the auditor was engaged on the conclusion. The Item 3.01 listing deficiency should be tracked on the same cadence as the restatement, since both share overlapping remediation dependencies (equity, controls, timely filing). The audit committee should also review the timing decision to file 4.02 and 2.02 within ten minutes on the same morning, and document the rationale in the minutes so it is defensible if later scrutinized. Finally, the committee should confirm whether the buried 2.01 language in the June 25 filing reflects a completed transaction that triggers 9.01 financial statement obligations.
Add the 4.02 restatement to the risk register with owners, target restatement filing dates, and interim disclosure controls. Add the 3.01 listing deficiency with the specific rule cited, the cure deadline, and the remediation option under active pursuit. Record in the minutes the reasoning for the June 2 filing sequencing and confirm audit committee awareness of the ten-minute gap. Document the internal review that led to the item classification choices on the June 25 8-K, particularly whether 2.01 was considered and rejected, and why. Preserve contemporaneous drafts of all six 8-Ks and the underlying counsel memoranda for the audit window.
The dataset contains no 10-K, 10-Q, S-1, S-3, 424B, DEF 14A, or Form 4 filings, so this audit surfaces no direct signals on going-concern language, ATM shelf utilization, dilution cadence, insider selling, executive compensation, or auditor changes — any of which could materially change the posture band. No Item 5.02 officer or director departure filings appeared in the window, and no Item 1.03 bankruptcy or receivership filings appeared. No Item 8.01 disclosures relating to reverse stock splits were detected, though this cannot be ruled out given the 3.01 context. The absence of these items is a data-coverage limitation, not an affirmative clean read.
The audit reviews only the six 8-K filings provided in the input dataset covering roughly April through June 2026. Signals are drawn from a standard disclosure-risk taxonomy that weights Item 4.02 (non-reliance), Item 3.01 (listing deficiency), Item 5.02 (officer/director changes), Item 1.03 (bankruptcy), and Item 4.01 (auditor change) as Tier-1 flags; item-labeling discrepancies and buried-item patterns are treated as Tier-2 structural flags. The severity band is assigned by combining Tier-1 flag count, clustering within the window, and structural labeling anomalies. This audit is filings-only and deliberately does not incorporate stock price, short interest, options activity, analyst notes, or third-party commentary. Because only one form type (8-K) was available, the audit cannot opine on periodic-report disclosure risk, dilution, or governance signals that would normally be surfaced from 10-K/10-Q, proxy, or Form 4 data.