Artifact GuideEU

EU GDPR penalties and fines

Article 83 sets maximum fine ceilings, not a tariff. The authority identifies the infringement, assesses its seriousness and the undertaking's turnover, applies aggravating or mitigating factors, checks the legal maximum, and tests the result for effectiveness, proportionality, and deterrence.

Use this guide to map the GDPR tier, CJEU fault condition, EDPB calculation steps, Article 58 corrective powers, and evidence for the individual case.

Author
Sorena AI
Published
May 9, 2026
Updated
Jul 25, 2026
Sections
8

Structured answer sets in this page tree.

Primary sources
5

Cited legal and guidance references.

Publication metadata
Sorena AI
Published May 9, 2026
Updated Jul 25, 2026
Overview

A GDPR cannot be predicted from the EUR 10 million or EUR 20 million headline alone. Article 83 sets two legal ceilings and case-specific factors. The EDPB's final Guidelines 04/2022 provide a five-step calculation method, while the CJEU requires an intentional or negligent infringement before an Article 83 fine may be imposed. Article 58 also allows non-monetary corrective measures that may be imposed instead of or alongside a fine.

Section 1

Article 83 fine tiers

First identify each infringement and the conduct from which it arises, then identify the applicable legal maximum. Article 83(4) covers several operational obligations, including controller and processor duties in Articles 8, 11, 25 to 39, certification duties, and monitoring-body duties. That tier can reach EUR 10,000,000, or for an undertaking, 2 percent of total worldwide annual turnover of the preceding financial year, whichever is higher.

Article 83(5) covers higher-tier infringements: basic processing principles and consent conditions, data-subject rights, international-transfer rules, certain Member State law obligations under Chapter IX, and non-compliance with Article 58 access, limitation, suspension, or order powers. Article 83(6) also puts non-compliance with a supervisory-authority order in the higher tier. The higher tier can reach EUR 20,000,000, or for an undertaking, 4 percent of total worldwide annual turnover of the preceding financial year, whichever is higher.

  • Treat EUR 10 million or 2 percent as the Article 83(4) maximum, not the starting fine.
  • Treat EUR 20 million or 4 percent as the Article 83(5) and 83(6) maximum, not the starting fine.
  • Where intentional or negligent conduct infringes several provisions in the same or linked processing operations, Article 83(3) says the total must not exceed the maximum for the gravest infringement. It does not erase the other infringements from the assessment.
  • Article 83(7) leaves room for Member States to decide whether and to what extent administrative fines apply to public authorities and bodies established in that Member State.
Section 2

Apply the EDPB five-step calculation method

The EDPB's final Guidelines 04/2022 explain a common calculation method for supervisory authorities. The Guidelines do not replace Article 83 or produce an automatic amount. The facts of the case and national procedural law still matter.

The method first identifies the processing operations and sanctionable conduct, including whether conduct gives rise to one or several infringements. It then selects a starting point using the nature of the infringement, its seriousness, and the undertaking's turnover. The authority adjusts for aggravating and mitigating circumstances, identifies the applicable legal maximum, and checks whether the resulting fine is effective, proportionate, and dissuasive.

  • Step 1 - conduct and infringements: identify the processing operations, the legal provisions infringed, and how the concurrence rules apply.
  • Step 2 - starting point: categorise the infringement, assess seriousness as low, medium, or high under the Guidelines, and account for the undertaking's turnover.
  • Step 3 - adjustment: apply the aggravating and mitigating circumstances supported by the case record.
  • Step 4 - legal maximum: check the applicable Article 83 ceiling and the undertaking concept where the percentage maximum applies.
  • Step 5 - final test: adjust if needed so the amount is effective, proportionate, and dissuasive in the individual case.
  • Planning limit: these steps organise an internal exposure assessment; they do not predict or bind the competent supervisory authority.
Section 3

Article 83 factors and the CJEU fault condition

Article 83(2) requires the supervisory authority to consider the circumstances of the individual case when deciding whether to impose a fine and when setting the amount.

In Deutsche Wohnen, C-807/21, the CJEU held that an Article 83 fine may be imposed only where it is established that the controller intentionally or negligently committed an infringement. A legal person can be fined directly as controller without first identifying an infringement by its management body. When the fine is imposed on a controller that forms part of an undertaking, the CJEU held that the percentage-based maximum is calculated using the turnover of the undertaking as a whole under the EU competition-law concept.

In ILVA, C-383/23, the CJEU distinguished the statutory maximum from the amount imposed in the individual case. Article 83(2) factors characterise the controller's or processor's conduct and the infringement, but the authority may also consider whether the addressee forms part of an undertaking when assessing its actual or material economic capacity and whether the amount is effective, proportionate, and dissuasive.

  • Document the nature, gravity, duration, processing purpose, number of affected data subjects, and level of damage.
  • Record the evidence relevant to whether the controller or processor knew, or could not be unaware, that its conduct risked infringing the GDPR. Do not treat a policy gap alone as proof of intent or negligence.
  • Keep mitigation evidence: containment steps, user-protection steps, remediation owners, completion dates, and proof that damage to data subjects was reduced where possible.
  • Show the degree of responsibility with Article 25 privacy-by-design records, Article 32 security measures, risk reviews, control tests, and decision approvals.
  • Record cooperation, notification route, affected data categories, prior Article 58 measures on the same subject matter, approved code or certification reliance, and any financial benefit gained or loss avoided.
Section 4

Article 58 powers before and beside fines

Do not treat an as the only enforcement result. Article 58 gives supervisory authorities investigative powers, corrective powers, and advisory or authorization powers. Article 83 says fines may be imposed in addition to, or instead of, several Article 58 corrective measures depending on the individual case.

For response planning, the most disruptive Article 58 outcomes may be non-monetary: an order to comply, a temporary or definitive processing limitation, a processing ban, an erasure or restriction order, a breach-communication order, or suspension of data flows.

  • Prepare for investigative powers: information requests, audits, certification reviews, alleged-infringement notices, access to personal data, and access to premises or processing equipment where procedural law allows.
  • Prepare for corrective powers: warnings, reprimands, orders to satisfy data-subject requests, orders to bring processing into compliance, breach-communication orders, processing limits or bans, erasure or restriction orders, certification withdrawal, fines, and data-flow suspension.
  • Track Article 58 orders as evidence inputs for Article 83 because repeat non-compliance with measures on the same subject matter is an assessment factor.
  • Route an Article 58 order or access request promptly to legal, privacy, security, and the accountable business owner. Record the response deadline, procedural route, and evidence owner instead of assuming every authority uses the same process.
Section 5

Accountability evidence that reduces uncertainty

The evidence file should prove the Article 83 factors, not merely assert compliance. Build it around the processing operation, the controller or processor role, the affected data categories, the specific infringement question, and the corrective steps taken.

The cited sources support accountability evidence for controllers and processors: Article 5(2) requires controllers to be able to demonstrate compliance, Article 24 requires appropriate technical and organisational measures that are reviewed and updated where necessary, Article 31 requires cooperation with supervisory authorities, and Article 83 applies administrative-fine tiers to controller and processor obligations where relevant.

Does every GDPR infringement automatically receive the maximum Article 83 fine?

No. Article 83 sets maximum ceilings, not fixed penalties. The authority assesses the individual case, and the EDPB method considers the conduct, seriousness, undertaking turnover, aggravating and mitigating factors, legal maximum, and whether the final amount is effective, proportionate, and dissuasive. The CJEU also requires an intentional or negligent infringement before an Article 83 fine may be imposed.

Can an Article 58 corrective order matter even before a fine is imposed?

Yes. Article 58 allows warnings, reprimands, compliance orders, processing limits or bans, erasure or restriction orders, breach-communication orders, certification withdrawal, fines, and suspension of data flows. Article 83 also treats compliance with earlier Article 58 measures on the same subject matter as a fine-assessment factor.

Does paying an settle every GDPR consequence?

No. Article 58 corrective measures can apply instead of or alongside a fine. Article 82 separately allows compensation for material or non-material damage caused by an infringement, subject to its conditions, and Article 84 requires Member States to lay down rules for other penalties. National procedure, appeals, and public-authority rules must be checked in the relevant Member State.

  • Keep ROPA entries, lawful-basis analysis, consent records where relevant, data-subject-right request logs, DPIAs or risk assessments, processor contracts, SCC or transfer files, security-control evidence, breach records, and supervisory-authority correspondence.
  • For processor-related exposure, keep the Article 28 contract or other legal act, controller instructions, sub-processor approvals, assistance records, breach escalation records, and evidence that processing stayed within the controller's documented instructions.
  • For breach-related exposure, keep the detection time, awareness assessment, risk assessment, notification decision, reasons for any delay, data-subject communication evidence, containment and recovery steps, and the documented breach-notification procedure.
  • For remediation, keep rejected alternatives, management approvals, control-test results, affected-service changes, customer or data-subject communications, and the owner who can show completion.
Section 6

Work a GDPR fine question from conduct to outcome

Use a conduct-level worksheet rather than multiplying the number of cited GDPR provisions by a headline maximum. For each processing operation, identify the controller or processor, the facts, the infringed provision, the Article 83 tier, the evidence of intent or negligence, the Article 83(2) factors, and any Article 58 measure already issued.

Concurrence matters. Article 83(3) caps the total fine for intentional or negligent infringements arising from the same or linked processing operations at the maximum for the gravest infringement. The EDPB method still requires the authority to identify all infringements and decide which conduct is separately sanctionable before applying that cap.

  • Worked case - Article 32 and delayed Article 33 notification: map the security failure and notification failure separately, then determine whether they arise from the same or linked processing operations. Both provisions sit in the Article 83(4) tier, but the authority still assesses duration, affected people, damage, responsibility, mitigation, notification, and cooperation.
  • Worked case - unlawful profiling plus rights failures: Article 5 or 6 and data-subject-right infringements sit in the Article 83(5) tier. Check Article 22 separately if a solely automated decision produces legal or similarly significant effects. Do not treat one upper-tier ceiling as proof that the maximum amount is appropriate.
  • Worked case - failure to obey an authority order: non-compliance with an Article 58(2) order falls under Article 83(6), using the higher ceiling. Preserve the order, service date, deadline, appeal or suspension status, response record, and evidence of what the organisation did after receipt.
  • Outcome record: state each established or disputed infringement, concurrence analysis, tier, turnover period and undertaking perimeter, Article 83(2) factors, fault evidence, corrective measures, compensation exposure, national penalties, and unresolved procedural questions.
Section 7

Definitions used in this GDPR penalties guide

: a monetary Article 58 corrective measure calculated under Article 83. It is case-specific, uses a legal ceiling rather than a tariff, and remains separate from compensation, national penalties, and non-monetary orders.

Supervisory authority: an independent Member State authority with Article 58 investigative and corrective powers. Cross-border cases require a separate competence and cooperation analysis rather than an assumption that one authority always acts alone.

Undertaking: the EU competition-law economic unit used for the percentage-based maximum and, where appropriate, the addressee's economic capacity. It can contain several legal persons, but it does not replace identification of the controller or processor that infringed the GDPR.

Controller: the person or body that determines the purposes and means of processing. A legal-person controller can be fined directly when its intentional or negligent infringement is established.

Processor: the person or body processing personal data on behalf of a controller. A processor has direct duties, but exposure must be mapped to the particular processor obligation and conduct.

Section 8

Separate fines, compensation, and national penalties

Article 83 administrative fines are one part of GDPR enforcement. Article 82 concerns compensation for material or non-material damage caused by an infringement. Article 84 requires Member States to provide rules for other penalties, especially for infringements not subject to Article 83 fines. Those routes have different conditions and should not be combined into one maximum-exposure number.

This page stays at the GDPR, final EDPB guidance, and cited CJEU judgment level. It does not determine national penalty procedures, criminal sanctions, public-authority exceptions, appeal deadlines, settlement procedures, or the outcome of a specific case. Check the law and supervisory-authority procedure in each relevant Member State.

  • Do not infer a Member State public-sector fine rule from Article 83(7) without a cited national source.
  • Do not assume every supervisory authority follows the same procedure, deadline, publication practice, or settlement process.
  • Do not use breach-notification timing as the only penalty clock; Article 83 assessment depends on the underlying infringement and the case-specific factors.
  • Do not substitute certifications, supplier answers, or policy statements for evidence of actual technical and organisational measures.
  • Do not treat an Article 83 fine ceiling as a cap on Article 82 compensation or on separate national penalties under Article 84.
Primary sources

References and citations

eur-lex.europa.eu
Referenced sections
  • Supports the distinction between the statutory maximum and case-specific amount and the role of undertaking-level economic capacity.
eur-lex.europa.eu
Referenced sections
  • Articles 82 to 84 separate compensation, administrative fines, Member State public-authority choices, procedural safeguards, and other national penalties.
"appropriate procedural safeguards"
ec.europa.eu
Referenced sections
  • Referenced in the source support as the breach-notification guidance endorsed by the EDPB; supports breach documentation and delayed-notification evidence for fine exposure.
"Personal data breach notification"
Related guides

Explore more topics

Does the EU GDPR apply outside the EU under Article 3?
A GDPR Article 3 territorial-scope FAQ covering EU establishment, non-EU targeting, monitoring in the EU, public-international-law cases, and Article 27 representatives.
EU GDPR Applicability Test for Products, Vendors, and Data Flows
A concrete GDPR scope test for personal data, controller and processor roles, EU establishment, EU targeting or monitoring, special-category and child data, transfers, vendors, and evidence.
EU GDPR Article 30 RoPA Intake Workflow
This GDPR Article 30 RoPA intake workflow helps capture controller and processor fields, owners, transfers, retention, security measures, and evidence before a processing activity goes live.
EU GDPR Article 6 Legal Bases FAQ
FAQ on the six Article 6 GDPR lawful bases, consent caveats, legitimate interests, public-task and legal-obligation limits, and Article 9 special-category data.
EU GDPR Automated Decision-Making and Profiling: Article 22 Scope, Safeguards, and Evidence
GDPR guide to profiling and Article 22 decisions: scope, transparency, lawful basis, DPIA triggers, safeguards, human intervention, challenge rights, and evidence.
EU GDPR Breach Notification 72 Hours: Article 33 and 34 workflow
Official source EU GDPR breach notification workflow covering awareness, 72-hour supervisory authority notices, processor escalation, high-risk data-subject communication, delay reasons, and evidence logs.
EU GDPR Breach Notification Workflow: 72-hour clock, risk assessment, and records
A concrete EU GDPR breach notification workflow for detecting and triaging incidents, starting the awareness clock, assessing risk, notifying authorities or data subjects, and keeping Article 33 records.
EU GDPR Checklist: scope, lawful basis, DSARs, DPIA, RoPA, transfers
This GDPR checklist helps review scope, lawful basis, notices, DSAR handling, DPIAs, RoPA, processor contracts, SCC transfers, breach notification, retention, security, and evidence.
EU GDPR Children and Special-Category Data Guide
GDPR guide to children's consent and special-category data: Article 8 national age variation, Article 9 conditions, transparency, DPIA triggers, safeguards, and evidence.
EU GDPR Compliance Checklist: scope, rights, DPIA, RoPA, transfers
Practical EU GDPR compliance guide for mapping scope, lawful basis, notices, data-subject rights, DPIAs, RoPA, processor terms, breaches, transfers, retention, security, and penalties.
EU GDPR Controller, Processor, and Joint Controller Roles
Classify GDPR controllers, processors, and joint controllers from actual decision-making, then document Article 26 allocation, Article 28 terms, instructions, and vendor evidence.
EU GDPR Data Subject Rights and DSAR Workflow
GDPR rights-request workflow for intake, identity checks, request scope, the one-month response clock, extensions, refusals, processor coordination, and evidence.
EU GDPR deadlines and compliance calendar
EU GDPR calendar for calculating rights-request deadlines, breach notification, DPIA and prior-consultation gates, transfer reviews, and retention checks.
EU GDPR DPIA and Prior Consultation Workflow
Screen high-risk processing, run a GDPR Article 35 DPIA, record mitigation, and identify when Article 36 prior consultation is required.
EU GDPR DPIA and risk management under Articles 35 and 36
EU GDPR DPIA guide covering Article 35 triggers and contents, CNIL and DPC PIA methods, residual risk, mitigation records, and prior consultation limits.
EU GDPR DSAR Exceptions: refusal, extensions, identity checks
FAQ on when EU GDPR controllers may extend, charge for, narrow, redact, or refuse a data subject access request under Articles 12 and 15.
EU GDPR DSAR Workflow: Intake, Clock, Rights, and Evidence
Run a GDPR DSAR workflow for intake, identity checks, rights scoping, one-month response timing, extensions, refusals, processor handoffs, and evidence records.
EU GDPR FAQ: scope, lawful basis, rights, DPIA, breaches, transfers
Direct EU GDPR FAQ answers on scope, controller and processor roles, lawful basis, data subject rights, DPIAs, breach notification, international transfers, and Article 83 fine tiers.
EU GDPR International Transfers and SCCs: Chapter V evidence guide
GDPR Chapter V guide to adequacy decisions, SCCs, transfer assessments, supplementary measures, Article 49 derogations, and EU-US DPF checks.
EU GDPR Lawful Basis and Consent Guide
Focused GDPR guide to Article 6 lawful bases, consent conditions, legitimate interests, special category data, withdrawal, and evidence records.
EU GDPR Lawful Basis and LIA Workflow for Article 6(1)(f)
Assess GDPR legitimate interests with a purpose, necessity, balancing, Article 21 objection, and evidence-record workflow based on Article 6(1)(f).
EU GDPR Lead Supervisory Authority and One-Stop-Shop
How GDPR main establishment, cross-border processing, Article 56 lead authority competence, and Article 60 cooperation fit together.
EU GDPR LIA Template for Article 6(1)(f)
This EU GDPR legitimate interests assessment template helps document Article 6(1)(f) purpose, necessity, balancing, safeguards, objection rights, and evidence.
EU GDPR Processor Contracts and Vendor Management | Article 28 Evidence Guide
EU GDPR Article 28 guide for processor contracts, sub-processor controls, controller-processor role boundaries, vendor evidence, and SCC transfer clauses where applicable.
EU GDPR Record of Processing Activities Template: Article 30 RoPA Fields
Build a GDPR Article 30 record of processing activities with separate controller and processor fields for purposes, data categories, recipients, transfers, erasure time limits, and security measures.
EU GDPR Requirements: scope, rights, security, DPIA, RoPA, and transfers
Overview of core EU GDPR requirements covering scope, principles, lawful basis, notices, data-subject rights, processors, RoPA, security, breaches, DPIAs, and international transfers.
EU GDPR Retention and Erasure Schedule
Build an EU GDPR retention and erasure schedule with purpose-based periods, expiry actions, Article 17 decisions, recipient notices, and deletion evidence.
EU GDPR SCC Transfer Impact Assessment FAQ
FAQ on when SCC transfer impact assessments are needed, what Clause 14 records, and when supplementary safeguards or transfer suspension are required.
EU GDPR Transfer TIA and SCC Workflow
A GDPR workflow for checking adequacy, selecting SCC modules, documenting transfer impact assessments, and recording supplementary measures for third-country transfers.
EU GDPR Transparency Notices: Articles 12, 13 and 14
GDPR privacy-notice guide for Articles 12, 13, and 14: direct collection, other data sources, purposes, lawful bases, recipients, transfers, retention, rights, and timing.
EU GDPR vs Brazil LGPD: scope, legal bases, rights, incidents, and transfers
Compare EU GDPR and Brazil LGPD scope, actors, legal bases, rights timing, security incidents, international transfers, evidence, regulators, and penalties.
EU GDPR vs California CCPA: scope, rights, opt-outs, and evidence
Compare EU GDPR and California CCPA scope, roles, consumer rights, response times, sale and sharing opt-outs, risk assessments, contracts, transfers, and enforcement.
EU GDPR vs ePrivacy Directive: personal data, cookies, consent, and communications
Compare the EU GDPR and ePrivacy Directive for personal data processing, consent and lawful basis, cookies and terminal access, electronic communications, and parallel compliance.
EU GDPR vs UK GDPR: Scope, Rights, Transfers, and Evidence
Compare the EU GDPR and amended UK GDPR across scope, rights, automated decisions, accountability, breaches, regulators, and international transfers.
GDPR processor vs controller: role boundaries and evidence
Decide whether a party is a GDPR controller, processor, or joint controller using purpose-and-means tests, Article 28 terms, Article 26 arrangements, and Article 30 records.
GDPR vs EU AI Act: privacy controls for AI systems
Map the GDPR work that remains necessary when an AI system processes personal data, including lawful basis, notices, DPIAs, Article 22, rights, security, records, and transfers.
GDPR vs EU Data Act: personal data, connected products, and access rights
Compare GDPR privacy duties with EU Data Act rights and duties for connected-product data, third-party access, data holders, users, contracts, cloud switching, and enforcement.
When does the EU GDPR require a DPIA?
Answer the EU GDPR DPIA threshold question with Article 35 triggers, high-risk criteria, supervisory-authority list checks, and DPIA content requirements.
When does the GDPR 72-hour breach notification clock start?
GDPR breach-awareness FAQ covering the Article 33 clock, processor escalation, delayed or phased notifications, risk assessment, and records to keep.