This is a research prototype. The data and analyses are preliminary and not yet validated — we'd welcome your .
An Israeli farm challenged a tax fine generated by an opaque automated system that the Tax Authority could not explain. The case highlighted broader concerns regarding the lack of transparency, accountability, and public oversight in government-deployed automated decision-making systems, with the authority citing security concerns to avoid disclosing the underlying logic.
An Israeli farmer, Moshe Har Shemesh, reportedly received a fine generated by a Tax Authority software system whose calculation officials were allegedly unable to explain. When the farmer reportedly sought access to the program or its source code to understand the basis for the amount, the authority allegedly refused, citing security concerns and the difficulty of extracting the embedded guidelines. The dispute reportedly later moved into legal proceedings focused on whether code and automated decision rules constitute information subject to public disclosure.
Domain classification, causal taxonomy, severity scores, and national security assessments were LLM-classified and may contain errors.
Challenges in understanding or explaining the decision-making processes of AI systems, which can lead to mistrust, difficulty in enforcing compliance standards or holding relevant actors accountable for harms, and the inability to identify and correct errors.
Also classified as
The Tax Authority delegated administrative discretion to automated software without public discussion or human review of the specific calculations.
The software exhibited a biased calculation error in VAT recalculations, leading to a court-ordered compensation of 2 million shekels.
The core of the dispute is the Tax Authority's inability to explain the automated fine and its refusal to disclose the software's source code, preventing public oversight.
AI system
Due to a decision or action made by an AI system
Unintentional
Due to an unexpected outcome from pursuing a goal
Post-deployment
Occurring after the AI model has been trained and deployed
The incident was caused by the automated tax software's opaque calculations and biased VAT adjustments occurring after its deployment.
An opaque, automated tax system in Israel issued biased fines and VAT calculations, leading to legal challenges over algorithmic transparency. While the incident highlights significant issues in public sector AI governance, due process, and civil rights, its direct national security impact remains minor.
The report describes the software as being programmed to exercise administrative discretion independently, imposing fines, deducting tax returns, and applying financial sanctions without human intervention or oversight.
High Risk: The system is used by a public authority to make decisions on tax fines and financial sanctions, which has significant implications for fundamental rights, public interest, and civil oversight.
The software's primary function is to process tax data, calculate fines, deduct tax returns, and apply financial sanctions automatically.
The report provides clear, detailed accounts of the legal proceedings, the arguments of both the Tax Authority and the plaintiffs, and the specific algorithmic bias identified in the VAT calculations. There is minimal ambiguity regarding the core issues of transparency and automated decision-making.
None, as the facts of the legal challenge and the software's lack of transparency are undisputed.
Technology
Opaque Algorithmic Logic
The software calculated fines automatically without explaining the math.
Proprietary Executable Delivery
The software was provided as an .exe file, preventing code inspection.
Asymmetric Calculation Logic
Fines only adjusted when the consumer price index went up, not down.
Human Factors
Automation Bias
Tax officials relied entirely on the software output without verification.
Lack of Technical Literacy
Employees and the public could not interpret the underlying software code.
Process and Methods
Lack of System Documentation
No written guidelines existed for the automated calculation logic.
No Routine Code Auditing
No process was established to review and verify software decisions.
Inefficient Extraction Methods
Extracting guidelines required costly and complex reverse engineering.
Management
Delegation of Discretion
Management allowed software to replace human judgment without oversight.
IP Protection Prioritization
Management prioritized proprietary rights over public accountability.
Inadequate Risk Planning
Failed to assess transparency and security risks before deployment.
Regulatory Environment
Ambiguous Information Definition
Unclear legal framework on whether source code counts as public information.
Lack of Algorithmic Mandates
No laws requiring explainability for automated government decisions.
AI system involved
Identified by automated extraction; can differ from the alleged developers above.
