Immutable Audit Trail
Every submission, schema version, correction filing, and timestamp — archived with full provenance for NCA examination. When an NCA requests your submission history, you have a defensible, complete record.
| Submission ID | NCA | Schema | Timestamp | Status |
|---|---|---|---|---|
| SUB-0041 | FCA | v3.1.3 | 2026-04-15 09:12 | Accepted |
| SUB-0040 | BaFin | pain.001.001.04 | 2026-04-14 14:33 | Accepted |
| SUB-0039 | ACPR | v2.4.1 | 2026-04-13 11:05 | Rejected |
| SUB-0039c | ACPR | v2.4.1 | 2026-04-13 16:44 | Corrected |
| SUB-0038 | DNB | v4.3 | 2026-04-12 08:21 | Accepted |
A complete record, examination-ready
Immutable records
Once a submission event is logged, it cannot be modified or deleted. Every record is hash-anchored with a cryptographic timestamp.
Schema version provenance
Every submission is linked to the exact schema version used for generation, including the XSD file hash. Demonstrates regulatory compliance at the technical layer.
Correction filing history
Correction and resubmission events are linked to their original submission with full diff documentation — showing exactly what changed and why.
Configurable retention
Foundation tier includes 12-month retention. Multi-NCA tier includes 36 months. Enterprise can configure custom retention periods matching NCA examination look-back windows.
Searchable log
Filter audit records by NCA, date range, schema version, submission outcome, or user. Export to CSV for offline review or examiner requests.
Role-based audit access
Grant read-only audit access to external auditors or compliance advisors without giving them submission permissions. Full audit log of who viewed what records.
What NCA examiners look for in a submission record
An NCA examination of your reporting history will focus on four categories of evidence:
-
1Submission timestampsEvidence that each quarterly submission was made within the NCA's published submission window, not after it closed.
-
2Schema version complianceProof that each submission used the current NCA-approved schema version at time of submission.
-
3Correction filingsWhere a submission was rejected and corrected, documentation of the correction timeline and the specific field or format change made.
-
4CompletenessEvidence that all required transactions were included in each submission — no unreported periods.