Datavault AI's Bitcoin Accounting Error Wipes 50% Off Its Stock
On October 28, 2026, shares of Datavault AI Inc. (DVLT) collapsed nearly 50% in a single trading session after the company told the Securities and Exchange Commission it had misclassified a large block of bitcoin received under a $150 million securities deal. The fallout includes multi-period financial restatements, a going-concern reassessment, and an unresolved inability to withdraw the bitcoin at the centre of the dispute. For accounting firms and CFOs advising companies that hold or receive digital assets, this case is an immediate reference point on what inadequate crypto accounting controls can cost.
What the Deal Actually Involved
In September 2025, Datavault AI entered a securities purchase agreement with Scilex Holding Co. Under the terms, Scilex agreed to acquire 15 million shares of Datavault AI common stock, plus a pre-funded warrant covering more than 263.9 million additional shares, for a total consideration of $150 million — payable entirely in bitcoin. The implied rate was approximately $112,915.52 per BTC, meaning roughly 1,328.43 BTC changed hands.
How the bitcoin moved
The bitcoin was credited to a Datavault AI digital wallet held at Biconomy Pte. Ltd. via an off-chain transfer. Between September 2025 and January 2026, Datavault AI sold a portion of those credited coins back to Scilex for approximately $40.5 million in cash. The company appears to have treated the remaining bitcoin balance as a liquid asset on its books throughout this period.
The withdrawal problem
In June 2026, Datavault AI attempted to move bitcoin from the Biconomy wallet to an external account. As of October 26, 2026 — the date of the SEC filing — that withdrawal had not been completed. The company provided no explanation in the filing for why it remains blocked. The unresolved withdrawal is now central to the going-concern question, because those balances were previously counted as available liquidity.
The Accounting Error at the Core
This is where the story becomes directly instructive for practitioners. Datavault AI has now determined that the bitcoin received from Scilex did not qualify for recognition as an asset on its balance sheet. Under US GAAP, when a company receives consideration for an equity issuance that has not yet been fully paid or is subject to collectability risk, the amount is treated as a subscription receivable — not a cash or asset equivalent. A subscription receivable is presented as a reduction of stockholders' equity, not as an asset line.
Why the distinction is material
Recording bitcoin as an asset inflated Datavault AI's reported asset base across multiple reporting periods. Treating it instead as a contra-equity item deflates total assets and can simultaneously change a company's liquidity picture, its debt covenant compliance, and any going-concern assessment that relied on those balances. The SEC has long taken the position that subscription receivables from related or concentrated counterparties should not be presented as assets precisely because collection is not assured.
Restatement scope and quantum
The company has disclosed the expected asset reductions from restating the affected periods:
| Period end | Expected reduction in total assets |
|---|---|
| 30 September 2025 | $8.1 million |
| 31 December 2025 | $92.2 million |
| 31 March 2026 | $57.1 million |
| 30 June 2026 | $49.0 million |
The peak restatement impact of $92.2 million at year-end 2025 reflects the full uncollected bitcoin balance before any partial disposals were recognised. The figures decline in later periods as the company had sold a portion back to Scilex for cash. Timing of the restated filings has not yet been determined.
Going-Concern Implications
Management has stated it is reassessing its going-concern evaluation. Two factors drive this. First, the company previously counted bitcoin credited to the Biconomy wallet as a source of liquidity; that balance can no longer be treated as accessible given the unresolved withdrawal situation. Second, collection of the remaining amounts owed by Scilex is described as uncertain, meaning the subscription receivable itself may require an allowance or write-down.
Under ASC 205-40, management must evaluate whether substantial doubt about the entity's ability to continue as a going concern exists within twelve months of the financial statement date. If restated figures remove a significant portion of reported liquid assets, and the replacement receivable is of doubtful collectability, auditors will need clear evidence of alternative liquidity before issuing an unmodified opinion. Firms advising DVLT or similar clients should be stress-testing these scenarios now, not after the restatement is filed.
Market Reaction and SEC Exposure
Trading data
DVLT closed at approximately $0.067 on October 28, down 49.6% from its prior-day close of $0.133. Volume reached nearly 250 million shares — roughly eight times the previous session's turnover. That surge in volume alongside a collapse in price signals the market treated the disclosure as a fundamental, not a technical, event.
Regulatory exposure
The SEC filing itself is a non-reliance disclosure — effectively a public statement that prior financial statements should not be trusted. These disclosures carry significant regulatory attention. The SEC's Division of Corporation Finance and its Office of the Chief Accountant have historically scrutinised companies that file non-reliance notifications, particularly where digital assets are involved, and especially where the error benefits management's reported liquidity position. Enforcement interest cannot be ruled out.
The wider context matters here too. Regulators in the US have been tightening expectations around how public companies account for digital asset transactions, and this case arrives as Congress is actively debating frameworks for digital asset disclosures. Firms advising public-company clients on crypto transactions should treat this as a signal that the SEC will not accept loose asset classification practices as a learning-curve allowance.
What This Means for Accounting Firms and CFOs
The Datavault AI situation exposes three distinct control gaps that practitioners should audit against right now.
Classification controls for crypto received as equity consideration
Any time a company receives digital assets as payment for shares, warrants, or other equity instruments, the first question is collectability and control. Is the crypto actually in the company's custody? Is the counterparty's obligation fully discharged? If the answer to either question is no, the asset recognition test under US GAAP is not met. Robust digital asset accounting software should flag transactions structured as off-chain credits from a third-party custodian as requiring enhanced review before they are posted as assets.
This is precisely the kind of nuanced classification that generic bookkeeping tools miss. The value of purpose-built crypto bookkeeping software lies in its ability to map transaction structures — off-chain credits, custodial arrangements, exchange-held wallets — against the relevant recognition criteria, rather than simply ingesting a balance and posting it.
Custodial and withdrawal risk
The inability to withdraw bitcoin from the Biconomy wallet after more than four months of trying is a separate but compounding problem. Any company holding material bitcoin balances on a third-party exchange or custodian should have documented withdrawal testing as part of its internal controls. The fact that DVLT apparently had no such control — or that the control failed silently — meant the liquidity problem was invisible until it became critical. Auditors should now be asking clients to demonstrate live withdrawal capability for any material crypto balance held off-platform.
Going-concern disclosures and liquidity forecasting
Companies that include digital asset balances in their liquidity analysis need to be certain those balances are accessible and realisable. Balances subject to counterparty risk, withdrawal restrictions, or collectability uncertainty should not appear in the twelve-month liquidity horizon without disclosure of those constraints. The going-concern reassessment here could have been avoided — or at least managed proactively — if the liquidity forecast had ring-fenced restricted or uncertain crypto balances from the outset.
Understanding how digital asset accounting software handles equity-linked crypto transactions is increasingly a baseline competency for any firm with public-company digital asset clients. As noted in our coverage of recent IASB standard-setting on provisions and obligations, the intersection of balance sheet recognition and uncertain future outflows (or inflows) is an area where standard-setters are actively sharpening requirements. The same rigour applies on the US GAAP side.
Separately, the broader regulatory environment — illustrated by the Senate's scrutiny of crypto payment arrangements involving related parties — underscores that transactions where digital assets flow between a public company and a significant counterparty will attract official attention, especially when financial restatements follow.
Frequently Asked Questions
Why couldn't Datavault AI record the bitcoin as an asset?
Under US GAAP, an asset must be recognised only when the company controls the resource and collection or receipt is probable. Bitcoin credited to a third-party custodian wallet via an off-chain transfer — where the counterparty's payment obligation may not be fully discharged — raises both control and collectability questions. The SEC's longstanding position is that subscription receivables from equity issuances should be presented as a reduction of stockholders' equity, not as assets, particularly where collection is not assured.
What is a subscription receivable and how does it differ from an asset?
A subscription receivable represents amounts owed to the company by shareholders in exchange for shares already issued. Under SEC guidance, this amount sits on the equity side of the balance sheet as a contra-equity item — reducing total stockholders' equity — rather than increasing total assets. The practical effect is a lower reported asset base and, in cases where management relied on that balance for liquidity, a reduced ability to demonstrate going-concern viability.
What triggers a going-concern reassessment?
Under ASC 205-40, management must evaluate whether substantial doubt exists about the company's ability to continue operating within twelve months of the reporting date. When a restatement removes a significant liquid asset from the balance sheet, or when a previously counted liquidity source turns out to be inaccessible — as with the blocked Biconomy withdrawal here — auditors and management are required to revisit whether the going-concern thresholds are breached and to disclose that reassessment to investors.
What should auditors check when a client holds crypto on a third-party exchange?
Auditors should obtain direct confirmation from the custodian of the balance held, test withdrawal capability by requesting evidence of a successful test withdrawal or reviewing recent withdrawal history, assess any terms of service restrictions that could prevent access, and evaluate whether the balance meets the control criteria for asset recognition. Where the exchange is offshore or lightly regulated, enhanced procedures — including review of the custodian's own financial health — are warranted.
How does this case affect other public companies holding bitcoin?
Companies that hold bitcoin acquired through straightforward market purchases and held in their own wallets or with regulated custodians are generally less exposed to this specific classification error. The risk is concentrated in transactions where crypto is received as consideration for equity, debt, or services from a single counterparty, held at a third-party platform, or subject to any form of restriction on withdrawal. CFOs should review all such arrangements against the subscription receivable guidance and document the rationale for any asset-side classification.
Source: The Block