The platform migration
“The core system or the KYC provider changes, and the old files end up in a system nobody can access anymore.”
Article 25 of Law 10/2010 requires you to keep due diligence and transaction records for ten years. It is the obligation that gets the least attention, and the one that turns any inspection into a problem when it has not been met.
Can you retrieve a customer file from eight years ago? Free assessment
Tell us how you store your records today and we will tell you whether they would hold up to a request for information.
Keeping records is not just storing them: it means being able to retrieve a specific document, complete and in context, eight years later.
We draft the policy that sets what is kept, for how long, on what medium, who can access it and—what almost nobody has—what is deleted when the period expires and how that deletion is recorded.
AML record keeping gives you a lawful basis for processing (a legal obligation), but it is not a blank check: you need to define purpose, access and erasure at expiry so that you do not clash with the GDPR.
Making sure the file not only exists but can be reconstructed exactly as it stood at the time.
Who holds what when onboarding or archiving is outsourced.
How historical records are retrieved and handed over in response to a request for information.
A dry run retrieving old customer files to check that the archive works.
Ten years, on a retrievable medium, with the ability to reconstruct the file as it stood.
Article 25 of Law 10/2010 requires obliged entities to keep, for a period of ten years, the documentation evidencing compliance with their due diligence obligations, as well as transaction documents and records. It is a long period, well above the one usually applied by default to ordinary business records.
What matters is not the period itself but what it implies: you do not comply by storing, you comply by being able to retrieve. An archive that exists but does not let you locate a specific customer’s file within a reasonable time, or that returns a document you cannot open because the format has become obsolete, does not satisfy Article 25, even if technically nothing has been lost.
And there is a second side that almost nobody works on: deletion. Keeping records beyond the legal period without justification is not prudence; it is processing data without a lawful basis. The retention policy has to say when records are kept and also when they are destroyed, with a record showing that they were destroyed.
Six blocks, each with its own start-date rule and its own pitfalls.
| Block | What it includes | When the period starts | Common mistake |
|---|---|---|---|
| Customer identification | Identity document, verification data, representation and powers of attorney | From the end of the business relationship | The period is counted from onboarding instead of offboarding, which shortens the real period by several years. |
| Beneficial owner | Organization charts, declarations, verifications and the reasoning behind the control-chain analysis | From the end of the relationship | The outcome is kept but not the reasoning, which is exactly what inspectors ask for. |
| Purpose and nature | Information on the customer’s business and the purpose of the relationship | From the end of the relationship | It stays in a salesperson’s loose notes that never reach the file. |
| Transactions | Documents and records evidencing each transaction | From the execution of the transaction | The accounting entry is kept but not the supporting documents that justified it. |
| Analysis and alerts | Alerts generated, analysis performed, conclusion and decision taken | From the close of the analysis | Alerts closed as false positives are deleted, and they are precisely the ones that show analysis took place. |
| Reports | Reports filed with SEPBLAC and acknowledgments of receipt | From filing | The acknowledgment is kept on its own, without the file that gave rise to it. |
The start date is not the same for every block: due diligence records are tied to the end of the business relationship, and transaction records to the execution of the transaction. It is advisable to set this down in writing in the retention policy to avoid premature deletion.
Two obligations that seem to conflict but in fact apply one after the other.
| Issue | AML framework (Law 10/2010) | GDPR framework | How it is resolved |
|---|---|---|---|
| Lawful basis for processing | Legal obligation to keep records | Compliance with a legal obligation (Art. 6(1)(c)) | The basis exists; it must be documented in the record of processing activities |
| Period | Ten years | As long as necessary for the purpose | The AML period sets the GDPR period; it does not go beyond it |
| Purpose | Preventing money laundering and responding to requests for information | Limited and explicit | The AML archive cannot be used for commercial purposes |
| Access | Restricted to those who need it | Data minimization and access control | Specific permissions and an access log |
| Right to erasure | Gives way to the legal obligation | Can be exercised, within limits | Refused, with reasons, during the period |
| When the period expires | The obligation to keep records ends | Requires erasure if there is no other basis | Documented deletion |
The apparent conflict between the two frameworks is almost always resolved the same way: during the legal period, retention prevails; once the period has expired, erasure prevails. What cannot be defended is keeping records indefinitely “just in case”.
The failure is rarely deliberate destruction: it is a migration, a change of provider or a format that dies.
“The core system or the KYC provider changes, and the old files end up in a system nobody can access anymore.”
“There is still a physical archive, and the criteria for what was digitized and what was not were never documented.”
“The customer’s records were in the email or on the computer of whoever handled the deal, not in a shared repository.”
“On-chain transactions are kept, but not the alerts or the analysis carried out on them.”
Record keeping is the obligation that holds up all the others: without a document, there is no proof that anything was complied with.
Being unable to produce a file is worse than having an incomplete one. A file with gaps can be argued over; a file that does not turn up is treated as nonexistent.
The breach comes to light at the worst moment: when there is already a request for information on the table and only a few days to respond.
And keeping too much is not neutral either. Holding personal data without a lawful basis after the period has expired is a different problem, but it can also be sanctioned.
| Severity | Amount | Basis or alternative |
|---|---|---|
| Minor infringements | up to €60,000 | Less significant breaches, or breaches with no appreciable impact on the AML/CFT system. |
| Serious infringements | €60,000 – €5,000,000 | Or 10% of the company’s total resources. |
| Very serious infringements | €150,000 – €10,000,000 | Or 10% of the entity’s own funds. |
It is the quickest test there is to find out whether your AML archive works. If it takes more than a day or comes back incomplete, you have a problem worth fixing before the next inspection.
Ten years, under Article 25 of Law 10/2010. The start date is not the same for every block of records: due diligence records are tied to the end of the business relationship, and transaction records to the execution of the transaction.
Yes, as long as integrity, legibility and retrievability are ensured for the whole period. What does not work is partial digitization without documented criteria, or a format that cannot be opened seven years from now. The retention policy must address storage medium, format and migrations.
For due diligence records, from the end of the business relationship, not from onboarding. This is one of the most common calculation errors and the one that leads to premature deletion: a customer with a fifteen-year relationship means keeping their file until ten years after they leave.
Yes, and they are among the most valuable records. An alert closed with documented analysis shows that the monitoring system works and that judgment was applied. Deleting them leaves a record showing only the alerts that ended in a report, which suggests—wrongly—that nothing else is analyzed.
During the legal retention period, the AML obligation serves as the lawful basis for processing and prevails over the right to erasure, which must be refused with reasons. Once the period has expired, the logic is reversed: if there is no other legal basis, the data must be erased. We cover this in detail on our data protection page.
The responsibility is still yours. The contract with the provider must guarantee retention for the legal period, access at any time and—critically—full return of the records when the relationship ends. If you outsource KYC or archiving, check that clause: it is the one most often missing. More on AML outsourcing.
It is strongly advisable. A retention policy that provides for deletion at expiry but leaves no record that it was carried out cannot explain why a file from twelve years ago is no longer there. The deletion record is what distinguishes compliant erasure from a loss of information.
Usually a sample of specific files by name and date. What is assessed is not only whether they turn up, but how long it takes to locate them and whether they come complete with their context: identification, beneficial owner, purpose, transactions, alerts and decisions.
Regulation (EU) 2024/1624 also regulates the retention period, with a similar scheme, and harmonizes it at EU level from July 10, 2027. Before that date, it is advisable to review your internal policy to check that there are no differences in how the period is calculated. More on the AMLR page.
Not without a basis that justifies it. Ongoing court proceedings, sanction proceedings or a pending claim may justify keeping specific records for longer. What does not hold up is indefinite, across-the-board retention as a default policy.
A useful retention policy fits in a few pages and answers five questions: what, how long, where, who has access and when it is deleted. Ten steps to write it and test it.
For each block of records. Due diligence from when the customer leaves; transactions from their execution. Without this precision, deletions will be premature or late.
A policy nobody has tested is a hypothesis. Once a year, ask for two old files at random and time how long it takes.
Define what is destroyed at expiry, who carries it out and how it is recorded. Documented deletion is part of compliance, not the opposite.
If you want to test your archive before the supervisor does, start with an AML/CFT audit or the external expert report.
Record keeping breaks down at specific, predictable moments. These are the four.
1) CaptureA file that lives in a salesperson’s email or in a local folder is not being kept: it is at risk of disappearing along with that person.
2) IntegrityStable format, preserved metadata and a record of versions. A PDF regenerated without its context loses much of its evidential value.
3) MigrationThis is when most records are lost. Every migration needs an explicit plan for historical records, not just for live data.
4) RetrievalThe real test. An archive that keeps everything but takes three weeks to locate a file does not solve a request for information with a ten-day deadline.
Quick decisionThree common questions and their answers.
Yes. It is the proof that analysis took place. Keep it with its conclusion and date.
Yes, if due diligence was started. Keep what was collected.
No, if the period has expired and no proceedings are open. And keep a record of the deletion.
A document setting out what, how long, where, who has access and when records are deleted.
Policy approved by the OCI, with version and date.
Start of the period defined for each block of records.
A specific section of the policy and the matching system settings.
Every relevant document reaches the single repository.
No records in local folders or email.
Locating a specific file within a reasonable time.
Written record of the annual test, with time taken and completeness.
Destruction at expiry, with a record.
Deletion log with date, scope and person responsible.
Any one of these should prompt you to run a retrieval test this week.
Terms that come up in archiving policies, requests for information and external expert reports.
The obligation to keep due diligence and transaction records for ten years.
Due diligence from the end of the relationship; transactions from their execution.
The document kept must be the same one, legible and with its context.
Being able to find a specific file within a time frame compatible with a request for information.
Documented destruction of information whose retention period has expired.
The legal obligation to keep records justifies processing during the period, not beyond it.
The moment when most records are lost. It requires an explicit plan for historical records.
Responsibility cannot be outsourced: the contract must guarantee access and return.
Harmonizes the retention regime at EU level from July 2027.
COMPLIANCE CONTROL CENTER · ARCHIVE
Cross the age of the file with its situation. The cell tells you what to do and how to record it.
Green: ordinary situation. Red: requires a documented decision.
All obliged entities under Law 10/2010, regardless of size.
We analyze whether you qualify as an obliged entity and which blocks of records you must keep given how you operate.
Mixed paper and digital archives, with digitization criteria that are almost never documented.
Platform migrations are the main point where records get lost in this sector.
Records tend to stay with the agent who handled the deal rather than in a shared repository.
None of them is detected until a request for information arrives, which is exactly the problem.
The period for due diligence records starts at the end of the relationship. Counting from onboarding leads to premature deletion of files that still had to be kept.
Alerts that did not lead to a report are the proof that analysis exists. Without them, the record suggests that you only look at what gets reported.
The migration project focuses on live data, and closed files are left in a system that nobody will be able to access two years later.
The provider holds the records and the contract does not say what happens when the relationship ends. When it does end, it is too late to negotiate.
Records are correctly destroyed at expiry but no record of it is kept, and years later you cannot tell compliant erasure apart from a loss.
The policy exists, the archive exists, and nobody has ever checked how long it takes to pull a file from eight years ago. It is an afternoon’s test.
Direct links to the consolidated texts and to the competent bodies.
Consolidated text. Article 25: record keeping.
BOEImplementing regulations: storage media and retention conditions.
EUR-LexHarmonizes the information retention regime from July 2027.
EUR-LexData protection framework: lawful basis, minimization and erasure.
AEPDGuidance on retention periods and the right to erasure.
SEPBLACFinancial intelligence unit and the authority that issues requests in inspections.
Initial publication, covering how AML record keeping fits with the GDPR and how deletion is handled.
Planned review: application of Regulation (EU) 2024/1624.
Tell us where you keep your files today and when your last system migration took place.
The record-keeping obligation is set out in Article 25 of Law 10/2010 of April 28 on the prevention of money laundering and terrorist financing. It requires obliged entities to keep, for ten years, the documentation evidencing compliance with their due diligence obligations, as well as the documents and records of the transactions carried out.
Complying with Article 25 is not just a matter of the document existing, physically or electronically. It requires integrity (the document kept is the same one and remains legible), context (the file can be reconstructed as it stood at the time) and retrievability within a time frame compatible with responding to a request for information. An archive that keeps everything but takes weeks to locate a specific file does not meet the obligation in substance, even if nothing has been lost.
This is where most errors are concentrated. Due diligence records are kept for ten years from the end of the business relationship, not from customer onboarding. Transaction records are tied to the execution of each transaction. Applying a single start date from onboarding leads to premature deletion of files that legally still had to be kept, and it is a recurring deficiency in external expert reports.
The legal retention obligation is a lawful basis for processing under Article 6(1)(c) of the General Data Protection Regulation, and during the legal period it allows erasure requests to be refused with reasons. Once the period has expired, the relationship is reversed: if there is no other legal basis, the data must be erased. Indefinite retention “just in case” has no support in either framework. You can see the full picture on our data protection page.
Regulation (EU) 2024/1624 (AMLR), applicable from July 10, 2027, also regulates the retention period for information obtained when applying due diligence measures, harmonizing it at EU level. For Spanish entities, the useful exercise before that date is to review the internal policy—especially the start-date rules and the deletion procedure—to identify differences and correct them in good time. This work fits naturally with the review of the AML manual and with the year’s external expert report.
Key legislation, linked to the official text:
Legislation and links reviewed in .