Chartered accountants · GDPR

Accountants & GDPR: the complete compliance guide

GDPR (EU Regulation 2016/679) requires every chartered accountancy firm to strictly govern the processing of personal data it handles: that of its own employees and prospects, but above all that of employees, executives and suppliers of its clients. The distinctive feature of the profession lies in its dual role: the firm is simultaneously a data controller and a data processor, which multiplies and compounds its obligations. This guide details the concrete obligations, applicable penalties, and a compliance roadmap tailored to the reality of an accountancy firm, regardless of its size.

DPO / CISO team — Data Comply One Updated on 15 June 2026

In brief

  • Regulation: GDPR.
  • Every firm is concerned, regardless of size: as soon as it processes personal data — which applies in 100% of cases (payroll, filings, executive records) — the obligations apply.
  • Maintaining a processing register.
  • Define a legal basis.
  • Governing subcontracting.
  • The GDPR provides for two tiers of fines: up to €10 million or 2% of global annual turnover for organisational infringements (register, security, sub-processing), and up to €20 million or 4% for infringements of core principles and individuals' rights, whichever amount is higher.

Regulatory deadlines

The key dates of this regulation.

May 2018

Entry into application

In force

What does GDPR cover?

GDPR is the European framework for the protection of personal data, applicable since 25 May 2018 and enforced in France by the CNIL. It rests on several key principles: lawfulness (a legal basis for each processing activity), data minimisation (collecting only what is necessary), limitation of retention periods, security, and accountability (being able to demonstrate compliance).

It distinguishes between the data controller, who determines the purposes and means of processing, and the processor, who acts on the controller's instructions. An accounting firm is the typical example of an actor combining both roles.

Is the 'Chartered Accountants' sector affected?

Every firm is concerned, without any threshold: as soon as it processes personal data — which is the case 100% of the time (payroll, filings, executive records) — the obligations apply. The size of the firm never exempts it; it only modulates the expected level of organisation and whether or not a simplified register must be maintained.

The firm acts as data controller for the management of its own staff, its prospecting, and its invoicing. It acts as a data processor for processing carried out on behalf of its clients: payroll, accounting, and social and tax declarations. This distinction governs the contractual clauses that must be put in place.

Detailed obligations

Maintain a processing activities register

Document all processing activities, both in the capacity of controller and processor: purposes, categories of data and individuals, recipients, retention periods, security measures. This is the cornerstone of compliance and the first document requested in the event of an audit.

Define a legal basis

Each processing activity must rest on a clear legal basis (performance of a contract, legal obligation, legitimate interest, consent). Commercial prospecting often requires consent or duly framed legitimate interest.

Govern subcontracting

Sign a data processing agreement compliant with Article 28 with each service provider: payroll software vendors, hosting providers, OCR solutions. The DPA sets out the instructions, security measures, the fate of data at the end of the contract, and the framework governing sub-processors.

Secure the data

Implement measures proportionate to data sensitivity: encryption, granular access rights management, strong authentication, logging, and backups. Payroll data justifies a high level of protection.

Control data retention periods.

Define, for each data category, a retention period consistent with the purpose and legal obligations, then archive or delete beyond that point. Unlimited retention of old records is a frequent compliance failure.

Respond to individuals' rights

Being able to handle access, rectification, and erasure requests within the one-month deadline, and to manage requests forwarded by clients for whom the firm acts as a processor.

Manage data breaches

Have a procedure in place for detecting, qualifying and notifying the supervisory authority within 72 hours, together with communication to data subjects in the event of high risk.

Sanctions & risks

The GDPR provides for two tiers of fines: up to €10 million or 2% of global annual turnover for organisational infringements (register, security, sub-processing), and up to €20 million or 4% for infringements of core principles and individuals' rights, whichever amount is higher.

Beyond the fine, a leak of financial and social data constitutes a major reputational disaster for a firm whose business is built on trust. Breaches can also lead to public reprimands and injunctions backed by periodic penalty payments.

Common mistakes in the sector

  • 1Role confusion. Failing to distinguish between controller and processor, leading to inadequate contractual clauses and an incomplete register.
  • 2Missing DPA. Using payroll or hosting software without a compliant data processing agreement.
  • 3Unlimited retention. Retaining old customer files indefinitely without a purge policy.
  • 4No rights request procedure. Not knowing how to handle an access or erasure request within the one-month deadline.

Practical case

A firm of 15 employees manages payroll for 200 client companies via a SaaS application. A CNIL audit reveals the absence of a DPA with the software vendor, a register limited solely to the controller role, and unlogged access to client files. The firm remedies the situation by signing the DPA, completing the register to reflect its processor role, and activating access logging — three actions that, if taken proactively, would have prevented the formal notice.

Compliance roadmap

  1. 1

    Map. Map all processing activities and tools used, including AI components, clearly distinguishing controller and processor roles.

  2. 2

    Build the register. Drafting and maintaining the record of processing activities for both roles.

  3. 3

    Regularise DPAs. Audit vendor and hosting provider contracts, and sign or update missing or incomplete DPAs.

  4. 4

    Formalise security and retention. Write a security policy and a retention policy, and deploy a breach management procedure.

  5. 5

    Appoint a DPO and train. Appoint an internal or outsourced DPO, train staff, and schedule an annual review.

Frequently asked questions

Yes, with no threshold: from the very first processing of personal data. Only the obligation to maintain a register may be lightened for organisations with fewer than 250 employees, but it remains required as soon as a processing activity is regular or involves sensitive data — which is the case for payroll.

Take action on GDPR

Free assessment or a chat with an expert dedicated to chartered accountants.

They already trust us

See how organisations in the chartered accountants sector secured their compliance with DCO.

See testimonials