A South African organisation is first accountable under POPIA. The GDPR becomes relevant where the organisation is established in the EEA, offers goods or services to people in the EEA, or monitors their behaviour. Article 5(2) of the GDPR requires the controller to be able to demonstrate that processing meets the principles in Article 5(1): lawfulness, fairness and transparency; purpose limitation; data minimisation; accuracy; storage limitation; and integrity and confidentiality. Demonstrate means a record. It does not mean a policy that says the principles are observed. POPIA imposes the same form of duty on the responsible party: the conditions for lawful processing must be met, and the Information Officer must ensure the compliance framework is implemented, monitored and maintained.

What the duties ask for

In practice both regimes are sets of operating processes. Under POPIA: a lawful basis for every purpose, a personal information impact assessment where Regulation 4(1)(b) requires one, operator contracts, security safeguards, data-subject participation rights, and breach notification to the Information Regulator and, where required, to the data subject. Under the GDPR, where it applies: records of processing under Article 30, a working process for data subject rights under Articles 15 to 22, a data protection impact assessment where Article 35 requires one, processor contracts under Article 28, security under Article 32, breach notification to the supervisory authority within 72 hours where feasible under Article 33, and communication to data subjects under Article 34 where the risk requires it.

Each of these has an owner, a trigger and a clock. A rights request starts a deadline. A breach starts a clock from awareness. A retention period ends in a disposal decision. A list can note that these exist. It cannot run them. King V still expects the governing body to oversee the technology and data risks that these processes address. The Information Officer runs the framework. The board does not.

What a list leaves unbuilt

Consent, rights, records of processing, impact assessments, retention and breaches are often run in separate tools and spreadsheets. The Information Officer then assembles a picture when the Regulator or a European supervisory authority asks. That picture is a reconstruction. It does not show that the rights process ran, that the breach clock started from a recorded awareness time, or that disposal was approved by someone other than the person who requested it.

A privacy notice is not a system. A record of processing that was last touched at implementation is not a system. A PIIA or DPIA template with empty fields is not an assessment. Accountability is the ability to show the process, not the ability to show the template.

How a management system meets it

A management system gives the Information Officer one hub. Consent, rights requests, records of processing, personal information impact assessments, breach response, retention and assurance each run as a process with an audit trail. A breach record sets the notification deadline from the base time. A rights request enters through a portal and is tracked. A record of processing is a sequence of steps, not a spreadsheet. Disposal goes through request, approval and execution, with a permanent log. Assurance items cover the POPIA conditions and, where the GDPR applies, the Article 5 principles, with evidence and reviewer notes. Conducting, reviewing, approving, signing and exporting each need a separate permission.

AICOB is the process model the privacy processes sit on. POPIA is mapped onto it as the primary South African duty. The GDPR articles are mapped onto it where the organisation has European operations or processes personal data of people in the EEA. The Information Officer Workbench is the environment. It does not replace the Information Officer. It gives the Information Officer a system of record. Where the EU AI Act also reaches the organisation, the same processes can carry the additional high-risk mappings. The mapping is explicit. The work is not duplicated.

None of this certifies the organisation or declares it compliant. Those decisions sit with the Information Regulator, a European supervisory authority where the GDPR applies, or the governing body itself under King V. The system makes the work visible so the decision can be made on evidence.