Betterment settles SEC charges over automated tax-loss harvesting errors
Betterment settled SEC charges regarding misstatements and failures in its automated tax-loss-harvesting service. The company paid $9 million in penalties and provided restitution to 25,000 affected clients.
A coding error prevented the automated tax-loss harvesting service from functioning as advertised for over 25,000 accounts.
Key facts
- What
- Betterment settled SEC charges regarding misstatements and failures in its automated tax-loss-harvesting service.
- Incident date
- Apr 1, 2016
- Who
- Betterment
- Failure mode
- Agentic Action Error
- AI surface
- Chatbot
- Severity
- High
What happened
Betterment's automated tax-loss harvesting service failed to operate as advertised due to coding errors and undisclosed constraints. This resulted in more than 25,000 client accounts missing out on potential tax benefits. The company settled with the SEC, paying a $9 million penalty and providing restitution to affected clients.
What broke inside the model
- 01 · TriggerAn agent plans a multi-step task.
- 02 · Model stepIt chooses a wrong or destructive action.
- 03 · Control gapNo confirmation gate guards the write.
- 04 · FailureThe action commits to a system of record.
- 05 · ConsequenceData is changed or destroyed irreversibly.
A wrong action commits, and the step is written before anything can stop it.
A coding error in the automated tax-loss harvesting algorithm prevented the system from executing the service for certain accounts. This failure was coupled with undisclosed constraints that limited the functionality of the tool.
What it cost
Sources
Cite this entry
https://failureindex.ai/failures/betterment-settles-sec-charges-automated-taxAI Failure Index. "Betterment settles SEC charges over automated tax-loss harvesting errors" (FI-0223). Realm Labs. https://failureindex.ai/failures/betterment-settles-sec-charges-automated-tax (indexed Jun 5, 2026).Data fields CC-BY 4.0, prose citation permitted. Incident ID FI-0223. Full dataset at /data.
Note from Realm Labs, the Index steward
How Realm would have caught this
- Prism
- OmniGuard
- AgentRealm
Realm can sit inline on the agent's action path and require that a destructive or high-consequence action clears a real check before it executes, so 'delete and recreate' or a wrong write is stopped at the moment of intent, not explained in the post-mortem.