One filing undid eighteen months of statements

Non reliance is bigger than a wrong number

Most readers understand a restatement as one figure getting corrected. This disclosure is structural. It tells the market that a whole stretch of filings can no longer be treated as dependable in the form they were issued. A chart, an article, or a customer facing summary built from any of those five filings may now need review, even if it never touched the specific line item named in the disclosure.

That is a wider blast radius than a single number correction, and it calls for a different kind of check.

Watching the same error travel across five filings

We built a timeline of the disputed accounting treatment across all five filings. The same warrant and standby agreement treatment recurred, identically, in all of them. Checked at the time a filing actually went out, instead of eighteen months later, the issue would have surfaced on day one, not just at the end.

That continuity is the core of a monitoring pitch that actually means something. Waiting for an annual audit to catch a recurring error is a different promise than catching drift the same week a filing lands.

Keeping the company's own framing

Richtech states that the adjustments are largely non cash and expects no change to its operating cash position. A fair account of this case carries that framing forward rather than dropping it, because a system that treats a routine restatement as a crisis will lose credibility with the readers it is trying to serve. Merlise separates the fact of non reliance, which the 8-K supports directly, from the more sensitive claim about a prior material weakness not being fixed, which needs more careful handling.

The evidence ledger

The same claim by claim view the product shows on a live document, built from this case.

How it resolves

The resolving record