Zero-Human Compliance System Accountability Disputes Spain Theory .

ZERO-HUMAN COMPLIANCE SYSTEM ACCOUNTABILITY DISPUTES IN SPAIN: THEORY, LEGAL FRAMEWORK AND DETAILED EXPLANATION WITH CASE LAWS

1. Introduction

Zero-Human Compliance System Accountability Disputes refer to legal and regulatory conflicts arising when an organisation relies on automated systems, artificial intelligence (AI), algorithms, software applications, or digital monitoring technologies to perform compliance functions without meaningful human involvement.

These systems may automatically identify suspicious financial transactions, assess customer risk, monitor sanctions compliance, determine whether regulatory requirements have been satisfied, generate suspicious-activity alerts, block financial transactions, or recommend regulatory action.

The concept of a zero-human compliance system does not necessarily mean that an organisation has no employees. Rather, it describes a compliance arrangement in which important regulatory decisions are made or implemented automatically, with little or no meaningful human review, intervention, or accountability.

In Spain, this issue is particularly important in banking, financial services, insurance, anti-money laundering (AML), data protection, consumer protection, and financial supervision.

The central legal question is:

Who is legally responsible when an automated compliance system makes an incorrect decision, fails to identify a regulatory violation, unlawfully processes personal data, or causes financial loss?

Potentially responsible parties may include:

The regulated financial institution.

The company's board of directors.

Senior management.

The compliance officer.

The data controller.

The software or AI system provider.

The technology outsourcing provider.

Other persons responsible for designing, deploying, supervising, or maintaining the system.

Spanish law does not generally permit a regulated organisation to avoid its legal responsibilities merely because a computer system performed the relevant compliance function.

The organisation remains subject to applicable statutory obligations, supervisory requirements, data-protection rules, and judicial review.

2. Meaning and Concept of Zero-Human Compliance Systems

A zero-human compliance system is an automated arrangement in which regulatory compliance activities are carried out through technological processes without meaningful human participation in individual decisions.

Such systems may perform several functions.

2.1 Automated Customer Identification

Banks and financial institutions may use automated systems to verify customer identities through digital documents, biometric verification, electronic databases, and identity-checking software.

A dispute may arise if the system incorrectly rejects a genuine customer or accepts a fraudulent identity.

2.2 Automated Customer Risk Classification

Compliance software may automatically classify customers as low-risk, medium-risk, or high-risk.

The classification may depend on factors such as:

Customer identity.

Geographic location.

Transaction history.

Business activities.

Politically exposed person status.

Sanctions-related information.

Transaction patterns.

Source of funds.

An inaccurate classification may result in account restrictions, enhanced due diligence, or the termination of banking services.

2.3 Automated Transaction Monitoring

Automated monitoring systems analyse financial transactions to identify suspicious patterns.

They may detect:

Unusual transfers.

Repeated high-value transactions.

Structuring of deposits.

Unusual international payments.

Potential sanctions violations.

Transactions inconsistent with a customer's profile.

A dispute arises where the system produces false alerts, overlooks suspicious transactions, or automatically restricts legitimate payments.

2.4 Automated Regulatory Reporting

Some compliance systems automatically generate reports and regulatory notifications.

Errors may arise where the system:

Reports inaccurate information.

Fails to report suspicious transactions.

Uses outdated customer information.

Misclassifies a transaction.

Produces incomplete regulatory records.

2.5 Automated Sanctions Screening

Financial institutions may use automated databases to identify customers or transactions connected with sanctioned persons and entities.

Incorrect matches can result in the wrongful freezing or rejection of transactions.

Failure to identify a genuine sanctions match may also expose the institution to regulatory consequences.

3. Development of Automated Compliance and Accountability in Spain

The development of automated compliance accountability in Spain can be divided into several stages.

3.1 Traditional Human-Based Compliance

Historically, compliance activities were performed mainly by employees, legal departments, internal auditors, risk-management teams, and compliance officers.

The institution's responsibilities were relatively straightforward because identifiable individuals conducted customer verification, reviewed suspicious transactions, and approved compliance decisions.

However, traditional systems were expensive, time-consuming, and sometimes inconsistent.

3.2 Introduction of Computerised Compliance Systems

With the development of digital banking and electronic financial transactions, Spanish financial institutions increasingly adopted computerised monitoring systems.

These systems improved:

Transaction monitoring.

Customer identification.

Recordkeeping.

Regulatory reporting.

Fraud detection.

Internal audit processes.

Nevertheless, responsibility remained with the financial institution and its legally responsible management.

3.3 Artificial Intelligence and Automated Decision-Making

The development of machine learning and AI introduced more complex compliance systems.

Modern systems can analyse large datasets, identify unusual patterns, calculate risk scores, and generate recommendations.

Some systems also initiate decisions automatically, such as blocking transactions or restricting customer access.

This creates accountability problems because the reasoning behind certain automated outputs may be difficult to understand or reconstruct.

3.4 Current Regulatory Approach

Spanish institutions must comply with a combination of:

Spanish banking and financial legislation.

EU data-protection law.

EU artificial-intelligence regulation.

Anti-money laundering legislation.

Operational-resilience requirements.

Consumer-protection law.

Corporate governance and internal-control requirements.

The key principle is that automation may change how compliance is performed, but it does not automatically eliminate the legal responsibility of the institution.

4. Spanish Legal Framework Governing Automated Compliance Accountability

There is no single Spanish statute specifically entitled the Zero-Human Compliance System Accountability Act.

Instead, the legal framework is derived from several interconnected laws and regulations.

4.1 Spanish Constitution of 1978

The Spanish Constitution provides fundamental principles governing automated compliance decisions.

Article 9(3): Legal Certainty and Prohibition of Arbitrariness

Public authorities must act according to the law, and the legal system protects legal certainty and prohibits arbitrary public action.

Where public authorities rely on automated systems, their actions must remain legally justified and subject to appropriate accountability.

Article 14: Equality

Automated compliance systems must not produce unlawful discrimination.

A risk-scoring algorithm that systematically disadvantages customers because of protected characteristics may raise constitutional and statutory concerns.

Article 18: Privacy and Personal Data

Article 18 protects privacy, honour, personal and family life, and personal data within the constitutional framework.

Article 18(4) specifically provides for legal limitations on the use of information technology to protect personal and family privacy and the full exercise of individual rights.

This provision is particularly important where automated compliance systems process extensive customer information.

Article 24: Effective Judicial Protection

Individuals must have access to effective judicial protection when their legal rights and interests are affected.

Automated decisions cannot be treated as immune from judicial scrutiny.

4.2 General Data Protection Regulation (GDPR)

Regulation (EU) 2016/679 is one of the most important legal instruments governing automated compliance systems.

Relevant provisions include:

Article 5: Principles relating to personal-data processing.

Article 6: Lawfulness of processing.

Article 9: Special categories of personal data.

Article 13: Information to be provided where personal data are collected from the data subject.

Article 14: Information where personal data have not been obtained from the data subject.

Article 15: Right of access.

Article 22: Automated individual decision-making, including profiling.

Article 25: Data protection by design and by default.

Article 32: Security of processing.

Article 35: Data protection impact assessment.

Articles 77–82: Complaints, judicial remedies, and compensation.

Article 22: Automated Individual Decision-Making

Article 22 gives individuals the right not to be subject to a decision based solely on automated processing, including profiling, where that decision produces legal effects concerning them or similarly significantly affects them, subject to the exceptions provided by the GDPR.

The main exceptions concern decisions that:

Are necessary for entering into or performing a contract.

Are authorised by EU or Member State law that also provides suitable safeguards.

Are based on the individual's explicit consent.

Where an applicable exception is used, Article 22(3) requires appropriate safeguards, including at least the right to obtain human intervention from the controller, express one's point of view, and contest the decision, subject to the applicable legal conditions.

This is particularly important in banking where automated decisions may affect account access, credit applications, or other significant financial services.

However, not every automated compliance alert constitutes an Article 22 decision. The actual effect of the processing and the circumstances of the decision must be examined.

4.3 Spanish Organic Law 3/2018

Organic Law 3/2018 on Personal Data Protection and Guarantee of Digital Rights supplements the GDPR in Spain.

It provides national rules concerning personal-data protection and digital rights.

Its provisions are relevant to automated compliance systems where customer information is processed, stored, classified, or used to make decisions.

Spanish institutions must ensure that automated processing respects applicable transparency, lawfulness, security, and accountability requirements.

4.4 Law 10/2010 on the Prevention of Money Laundering and Terrorist Financing

Law 10/2010 establishes Spain's principal anti-money laundering and counter-terrorist financing framework.

Financial institutions and other regulated entities must implement appropriate measures concerning:

Customer due diligence.

Identification of beneficial owners.

Business relationship monitoring.

Transaction examination.

Suspicious transaction reporting.

Record retention.

Internal control procedures.

Risk assessment.

Automated AML systems may assist with these obligations.

However, an institution cannot ordinarily defend a failure to comply simply by arguing that its software failed to generate an alert.

The institution remains responsible for establishing and maintaining an effective compliance framework under the applicable legislation.

4.5 Law 10/2014 on the Organisation, Supervision and Solvency of Credit Institutions

Law 10/2014 establishes important requirements concerning the organisation, governance, solvency, and supervision of Spanish credit institutions.

It is relevant to automated compliance because banks must maintain suitable organisational structures, internal controls, and risk-management arrangements.

Where a bank uses automated compliance systems, its governance arrangements should address:

System reliability.

Internal accountability.

Risk management.

Compliance monitoring.

Outsourcing risks.

Internal audit.

Management oversight.

4.6 Royal Decree 84/2015

Royal Decree 84/2015 develops the regulatory framework under Law 10/2014.

It is relevant to the organisation and supervision of credit institutions, including governance and internal-control arrangements.

The use of automated systems must be integrated into the institution's overall regulatory and organisational responsibilities.

4.7 Digital Operational Resilience Act (DORA)

Regulation (EU) 2022/2554, known as the Digital Operational Resilience Act, became applicable on 17 January 2025.

DORA is particularly important for automated compliance systems used by financial institutions.

It establishes requirements concerning:

ICT risk management.

Digital operational resilience.

ICT-related incident reporting.

Digital operational resilience testing.

Management of ICT third-party risks.

Oversight of critical ICT third-party service providers.

Financial institutions cannot transfer their overall regulatory responsibility simply by outsourcing compliance technology to an external software provider.

DORA strengthens the requirements for managing technological risks and maintaining appropriate governance arrangements.

4.8 EU Artificial Intelligence Act

Regulation (EU) 2024/1689 establishes the European Union's harmonised rules on artificial intelligence.

It is directly relevant to financial institutions using AI-based compliance systems.

The regulation adopts a risk-based approach and establishes different obligations depending on the nature and intended purpose of the AI system.

Certain AI applications used in assessing the creditworthiness of natural persons or establishing their credit scores are classified as high-risk, subject to the applicable exceptions.

However, an AML monitoring system is not automatically classified as high-risk merely because it is used by a bank. Its classification depends on its intended purpose and the relevant provisions of the regulation.

Relevant AI Act requirements include:

Risk management.

Data governance.

Technical documentation.

Recordkeeping.

Transparency.

Human oversight.

Accuracy and robustness.

Cybersecurity.

The AI Act has phased application dates. Some provisions applied earlier, while the general application date is 2 August 2026, subject to the regulation's specific transitional provisions and subsequent amendments.

5. Theoretical Foundations of Zero-Human Compliance Accountability

The concept can be explained through several legal and governance theories.

5.1 Corporate Responsibility Theory

Under corporate responsibility theory, a legal entity remains responsible for ensuring that its business activities comply with applicable laws.

A company cannot ordinarily avoid its obligations by assigning regulatory functions to software.

For example, if a Spanish bank uses an automated AML monitoring system that fails to identify suspicious transactions, the bank may still face regulatory consequences if its compliance arrangements were inadequate.

The relevant question is whether the institution fulfilled its statutory and organisational obligations.

5.2 Agency Theory

Agency theory examines relationships between principals and agents.

In automated compliance, the financial institution acts as the principal, while software developers, technology providers, consultants, and outsourced service providers may perform functions on its behalf.

This creates potential accountability gaps.

For example:

The bank purchases an automated compliance system.

The technology provider designs the algorithm.

The system automatically classifies customers.

Employees rely on its outputs.

An incorrect classification causes financial harm.

The institution may attempt to attribute responsibility to the technology provider.

However, the allocation of contractual responsibilities does not necessarily remove the institution's regulatory duties.

5.3 Algorithmic Accountability Theory

Algorithmic accountability theory requires organisations to explain and justify the operation and consequences of automated decision-making systems.

The main principles include:

Transparency.

Explainability.

Auditability.

Accuracy.

Non-discrimination.

Human oversight where required.

Effective complaint and correction mechanisms.

The theory is particularly relevant where automated systems make decisions affecting customer rights.

5.4 Strict Regulatory Responsibility

Certain regulatory obligations are imposed directly on regulated institutions.

In these circumstances, responsibility may arise from the institution's failure to comply with the relevant legal duty, regardless of whether the failure was caused by an employee, software malfunction, or outsourced service provider.

This does not mean that every automated error automatically establishes liability. The applicable legal provision, breach, fault requirements, causation, and available defences must be examined.

5.5 Human Accountability Principle

The human accountability principle recognises that important legal and organisational responsibilities must remain attributable to identifiable persons or institutions.

Even where a compliance system operates automatically, the organisation should identify who is responsible for:

Approving its deployment.

Establishing compliance policies.

Monitoring performance.

Reviewing material errors.

Managing system failures.

Ensuring regulatory reporting.

Correcting unlawful decisions.

This principle is supported by the governance and accountability requirements found in European data-protection, banking, and AI legislation.

6. Main Types of Zero-Human Compliance Accountability Disputes

6.1 Incorrect Automated AML Classification

A bank's automated system may classify a legitimate customer as high-risk without adequate justification.

The bank may consequently request additional documentation, delay payments, restrict access to services, or terminate a relationship where legally permitted.

The customer may challenge the decision on grounds including inaccurate personal data, lack of transparency, disproportionate processing, discrimination, or failure to comply with applicable banking and consumer-protection requirements.

6.2 Failure to Detect Suspicious Transactions

An automated system may fail to identify transactions associated with money laundering or terrorist financing.

A regulatory dispute may arise where the institution's monitoring arrangements were inadequate or its failure to act violated applicable statutory obligations.

The institution may be investigated by the competent Spanish authorities.

6.3 Automated Account Freezing

A financial institution may automatically restrict an account after a sanctions alert or suspicious-transaction detection.

A dispute may arise if the alert is incorrect or the institution imposes restrictions without an adequate legal basis.

The institution must distinguish between restrictions required by law and discretionary risk-management measures.

6.4 Algorithmic Discrimination

An automated compliance system may disadvantage customers because of nationality, geographical origin, disability, or other protected characteristics.

A dispute may arise under equality, data-protection, consumer-protection, or anti-discrimination legislation.

The use of geographical or behavioural risk indicators is not automatically unlawful, but the processing must have an appropriate legal basis and comply with applicable equality and proportionality requirements.

6.5 Automated Credit and Financial Risk Decisions

Automated systems may determine whether a customer qualifies for credit or assign a risk score that materially influences the decision.

A customer may challenge the outcome where the system uses inaccurate data, produces discriminatory results, or makes a significant decision without complying with applicable legal requirements.

6.6 Outsourced Compliance Failures

A bank may rely on an external technology company to perform AML screening, identity verification, or regulatory monitoring.

A dispute may arise when the provider's software malfunctions or fails to perform the agreed compliance functions.

The institution's statutory duties remain relevant even where contractual responsibility is allocated to the provider.

7. Important Case Laws Relevant to Automated Compliance Accountability in Spain

There is no established body of Spanish case law specifically using the legal term "zero-human compliance system accountability disputes."

The following decisions are relevant by analogy because they address automated decision-making, data protection, algorithmic accountability, financial regulation, consumer protection, and the legal responsibilities of organisations.

Case 1: SCHUFA Holding (Scoring) – Case C-634/21 (2023)

Court: Court of Justice of the European Union.

Background:

The case concerned credit scoring by SCHUFA, a German credit information agency.

The agency calculated a creditworthiness score using automated processing. Financial institutions could rely heavily on that score when deciding whether to provide credit.

Legal issue:

Whether the automated creation of a credit score could constitute automated decision-making within the meaning of Article 22 GDPR.

Judgment:

The CJEU held that the automated establishment of a probability value concerning a person's ability to meet financial commitments may itself constitute a decision within Article 22 where a third party draws strongly on that score when establishing, implementing, or terminating a contractual relationship.

Importance for Spain:

This decision is highly relevant to Spanish banks using automated credit-scoring and risk-classification systems.

It demonstrates that an institution cannot necessarily avoid GDPR obligations by describing its algorithmic output as merely a recommendation when that output effectively determines the customer's treatment.

Case 2: OQ v Land Hessen (Case C-203/22, 2025)

Court: Court of Justice of the European Union.

Background:

The case concerned automated credit scoring and the rights of individuals whose personal information was processed to assess creditworthiness.

Legal issue:

The Court was asked to clarify the interpretation of GDPR Article 22 and the legal requirements applicable to automated credit-scoring arrangements.

Importance:

The decision forms part of the developing European jurisprudence on the legal significance of automated scores and the rights of individuals affected by algorithmic assessments.

Relevance for Spain:

Spanish financial institutions must consider the CJEU's interpretation of Article 22 when using automated creditworthiness and risk-assessment systems.

The precise legal consequences depend on the role played by the score in the final decision and the applicable GDPR safeguards.

Case 3: SCHUFA Holding (Insolvency Discharge) – Case C-26/22 and Case C-64/22 (2024)

Court: Court of Justice of the European Union.

Background:

The cases concerned the retention of personal information relating to insolvency discharges by a private credit information agency.

Legal issue:

Whether the retention of such information by a private credit information agency was compatible with GDPR requirements, particularly data minimisation and storage limitation.

Judgment:

The Court examined the legal basis and proportionality of retaining personal information concerning insolvency discharges and the relationship between private databases and official public information.

Importance for Spain:

The judgment is relevant to financial compliance systems that use external databases for customer risk assessments.

It demonstrates that the availability of personal information in a database does not automatically justify unlimited retention or use of that information.

Case 4: Google Spain SL and Google Inc. v Agencia Española de Protección de Datos and Mario Costeja González (Case C-131/12, 2014)

Court: Court of Justice of the European Union.

Background:

The dispute originated in Spain and concerned personal information appearing in search-engine results.

Legal issue:

Whether search-engine operators could be considered data controllers and whether individuals could request removal of certain search results under data-protection law.

Judgment:

The Court held that search-engine operators could be data controllers in relation to their processing of personal data and recognised a right to request removal of certain search results under the conditions established by EU law.

Importance for automated compliance:

The decision is relevant because automated compliance systems often collect and process information from external databases.

It demonstrates that organisations using automated data-processing systems may have independent data-controller responsibilities.

A financial institution cannot automatically avoid data-protection responsibility by claiming that information originated from a third-party database.

Case 5: Wirtschaftsakademie Schleswig-Holstein (Case C-210/16, 2018)

Court: Court of Justice of the European Union.

Background:

The case concerned the responsibility of a company operating a Facebook fan page and the processing of personal data through the platform.

Legal issue:

Whether an organisation could be a joint controller where it participated in determining the purposes and means of processing personal data, even though another organisation operated the underlying technology.

Judgment:

The CJEU recognised that joint controllership may arise where an organisation participates in determining the purposes and means of processing, even if it does not itself have direct access to all personal data.

Importance for Spain:

The case is relevant to financial institutions using outsourced compliance platforms.

A bank may have data-protection responsibilities even when a technology provider operates the system and controls the technical infrastructure.

Case 6: Fashion ID GmbH & Co. KG (Case C-40/17, 2019)

Court: Court of Justice of the European Union.

Background:

The dispute concerned the use of a third-party social media plugin on a commercial website and the resulting transfer of personal data.

Legal issue:

Whether a website operator could be a joint controller for certain personal-data processing operations carried out through a third-party plugin.

Judgment:

The Court held that joint controllership may exist in relation to the collection and transmission of personal data where the website operator participates in determining their purposes and means.

However, responsibility does not automatically extend to processing operations for which the organisation does not determine the purposes and means.

Importance for automated compliance:

The decision is useful when assessing the respective responsibilities of Spanish banks and external technology providers.

It shows that responsibility must be allocated according to the actual processing activities and the role played by each organisation.

Case 7: Nowak v Data Protection Commissioner (Case C-434/16, 2017)

Court: Court of Justice of the European Union.

Background:

The dispute concerned whether information contained in an examination script and examiner comments constituted personal data.

Legal issue:

Whether information connected with an individual's examination performance fell within the definition of personal data.

Judgment:

The Court adopted a broad interpretation of personal data and held that information concerning a person may qualify as personal data where it relates to that individual by reason of its content, purpose, or effect.

Importance for Spain:

Automated compliance systems may generate customer risk scores, behavioural profiles, and internal assessments.

Such information may constitute personal data and therefore be subject to GDPR rights and obligations.

Case 8: Peter Paul and Others v Germany (Case C-222/02, 2004)

Court: Court of Justice of the European Union.

Background:

Depositors sought compensation from public authorities following the failure of a bank and alleged inadequate banking supervision.

Legal issue:

Whether EU banking legislation required Member States to establish liability of supervisory authorities for alleged failures in prudential supervision.

Judgment:

The Court held that the relevant directives did not themselves require Member States to establish the particular compensation right claimed.

Importance for automated compliance:

The decision is relevant to the distinction between regulatory responsibility and private damages liability.

A compliance failure may lead to supervisory consequences without automatically establishing a customer's right to compensation. The relevant national and EU legal requirements must be examined.

Case 9: Banco Español de Crédito SA v Joaquín Calderón Camino (Case C-618/10, 2012)

Court: Court of Justice of the European Union.

Background:

The dispute concerned an unfair contractual term in a consumer credit agreement and the ability of national courts to examine unfair terms.

Legal issue:

Whether Spanish procedural rules were compatible with the consumer-protection requirements of Directive 93/13/EEC.

Judgment:

The CJEU held that national procedural rules must not undermine the effectiveness of EU consumer-protection law.

Importance for automated compliance:

The decision is relevant where banks use automated systems to enforce contractual terms, restrict services, or process consumer claims.

Automation cannot be used to avoid mandatory consumer-protection requirements.

Case 10: Aziz v Caixa d'Estalvis de Catalunya, Tarragona i Manresa (Case C-415/11, 2013)

Court: Court of Justice of the European Union.

Background:

The dispute concerned mortgage enforcement procedures in Spain and potentially unfair contractual terms.

Legal issue:

Whether Spanish mortgage enforcement procedures provided effective protection against unfair contractual terms.

Judgment:

The Court held that the Spanish procedural framework did not provide sufficiently effective protection in the circumstances examined.

Importance for automated compliance:

The judgment illustrates that financial institutions must operate within a framework of effective judicial protection.

Automated enforcement and compliance systems cannot remove the ability of customers to challenge unlawful contractual or financial decisions.

Case 11: Gutiérrez Naranjo and Others (Joined Cases C-154/15, C-307/15 and C-308/15, 2016)

Court: Court of Justice of the European Union.

Background:

The cases concerned unfair mortgage floor clauses in Spanish banking contracts.

Legal issue:

Whether the retrospective effects of declaring unfair contractual terms invalid could be restricted.

Judgment:

The Court held that the limitation of the retrospective effects of invalidity was incompatible with Directive 93/13/EEC.

Importance for automated compliance:

The case supports the principle that banks cannot rely on internal systems or standardised processes to avoid substantive consumer rights.

Where an automated system processes claims relating to unfair contractual terms, the bank must ensure that the applicable legal protections are respected.

Case 12: Orange România SA v Autoritatea Națională de Supraveghere a Prelucrării Datelor cu Caracter Personal (Case C-61/19, 2020)

Court: Court of Justice of the European Union.

Background:

The case concerned the validity of consent for personal-data processing in a commercial relationship.

Legal issue:

Whether consent could be regarded as freely given, specific, informed, and unambiguous where the relevant arrangements did not adequately demonstrate the individual's genuine agreement.

Judgment:

The Court clarified the requirements for valid consent under EU data-protection law and emphasised that the data controller must be able to demonstrate valid consent where it relies on consent as its legal basis.

Importance for Spain:

Spanish banks using automated onboarding, identity verification, or compliance platforms must ensure that consent is legally valid where consent is the chosen basis for processing.

8. Spanish Data Protection Authority and Automated Decision Accountability

The Spanish Data Protection Agency (Agencia Española de Protección de Datos or AEPD) plays an important role in enforcing data-protection requirements.

It investigates complaints concerning unlawful personal-data processing and may impose corrective measures and administrative penalties within its legal competence.

Its work is particularly relevant to automated compliance systems.

Potential issues include:

Lack of transparency concerning automated profiling.

Unlawful processing of customer data.

Excessive data retention.

Inaccurate risk profiles.

Failure to respect data-subject rights.

Inadequate security arrangements.

Failure to conduct a required data-protection impact assessment.

Failure to provide appropriate safeguards for significant automated decisions.

The AEPD's guidance and decisions should be considered alongside the GDPR, Organic Law 3/2018, and relevant CJEU jurisprudence.

9. Allocation of Legal Responsibility in Zero-Human Compliance Systems

One of the most difficult legal questions is identifying the person or organisation responsible for a compliance system failure.

9.1 Responsibility of the Financial Institution

The regulated institution is generally responsible for ensuring that its compliance framework satisfies the applicable legal requirements.

It must ensure that automated systems are appropriately selected, implemented, tested, monitored, and reviewed.

The use of external software does not automatically transfer the institution's regulatory responsibilities.

9.2 Responsibility of the Board of Directors

The board of directors is responsible for appropriate corporate governance and oversight within the applicable statutory framework.

It should ensure that the institution has adequate risk-management and internal-control arrangements.

Where an institution deploys a system that makes important decisions without appropriate controls, questions may arise concerning board oversight and governance.

9.3 Responsibility of Senior Management

Senior management must ensure that compliance arrangements operate effectively.

This may involve:

Approval of system policies.

Allocation of responsibilities.

Monitoring system performance.

Reviewing significant failures.

Ensuring adequate resources.

Escalating material compliance risks.

9.4 Responsibility of Compliance Officers

Compliance officers may have responsibilities under applicable law, internal policies, and employment arrangements.

However, their liability must be assessed individually.

A compliance officer is not automatically personally liable for every error produced by an automated system.

The relevant issues include the officer's legal duties, authority, knowledge, conduct, and involvement in the failure.

9.5 Responsibility of Software Providers

Technology providers may face contractual, civil, data-protection, or other legal responsibility depending on their role.

For example, a provider may be liable where:

The software fails to perform agreed functions.

The provider negligently designs or maintains the system.

The provider unlawfully processes personal data.

The provider breaches contractual security obligations.

The provider misrepresents the capabilities of the system.

The allocation of responsibility depends on the contract, applicable legislation, the provider's legal role, and the facts of the case.

10. Evidence Required in Automated Compliance Disputes

Evidence is particularly important because automated systems may produce decisions without easily understandable explanations.

The following records may be relevant:

System design documentation.

Algorithmic decision logs.

Customer risk-assessment records.

Transaction-monitoring alerts.

Internal compliance policies.

Human-review records.

Software testing results.

Data-protection impact assessments.

Vendor contracts.

System audit reports.

Records of model updates.

Incident reports.

Customer communications.

Regulatory notifications.

Board and management oversight records.

Under GDPR Article 5(2), the controller is responsible for and must be able to demonstrate compliance with the relevant data-protection principles.

Article 24 also requires controllers to implement appropriate technical and organisational measures and be able to demonstrate that processing complies with the GDPR.

These accountability requirements are important when a dispute concerns a system that operates with minimal human involvement.

11. Remedies Available to Individuals and Organisations in Spain

Individuals affected by automated compliance decisions may have several legal remedies.

11.1 Request for Information

An individual may exercise applicable GDPR rights to obtain information about personal-data processing.

Article 15 may provide access to personal data and meaningful information about relevant automated decision-making, including the logic involved and the significance and envisaged consequences of the processing, subject to the GDPR's conditions.

11.2 Request for Rectification

Under Article 16 GDPR, individuals may request correction of inaccurate personal data.

This is important where an automated compliance system uses incorrect customer information.

11.3 Request for Erasure

Article 17 GDPR provides a right to erasure in specified circumstances.

However, erasure is not absolute. Financial institutions may have legal obligations to retain certain records.

11.4 Objection to Processing

Article 21 GDPR provides a right to object in specified circumstances, including certain processing based on legitimate interests or public tasks.

The applicability of this right depends on the legal basis and nature of the processing.

11.5 Complaint to the AEPD

An individual may lodge a complaint with the Spanish Data Protection Agency where they believe that personal-data processing violates the GDPR or Spanish data-protection law.

11.6 Judicial Proceedings

Individuals may seek judicial remedies where an automated compliance decision violates contractual, statutory, constitutional, or data-protection rights.

Depending on the dispute, proceedings may be brought before the competent civil, administrative, employment, or other jurisdiction.

11.7 Compensation

Article 82 GDPR provides a right to compensation for material or non-material damage suffered as a result of an infringement of the GDPR, subject to the legal requirements.

A mere infringement does not automatically establish a right to compensation. The claimant must establish the relevant damage and causal connection under the applicable legal principles.

12. Hypothetical Examples of Zero-Human Compliance Disputes

Example 1: Incorrect AML Risk Classification

A Spanish bank uses an automated monitoring platform to classify customers according to money-laundering risk.

A customer is incorrectly classified as high-risk because the system associates the customer's name with another individual appearing in a sanctions database.

The bank automatically restricts the customer's transactions.

The customer challenges the decision.

Potential legal issues include:

Accuracy of personal data.

Lawfulness of processing.

Proportionality of the restriction.

Compliance with applicable sanctions requirements.

GDPR Article 22, if the decision falls within its scope.

Availability of meaningful review and correction procedures.

Example 2: Failure to Identify Suspicious Transactions

A bank's automated AML system fails to identify a series of suspicious international transfers.

A regulatory investigation later identifies deficiencies in the institution's transaction-monitoring arrangements.

Potential consequences include supervisory investigation, corrective measures, and administrative sanctions where the applicable legal requirements are satisfied.

The bank cannot automatically avoid responsibility by arguing that the software failed to generate an alert.

Example 3: Automated Rejection of a Credit Application

A financial institution rejects a customer's credit application solely on the basis of an automated risk score.

The customer believes that inaccurate information was used.

Potential legal issues include:

GDPR Article 22.

Accuracy under Article 5.

Access rights under Article 15.

Rectification under Article 16.

Consumer-protection requirements.

Applicable AI Act obligations where the system is within scope.

Example 4: Outsourced Compliance System Failure

A Spanish bank outsources its customer-screening operations to an international technology company.

The provider fails to update its sanctions database, resulting in inaccurate screening.

Potential legal issues include:

Contractual liability.

Data-protection obligations.

Outsourcing risk management.

DORA requirements.

Internal governance.

Regulatory responsibility of the bank.

13. The Relationship Between Zero-Human Compliance and the AI Act

The AI Act introduces an important regulatory dimension to automated compliance systems.

It does not impose the same requirements on every AI system.

Instead, its requirements depend on the system's classification and intended purpose.

13.1 High-Risk AI Systems

Certain AI systems used in assessing the creditworthiness of natural persons or establishing their credit scores are classified as high-risk under Annex III, subject to the specific exception concerning systems used to detect financial fraud.

Relevant requirements may include:

Risk-management systems.

Data governance.

Technical documentation.

Recordkeeping.

Transparency.

Human oversight.

Accuracy.

Robustness.

Cybersecurity.

13.2 Human Oversight

Article 14 of the AI Act requires appropriate human-oversight measures for high-risk AI systems.

The purpose is to reduce risks to health, safety, and fundamental rights.

Human oversight should be meaningful and appropriate to the system's risks.

It should not be reduced to a person mechanically approving every automated output without understanding or assessing it.

13.3 Accountability of Providers and Deployers

The AI Act distinguishes between providers and deployers.

Providers have obligations relating to the development and placing on the market of AI systems.

Deployers have obligations relating to the use and operation of those systems.

A Spanish bank using a third-party AI system may therefore have obligations as a deployer, even though it did not develop the technology.

14. Challenges in Establishing Accountability

Several difficulties arise in zero-human compliance disputes.

14.1 Lack of Transparency

Some AI systems use complex models that make it difficult to explain how a particular risk score was generated.

14.2 Responsibility Gaps

A bank may blame the software provider, while the provider may argue that the bank used the system incorrectly.

14.3 Inadequate Human Oversight

A system may technically include a human-review process, but the reviewer may lack sufficient authority, time, information, or expertise.

14.4 Inaccurate Data

An automated system may produce an incorrect result because its underlying information is outdated, incomplete, or inaccurate.

14.5 Discrimination

Automated systems may reproduce discriminatory patterns present in historical data or indirectly disadvantage certain groups.

14.6 Difficulties in Proving Causation

A customer may struggle to demonstrate that a particular algorithmic decision directly caused financial loss.

14.7 Cross-Border Outsourcing

A Spanish institution may use an AI or compliance provider established outside Spain, creating additional questions concerning applicable law, jurisdiction, data transfers, and regulatory cooperation.

15. Suggested Compliance and Accountability Framework for Spanish Financial Institutions

A responsible automated compliance system should incorporate the following safeguards.

1. Clear institutional responsibility

The institution should identify the departments and senior persons responsible for the system.

2. Human oversight

Important decisions should be subject to meaningful human intervention where required by law and appropriate to the risks.

3. Regular system testing

Systems should be tested for accuracy, reliability, discrimination, and operational weaknesses.

4. Audit trails

The institution should maintain records showing how decisions were generated and implemented.

5. Data accuracy

Customer information should be reviewed and corrected where necessary.

6. Explainability

The institution should be able to provide legally required explanations about relevant automated processing.

7. Vendor supervision

External technology providers should be assessed and monitored under appropriate contractual and regulatory arrangements.

8. Incident reporting

Material technology and compliance incidents should be identified, recorded, and reported where required.

9. Complaint mechanisms

Customers should have accessible procedures for challenging incorrect automated decisions.

10. Board-level oversight

The board and senior management should receive appropriate information about material compliance-system risks.

16. Future Development of Zero-Human Compliance Accountability in Spain

The legal treatment of automated compliance is likely to become more important as financial institutions increasingly use AI and advanced data analytics.

Future developments may include:

Greater regulatory scrutiny of automated AML monitoring.

Stronger AI governance requirements.

More detailed rules concerning algorithmic transparency.

Increased enforcement of GDPR Article 22.

Greater supervision of outsourced compliance technology.

More sophisticated digital operational-resilience requirements.

Development of case law concerning algorithmic discrimination.

Increased judicial scrutiny of automated account restrictions and credit decisions.

Spanish authorities will need to balance technological innovation with consumer protection, financial stability, privacy, and legal accountability.

17. Conclusion

Zero-Human Compliance System Accountability Disputes represent an important emerging area of Spanish financial and regulatory law.

The increasing use of AI, automated transaction monitoring, customer risk scoring, sanctions screening, and digital compliance platforms creates new questions concerning responsibility and legal accountability.

Spanish law does not generally allow financial institutions to escape their statutory obligations merely because compliance functions are performed by automated systems or external technology providers.

The Spanish Constitution, GDPR, Organic Law 3/2018, Law 10/2010, Law 10/2014, DORA, and the EU AI Act collectively establish a framework governing automated compliance activities.

The decisions in SCHUFA, Google Spain, Wirtschaftsakademie, Fashion ID, Peter Paul, Banco Español de Crédito, and Aziz provide important principles concerning automated decisions, personal-data accountability, financial responsibility, and consumer protection.

The central principle is that automation may perform compliance functions, but it does not automatically eliminate the legal responsibility of the organisation using the system.

A lawful and effective compliance framework must therefore combine technological efficiency with transparency, appropriate oversight, auditability, data accuracy, regulatory supervision, and effective remedies for affected individuals.

18. Principal Legal Authorities

A. Spanish Constitutional and National Legislation

Spanish Constitution of 1978, Articles 9(3), 14, 18, 24, 33 and 103.

Organic Law 3/2018 on Personal Data Protection and Guarantee of Digital Rights.

Law 10/2010 on the Prevention of Money Laundering and Terrorist Financing.

Law 10/2014 on the Organisation, Supervision and Solvency of Credit Institutions.

Royal Decree 84/2015 implementing Law 10/2014.

Law 29/1998 regulating the Administrative Jurisdiction.

Law 7/2020 for the Digital Transformation of the Financial System.

B. European Union Legislation

Regulation (EU) 2016/679 – General Data Protection Regulation.

Regulation (EU) 2022/2554 – Digital Operational Resilience Act.

Regulation (EU) 2024/1689 – Artificial Intelligence Act.

Directive (EU) 2015/2366 – Payment Services Directive 2.

Directive (EU) 2015/849 – Fourth Anti-Money Laundering Directive, as amended.

Directive (EU) 2013/36 – Capital Requirements Directive, as amended.

Regulation (EU) No. 575/2013 – Capital Requirements Regulation, as amended.

Directive 93/13/EEC – Unfair Terms in Consumer Contracts.

C. Important Judicial Decisions

SCHUFA Holding (Scoring), Case C-634/21 (2023).

OQ v Land Hessen, Case C-203/22 (2025).

SCHUFA Holding (Insolvency Discharge), Cases C-26/22 and C-64/22 (2024).

Google Spain, Case C-131/12 (2014).

Wirtschaftsakademie Schleswig-Holstein, Case C-210/16 (2018).

Fashion ID, Case C-40/17 (2019).

Nowak v Data Protection Commissioner, Case C-434/16 (2017).

Peter Paul and Others v Germany, Case C-222/02 (2004).

Banco Español de Crédito, Case C-618/10 (2012).

Aziz v Catalunyacaixa, Case C-415/11 (2013).

Gutiérrez Naranjo and Others, Joined Cases C-154/15, C-307/15 and C-308/15 (2016).

Orange România, Case C-61/19 (2020).

Final legal observation: The phrase "zero-human compliance system" is a theoretical and descriptive concept rather than a formally recognised category of Spanish statutory law. The legal analysis must therefore identify the actual activity involved, the relevant legal duty, the role of the institution and technology provider, the effect of the automated decision, and the available regulatory or judicial remedy. The cited CJEU decisions establish principles of EU law that apply in Spain, but they do not all concern Spanish financial institutions directly.

LawGratis provides pro bono legal aid and resources to empower communities. Join us in making justice reachable for everyone! Follow our community on Instagram, YouTube, Facebook, and LinkedIn.

LEAVE A COMMENT