The obligation the change log answers is not written as a deadline, and it is the hardest one to satisfy retrospectively: an authority will ask what your register said on a date that has already passed, sometimes years ago.

Every snapshot freezes what the register said at that moment and stamps it with a SHA-256 hash. Snapshots cannot be edited or deleted by anyone, including an administrator with every other right in the database. That is not a permission you have failed to find — it is the point of the feature.

Chatter and the change log answer different questions. Chatter tells you that something changed and who changed it. The change log tells you what the register said on a given date. The first is useful during the week. The second is what an authority asks for years later, and no amount of chatter reconstructs it.

Recording a person who leaves and comes back. Someone stops being a real beneficiary and later becomes one again — a family transfer that is reversed, a shareholders' agreement that lapses and is renewed. Record the cessation date on the first entry and create a new entry for the second period. Both stay on the register. Overwriting the original entry with new dates would produce a record showing continuous ownership, which is false, and would erase the gap that a reviewer specifically wants to see.

Worked example. Al Mirfa Contracting LLC now has four snapshots: activation on 11 March 2026, the completion of the register on 20 March 2026, the ownership change notified on 14 July 2026, and the authority request of 5 October 2026 from the next lesson. Asked in 2031 what the register said in June 2026, you read the snapshot taken on 20 March 2026, because it was the current one until the July change. You do not reconstruct it, and you do not rely on anyone's memory.

A retention point worth raising with your advisor. Because snapshots cannot be deleted, personal data recorded in them persists for as long as the register does. The user guide documents no purge mechanism, so this course will not describe one. Given what these records contain, decide deliberately who holds UBO: Manager, and revisit that list when people change roles.

The failure mode. "A register snapshot cannot be modified" is working as intended. Take a new snapshot; the old ones stay. If a snapshot contains a genuine mistake, the correct repair is a corrected current record plus the trail showing when you found it — not a rewritten past.