Zum Hauptinhalt springen
ISO/IEC 27701:2025 · Annex A, Table A.1 · Control for PII controllers

A.1.5.4 Records of transfer of PII

Updated on 5 min Reviewed by: Cenedril Editorial
ISO/IEC 27701:2025GDPR

An insurance broker passes customer data to several insurers and receives policy data back. A customer withdraws her consent and asks for erasure. In the broker’s own system, this is done quickly. Which insurers received her data and when, and to whom the erasure request has to go there, nobody knows, because the data was passed on as email attachments by individual employees. A.1.5.4 requires transfers of personal data to and from third parties to be recorded and cooperation with those parties to be arranged so that later concerns of data subjects can be dealt with together.

Data subject rights do not stop at the boundary of your own organization. Whoever has passed data on must be able to follow up with corrections and deletions, and that takes two things: knowing where the data went, and a partner who plays along.

What does the standard require?

The control combines a duty to document with a duty to cooperate.

  • Record both directions. Transfers to third parties and transfers from third parties are both recorded.
  • Secure cooperation. Cooperation with the parties involved is arranged so that future concerns relating to the obligations towards data subjects can be met.
  • Typical cases. Inbound, this can be data that another controller has changed because it met obligations of its own, such as a correction. Outbound, these are transfers that pass legitimate requests from data subjects on to third parties, for example an erasure request after consent has been withdrawn.
  • Govern retention. A policy sets how long these records are kept.
  • Record sparingly. Data minimization applies to the records themselves: only what is really needed stays.

In practice

Keep a register of transfers. Recurring transfers follow from the record of processing activities and are entered with a frequency. One-off transfers, such as a data export for an expert witness, get an entry of their own. Each entry names the third party, the date or frequency, the categories of data and people, the purpose and the basis.

Agree cooperation by contract. Include a cooperation clause in the agreement with every recipient: contact point, handling deadlines and the obligation to correct, delete or block data on request. The contact point goes into the recipient’s entry in the register.

Process inbound changes. When partners deliver corrected data or erasure notices, a procedure is needed that carries them into all affected systems and records their receipt.

Link with data subject requests. For an access request, the register supplies the recipients. For a correction or erasure, it shows whom you have to notify and documents that you did so.

Keep records lean. Only the metadata of the transfer is recorded. The retention period of the records is set in the Records Retention Schedule.

Typical audit evidence

For A.1.5.4, auditors typically expect:

  • Register of transfers with recurring and one-off entries in both directions
  • Cooperation clauses in agreements with recipients and suppliers (→ Supplier Register)
  • Policy on the retention period of the records (→ Records Retention Schedule)
  • Evidence of passed-on data subject concerns, such as erasure notices to recipients with confirmation
  • Rules for transfers over approved channels (→ Information Transfer Policy)

KPI

% of PII transfers with complete and up-to-date records

Complete means: all four details plus basis and contact point are recorded. Up to date means: the entry reflects the current state, and a data flow that has ended is marked as ended. The target is 100%. A good cross-check is the comparison with supplier contracts, since every contract involving a data flow needs an entry.

Supporting KPIs:

  • Share of recipients with an agreed cooperation clause
  • Average time to pass an erasure request on to all recipients
  • Number of transfers recorded only after the fact

Article 30(1)(d) and (e) GDPR require the categories of recipients and transfers to third countries in the record of processing. Article 19 obliges the controller to communicate rectifications, erasures and restrictions to each recipient, unless this proves impossible or involves disproportionate effort, and to inform the data subject about those recipients on request. Where data has been made public, Article 17(2) requires other controllers to be informed of the erasure request. Article 5(2) requires compliance to be demonstrable, and Article 5(1)(c) applies to the records themselves too (→ GDPR General Data Protection Regulation).

A.1.5.4 provides the memory that other controls need for their work:

Sources

Frequently asked questions

Do I have to record every single transfer?

Recurring transfers can be kept as one entry with a frequency, such as the monthly delivery to the payroll bureau. One-off transfers get an entry of their own. What matters is that, when a request comes in later, you can say who received which data and when.

How long do I keep the records?

The standard requires a policy that sets this period, without naming a figure. It is common to base it on the time during which data subjects may still raise concerns about the transferred data or evidence may be requested. The period goes into the retention schedule.

What belongs in a cooperation clause with the recipient?

A contact point, deadlines for handling and the obligation to correct, delete or block data on request. A confirmation once this has been done also helps, so that you can prove completion to the data subject.

No Cookies!

This wiki collects nothing, bakes nothing and leaves nothing behind. There's nothing to consent to. Privacy doesn't get better than this.