Customer asks a client for compensation over an AI tool: GDPR Article 82 claim sheet with reply-by dates for accountants and their SME clients (damage, security proof, AI supplier recourse, C-300/21, C-340/21, C-667/21)
What you get: a finished compensation claim sheet for accountants, tax advisers and bookkeepers whose small business clients receive a letter from a customer, patient, applicant or employee asking for money over an AI tool (a chatbot log kept too long, a leaked call recording, a CV tool used without notice, wrong data from an AI invoice or payslip reader). One row per claim: type in fourteen short answers and the sheet returns the reply-by date, the days left, a result (ASK WHAT DAMAGE WAS SUFFERED, GATHER SECURITY EVIDENCE FIRST, PREPARE REPLY AND NOTIFY AI SUPPLIER, PROCESSOR: CHECK ART 82(2) DUTIES, PROCESSOR EXPOSED, COURT CLAIM: GET A LAWYER NOW, PREPARE REPLY or CLOSED) and a to-do list citing GDPR Article 82 and the three Court of Justice judgments behind each step. Also included: a checklist for the first read of the claim, a holding reply, a notice to the AI supplier and a client email. Formulas tested in LibreOffice on nine made-up rows.
Short answer: "Any person who has suffered material or non-material damage as a result of an infringement" of the GDPR can claim compensation from the controller or processor (GDPR Article 82(1)). The Court of Justice has said that an infringement alone is not enough: damage and a causal link must exist, but national courts may not demand that non-material damage reach a minimum level of seriousness (C-300/21, 4 May 2023). Fear of misuse of leaked data can itself be non-material damage, and after a hack the business must prove its security measures were appropriate (C-340/21, 14 December 2023). Compensation makes good the damage actually suffered and is not a punishment (C-667/21, 21 December 2023). When the AI supplier is part of the same processing, each one responsible can be held liable for the entire damage and can then claim back the other's share (Article 82(4)-(5)).
Why clients bring these claims to their accountant
- It is a money question first: should a provision be booked, does the insurance cover it, can the AI supplier be asked to pay part?
- Claims letters now often follow a data request or a complaint, and the accountant has the supplier contracts and invoices that show which AI tool was used.
- Payroll bureaus and bookkeepers are often the processor themselves: Article 82(2) makes a processor liable only in two cases, and the sheet sorts those.
- Small amounts add up: a voucher for one customer can become a pattern if the cause (a chatbot setting, a missing notice) is not fixed.
Step 1: tab 1, Claims (one row per claim)
| Column | What to write | Source |
|---|---|---|
| A | Client and the AI tool concerned | The claim |
| B | Who claims and what happened, in a few words | The claim |
| C | Infringement alleged: Security breach, Unlawful processing, Missed data request, Wrong AI output or Other | The claim |
| D | Damage claimed: Material, Non-material, Both or None stated | Art 82(1) |
| E | Is the damage described with facts? Y or N | C-300/21 |
| F | Amount claimed in EUR (blank if none) | The claim |
| G | Client's role for this processing: Controller, Processor or Joint | Art 4(7)-(8), Art 26, Art 28 |
| H | Is the AI supplier involved in the same processing? Y or N | Art 82(4) |
| I | Did the supplier (or, for a processor client, the client itself) act outside the controller's instructions? Y, N or Unknown | Art 82(2), Art 28(10) |
| J | Is evidence of the security measures held? Y, Partly or N | Art 32, C-340/21 |
| K | Date the claim was received (a date) | Envelope or email |
| L | Reply-by date in the letter (a date), if there is one | The claim |
| M | May insurance cover it? Y, N or Unknown | Policy |
| N | Status: Open, Court or Settled | You |
| O | Reply by: =IF(L2<>"",L2,IF(K2<>"",K2+Settings!$B$2,"")) (Settings!B2 holds your internal reply days when the letter gives no date; 14 in the example, our working default, not a legal period) | Formula |
| P | Days left: =IF(O2="","",O2-Settings!$B$1) (Settings!B1 holds the check date; put =TODAY() there in your copy) | Formula |
| Q | Result: =IF(A2="","",IF(N2="Settled","CLOSED: KEEP THE FILE",IF(N2="Court","COURT CLAIM: GET A LAWYER NOW",IF(AND(D2="None stated",E2<>"Y"),"ASK WHAT DAMAGE WAS SUFFERED",IF(G2="Processor",IF(I2="Y","PROCESSOR EXPOSED: CHECK INSTRUCTIONS","PROCESSOR: CHECK ART 82(2) DUTIES"),IF(AND(C2="Security breach",J2<>"Y"),"GATHER SECURITY EVIDENCE FIRST",IF(H2="Y","PREPARE REPLY AND NOTIFY AI SUPPLIER","PREPARE REPLY"))))))) | Formula (our working rule) |
| R | Deadline: =IF(OR(A2="",N2="Settled"),"",IF(O2="","NO DATE: LOG THE DATE RECEIVED",IF(P2<0,"LATE BY "&-P2&" DAYS: REPLY TODAY",IF(P2=0,"DUE TODAY",IF(P2<=3,"DUE IN "&P2&" DAYS: URGENT","DUE IN "&P2&" DAYS"))))) | Formula |
| S | To-do: =IF(OR(A2="",N2="Settled"),"",TEXTJOIN("; ",TRUE,IF(AND(D2="None stated",E2<>"Y"),"ask the claimant to describe the damage actually suffered: an infringement alone does not give a right to compensation (C-300/21)",""),IF(OR(D2="Non-material",D2="Both"),"non-material damage needs no minimum seriousness (C-300/21) and fear of misuse can itself be damage (C-340/21), but it must be shown",""),IF(C2="Security breach","collect proof that the security measures were appropriate to the risk (Art 32): the controller carries that burden, and a hack by a third party does not on its own exempt it (C-340/21)",""),IF(C2="Missed data request","answer the underlying data request now (Art 12 to 22)",""),IF(G2="Joint","check the joint controller arrangement (Art 26)",""),IF(H2="Y","tell the AI supplier in writing now: each party responsible can be liable for the entire damage and the one who pays can claim back the other share (Art 82(4)-(5))",""),IF(AND(I2="Y",G2<>"Processor"),"check whether the AI supplier acted outside instructions: it is then liable under Art 82(2), or treated as a controller (Art 28(10))",""),IF(AND(G2="Processor",I2<>"Y"),"a processor is liable only for breaching processor duties or acting outside lawful instructions (Art 82(2)): send the controller the claim and your instructions",""),IF(AND(G2="Processor",I2="Y"),"acting outside or contrary to the controller lawful instructions makes a processor liable (Art 82(2)), and deciding purposes and means makes it a controller for that processing (Art 28(10)): get advice",""),IF(F2>0,"compare the amount with the evidence: compensation makes good the damage actually suffered and is not punitive (C-667/21); the amount follows national rules (C-300/21)",""),IF(M2<>"N","tell the insurer within the policy notice period",""),IF(N2="Court","court: Member State of an establishment or of the claimant habitual residence (Art 79(2), 82(6)); get a lawyer",""),"do not admit liability or pay before advice; keep the letter, dates and every reply")) | Formula |
Copy the formulas into row 2 and fill down. Format columns K, L and O as dates and P as a number. TEXTJOIN works in Excel 2019 or later, Microsoft 365, Google Sheets and LibreOffice. Column Q is our working rule for sorting the work, not a legal test of whether the claim succeeds: it checks settled and court cases first, then a missing description of damage, a processor role, security evidence and the AI supplier.
Example rows (made up) and what the sheet returns at 29 Oct 2026
| Example (made up) | Key answers | Reply by | Result | Deadline |
|---|---|---|---|---|
| 1: dental clinic, AI phone answering: patient says a call recording leaked, EUR 2,000 | Security breach, non-material, controller, supplier involved, security evidence partly held | 2026-11-03 | GATHER SECURITY EVIDENCE FIRST | DUE IN 5 DAYS |
| 2: web shop, AI chatbot: chat log kept too long | No damage stated, supplier involved, no date in letter, received 22 Oct | 2026-11-05 | ASK WHAT DAMAGE WAS SUFFERED | DUE IN 7 DAYS |
| 3: recruitment agency, AI CV tool: data used without notice, EUR 5,000 | Both kinds of damage, supplier acted outside instructions, received 8 Oct | 2026-10-22 | PREPARE REPLY AND NOTIFY AI SUPPLIER | LATE BY 7 DAYS: REPLY TODAY |
| 4: payroll bureau (processor), AI payslip reader: wrong tax data, EUR 800 | Material, client is processor, stayed within instructions | 2026-11-10 | PROCESSOR: CHECK ART 82(2) DUTIES | DUE IN 12 DAYS |
| 5: salon, AI booking assistant: access request never answered, EUR 500 | Missed data request, non-material | 2026-11-01 | PREPARE REPLY | DUE IN 3 DAYS: URGENT |
| 6: estate agent, AI note-taker shared with a partner: notes passed on, EUR 1,500 | Joint controllers, received 15 Oct, no date in letter | 2026-10-29 | PREPARE REPLY | DUE TODAY |
| 7: gym, AI camera analytics: member has gone to court, EUR 3,000 | Court, supplier involved | 2026-11-28 | COURT CLAIM: GET A LAWYER NOW | DUE IN 30 DAYS |
| 8: bakery, AI email assistant: settled with a voucher | Settled | 2026-10-15 | CLOSED: KEEP THE FILE | (empty) |
| 9: payroll bureau (processor), AI tool used outside the contract, EUR 1,200 | Processor acted outside instructions, no dates logged | (empty) | PROCESSOR EXPOSED: CHECK INSTRUCTIONS | NO DATE: LOG THE DATE RECEIVED |
The to-do for row 2, for example, reads: "ask the claimant to describe the damage actually suffered: an infringement alone does not give a right to compensation (C-300/21); tell the AI supplier in writing now: each party responsible can be liable for the entire damage and the one who pays can claim back the other share (Art 82(4)-(5)); tell the insurer within the policy notice period; do not admit liability or pay before advice; keep the letter, dates and every reply".
Step 2: checklist for the first read of the claim (10 minutes)
- Who claims, for what, and how much: name, the event, the amount and any date to reply. Log the date the letter arrived.
- What infringement is alleged? Article 82(1) needs an infringement of the GDPR, damage and a link between the two. The Court of Justice held that "the mere infringement" of the GDPR "is not sufficient to confer a right to compensation" (C-300/21, operative part 1).
- What damage is described? Material (money lost, costs) or non-material (distress, loss of control, fear of misuse). No minimum seriousness may be required for non-material damage (C-300/21, operative part 2), and fear of misuse "is capable, in itself" of being non-material damage (C-340/21, operative part 6).
- Was it a breach or hack? An unauthorised disclosure by a third party does not by itself mean the security measures were inadequate, but in a damages action the controller bears the burden of proving they were appropriate (C-340/21, operative parts 1, 3 and 5). Collect the security record now: access settings, two-factor login, retention settings, the supplier's security terms.
- Who else was involved? Find the AI supplier contract. A processor is liable only where it breached obligations aimed at processors or acted outside or contrary to the controller's lawful instructions (Article 82(2)); a processor that decides purposes and means is treated as a controller for that processing (Article 28(10)).
- The exemption is narrow: a controller or processor is exempt only "if it proves that it is not in any way responsible for the event giving rise to the damage" (Article 82(3)). Liability rests on a fault that is presumed unless the business proves the event is in no way attributable to it (C-667/21, operative part 5).
- Insurance and provision: check the policy's notice clause; discuss with the client whether a provision or a note is needed under the accounting rules that apply to them.
- Is a court case already filed? Proceedings may be brought in the Member State where the controller or processor has an establishment or where the person habitually resides (Articles 79(2) and 82(6)). A not-for-profit body may claim compensation on the person's behalf where national law allows (Article 80(1)).
Related sheets: Article 32 access and security sheet for AI accounts, personal data breach 72-hour sheet, Article 28 processor agreement (DPA) clause check and data protection authority letter reply sheet.
Holding reply to the claimant (template)
Subject: Your letter of [date] about [AI tool / event]
Dear [name],
Thank you for your letter of [date], which we received on [date]. We take it seriously and are looking into what happened with [AI tool / event]. To assess your request, please tell us what damage you have suffered as a result, with any documents that show it (for example costs incurred or how you have been affected). We will reply in full by [date]. If you have a data request we have not yet answered, please tell us and we will deal with it straight away.
This letter is not an admission of liability. Kind regards, [name, role], [client name]
Notice to the AI supplier (template)
Subject: Compensation claim involving [AI tool], account [number]: please preserve records and reply by [date]
Hello,
We have received a compensation claim under GDPR Article 82 concerning [event] on [date] involving your service. Please (1) preserve all logs and records for our account for [period]; (2) tell us by [date] whether any incident, sub-processor or change on your side is linked to this event; (3) send the information you must make available under Article 28(3)(h) and [clause number] of our data processing terms. We reserve our right to claim back the part of any compensation that corresponds to your responsibility (Article 82(5)).
Kind regards, [client name]
Email to business clients (template)
Subject: A customer asks for money over your AI tool? Send us the letter before you reply
Dear [name],
If a customer, patient, applicant or employee asks you for compensation over data, for example about a chatbot, a call recording, an AI note-taker or an AI tool that got their details wrong, please forward the letter to us the same day and do not admit anything or pay yet. We will log the claim, give you the reply-by date, list what evidence to collect, check whether your AI supplier shares responsibility and whether your insurance should be told, and prepare a holding reply.
This is a first sort, not legal advice. For court claims we will recommend a lawyer. Kind regards, [firm]
Keep the AI tool list and evidence ready before a claim arrives
Most claims turn on two questions: which AI tool did what, and what proof is there that it was set up properly? Record each AI tool, its supplier and the evidence (contract, settings, notices, replies) in the EURO AI Register free edition. It runs in your browser with no account and no upload, covers your first 10 AI systems and 10 evidence records, the screening questions, duties by role with dates, and a printable Article 4 AI-literacy record.
When a client has more than 10 systems, the EURO AI Register membership starts at $19 a month and adds unlimited systems, rule updates and email help. Neither tool is legal advice or proof of compliance.
Partner programme opening soon
Partner programme opening soon: join the free waitlist. Planned terms are 50% of each referred sale (75% once you have 5+ paying customers), single level, paid through Gumroad only from revenue received.
Limits and open points
Not read for this guide: we built it from the text of Regulation (EU) 2016/679 (GDPR) and the operative parts of judgments C-300/21, C-340/21 and C-667/21, all on EUR-Lex. We did not read later Court of Justice judgments on Article 82, national rules on limitation periods, procedure, costs and the amount of damages, national rules on representative actions (Article 80 and Directive (EU) 2020/1828), insurance terms, accounting standards on provisions, or EDPB and national guidance; check them for the client's country. Open points: the GDPR sets no reply period for a compensation claim: the 14-day internal default and "do not admit liability before advice" are our practical advice, not rules in the text. Whether a claim succeeds is for the national court; the sheet sorts the work and does not decide legal questions, and court claims call for a lawyer.
Frequently asked questions
Can a customer get compensation just because a GDPR rule was broken?
No. The Court of Justice held that the mere infringement of the GDPR is not sufficient to confer a right to compensation under Article 82(1); damage must have been suffered as a result (C-300/21, 4 May 2023). But national courts may not require non-material damage to reach a minimum level of seriousness.
Is fear that leaked data will be misused enough?
It can be. The Court of Justice held that the fear experienced by a person about possible misuse of their data by third parties after a GDPR infringement is capable, in itself, of constituting non-material damage (C-340/21, 14 December 2023).
Who must prove that security was adequate after a hack?
The controller. In an action for damages under Article 82, the controller bears the burden of proving that its security measures were appropriate under Article 32, and a hack by a third party does not on its own exempt it (C-340/21).
Can the AI supplier be made to pay part?
Where the controller and the AI supplier are both involved in the same processing and both responsible, each can be held liable for the entire damage, and the one who paid can claim back the other's share (GDPR Article 82(4)-(5)). A processor is liable only for breaching processor duties or acting outside lawful instructions (Article 82(2)).
Not legal advice. The sheet helps sort a compensation claim; it does not decide legal questions. Spotted an error? Write to mininglife7@gmail.com and we correct it.
Sources
- Regulation (EU) 2016/679 (GDPR): Article 4(7), (8) and (10), Article 26(1), Article 28(3)(h) and 28(10), Article 32(1), Article 79, Article 80, Article 82(1)-(6), recitals 142, 146 and 147 — eur-lex.europa.eu, CELEX 32016R0679 (read 29 Oct 2026)
- Court of Justice, Case C-300/21 Österreichische Post, judgment of 4 May 2023, ECLI:EU:C:2023:370, operative parts 1-3 — CELEX 62021CJ0300 (read 29 Oct 2026)
- Court of Justice, Case C-340/21 Natsionalna agentsia za prihodite, judgment of 14 December 2023, ECLI:EU:C:2023:986, operative parts 1-6 — CELEX 62021CJ0340 (read 29 Oct 2026)
- Court of Justice, Case C-667/21 Krankenversicherung Nordrhein, judgment of 21 December 2023, ECLI:EU:C:2023:1022, operative parts 4-5 — CELEX 62021CJ0667 (read 29 Oct 2026)
Unadhi Guides are free, independent explainers. We correct errors as soon as we find them: write to mininglife7@gmail.com.