Elster - Software

For a decade, Elster was hailed as a triumph of e-government. Its software was free, secure, and ruthlessly efficient. The company’s engineers, many recruited from the same technical universities that fed Deutsche Bahn and Siemens, believed in a philosophy they called Perfektion durch Zwang (Perfection through Compulsion). If a user made a mistake, the software would not simply warn them—it would refuse to proceed. This was not a bug; it was a feature.

In the end, the most sophisticated tax software in Europe was undone by a simple truth: a plumber with a wet signature and a kind tax officer is infinitely more efficient than a flawless machine that says “no.” elster software

The lesson for modern engineers is uncomfortable. We are now building large language models and automated decision systems that promise to replace human judgment. Elster reminds us that the real world is fuzzy, contradictory, and full of exceptions. A system that is 99% precise but 0% tolerant is not a tool—it is a barrier. Elster did not fail because it was poorly coded. It failed because it succeeded in coding the law so perfectly that it forgot the law is, at its heart, a human institution meant to be interpreted, not executed. For a decade, Elster was hailed as a triumph of e-government

For professional tax advisors and large corporations—users who understood the system—Elster was a powerful tool. But for small business owners, freelancers, and ordinary citizens, it became a nightmare. The software’s refusal to accept “close enough” answers meant that a single misplaced decimal or a missing auxiliary form would freeze the entire submission. Unlike a human clerk, who could exercise discretion or request additional documentation, Elster offered only a cryptic error code: “Validation failed on field 42.3 (Betriebsausgaben).” If a user made a mistake, the software

Elster Software was dismantled in 2018, its assets nationalized and its team dispersed. But its ghost haunts every conversation about AI, automation, and governance today. Elster’s failure was a textbook case of Goodhart’s law applied to software: when a metric (strict schema validation) becomes the target, it ceases to be a good metric. By eliminating all ambiguity, Elster eliminated all discretion, and without discretion, a bureaucratic system cannot function.