Systems
Retention settings that survive tenant upgrades
Cloud ERP vendors ship frequent releases. Most improve something. Some quietly alter how long change documents, security logs, or attachment metadata remain queryable. Audit trail readiness requires a deliberate re-check after each window — not a hopeful assumption that last year’s setting still holds.
Write the baseline once
Record, in a short control file: log name, retention period, storage location (tenant vs. external archive), export method, and the person who can adjust the setting. Screenshot the configuration page with a visible date.
After each release
Compare the live setting to the baseline within five business days. Run a sample extract for a known historical change — a journal you posted last quarter, a role grant from last month. If the extract is thinner than before, open a ticket before fieldwork, not during it.
Attachments are a separate story
Header logs may remain while supporting PDFs move to a colder store with different permissions. Confirm that auditors can still retrieve attachments under your evidence process, including for closed periods.
Korea calendar tip
Statutory seasons rarely align with vendor release calendars. If a major upgrade lands six weeks before your audit, schedule the retention re-test as a named milestone on the controllership calendar, not as an IT side task.
Module five of Cloud ERP Audit Trail Readiness includes a reusable re-test checklist.