EU AMLR Record Retention: When Can You Keep a Reference Instead of a Copy?
Customer due diligence and transaction evidence under the EU Anti-Money Laundering Regulation
Published
An EU financial-services team stores a customer-verification file in a specialist repository and links it from its records application. Years later, the original supplier has changed its software and the customer's details have been updated. Can the team still produce the evidence it retained, rather than a fresh view of today's customer profile?
A reference can replace a retained copy under AMLR Article 77(2) only when its conditions are met. A mutable link plus change detection is insufficient. Treat the reference as a governed evidence relationship, with a named source owner and a tested retrieval route.
What AMLR means for a document team
AMLR is the EU Anti-Money Laundering Regulation, Regulation (EU) 2024/1624. It harmonises rules for businesses covered by anti-money-laundering and counter-terrorist-financing obligations. Customer due diligence (CDD) is the process of identifying customers, understanding their relationships, and assessing relevant risk. The Council's overview of the AML package explains the wider framework. This guide focuses on the records supporting those processes.
The general application date is July 10, 2027. Article 90 sets a July 2029 exception for the football-sector entities it identifies. Establish the entity's scope and applicable national requirements with its compliance and legal owners.
The implementation questions below are an evidence-management design, not a determination that a particular source or configuration satisfies the regulation. Have the responsible compliance owner approve the chosen record categories and procedures.
Choose the representation for each evidence category
Governed copy
Preserve the selected file in the records repository. Keep its identity, source, integrity information, access rules, and retention policy together. This gives the records team a direct preservation and retrieval path.
Governed reference
Keep the evidence in an approved source and register its exact identity and retrieval relationship. Assign the source controls and recovery responsibilities explicitly, including what happens when the provider changes.
A screening score, extracted field, or review decision describes an assessment. Keep it connected to the evidence and method used at that time. Do not treat a regenerated result as a substitute for the record that supported the original decision.
Design the reference as an operational record
| Design element | What to record and exercise |
|---|---|
| Evidence identity | Source system, object and version identifiers, evidence category, customer or transaction relationship, and capture context. |
| Source protection | Version-preservation configuration, administrative permissions, retention settings, and evidence of the applied controls. |
| Retrieval route | Authorised service path, responsible operator, tested export format, recovery route, and retrieval-test results. |
| Lifecycle ownership | Business trigger, policy version, preservation directions, review and release decisions, source acknowledgements, and exceptions. |
Use a durable object identity rather than an expiring download URL. Measure the complete retrieval operation: finding the customer file, resolving the reference, authorising access, and producing the intended evidence. A successful database lookup alone does not exercise that path.
Use FormKiQ immutable retention for WORM protection
WORM means Write Once, Read Many. FormKiQ's commercial platform provides Governance-mode immutable retention backed by S3 Object Lock. Apply immutable retention to the document versions that require storage-level protection, with the retention period and policy assigned through the records workflow.
S3 Object Lock protects specified versions; new versions can still be created. Bind retrieval to the intended protected version. Governance mode permits authorised bypass, so restrict bypass permissions and review them as part of the deployment's access policy. The compliance owner assesses that control model against the applicable evidence requirements.
A checksum helps compare recovered content with an earlier observed value, and audit history records activity. Use both to verify and explain preservation alongside immutable retention. A checksum or activity log alone does not prevent modification.
For evidence retained in an external repository, apply the approved WORM or preservation controls to the source version. A FormKiQ reference records the relationship; protecting that metadata does not lock a file held elsewhere. For managed copies, FormKiQ immutable retention provides the document-content protection within the platform.
Work through a referenced customer-verification file
Consider a fictional payment firm with a customer file identified as CDD-00421. Its approved design keeps selected verification evidence in a protected source repository and manages the records workflow in FormKiQ.
Register the approved evidence
The records officer selects the approved category and links the source object and fixed version to the customer file. The source version has the approved immutable protection; any managed evidence copies in FormKiQ receive their configured immutable-retention policy. The application records the source owner, protection configuration, policy, and supporting verification result.
Exercise a request after a source change
The source receives a newer customer document. An authorised operator retrieves the retained evidence for CDD-00421, confirms the version and integrity information, and exports it through the approved channel. The test records elapsed time and any manual dependency.
Apply a relationship event
A confirmed relationship-termination event reaches the records application through the configured integration. It identifies the affected records and calculates review dates using the approved policy. Late or corrected events enter a review queue instead of silently replacing prior decisions.
Review preservation and disposition
At the relevant review point, an authorised officer checks active preservation directions and the current policy basis. Approved actions are coordinated with the source owner, and the application retains the decision, acknowledgements, and unresolved exceptions.
Model business events and preservation directions separately
- 1 · Trigger
Capture the business event
Identify the relationship or transaction event, its effective date, source, and accountable owner.
- 2 · Preserve
Track the direction
Keep authority, scope, start, review, and release information separate from the underlying schedule.
- 3 · Review
Coordinate the outcome
Record the approved action and reconcile execution across copies, references, source files, and derived content.
A reference introduces another execution boundary. Removing a pointer and deleting its source content are different operations. Record what each action affects and who acknowledges completion. The related hold, retention, and backup guide explains the separate control purposes, while the ingest-or-link guide covers the broader storage decision.
Run one evidence-retrieval exercise
- Approve the reference categories and retrieval procedure with the compliance owner.
- Retrieve a fixed source version after a newer version has been published, using normal operator permissions.
- Test source protection against the relevant administrative roles; distinguish blocked changes from changes merely logged.
- Exercise expired credentials, unavailable encryption keys, provider outage, and the approved recovery route.
- Send termination, transaction, refusal, and corrected events through the configured mapping and inspect the resulting review dates.
- Apply and release a preservation direction without losing the original schedule or its history.
- Reconcile an authorised disposition action across the reference, source evidence, retained copies, and operational exceptions.
Choose references by demonstrated evidence behaviour
Begin with one record category and one source system. Demonstrate the version, protection, retrieval, and lifecycle behaviour before extending the pattern across the customer file. That gives the records, compliance, and integration teams a concrete basis for approving a reference-based design.
Regulatory text reviewed: November 13, 2026, against Regulation (EU) 2024/1624. Application scope and local requirements should be assessed by the responsible compliance and legal owners. The example and design fields are illustrative.