A record should evidence inputs, sources, versions, results and human assessment. Old records preserve history; current transactions may require fresh checks after changes to lists, persons, ownership or transaction conditions.
What the record should explain
Save persons and roles, name variants, timing and each source’s outcome. Distinguish publication, retrieval and screening times. Attach original identifiers and confirmation/exclusion reasons for alerts. Mark missing sources and alternative procedures. A PDF cover or similarity score alone does not adequately explain what was done.
Documentation forming part of AML identification or due diligence is governed by Section 16. Ordinary businesses do not automatically adopt AML retention because they use the same software. Set purpose, legal basis, duration and access according to status. Public source data differs from individual client files; sensitive notes must not enter public snapshots.
Triggers for fresh screening
Define events: new entries, changed owners, representatives, counterparties, banks, services or destinations and significant transactions. Add periodic frequency based on risk and sector rules. A universal interval does not explain proportionality. Refresh long-inactive relationships before new performance rather than relying only on the original contract date.
A list-update notification does not rescreen clients unless monitoring is actually configured. Assign responsibility for processing updates, finding affected files and documenting resolution. Record coverage gaps and catch-up. Test responses to aliases, delistings and ownership changes as well as new rows.
Preserve history and accountability
Attach new conclusions with dates and change reasons. Confirmed relevant alerts require current action; old negative reports do not authorise continuation. Export evidence, reasons and source status. Assign cover for staff absence and verify that records remain retrievable after software-provider termination.
A repeated check must be a new action
For repeated screening, save a new time, actual source versions, current inputs and result. Keep the link to the previous record so changes remain visible. Record technical failure as a failed attempt without changing the last successful check date. A newly generated export from old data differs from a fresh check against current distributions.
Ownership changes may also alter the screened-person list. Do not compare only match counts. Document added persons, ended links and why coverage is sufficient for the decision. For an office provider, a change of representative or unusual redirection of the service may trigger review. Use calendar intervals alongside these triggers; they alone do not ensure a response to material changes during a relationship.
Practical steps
- Define record fields.
- Set periodic and event checks.
- Assign outage responses.
- Test export and retrieval.
Illustrative scenario
A changed ready-made company purchaser triggers fresh screening; the original remains a separate version.
When the situation differs
A system updates an old PDF’s date without reloading data or rescreening persons.
What to document
- Inputs, versions, times and conclusions.
- Resolution of updates and outages.
- Retention rule and export.
Common pitfalls
- Treating a newsletter as monitoring.
- Overwriting history.
Frequently asked questions
Must a new file be created?
Not necessarily. Each check needs identifiable timing, evidence, results and decision reasons linked to its history.
Put this guidance into practice
Choose a record for the step you are working on. Adapt it to your profession and actual case.
Complete client information online
Where to go next
- A name match: how to establish whether it is your client — A practical procedure for distinguishing a false match, confirmed identity and an unresolved sanctions alert.
- No match found: what the result actually means — How to interpret a negative sanctions result and recognise incomplete data, incorrect queries and restrictions outside lists.
Sources and legal references
- Zákon č. 253/2008 Sb., znění od 11. 1. 2026 ↗
§ 6, § 8 odst. 8, § 9 odst. 2, § 16, § 18 · accessed 2026-10-04 - MZV: Otevřená data a změna struktury k 23. 7. 2026 ↗
CSV a poznámka k aktualizaci · accessed 2026-10-04 - EU: Konsolidovaný seznam finančních sankcí ↗
rozsah dat, distribuce a aktualizace · accessed 2026-10-04 - OSN: Konsolidovaný seznam Rady bezpečnosti ↗
složení, identifikátory a jednotlivé sankční režimy · accessed 2026-10-04
Editorial work and source checks are not independent legal approval of your particular process. Compare the conditions and exceptions with your own circumstances.
