Finalize decision
Freeze decisions, minutes and supporting material by period or meeting.
MOBILE-ID · TRUSTED LTANS
Audit & Compliance Evidence
Retain decisions and approved documents to assemble audit packages by business unit or case.
Problem and records to preserve
Staff and system changes can obscure which version was approved.
SYNTHETIC CASE
Synthetic governance-decision set
AUDIT-SYN-001| Element | Illustrative scope |
|---|---|
| Decision makers / users | Finance, HR, procurement and internal audit |
| Source system | ERP / approval system |
| Revision | Retain approver, document set and effective date; supplements have their own relationships. |
| Record relationship | An adjustment links the closed period and change source. |
Sector-specific record journey
Link approval
Link actual approvers/revisions; audit trails do not replace document evidence.
Preserve
Evidence the frozen set and track outstanding work before closing the period.
Find by period
Search by authorized period/decision/unit; report figures must trace to source transactions.
Authorize export
Approve export scope and redact out-of-scope data before sealing a separate package.
Delivered artifacts
| Recipient | Artifact |
|---|---|
| Source system | Intake receipts, source/revision-to-archiveId/jobId mappings and per-item errors. |
| Package recipient | Decision/minutes package with traceable adjustment reports. |
| Record owner / operations | Completed/outstanding inventory, applied decisions and report references; no automatic legal conclusion. |
Rights, retention and deployment
Report readers do not implicitly access all source documents.
Measure audit-package preparation time in the PoC; publish no reduction without measurements.
Retention authority and exit
The owner must approve the retention authority and trigger for this record class: Governance decisions and approved documents for an audit period.
Sample dossier and tests
Synthetic text files exercise inventory and hashing; they are not signed contracts, real records or ERS/XMLERS.
Download synthetic dossier| Test | Expected outcome |
|---|---|
| Intact | File inventory, size and SHA-256 match the manifest. |
| Missing / changed bytes | The verifier rejects the package without claiming inventory success. |
| Sector business case | Replaying one event cannot increase usage totals. |
Scope a PoC for this dossier
Test revision changes and event replay; do not double-count usage or overwrite historical records.
Prepare a sector-specific requestFinalization point and specific acceptance
| Control point | Requirement |
|---|---|
| Source event | Governance decisions and approved documents for an audit period. |
| Revision / decision | Retain approver, document set and effective date; supplements have their own relationships. |
| Test and expected result | Do not export outside authorized units; reconcile all in-period decisions. |
Sample inventory/hashing checks bytes only. Authorization, decision and state cases must run in the provisioned test environment before business acceptance.
Source-system handoff record
| Information | Value / decision |
|---|---|
| Record | AUDIT-SYN-001 |
| Source system | ERP / approval system |
| Revision relationship | An adjustment links the closed period and change source. |
| Recipient and output | Decision/minutes package with traceable adjustment reports. |
| Rights and authority | Report readers do not implicitly access all source documents. |
| Required rejection test | Replaying one event cannot increase usage totals. |
Sector information is source business metadata, not automatically new REST fields. Agree field mapping and ownership before a PoC.