GDPR for Accountants and Bookkeepers in Ireland: A Guide

Last updated 16 November 2026. General information only, not legal advice.

Accountants, bookkeepers, payroll bureaus and tax advisers hold some of the most detailed personal data any business sees: PPS numbers, bank details, salaries, ID documents collected for anti-money laundering checks, and sometimes health information linked to tax reliefs. This guide explains how GDPR applies to an Irish practice and where it meets your anti-money laundering and Revenue record-keeping duties.

Does GDPR apply to accountants and bookkeepers?

Yes. GDPR (Regulation (EU) 2016/679), together with the Data Protection Act 2018, applies to any business that processes personal data, whatever its size. A sole-practitioner bookkeeper is covered in the same way as a large firm. The obligations scale with the risk of what you do, and an accounting practice handles a lot of sensitive financial data, so expectations of security and organisation are high. The regulator in Ireland is the Data Protection Commission (DPC).

If you are new to the basics, start with our GDPR guide for small businesses in Ireland, then come back here for the issues specific to accounting work.

Controller or processor? It depends on the service

The first question for any practice is what role it plays for each type of client data. The DPC’s guidance is that whether you are a controller or a processor is a question of fact, assessed case by case. A controller decides the purposes and means of processing; a processor acts only on a controller’s documented instructions.

When the practice is likely to be a controller

Where you exercise your own professional judgement and carry your own legal duties, you are generally deciding how and why data is used. Examples include preparing tax returns and accounts as an adviser, carrying out audits, and performing customer due diligence under anti-money laundering law. In those cases you need your own lawful basis, your own privacy notice and your own retention rules.

When the practice may be a processor

Some services are closer to pure outsourcing: running a client’s payroll exactly as instructed, or keying transactions into the client’s own bookkeeping system. Here you may be acting as the client’s processor, which means Article 28 GDPR requires a written data processing agreement setting out the instructions, confidentiality, security, use of sub-processors and what happens to the data at the end of the engagement.

Many practices are both. Record your conclusion for each service line in engagement letters and your record of processing. Our guide to data processing agreements in Ireland covers what an Article 28 contract must contain.

Lawful basis for client and employee data

Most processing by an accounting practice rests on one of three lawful bases in Article 6 GDPR:

  • Contract (Article 6(1)(b)): processing needed to deliver the services in your engagement letter.
  • Legal obligation (Article 6(1)(c)): processing you are required to carry out, for example anti-money laundering checks and keeping records that the law requires.
  • Legitimate interests (Article 6(1)(f)): for example, keeping files to defend a possible professional negligence claim, supported by a documented assessment.

Consent is rarely the right basis for core accounting work. Where health data appears (for instance, supporting documents for medical expense or disability-related tax reliefs), it is special-category data under Article 9, so you also need an Article 9 condition and should restrict who can see it.

Retention: balancing GDPR against AML and Revenue rules

GDPR’s storage limitation principle (Article 5(1)(e)) says you should keep personal data no longer than necessary. For accountants, “necessary” is shaped by several specific statutory periods:

  • Anti-money laundering records. Auditors, external accountants and tax advisers are designated persons under the Criminal Justice (Money Laundering and Terrorist Financing) Act 2010. Section 55 requires customer due diligence and transaction records to be kept for at least five years, generally from the end of the business relationship or the completion of the transaction. A member of An Garda Síochána can direct that the period be extended by up to a further five years in specific circumstances. Importantly, the Act also says that personal data kept solely for AML purposes must be deleted once the retention period ends.
  • Tax records. Section 886 of the Taxes Consolidation Act 1997 requires taxpayers to keep records for six years after the completion of the transactions to which they relate. This is primarily the client’s obligation, but it shapes how long your copies are useful to the client.
  • Your own business needs. If you keep files longer to deal with possible professional negligence claims, write down the period and the reason.

Put these periods into a written retention schedule, set a review date for each category, and build in a routine for secure deletion. Our guide on building a data retention schedule walks through the process.

Security: the area where practices most often fall down

Article 32 GDPR requires security appropriate to the risk. For a practice handling bank details, PPS numbers and identity documents, the risk is high. Practical measures to consider include:

  • A secure client portal for exchanging documents instead of ordinary email attachments.
  • Multi-factor authentication on email, practice management software and cloud accounting platforms.
  • Role-based access, so seasonal or junior staff only see the files they work on.
  • Encrypted laptops and phones, and a clear policy on working from home.
  • Checks on any software provider or outsourced bookkeeper who touches client data (they are your processors and need an Article 28 contract).

Personal data breaches

Misdirected emails and compromised mailboxes are common breaches in practices. Under Article 33, a controller must notify the DPC without undue delay and, where feasible, within 72 hours of becoming aware of a breach, unless it is unlikely to result in a risk to individuals. Where the risk is high, Article 34 also requires you to tell the affected individuals. If you are acting as a processor for a client, you must notify that client without undue delay so that it can decide on notification. All breaches, including those you do not report, must be recorded internally. See our 72-hour data breach response guide for a step-by-step plan.

Transparency and client rights

Clients, and people whose data clients pass to you (such as their employees), must be told how their data is used. Your privacy notice should cover purposes, lawful bases, retention, who you share data with (for example Revenue and software providers) and how to exercise rights. Subject access requests under Article 15 must normally be answered within one month.

Records, training and the DPO question

Article 30 requires a record of processing activities. Organisations with fewer than 250 employees are exempt only in narrow cases, and the exemption does not apply where processing is more than occasional or includes special-category data, which describes most accounting practices.

Most accounting and bookkeeping practices will not be legally required to appoint a Data Protection Officer, because their core activities do not usually involve large-scale processing of special-category data or large-scale systematic monitoring under Article 37. Larger firms and payroll bureaus should assess this carefully. Our guide to whether you need a DPO explains the test.

For more on each topic, see our GDPR and data protection guides and services hub. If you prefer to do the work yourself, our self-complete GDPR for Accountants template provides editable documents with plain-English guidance notes.

Need help with this? Plus Promotions Limited provides GDPR compliance services for Irish businesses, including policies, records of processing, retention schedules and processor contracts for professional practices, from €995.

Frequently asked questions

Does GDPR apply to bookkeepers in Ireland?

Yes. GDPR and the Data Protection Act 2018 apply to every business that processes personal data, including sole-trader bookkeepers. Whether a bookkeeper acts as controller or processor depends on the service and must be assessed case by case.

Is an accountant a data controller or a data processor?

It depends on the engagement. Where an accountant applies professional judgement and has its own legal duties, such as tax advice, audit or anti-money laundering checks, it is generally a controller. Where it simply follows a client’s instructions, such as running payroll exactly as directed, it may be a processor and needs an Article 28 data processing agreement.

How long should accountants keep client records under GDPR?

There is no single period. Anti-money laundering records must be kept for at least five years under section 55 of the Criminal Justice (Money Laundering and Terrorist Financing) Act 2010, and tax records generally for six years under section 886 of the Taxes Consolidation Act 1997. Any longer period, such as for possible claims, should be justified and written into a retention schedule.

Do accountants need a Data Protection Officer?

Usually not. A DPO is mandatory under Article 37 only for public bodies or where core activities involve large-scale systematic monitoring or large-scale processing of special-category or criminal data. Larger firms and payroll bureaus should assess the test and record their decision.

What should an accountancy practice do after a GDPR data breach?

Contain the breach, assess the risk to the people affected, and notify the Data Protection Commission within 72 hours where the breach is likely to result in a risk. Tell the individuals where the risk is high, record the breach internally, and if you were acting as a processor, notify the client without undue delay.

OnlineLegalServices.ie is not a solicitor’s practice and does not give legal advice. Our data protection services are compliance consultancy. For legal advice on your own situation, speak to a solicitor.