Selected UK financial-sector AML, CTF and proliferation-financing controls, checked on 10 September 2026 against revised MLR 2017 legislation and publisher-issued guidance. Includes financial-sanctions and SAR operational guidance. This is a scoped research handbook, not comprehensive legal coverage or a compliance approval.
This public research preview maps selected Danish AML/CTF requirements from national legislation, supervisory material and supranational sources. It is not a complete country assessment: source monitoring, known official instruments, sanctions currentness, the current national AML risk picture, independent content review and customer-journey evidence remain open.
Protect and retain payment-transfer informationlegislation
Protect and retain payment-transfer information
What this requires
Payer and payee payment service providers must retain the required transfer-information records for five years and delete personal data afterwards unless a lawful further-retention provision applies.
RegCanary explanation
Use transfer data for AML/TF purposes, not incompatible purposes or commercial exploitation, and give new clients the required privacy information. Preserve confidentiality and respond fully and without delay to qualifying UK or Gibraltar authority enquiries.
Original downloaded to data/country-handbook-evidence/uk/uk-funds-transfer-2015-847-20260910.xml and parsed with ElementTree. Articles 2 and 4-16 checked in the UK-amended national version, not the repealed EU-only version. UK/Gibraltar scope and EUR 1,000 thresholds remain in the inspected text. Article 16(2) retains national-law qualifications; no generic ten-year permission is inferred. Web XHTML extraction failed but the official XML download succeeded.
Recent document checks
: unchanged, document 2d9221b2e9e3
: unchanged, document 2d9221b2e9e3
: unchanged, document 2d9221b2e9e3
: unchanged, document 2d9221b2e9e3
: unchanged, document 2d9221b2e9e3
Evidence diagnostics
Record ID
uk-payment-information-retention
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
requirements
Status when reviewed
current
Review status
source checked
Effective from
Not recorded
Effective to
Not recorded
No conditions are recorded. This does not establish that none apply.
No exceptions are recorded. This does not establish that none apply.
Retain suspicion reports and reporting decisionsguidance
Retain suspicion reports and reporting decisions
What this requires
JMLSG recommends retaining internal and external suspicion reports for at least five years from the report date, together with the actions taken and relevant decision material.
RegCanary explanation
Keep copies of SARs sent to the NCA. Where the nominated officer decides not to report, document the reasons and retain them with the internal report and material considered. This guidance retention anchor differs from the statutory CDD relationship-end or transaction-completion anchor.
Applicability
Business lines
all
Customer types
all
Stages
all
Supporting provision
JMLSG Part I paragraphs 6.32 and 8.21-8.23
Baseline document
Joint Money Laundering Steering Group
Source diagnostics
Lifecycle
Not recorded
Language
en
Retrieved
10 Sept 2026
Extraction
captured
Latest automated check
12 Oct 2026
Check outcome
unchanged
Evidence review
unvalidated
Type
guidance
Version
June 2023, updated August 2025, as linked from Current Guidance; read with later revisions
Original downloaded to data/country-handbook-evidence/uk/jmlsg-part-i-aug-2025.pdf. Paragraphs 5.3.69-5.3.75 inspected via web text and PDF page 88 via pdftotext. Current means publisher-listed base guidance, not that all text reflects 2026 law. No wholesale republication; original is a local research capture subject to publisher rights. Core-control expansion checked paragraphs 6.32 and 8.21-8.23 using pdftotext on the retained original. The five-year suspicion-report retention statement is guidance, not a new statutory period.
Recent document checks
: unchanged, document 5ddd575e79e3
: unchanged, document 5ddd575e79e3
: unchanged, document 5ddd575e79e3
: unchanged, document 5ddd575e79e3
: unchanged, document 5ddd575e79e3
Evidence diagnostics
Record ID
uk-sar-decision-retention
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
requirements
Status when reviewed
current
Review status
source checked
Effective from
Not recorded
Effective to
Not recorded
No conditions are recorded. This does not establish that none apply.
No exceptions are recorded. This does not establish that none apply.
Keep permitted frozen-account credits separate from releaselegislation
Keep permitted frozen-account credits separate from release
What this requires
Under the Russia regime, specified frozen-account credits and transfers can fall within statutory exceptions, but those exceptions do not provide general permission to release frozen money.
RegCanary explanation
Regulation 58(3) permits a relevant institution to credit interest or other earnings. Paragraph (4) permits specified incoming credits against the making-funds-available prohibitions; the money remains subject to the freeze. Paragraph (5) permits the specified transfer of funds to a relevant institution for crediting to an account held or controlled directly or indirectly by a designated person, in discharge or partial discharge of an obligation arising before designation. Under paragraphs (9)-(10), where that person is an entity C owned or controlled directly or indirectly by designated person D, C is treated for paragraph (5) as becoming designated at the same time as D, not when the firm first identifies C's ownership/control or C is separately listed. Paragraph (6) permits the narrowly defined transfer to a ring-fenced body. Report credits under paragraph (4) and transfers under paragraph (6) to the Treasury without delay.
Applicability
Business lines
all
Customer types
all
Stages
all
Supporting provision
Russia Regulations 11, 58(3)-(10), 70(5), (7)
Baseline document
Secretary of State / legislation.gov.uk
Source diagnostics
Lifecycle
Not recorded
Language
en
Retrieved
10 Sept 2026
Extraction
captured
Latest automated check
12 Oct 2026
Check outcome
unchanged
Evidence review
unvalidated
Type
legislation
Version
Official revised XML captured 11 September 2026 London time; document RestrictStartDate 2026-05-20
Original downloaded to data/country-handbook-evidence/uk/russia-sanctions-revised-20260911.xml. ElementTree extraction checked regulations 2-3, 5, 7-8, 10-15, 19, 58, 64, 66-67, 70-71 and 79(3), (6), Schedule 1 and selected Schedule 5 paragraphs. No future RestrictStartDate nodes or Unapplied metadata elements found in the downloaded snapshot; this is not a comprehensive amendment/legal-perimeter audit. These source_checked additions map only the stated Russia-regime provisions, not all sectoral sanctions or all UK regimes. Native English statutory original, not a translation. Freeze recheck: official original recaptured unchanged at data/country-handbook-evidence/uk/russia-sanctions-freeze-20260911.xml, 2026-09-11T07:50:08.614Z; SHA-256 146f749d478109c2e8c72d7620eaab8dbe1352d270d35828e95566935573e99f matches the retained source. Further inspected regulations 18A, 70(1ZA)-(1ZB), (3)-(4), (7), 71 and 79(3), (5)-(6).
Recent document checks
: unchanged, document 146f749d4781
: unchanged, document 146f749d4781
: unchanged, document 146f749d4781
: unchanged, document 146f749d4781
: unchanged, document 146f749d4781
Evidence diagnostics
Record ID
uk-russia-frozen-account-exceptions
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
requirements
Status when reviewed
current
Review status
source checked
Effective from
Not recorded
Effective to
Not recorded
No conditions are recorded. This does not establish that none apply.
No exceptions are recorded. This does not establish that none apply.
Establish actual Russia licensing or exception authority before actinglegislation
Establish actual Russia licensing or exception authority before acting
What this requires
For otherwise prohibited activity under the mapped Russia asset-freeze rules, establish that a statutory exception applies or that the act is authorised by an applicable Treasury licence, and comply with its conditions.
RegCanary explanation
A Treasury licence must specify the acts it authorises and may be general, individual or for a description of persons, with conditions and a defined or indefinite duration. It can be varied, revoked or suspended. Individual asset-freeze licences are constrained by the statutory licensing purposes; basic needs, legal fees and routine asset-maintenance fees are examples of purposes, not automatic payment permissions. A person purporting to act under a Treasury licence commits an offence if it fails to comply with a condition.
Applicability
Business lines
all
Customer types
all
Stages
all
Supporting provision
Russia Regulations 11(2), 12(2), 13(2), 14(2), 15(2), 58(1)-(2), 64(1)-(3), 66(1)-(7), 67(1)-(2); Schedule 5 Part 1 paragraphs 1-4
Baseline document
Secretary of State / legislation.gov.uk
Source diagnostics
Lifecycle
Not recorded
Language
en
Retrieved
10 Sept 2026
Extraction
captured
Latest automated check
12 Oct 2026
Check outcome
unchanged
Evidence review
unvalidated
Type
legislation
Version
Official revised XML captured 11 September 2026 London time; document RestrictStartDate 2026-05-20
Original downloaded to data/country-handbook-evidence/uk/russia-sanctions-revised-20260911.xml. ElementTree extraction checked regulations 2-3, 5, 7-8, 10-15, 19, 58, 64, 66-67, 70-71 and 79(3), (6), Schedule 1 and selected Schedule 5 paragraphs. No future RestrictStartDate nodes or Unapplied metadata elements found in the downloaded snapshot; this is not a comprehensive amendment/legal-perimeter audit. These source_checked additions map only the stated Russia-regime provisions, not all sectoral sanctions or all UK regimes. Native English statutory original, not a translation. Freeze recheck: official original recaptured unchanged at data/country-handbook-evidence/uk/russia-sanctions-freeze-20260911.xml, 2026-09-11T07:50:08.614Z; SHA-256 146f749d478109c2e8c72d7620eaab8dbe1352d270d35828e95566935573e99f matches the retained source. Further inspected regulations 18A, 70(1ZA)-(1ZB), (3)-(4), (7), 71 and 79(3), (5)-(6).
Recent document checks
: unchanged, document 146f749d4781
: unchanged, document 146f749d4781
: unchanged, document 146f749d4781
: unchanged, document 146f749d4781
: unchanged, document 146f749d4781
Evidence diagnostics
Record ID
uk-russia-licences-exceptions
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
requirements
Status when reviewed
current
Review status
source checked
Effective from
Not recorded
Effective to
Not recorded
No conditions are recorded. This does not establish that none apply.
No exceptions are recorded. This does not establish that none apply.
Give management useful AML oversight information · review pendingguidance / Review pending
Give management useful AML oversight information
What this requires
FCA guidance expects senior-management oversight and at least annual MLRO reporting on control effectiveness.
RegCanary explanation
Provide information that supports management challenge and follow-up. SYSC 6.3.7G addresses annual MLRO reporting, training and documentation; FCG 3.2.1G illustrates governance and challenge. Related SYSC R provisions are binding rules where applicable, not reclassified as guidance by this entry.
Earlier web-fetched HTML content checked. Section contains both R rules and G guidance: source kind is a schema-level categorisation, not a claim that R provisions are optional. Handbook rule application is not determined solely by a business-line label. No effective dates inferred from the page update date. Delivery original captured from https://handbook.fca.org.uk/handbook/sysc6/sysc6s3 at 2026-09-11T07:29:04.210Z to data/country-handbook-evidence/uk/uk-fca-sysc-6-3-delivery-20260911.html; SHA-256 382b86f56862df89c3f7a9004ffa643fa1265e1af26a056af58559b49f227f1d. Timestamp records local download completion. Official publisher English, not a translation. The original's text was inspected; capture does not imply every provision is verified. Freeze recheck: official original recaptured unchanged at data/country-handbook-evidence/uk/fca-sysc6-3-freeze-20260911.html, 2026-09-11T07:51:54.218Z; SHA-256 382b86f56862df89c3f7a9004ffa643fa1265e1af26a056af58559b49f227f1d matches the retained source. Binding R provisions 6.3.1, 6.3.3, 6.3.8 and 6.3.9 checked separately from G guidance.
Web-fetched content checked at FCG 3.2.1-3.2.3. Guidance and examples, not a new standalone legislative duty. The initial FCG review did not audit application tables; the later binding-rule freeze uses the separate official SYSC application source. Delivery original captured from https://handbook.fca.org.uk/handbook/fcg3/fcg3s2 at 2026-09-11T07:29:04.337Z to data/country-handbook-evidence/uk/uk-fca-fcg-3-2-delivery-20260911.html; SHA-256 1383b903dc0cfda5750abc9c1bd7e051dcacd3db1dba96edfb6226b2c5636893. Timestamp records local download completion. Official publisher English, not a translation. The original's text was inspected; capture does not imply every provision is verified.
Recent document checks
: unchanged, document 5cc5af998964
: unchanged, document 5cc5af998964
: unchanged, document 5cc5af998964
: unchanged, document 5cc5af998964
: unchanged, document 5cc5af998964
Review pending
Financial Conduct Authority
Source diagnostics
Lifecycle
Not recorded
Language
en
Retrieved
11 Sept 2026
Extraction
captured
Latest automated check
12 Oct 2026
Check outcome
unchanged
Evidence review
requires-revalidation
Type
legislation
Version
Live official section captured 11 September 2026; displayed page update 29/05/2026; provision dates differ
Official English original HTML downloaded unchanged to data/country-handbook-evidence/uk/fca-sysc1-full-freeze-20260911.html; SHA-256 18df81cbf35f1f7ef6bf8c480345e9b677a4213b24ae7fd4d2627a53786871ec; capture completion 2026-09-11T07:50:07.303Z. Parsed with Cheerio preserving table rows/cells for application mapping. National regulator original, not a translation. Schema kind legislation denotes binding Handbook rules/definitions, not an Act of Parliament; G guidance remains non-binding. Checked SYSC 1.1A.1G-1BG, Annex 1 Parts 1-3, Table A columns A/A+/A++/B and Table B columns A/B for SYSC 6.1.1 and 6.3.1/3/8/9. The displayed 25 October 2027 future version is not used as current law. No displayed update or capture date is assigned as a compound duty's effective date.
Recent document checks
: unchanged, document 89d70b43b06b
: unchanged, document 89d70b43b06b
: unchanged, document 89d70b43b06b
: unchanged, document 89d70b43b06b
: unchanged, document 89d70b43b06b
Evidence diagnostics
Record ID
uk-fca-aml-oversight
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
requirements
Baseline review status
source checked
Review status
needs review
Effective from
Not recorded
Effective to
Not recorded
No conditions are recorded. This does not establish that none apply.
No exceptions are recorded. This does not establish that none apply.
Monitor payment and e-money controls and report to management · review pendinglegislation / Review pending
Monitor payment and e-money controls and report to management
What this requires
An MLR-relevant e-money issuer or payment service provider must appoint an individual to monitor and manage compliance with its AML and proliferation-financing controls.
RegCanary explanation
The individual must identify higher-risk situations, maintain control and risk-management records, embed the controls in relevant functions and business changes, and report to senior management whenever appropriate and at least annually.
Official original downloaded from https://www.legislation.gov.uk/uksi/2017/692/data.xml to data/country-handbook-evidence/uk/mlr-2017-revised.xml; parsed with Python ElementTree. Web reader rejected XHTML; direct XML succeeded. Inspected provisions and unapplied-effects metadata. Future reg. 34A and Sch. 6 para. 7(ga) are not current duties; metadata also identifies an obsolete 2019 reg. 3(1) effect that requires no application. English official legislative text, not a translation. Version dates are not assigned as commencement dates to compound requirements. Fresh read-only download completed 2026-09-10T19:02:53Z at data/country-handbook-evidence/uk/mlr-2017-entity-expansion-20260910.xml; SHA-256 is identical to the first capture. Entity expansion checked regulations 5, 6, 28, 30(6)-(7), 30A, 30ZA(5), 42-45 (selected information paragraphs) and Schedule 3AZA. See docs/country-handbooks/uk-entity-expansion.md. Core-control re-download at data/country-handbook-evidence/uk/mlr-2017-core-controls-20260910.xml completed 2026-09-10T20:35:30Z with the same SHA-256. Further inspected regulations 19A, 20, 21, 24, 29, 34, 38-41 and 64A-64H. See docs/country-handbooks/uk-coverage-completion.md. Delivery original captured from https://www.legislation.gov.uk/uksi/2017/692/data.xml at 2026-09-11T07:33:37.592Z to data/country-handbook-evidence/uk/mlr-2017-delivery-20260911.xml; SHA-256 694f11c106b2b5328a4bcabf5a2d6f48ac39ec06670302b4e19c20bcfdb70811. Timestamp records local download completion. Official publisher English, not a translation. The original's text was inspected; capture does not imply every provision is verified. Fresh XML parsed with ElementTree: legislative body and commentary are identical to the prior retained original; differences are confined to metadata. Prior originals remain retained.
Recent document checks
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
Evidence diagnostics
Record ID
uk-payment-compliance-officer
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
requirements
Baseline review status
source checked
Review status
needs review
Effective from
Not recorded
Effective to
Not recorded
No conditions are recorded. This does not establish that none apply.
No exceptions are recorded. This does not establish that none apply.
Apply the insurer-route FCA AML rules where in scope · review pendinglegislation / Review pending
Apply the insurer-route FCA AML rules where in scope
What this requires
For an insurer-route firm and activity within SYSC 3.2.6A-6J, maintain proportionate AML systems, assess their adequacy regularly and assign senior responsibility and an empowered MLRO, subject to the specific exclusions.
RegCanary explanation
SYSC 3.2.6AR and 6CR require money-laundering risk systems and regular adequacy assessments. Paragraphs 6HR and 6IR require overall responsibility to sit with a director or senior manager and require an MLRO with sufficient authority, independence, resources and information. The broader financial-crime control duty in 3.2.6R is distinct from the narrower AML-specific application of 6AR-6JG. Annual MLRO reporting in 6GG is guidance. A bank or adviser distributing an insurance product does not become an insurer-route firm merely by offering that product.
Official English original HTML downloaded unchanged to data/country-handbook-evidence/uk/fca-sysc3-2-freeze-20260911.html; SHA-256 1e4dc02bf92d9b6a5515b207baca94d046012638a1634ab690f5d81225e209ca; capture completion 2026-09-11T07:49:09.985Z. Parsed with Cheerio preserving table rows/cells for application mapping. National regulator original, not a translation. Schema kind legislation denotes binding Handbook rules/definitions, not an Act of Parliament; G guidance remains non-binding. Checked the cited R provisions and distinguished related G guidance. No displayed update or capture date is assigned as a compound duty's effective date.
Recent document checks
: failed, document 3b2b3597ded5
: unchanged, document 3b2b3597ded5
: unchanged, document 3b2b3597ded5
: unchanged, document 3b2b3597ded5
: unchanged, document 3b2b3597ded5
Review pending
Financial Conduct Authority
Source diagnostics
Lifecycle
Not recorded
Language
en
Retrieved
11 Sept 2026
Extraction
captured
Latest automated check
12 Oct 2026
Check outcome
unchanged
Evidence review
requires-revalidation
Type
legislation
Version
Live official section captured 11 September 2026; displayed page update 29/05/2026; provision dates differ
Official English original HTML downloaded unchanged to data/country-handbook-evidence/uk/fca-sysc1-full-freeze-20260911.html; SHA-256 18df81cbf35f1f7ef6bf8c480345e9b677a4213b24ae7fd4d2627a53786871ec; capture completion 2026-09-11T07:50:07.303Z. Parsed with Cheerio preserving table rows/cells for application mapping. National regulator original, not a translation. Schema kind legislation denotes binding Handbook rules/definitions, not an Act of Parliament; G guidance remains non-binding. Checked SYSC 1.1A.1G-1BG, Annex 1 Parts 1-3, Table A columns A/A+/A++/B and Table B columns A/B for SYSC 6.1.1 and 6.3.1/3/8/9. The displayed 25 October 2027 future version is not used as current law. No displayed update or capture date is assigned as a compound duty's effective date.
Recent document checks
: unchanged, document 89d70b43b06b
: unchanged, document 89d70b43b06b
: unchanged, document 89d70b43b06b
: unchanged, document 89d70b43b06b
: unchanged, document 89d70b43b06b
Review pending
Financial Conduct Authority
Source diagnostics
Lifecycle
Not recorded
Language
en
Retrieved
11 Sept 2026
Extraction
captured
Latest automated check
12 Oct 2026
Check outcome
unchanged
Evidence review
requires-revalidation
Type
legislation
Version
Live official glossary entry captured 11 September 2026; no separate edition date asserted
Official English original HTML downloaded unchanged to data/country-handbook-evidence/uk/fca-glossary-firm-freeze-20260911.html; SHA-256 37ea994b0ab1626da9d0ba23256f6fa8b901cfb01d8f8f0fae867381812962ed; capture completion 2026-09-11T07:50:29.749Z. Parsed with Cheerio preserving table rows/cells for application mapping. National regulator original, not a translation. Schema kind legislation denotes binding Handbook rules/definitions, not an Act of Parliament; G guidance remains non-binding. Checked the definition and section-specific extensions; payment-services/e-money permission and MLR registration do not themselves establish the general SYSC firm definition. No displayed update or capture date is assigned as a compound duty's effective date.
Recent document checks
: unchanged, document 6093006d0f42
: unchanged, document 6093006d0f42
: unchanged, document 6093006d0f42
: unchanged, document 6093006d0f42
: unchanged, document 6093006d0f42
Review pending
Financial Conduct Authority
Source diagnostics
Lifecycle
Not recorded
Language
en
Retrieved
11 Sept 2026
Extraction
captured
Latest automated check
12 Oct 2026
Check outcome
unchanged
Evidence review
requires-revalidation
Type
legislation
Version
Live official glossary entry captured 11 September 2026; no separate edition date asserted
Official English original HTML downloaded unchanged to data/country-handbook-evidence/uk/fca-glossary-authorised-person-freeze-20260911.html; SHA-256 97ccc8793a8ba076e79a943c06c0fbd9a27412b7286f1a9a0b7766f2989aa31f; capture completion 2026-09-11T07:50:50.541Z. Parsed with Cheerio preserving table rows/cells for application mapping. National regulator original, not a translation. Schema kind legislation denotes binding Handbook rules/definitions, not an Act of Parliament; G guidance remains non-binding. Checked the definition and section-specific extensions; payment-services/e-money permission and MLR registration do not themselves establish the general SYSC firm definition. No displayed update or capture date is assigned as a compound duty's effective date.
Recent document checks
: unchanged, document e2bd4887e2d0
: unchanged, document e2bd4887e2d0
: unchanged, document e2bd4887e2d0
: unchanged, document e2bd4887e2d0
: unchanged, document e2bd4887e2d0
Evidence diagnostics
Record ID
uk-fca-sysc3-binding-aml
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
requirements
Baseline review status
source checked
Review status
needs review
Effective from
Not recorded
Effective to
Not recorded
No conditions are recorded. This does not establish that none apply.
No exceptions are recorded. This does not establish that none apply.
Maintain approved AML and proliferation-financing controls · review pendinglegislation / Review pending
Maintain approved AML and proliferation-financing controls
What this requires
For UK business within the MLR relevant-person scope, maintain proportionate, senior-management-approved controls for money laundering, terrorist financing and proliferation financing. Keep policies under review and document changes and internal communication.
RegCanary explanation
Control design must reflect the firm's actual activities and risks. Cover risk management, internal controls, CDD, records and compliance oversight, including scrutiny of unusually complex or large transactions, unusual patterns and transactions without apparent economic or legal purpose. Assess the risks of new products, business practices and technology in preparation for and during adoption, and mitigate those risks where necessary.
Applicability
Business lines
all
Customer types
all
Stages
all
Supporting provision
MLR 2017 regulations 8(1)-(2), 10, 14A, 15, 19(1)-(4) and 19A(1)-(4)
Review pending
HM Treasury / legislation.gov.uk
Source diagnostics
Lifecycle
Not recorded
Language
en
Retrieved
11 Sept 2026
Extraction
captured
Latest automated check
12 Oct 2026
Check outcome
unchanged
Evidence review
requires-revalidation
Type
legislation
Version
Revised XML retrieved 2026-09-11; document RestrictStartDate 2026-06-30; individual provisions have different amendment histories
Official original downloaded from https://www.legislation.gov.uk/uksi/2017/692/data.xml to data/country-handbook-evidence/uk/mlr-2017-revised.xml; parsed with Python ElementTree. Web reader rejected XHTML; direct XML succeeded. Inspected provisions and unapplied-effects metadata. Future reg. 34A and Sch. 6 para. 7(ga) are not current duties; metadata also identifies an obsolete 2019 reg. 3(1) effect that requires no application. English official legislative text, not a translation. Version dates are not assigned as commencement dates to compound requirements. Fresh read-only download completed 2026-09-10T19:02:53Z at data/country-handbook-evidence/uk/mlr-2017-entity-expansion-20260910.xml; SHA-256 is identical to the first capture. Entity expansion checked regulations 5, 6, 28, 30(6)-(7), 30A, 30ZA(5), 42-45 (selected information paragraphs) and Schedule 3AZA. See docs/country-handbooks/uk-entity-expansion.md. Core-control re-download at data/country-handbook-evidence/uk/mlr-2017-core-controls-20260910.xml completed 2026-09-10T20:35:30Z with the same SHA-256. Further inspected regulations 19A, 20, 21, 24, 29, 34, 38-41 and 64A-64H. See docs/country-handbooks/uk-coverage-completion.md. Delivery original captured from https://www.legislation.gov.uk/uksi/2017/692/data.xml at 2026-09-11T07:33:37.592Z to data/country-handbook-evidence/uk/mlr-2017-delivery-20260911.xml; SHA-256 694f11c106b2b5328a4bcabf5a2d6f48ac39ec06670302b4e19c20bcfdb70811. Timestamp records local download completion. Official publisher English, not a translation. The original's text was inspected; capture does not imply every provision is verified. Fresh XML parsed with ElementTree: legislative body and commentary are identical to the prior retained original; differences are confined to metadata. Prior originals remain retained.
Recent document checks
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
Evidence diagnostics
Record ID
uk-aml-policies
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
requirements
Baseline review status
source checked
Review status
needs review
Effective from
Not recorded
Effective to
Not recorded
No conditions are recorded. This does not establish that none apply.
No exceptions are recorded. This does not establish that none apply.
Retain CDD and reconstructable transaction records · review pendinglegislation / Review pending
Retain CDD and reconstructable transaction records
What this requires
Keep specified CDD and transaction records for the statutory period, then apply the personal-data deletion rules.
RegCanary explanation
The usual period is five years from known or reasonably believed completion of an occasional transaction or end of the business relationship. Supporting records must permit transaction reconstruction. Regulation 40(4) limits the obligation for relationship transaction records to ten years; it is not a universal cap on every CDD record. The records expressly include the specified crypto-transfer information. Maintain systems to answer qualifying law-enforcement enquiries fully and rapidly about relationships in the previous five years; crypto-transfer information requests under regulation 64H require a full response without delay. Personal data obtained under the MLRs is subject to the purpose and customer-information requirements in regulation 41. Before a new customer's business relationship or occasional transaction, provide the regulation 41(6) statement limiting personal-data use to ML/TF/PF prevention or another permitted use, in addition to the UK GDPR Article 13 information. This is a pre-relationship or pre-transaction notice, not merely a deletion-stage task.
Applicability
Business lines
all
Customer types
all
Stages
all
Supporting provision
MLR 2017 regulations 40(1)-(9), 21(8)-(9), 41(1), (3), (6)-(8) and 64H
Review pending
HM Treasury / legislation.gov.uk
Source diagnostics
Lifecycle
Not recorded
Language
en
Retrieved
11 Sept 2026
Extraction
captured
Latest automated check
12 Oct 2026
Check outcome
unchanged
Evidence review
requires-revalidation
Type
legislation
Version
Revised XML retrieved 2026-09-11; document RestrictStartDate 2026-06-30; individual provisions have different amendment histories
Official original downloaded from https://www.legislation.gov.uk/uksi/2017/692/data.xml to data/country-handbook-evidence/uk/mlr-2017-revised.xml; parsed with Python ElementTree. Web reader rejected XHTML; direct XML succeeded. Inspected provisions and unapplied-effects metadata. Future reg. 34A and Sch. 6 para. 7(ga) are not current duties; metadata also identifies an obsolete 2019 reg. 3(1) effect that requires no application. English official legislative text, not a translation. Version dates are not assigned as commencement dates to compound requirements. Fresh read-only download completed 2026-09-10T19:02:53Z at data/country-handbook-evidence/uk/mlr-2017-entity-expansion-20260910.xml; SHA-256 is identical to the first capture. Entity expansion checked regulations 5, 6, 28, 30(6)-(7), 30A, 30ZA(5), 42-45 (selected information paragraphs) and Schedule 3AZA. See docs/country-handbooks/uk-entity-expansion.md. Core-control re-download at data/country-handbook-evidence/uk/mlr-2017-core-controls-20260910.xml completed 2026-09-10T20:35:30Z with the same SHA-256. Further inspected regulations 19A, 20, 21, 24, 29, 34, 38-41 and 64A-64H. See docs/country-handbooks/uk-coverage-completion.md. Delivery original captured from https://www.legislation.gov.uk/uksi/2017/692/data.xml at 2026-09-11T07:33:37.592Z to data/country-handbook-evidence/uk/mlr-2017-delivery-20260911.xml; SHA-256 694f11c106b2b5328a4bcabf5a2d6f48ac39ec06670302b4e19c20bcfdb70811. Timestamp records local download completion. Official publisher English, not a translation. The original's text was inspected; capture does not imply every provision is verified. Fresh XML parsed with ElementTree: legislative body and commentary are identical to the prior retained original; differences are confined to metadata. Prior originals remain retained.
Recent document checks
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
Evidence diagnostics
Record ID
uk-record-retention
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
requirements
Baseline review status
source checked
Review status
needs review
Effective from
Not recorded
Effective to
Not recorded
No conditions are recorded. This does not establish that none apply.
No exceptions are recorded. This does not establish that none apply.
Allocate compliance responsibility and independent oversight
What this requires
Appoint a nominated officer and, where appropriate to the size and nature of the business, a senior compliance officer, employee screening and an independent audit function.
RegCanary explanation
Notify the supervisor of initial and subsequent officer appointments within 14 days. Screening assesses relevant employees' competence and integrity before and during appointment. Independent audit evaluates controls, recommends improvements and monitors follow-up. The nominated officer assesses internal disclosures using all relevant information available to the firm.
Applicability
Business lines
all
Customer types
all
Stages
all
Supporting provision
MLR 2017 regulation 21(1)-(6), (10)
Review pending
HM Treasury / legislation.gov.uk
Source diagnostics
Lifecycle
Not recorded
Language
en
Retrieved
11 Sept 2026
Extraction
captured
Latest automated check
12 Oct 2026
Check outcome
unchanged
Evidence review
requires-revalidation
Type
legislation
Version
Revised XML retrieved 2026-09-11; document RestrictStartDate 2026-06-30; individual provisions have different amendment histories
Official original downloaded from https://www.legislation.gov.uk/uksi/2017/692/data.xml to data/country-handbook-evidence/uk/mlr-2017-revised.xml; parsed with Python ElementTree. Web reader rejected XHTML; direct XML succeeded. Inspected provisions and unapplied-effects metadata. Future reg. 34A and Sch. 6 para. 7(ga) are not current duties; metadata also identifies an obsolete 2019 reg. 3(1) effect that requires no application. English official legislative text, not a translation. Version dates are not assigned as commencement dates to compound requirements. Fresh read-only download completed 2026-09-10T19:02:53Z at data/country-handbook-evidence/uk/mlr-2017-entity-expansion-20260910.xml; SHA-256 is identical to the first capture. Entity expansion checked regulations 5, 6, 28, 30(6)-(7), 30A, 30ZA(5), 42-45 (selected information paragraphs) and Schedule 3AZA. See docs/country-handbooks/uk-entity-expansion.md. Core-control re-download at data/country-handbook-evidence/uk/mlr-2017-core-controls-20260910.xml completed 2026-09-10T20:35:30Z with the same SHA-256. Further inspected regulations 19A, 20, 21, 24, 29, 34, 38-41 and 64A-64H. See docs/country-handbooks/uk-coverage-completion.md. Delivery original captured from https://www.legislation.gov.uk/uksi/2017/692/data.xml at 2026-09-11T07:33:37.592Z to data/country-handbook-evidence/uk/mlr-2017-delivery-20260911.xml; SHA-256 694f11c106b2b5328a4bcabf5a2d6f48ac39ec06670302b4e19c20bcfdb70811. Timestamp records local download completion. Official publisher English, not a translation. The original's text was inspected; capture does not imply every provision is verified. Fresh XML parsed with ElementTree: legislative body and commentary are identical to the prior retained original; differences are confined to metadata. Prior originals remain retained.
Recent document checks
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
Evidence diagnostics
Record ID
uk-governance-screening-audit
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
requirements
Baseline review status
source checked
Review status
needs review
Effective from
Not recorded
Effective to
Not recorded
No conditions are recorded. This does not establish that none apply.
No exceptions are recorded. This does not establish that none apply.
Provide relevant employees and business agents with regular training on recognising and handling potential money laundering, terrorist financing and proliferation financing.
RegCanary explanation
Make relevant staff and agents aware of applicable financial-crime law and data-protection requirements. Keep written records of the measures and training provided. Content and frequency must reflect the nature and size of the business and its risks.
Applicability
Business lines
all
Customer types
all
Stages
all
Supporting provision
MLR 2017 regulation 24(1)-(3)
Review pending
HM Treasury / legislation.gov.uk
Source diagnostics
Lifecycle
Not recorded
Language
en
Retrieved
11 Sept 2026
Extraction
captured
Latest automated check
12 Oct 2026
Check outcome
unchanged
Evidence review
requires-revalidation
Type
legislation
Version
Revised XML retrieved 2026-09-11; document RestrictStartDate 2026-06-30; individual provisions have different amendment histories
Official original downloaded from https://www.legislation.gov.uk/uksi/2017/692/data.xml to data/country-handbook-evidence/uk/mlr-2017-revised.xml; parsed with Python ElementTree. Web reader rejected XHTML; direct XML succeeded. Inspected provisions and unapplied-effects metadata. Future reg. 34A and Sch. 6 para. 7(ga) are not current duties; metadata also identifies an obsolete 2019 reg. 3(1) effect that requires no application. English official legislative text, not a translation. Version dates are not assigned as commencement dates to compound requirements. Fresh read-only download completed 2026-09-10T19:02:53Z at data/country-handbook-evidence/uk/mlr-2017-entity-expansion-20260910.xml; SHA-256 is identical to the first capture. Entity expansion checked regulations 5, 6, 28, 30(6)-(7), 30A, 30ZA(5), 42-45 (selected information paragraphs) and Schedule 3AZA. See docs/country-handbooks/uk-entity-expansion.md. Core-control re-download at data/country-handbook-evidence/uk/mlr-2017-core-controls-20260910.xml completed 2026-09-10T20:35:30Z with the same SHA-256. Further inspected regulations 19A, 20, 21, 24, 29, 34, 38-41 and 64A-64H. See docs/country-handbooks/uk-coverage-completion.md. Delivery original captured from https://www.legislation.gov.uk/uksi/2017/692/data.xml at 2026-09-11T07:33:37.592Z to data/country-handbook-evidence/uk/mlr-2017-delivery-20260911.xml; SHA-256 694f11c106b2b5328a4bcabf5a2d6f48ac39ec06670302b4e19c20bcfdb70811. Timestamp records local download completion. Official publisher English, not a translation. The original's text was inspected; capture does not imply every provision is verified. Fresh XML parsed with ElementTree: legislative body and commentary are identical to the prior retained original; differences are confined to metadata. Prior originals remain retained.
Recent document checks
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
Evidence diagnostics
Record ID
uk-staff-agent-training
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
requirements
Baseline review status
source checked
Review status
needs review
Effective from
Not recorded
Effective to
Not recorded
No conditions are recorded. This does not establish that none apply.
No exceptions are recorded. This does not establish that none apply.
Apply group controls and address overseas legal barriers · review pendinglegislation / Review pending
Apply group controls and address overseas legal barriers
What this requires
A relevant parent undertaking must apply appropriate AML and proliferation-financing controls across relevant subsidiaries and overseas branches.
RegCanary explanation
Maintain group data-protection and information-sharing policies, including sharing customer, account and transaction information for financial-crime control purposes. For relevant operations in a third country with less strict requirements, apply equivalent measures as far as local law permits; where local law prevents this, notify the UK supervisor and take additional measures to address the risk.
Applicability
Business lines
all
Customer types
all
Stages
all
Supporting provision
MLR 2017 regulation 20(1)-(5)
Review pending
HM Treasury / legislation.gov.uk
Source diagnostics
Lifecycle
Not recorded
Language
en
Retrieved
11 Sept 2026
Extraction
captured
Latest automated check
12 Oct 2026
Check outcome
unchanged
Evidence review
requires-revalidation
Type
legislation
Version
Revised XML retrieved 2026-09-11; document RestrictStartDate 2026-06-30; individual provisions have different amendment histories
Official original downloaded from https://www.legislation.gov.uk/uksi/2017/692/data.xml to data/country-handbook-evidence/uk/mlr-2017-revised.xml; parsed with Python ElementTree. Web reader rejected XHTML; direct XML succeeded. Inspected provisions and unapplied-effects metadata. Future reg. 34A and Sch. 6 para. 7(ga) are not current duties; metadata also identifies an obsolete 2019 reg. 3(1) effect that requires no application. English official legislative text, not a translation. Version dates are not assigned as commencement dates to compound requirements. Fresh read-only download completed 2026-09-10T19:02:53Z at data/country-handbook-evidence/uk/mlr-2017-entity-expansion-20260910.xml; SHA-256 is identical to the first capture. Entity expansion checked regulations 5, 6, 28, 30(6)-(7), 30A, 30ZA(5), 42-45 (selected information paragraphs) and Schedule 3AZA. See docs/country-handbooks/uk-entity-expansion.md. Core-control re-download at data/country-handbook-evidence/uk/mlr-2017-core-controls-20260910.xml completed 2026-09-10T20:35:30Z with the same SHA-256. Further inspected regulations 19A, 20, 21, 24, 29, 34, 38-41 and 64A-64H. See docs/country-handbooks/uk-coverage-completion.md. Delivery original captured from https://www.legislation.gov.uk/uksi/2017/692/data.xml at 2026-09-11T07:33:37.592Z to data/country-handbook-evidence/uk/mlr-2017-delivery-20260911.xml; SHA-256 694f11c106b2b5328a4bcabf5a2d6f48ac39ec06670302b4e19c20bcfdb70811. Timestamp records local download completion. Official publisher English, not a translation. The original's text was inspected; capture does not imply every provision is verified. Fresh XML parsed with ElementTree: legislative body and commentary are identical to the prior retained original; differences are confined to metadata. Prior originals remain retained.
Recent document checks
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
Evidence diagnostics
Record ID
uk-group-controls
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
requirements
Baseline review status
source checked
Review status
needs review
Effective from
Not recorded
Effective to
Not recorded
No conditions are recorded. This does not establish that none apply.
No exceptions are recorded. This does not establish that none apply.
Assess whether proposed handling of property would conceal, disguise, convert, transfer or remove criminal property, facilitate its acquisition, retention, use or control, or involve its acquisition, use or possession.
RegCanary explanation
Criminal property includes a benefit from criminal conduct, or property representing that benefit, where the person knows or suspects its criminal character. The offences and their mental elements differ. A routine SAR does not by itself authorise an otherwise prohibited act; assess an applicable defence or statutory exception before proceeding.
Applicability
Business lines
all
Customer types
all
Stages
all
Supporting provision
POCA 2002 sections 327(1)-(2B), 328(1)-(4), 329(1)-(4), 338 and 340(2)-(3), (9)-(11)
Review pending
UK Parliament / legislation.gov.uk
Source diagnostics
Lifecycle
Not recorded
Language
en
Retrieved
11 Sept 2026
Extraction
captured
Latest automated check
12 Oct 2026
Check outcome
unchanged
Evidence review
requires-revalidation
Type
legislation
Version
Official provision-scoped revised XML; root RestrictStartDate 2026-06-30; captured 11 September 2026
Original downloaded unchanged to data/country-handbook-evidence/uk/poca-part-7-delivery-20260911.xml. SHA-256 a4b5f9ad5ebf63c86e39a89a6b2ca1c08cfbe9acec717d1df9f22f834116f4fa; capture completion 2026-09-11T07:39:46.896Z. English national original, not a translation. Selected mapped text matches the corresponding full revised XML provisions at the same version. ElementTree reference check found no missing commentary targets; current extractCountrySource returned extracted-text, source-provision-identifiers and no warnings. This scoped original avoids, but does not resolve or approve, the full-document section 195S annotation defect. No effective date inferred from the root version or capture date.
Recent document checks
: unchanged, document 8204b9bb6342
: unchanged, document 8204b9bb6342
: unchanged, document 8204b9bb6342
: unchanged, document 8204b9bb6342
: unchanged, document 8204b9bb6342
Evidence diagnostics
Record ID
uk-poca-criminal-property
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
requirements
Baseline review status
source checked
Review status
needs review
Effective from
Not recorded
Effective to
Not recorded
No conditions are recorded. This does not establish that none apply.
No exceptions are recorded. This does not establish that none apply.
Resolve the designation and the applicable sanctions measure · review pendingimplementation / Review pending
Resolve the designation and the applicable sanctions measure
What this requires
Use the current UK Sanctions List to identify published designations and their measures, then check the governing regulation and any applicable ownership or control rules.
RegCanary explanation
The list is the official published source for UK sanctions designations following closure of the OFSI Consolidated List on 28 January 2026. It is not itself a universal asset-freeze rule. Under the Russia Regulations the Secretary of State can designate for different purposes; only designation for regulations 11 to 15 supplies the designated-person definition for those asset-freeze provisions. Publicity can be restricted in the statutory circumstances. The publication also identifies a separate Russia list for certain financial and investment restrictions.
Applicability
Business lines
all
Customer types
all
Stages
all
Supporting provision
Russia Regulations 5(1)-(3), 8(1)-(2), (6)-(9), 10; SAMLA 2018 sections 1(1), 3(1), 21; FCDO UK Sanctions List publication: opening notice and 'Russia: list of entities named in relation to financial and investment restrictions'; OFSI general guidance sections 2.2 and 4
Baseline document
Secretary of State / legislation.gov.uk
Source diagnostics
Lifecycle
Not recorded
Language
en
Retrieved
10 Sept 2026
Extraction
captured
Latest automated check
12 Oct 2026
Check outcome
unchanged
Evidence review
unvalidated
Type
legislation
Version
Official revised XML captured 11 September 2026 London time; document RestrictStartDate 2026-05-20
Original downloaded to data/country-handbook-evidence/uk/russia-sanctions-revised-20260911.xml. ElementTree extraction checked regulations 2-3, 5, 7-8, 10-15, 19, 58, 64, 66-67, 70-71 and 79(3), (6), Schedule 1 and selected Schedule 5 paragraphs. No future RestrictStartDate nodes or Unapplied metadata elements found in the downloaded snapshot; this is not a comprehensive amendment/legal-perimeter audit. These source_checked additions map only the stated Russia-regime provisions, not all sectoral sanctions or all UK regimes. Native English statutory original, not a translation. Freeze recheck: official original recaptured unchanged at data/country-handbook-evidence/uk/russia-sanctions-freeze-20260911.xml, 2026-09-11T07:50:08.614Z; SHA-256 146f749d478109c2e8c72d7620eaab8dbe1352d270d35828e95566935573e99f matches the retained source. Further inspected regulations 18A, 70(1ZA)-(1ZB), (3)-(4), (7), 71 and 79(3), (5)-(6).
Recent document checks
: unchanged, document 146f749d4781
: unchanged, document 146f749d4781
: unchanged, document 146f749d4781
: unchanged, document 146f749d4781
: unchanged, document 146f749d4781
Review pending
UK Parliament / legislation.gov.uk
Source diagnostics
Lifecycle
Not recorded
Language
en
Retrieved
10 Sept 2026
Extraction
captured
Latest automated check
12 Oct 2026
Check outcome
unchanged
Evidence review
requires-revalidation
Type
legislation
Version
Official revised XML captured 11 September 2026 London time; document RestrictStartDate 2025-10-16
Original downloaded to data/country-handbook-evidence/uk/samla-2018-revised-20260911.xml. ElementTree extraction checked sections 1(1), 3(1), 21 and 60. The enabling framework is distinguished from the actual prohibitions in regime regulations. No source publication, snapshot or capture date is assigned as commencement of a compound requirement. Native English statutory original; not a complete SAMLA review.
Recent document checks
: unchanged, document 23c852a64b23
: unchanged, document 23c852a64b23
: unchanged, document 23c852a64b23
: unchanged, document 23c852a64b23
: unchanged, document 23c852a64b23
Review pending
Foreign, Commonwealth & Development Office
Source diagnostics
Lifecycle
Not recorded
Language
en
Retrieved
10 Sept 2026
Extraction
captured
Latest automated check
12 Oct 2026
Check outcome
unchanged
Evidence review
requires-revalidation
Type
sanctions
Version
Live publication page; 28 January 2026 change notice confirms OFSI Consolidated List closure
Publication-page evidence only, not a downloaded designation dataset. UK Sanctions List is the current designation source; the old OFSI Consolidated List is no longer updated. List-change date is not a commencement date for sanctions prohibitions. Original HTML now captured at data/country-handbook-evidence/uk/fcdo-sanctions-list-20260911.html on 11 September 2026 London time (2026-09-10T23:43:05Z UTC). Parsed using HTMLParser excluding scripts/styles. The hash is of the original response bytes, not extracted text. Rechecked the single-list notice and separate Russia financial/investment-list notice; this capture is the publication page, not a downloaded designation dataset or case-match verification.
Recent document checks
: unchanged, document 6cdec4038406
: unchanged, document 6cdec4038406
: changed, document 6cdec4038406
: changed, document 313c54fb15e8
: changed, document b5ee89013398
Review pending
Office of Financial Sanctions Implementation / HM Treasury
Web-fetched official English guidance; chapters 2-6 inspected selectively. The earlier capture was web-only. Underlying sanctions instruments, particular licences and individual designations are not exhaustively checked. Original HTML now captured at data/country-handbook-evidence/uk/ofsi-general-20260911.html on 11 September 2026 London time (2026-09-10T23:43:04Z UTC). Parsed using HTMLParser excluding scripts/styles. The hash is of the original response bytes, not extracted text. Rechecked the cryptoasset/dealing definitions, reporting and frozen-account/exception passages supporting the bounded Russia additions.
Recent document checks
: unchanged, document cb2c88de51e0
: unchanged, document cb2c88de51e0
: unchanged, document cb2c88de51e0
: unchanged, document cb2c88de51e0
: unchanged, document cb2c88de51e0
Evidence diagnostics
Record ID
uk-sanctions-designation-measures
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
requirements
Baseline review status
source checked
Review status
needs review
Effective from
Not recorded
Effective to
Not recorded
No conditions are recorded. This does not establish that none apply.
No exceptions are recorded. This does not establish that none apply.
Check the activity-specific AML supervisor and register · review pendinglegislation / Review pending
Check the activity-specific AML supervisor and register
What this requires
Where regulation 54 requires a registering authority to maintain a register for the firm's activity, do not carry on an activity listed in regulation 56(1) without inclusion in the appropriate register unless a statutory exception applies.
RegCanary explanation
Regulation 7 allocates supervision by activity and legal status, including FCA supervision of qualifying credit and financial institutions, electronic money institutions and cryptoasset exchange or custodian wallet providers, and HMRC supervision of specified money services not supervised by the FCA. This is distinct from a firm's trading label. Apply the registration prohibition to the actual registerable activity; a bank's general authorisation and a crypto firm's AML registration are not interchangeable.
Applicability
Business lines
all
Customer types
all
Stages
all
Supporting provision
MLR 2017 regulations 7(1)-(6), 54(1)-(2), 56(1)-(5) and 56A
Review pending
HM Treasury / legislation.gov.uk
Source diagnostics
Lifecycle
Not recorded
Language
en
Retrieved
11 Sept 2026
Extraction
captured
Latest automated check
12 Oct 2026
Check outcome
unchanged
Evidence review
requires-revalidation
Type
legislation
Version
Revised XML retrieved 2026-09-11; document RestrictStartDate 2026-06-30; individual provisions have different amendment histories
Official original downloaded from https://www.legislation.gov.uk/uksi/2017/692/data.xml to data/country-handbook-evidence/uk/mlr-2017-revised.xml; parsed with Python ElementTree. Web reader rejected XHTML; direct XML succeeded. Inspected provisions and unapplied-effects metadata. Future reg. 34A and Sch. 6 para. 7(ga) are not current duties; metadata also identifies an obsolete 2019 reg. 3(1) effect that requires no application. English official legislative text, not a translation. Version dates are not assigned as commencement dates to compound requirements. Fresh read-only download completed 2026-09-10T19:02:53Z at data/country-handbook-evidence/uk/mlr-2017-entity-expansion-20260910.xml; SHA-256 is identical to the first capture. Entity expansion checked regulations 5, 6, 28, 30(6)-(7), 30A, 30ZA(5), 42-45 (selected information paragraphs) and Schedule 3AZA. See docs/country-handbooks/uk-entity-expansion.md. Core-control re-download at data/country-handbook-evidence/uk/mlr-2017-core-controls-20260910.xml completed 2026-09-10T20:35:30Z with the same SHA-256. Further inspected regulations 19A, 20, 21, 24, 29, 34, 38-41 and 64A-64H. See docs/country-handbooks/uk-coverage-completion.md. Delivery original captured from https://www.legislation.gov.uk/uksi/2017/692/data.xml at 2026-09-11T07:33:37.592Z to data/country-handbook-evidence/uk/mlr-2017-delivery-20260911.xml; SHA-256 694f11c106b2b5328a4bcabf5a2d6f48ac39ec06670302b4e19c20bcfdb70811. Timestamp records local download completion. Official publisher English, not a translation. The original's text was inspected; capture does not imply every provision is verified. Fresh XML parsed with ElementTree: legislative body and commentary are identical to the prior retained original; differences are confined to metadata. Prior originals remain retained.
Recent document checks
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
Evidence diagnostics
Record ID
uk-activity-supervision-registration
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
requirements
Baseline review status
source checked
Review status
needs review
Effective from
Not recorded
Effective to
Not recorded
No conditions are recorded. This does not establish that none apply.
No exceptions are recorded. This does not establish that none apply.
Notify the FCA of money-service or trust/company-service activity · review pendinglegislation / Review pending
Notify the FCA of money-service or trust/company-service activity
What this requires
An FCA-supervised authorised person must notify the FCA before, or within 28 days of, starting money-service or trust/company-service activity and within 28 days of stopping it.
RegCanary explanation
After information has been provided under regulation 23, notify a material change or correct an inaccuracy within 30 days of the change or discovery. Use the form and verification method specified by the FCA. The notification duty is separate from any applicable registration or authorisation restriction; its 28-day notification window does not override those restrictions.
Applicability
Business lines
all
Customer types
all
Stages
all
Supporting provision
MLR 2017 regulation 23(1)-(5)
Review pending
HM Treasury / legislation.gov.uk
Source diagnostics
Lifecycle
Not recorded
Language
en
Retrieved
11 Sept 2026
Extraction
captured
Latest automated check
12 Oct 2026
Check outcome
unchanged
Evidence review
requires-revalidation
Type
legislation
Version
Revised XML retrieved 2026-09-11; document RestrictStartDate 2026-06-30; individual provisions have different amendment histories
Official original downloaded from https://www.legislation.gov.uk/uksi/2017/692/data.xml to data/country-handbook-evidence/uk/mlr-2017-revised.xml; parsed with Python ElementTree. Web reader rejected XHTML; direct XML succeeded. Inspected provisions and unapplied-effects metadata. Future reg. 34A and Sch. 6 para. 7(ga) are not current duties; metadata also identifies an obsolete 2019 reg. 3(1) effect that requires no application. English official legislative text, not a translation. Version dates are not assigned as commencement dates to compound requirements. Fresh read-only download completed 2026-09-10T19:02:53Z at data/country-handbook-evidence/uk/mlr-2017-entity-expansion-20260910.xml; SHA-256 is identical to the first capture. Entity expansion checked regulations 5, 6, 28, 30(6)-(7), 30A, 30ZA(5), 42-45 (selected information paragraphs) and Schedule 3AZA. See docs/country-handbooks/uk-entity-expansion.md. Core-control re-download at data/country-handbook-evidence/uk/mlr-2017-core-controls-20260910.xml completed 2026-09-10T20:35:30Z with the same SHA-256. Further inspected regulations 19A, 20, 21, 24, 29, 34, 38-41 and 64A-64H. See docs/country-handbooks/uk-coverage-completion.md. Delivery original captured from https://www.legislation.gov.uk/uksi/2017/692/data.xml at 2026-09-11T07:33:37.592Z to data/country-handbook-evidence/uk/mlr-2017-delivery-20260911.xml; SHA-256 694f11c106b2b5328a4bcabf5a2d6f48ac39ec06670302b4e19c20bcfdb70811. Timestamp records local download completion. Official publisher English, not a translation. The original's text was inspected; capture does not imply every provision is verified. Fresh XML parsed with ElementTree: legislative body and commentary are identical to the prior retained original; differences are confined to metadata. Prior originals remain retained.
Recent document checks
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
Evidence diagnostics
Record ID
uk-fca-msb-tcsp-notification
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
requirements
Baseline review status
source checked
Review status
needs review
Effective from
Not recorded
Effective to
Not recorded
No conditions are recorded. This does not establish that none apply.
No exceptions are recorded. This does not establish that none apply.
Apply binding FCA AML controls under the SYSC 6 route · review pendinglegislation / Review pending
Apply binding FCA AML controls under the SYSC 6 route
What this requires
For a Handbook firm and activity within SYSC 6.3, maintain proportionate AML systems, assess their adequacy regularly, allocate senior responsibility and appoint an appropriately empowered MLRO where the appointment rule applies.
RegCanary explanation
SYSC 6.3.1R and 6.3.3R require systems that identify, assess, monitor and manage money-laundering risk and regular adequacy assessments. Under 6.3.8R allocate overall AML responsibility to a director or senior manager, who may also be the MLRO, but not to a person approved for the other overall responsibility function. Under 6.3.9R the MLRO needs sufficient authority, independence, resources and information. SYSC 6.1.1R separately requires adequate regulatory-compliance and financial-crime policies covering the firm, managers, employees and appointed representatives or tied agents. Its organisational-rule scope is broader than the defined common-platform financial-crime requirements; do not apply the narrower SYSC 6.3 exclusions to it automatically. An annual MLRO report under 6.3.7G remains guidance, not the frequency imposed by the regular-assessment rule.
Applicability
Business lines
all
Customer types
all
Stages
all
Supporting provision
SYSC 6.1.1R; 6.3.1R, 6.3.3R, 6.3.8R-6.3.9R; SYSC 1 Annex 1 2.1R-2.6ER, 2.8R, 2.11R-2.13BR, 2.15R-2.18AG, 3.1G-3.3R, Table A and Table B rows for 6.1.1 and 6.3.1/3/8/9; Glossary firm (1), authorised person; SYSC 1.1A.1BG
Earlier web-fetched HTML content checked. Section contains both R rules and G guidance: source kind is a schema-level categorisation, not a claim that R provisions are optional. Handbook rule application is not determined solely by a business-line label. No effective dates inferred from the page update date. Delivery original captured from https://handbook.fca.org.uk/handbook/sysc6/sysc6s3 at 2026-09-11T07:29:04.210Z to data/country-handbook-evidence/uk/uk-fca-sysc-6-3-delivery-20260911.html; SHA-256 382b86f56862df89c3f7a9004ffa643fa1265e1af26a056af58559b49f227f1d. Timestamp records local download completion. Official publisher English, not a translation. The original's text was inspected; capture does not imply every provision is verified. Freeze recheck: official original recaptured unchanged at data/country-handbook-evidence/uk/fca-sysc6-3-freeze-20260911.html, 2026-09-11T07:51:54.218Z; SHA-256 382b86f56862df89c3f7a9004ffa643fa1265e1af26a056af58559b49f227f1d matches the retained source. Binding R provisions 6.3.1, 6.3.3, 6.3.8 and 6.3.9 checked separately from G guidance.
Recent document checks
: unchanged, document 22af8b3a868d
: unchanged, document 22af8b3a868d
: unchanged, document 22af8b3a868d
: unchanged, document 22af8b3a868d
: unchanged, document 22af8b3a868d
Review pending
Financial Conduct Authority
Source diagnostics
Lifecycle
Not recorded
Language
en
Retrieved
11 Sept 2026
Extraction
captured
Latest automated check
12 Oct 2026
Check outcome
unchanged
Evidence review
requires-revalidation
Type
legislation
Version
Live official section captured 11 September 2026; displayed page update 23/10/2025; provision dates differ
Official English original HTML downloaded unchanged to data/country-handbook-evidence/uk/fca-sysc6-1-freeze-20260911.html; SHA-256 722dd46cc106986ca59c6afc26504c1aa51e746b6987ea0d94297cbb5a841abe; capture completion 2026-09-11T07:50:07.593Z. Parsed with Cheerio preserving table rows/cells for application mapping. National regulator original, not a translation. Schema kind legislation denotes binding Handbook rules/definitions, not an Act of Parliament; G guidance remains non-binding. Checked the cited R provisions and distinguished related G guidance. No displayed update or capture date is assigned as a compound duty's effective date.
Recent document checks
: unchanged, document ecb378a9e205
: unchanged, document ecb378a9e205
: unchanged, document ecb378a9e205
: unchanged, document ecb378a9e205
: unchanged, document ecb378a9e205
Review pending
Financial Conduct Authority
Source diagnostics
Lifecycle
Not recorded
Language
en
Retrieved
11 Sept 2026
Extraction
captured
Latest automated check
12 Oct 2026
Check outcome
unchanged
Evidence review
requires-revalidation
Type
legislation
Version
Live official section captured 11 September 2026; displayed page update 29/05/2026; provision dates differ
Official English original HTML downloaded unchanged to data/country-handbook-evidence/uk/fca-sysc1-full-freeze-20260911.html; SHA-256 18df81cbf35f1f7ef6bf8c480345e9b677a4213b24ae7fd4d2627a53786871ec; capture completion 2026-09-11T07:50:07.303Z. Parsed with Cheerio preserving table rows/cells for application mapping. National regulator original, not a translation. Schema kind legislation denotes binding Handbook rules/definitions, not an Act of Parliament; G guidance remains non-binding. Checked SYSC 1.1A.1G-1BG, Annex 1 Parts 1-3, Table A columns A/A+/A++/B and Table B columns A/B for SYSC 6.1.1 and 6.3.1/3/8/9. The displayed 25 October 2027 future version is not used as current law. No displayed update or capture date is assigned as a compound duty's effective date.
Recent document checks
: unchanged, document 89d70b43b06b
: unchanged, document 89d70b43b06b
: unchanged, document 89d70b43b06b
: unchanged, document 89d70b43b06b
: unchanged, document 89d70b43b06b
Review pending
Financial Conduct Authority
Source diagnostics
Lifecycle
Not recorded
Language
en
Retrieved
11 Sept 2026
Extraction
captured
Latest automated check
12 Oct 2026
Check outcome
unchanged
Evidence review
requires-revalidation
Type
legislation
Version
Live official glossary entry captured 11 September 2026; no separate edition date asserted
Official English original HTML downloaded unchanged to data/country-handbook-evidence/uk/fca-glossary-firm-freeze-20260911.html; SHA-256 37ea994b0ab1626da9d0ba23256f6fa8b901cfb01d8f8f0fae867381812962ed; capture completion 2026-09-11T07:50:29.749Z. Parsed with Cheerio preserving table rows/cells for application mapping. National regulator original, not a translation. Schema kind legislation denotes binding Handbook rules/definitions, not an Act of Parliament; G guidance remains non-binding. Checked the definition and section-specific extensions; payment-services/e-money permission and MLR registration do not themselves establish the general SYSC firm definition. No displayed update or capture date is assigned as a compound duty's effective date.
Recent document checks
: unchanged, document 6093006d0f42
: unchanged, document 6093006d0f42
: unchanged, document 6093006d0f42
: unchanged, document 6093006d0f42
: unchanged, document 6093006d0f42
Review pending
Financial Conduct Authority
Source diagnostics
Lifecycle
Not recorded
Language
en
Retrieved
11 Sept 2026
Extraction
captured
Latest automated check
12 Oct 2026
Check outcome
unchanged
Evidence review
requires-revalidation
Type
legislation
Version
Live official glossary entry captured 11 September 2026; no separate edition date asserted
Official English original HTML downloaded unchanged to data/country-handbook-evidence/uk/fca-glossary-authorised-person-freeze-20260911.html; SHA-256 97ccc8793a8ba076e79a943c06c0fbd9a27412b7286f1a9a0b7766f2989aa31f; capture completion 2026-09-11T07:50:50.541Z. Parsed with Cheerio preserving table rows/cells for application mapping. National regulator original, not a translation. Schema kind legislation denotes binding Handbook rules/definitions, not an Act of Parliament; G guidance remains non-binding. Checked the definition and section-specific extensions; payment-services/e-money permission and MLR registration do not themselves establish the general SYSC firm definition. No displayed update or capture date is assigned as a compound duty's effective date.
Recent document checks
: unchanged, document e2bd4887e2d0
: unchanged, document e2bd4887e2d0
: unchanged, document e2bd4887e2d0
: unchanged, document e2bd4887e2d0
: unchanged, document e2bd4887e2d0
Evidence diagnostics
Record ID
uk-fca-sysc6-binding-aml
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
requirements
Baseline review status
source checked
Review status
needs review
Effective from
Not recorded
Effective to
Not recorded
No conditions are recorded. This does not establish that none apply.
No exceptions are recorded. This does not establish that none apply.
Denmark
Protect investigation and reporting confidentialitylegislation
Protect investigation and reporting confidentiality
What this requires
Do not disclose that an AML investigation or report exists, is planned or is being considered, except under a specific lawful disclosure route.
RegCanary explanation
Section 38(1) applies to the obliged firm, management, employees and relevant persons carrying out special duties. It covers section 25 investigations and section 26 reports, including contemplated action. This remains relevant to customer-facing offboarding notices. Sections 25(4) and 26(7) restrict subject access to the specified investigation/reporting personal data; they do not erase all other customer data rights. Permitted regulator, law-enforcement, group and same-customer/same-transaction disclosures have distinct statutory conditions.
Applicability
Business lines
all
Customer types
all
Stages
onboarding, ongoing, investigation, offboarding
Supporting provision
LBK 433/2026 section 38(1)-(8), pp. 13-14; section 25(4), p. 9; section 26(7), p. 10
Downloaded original: data/country-handbook-evidence/dk/lbk-433-2026.pdf, 35 pages; inspected with pdftotext. Current reference is supported by the live Finanstilsynet index. The consolidation includes the amendment to section 38 b from Act 1638/2025 and explains the revoked, unincorporated amendment from Act 712/2025. Publication on 21 April 2026 is NOT treated as the commencement of all provisions. The JavaScript landing page did not expose amendment-status metadata. The bounded follow-up verified promulgated Act 764/2026 and its 15 September commencement; see the promulgated Act 764/2026 and the dated governance-review limitation. Danish original governs; English summaries are editorial, not an official translation.
Recent document checks
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
Conditions
Only section 1 obliged activities and the persons described by section 38. Review access requests and customer communications for protected information without treating confidentiality as a blanket exemption from all explanation duties.
Exceptions
Section 38(2) permits specified requested disclosures for supervision/enforcement; subsections 3-6 provide conditional group/professional and same-customer/same-transaction routes. Check recipient, purpose, jurisdiction, confidentiality and data protection before disclosure.
Evidence diagnostics
Record ID
dk-confidentiality
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
requirements
Status when reviewed
current
Review status
source checked
Effective from
Not recorded
Effective to
Not recorded
Give AML privacy information and retain then delete the correct recordslegislation
Give AML privacy information and retain then delete the correct records
What this requires
Inform individual customers before onboarding about AML personal-data processing; retain required AML records for at least five years after termination and delete personal data at five years unless another law provides otherwise.
RegCanary explanation
Section 16 requires advance information for natural-person relationships/occasional transactions and limits AML-collected personal data to AML/CTF purposes, excluding commercial reuse. Section 30 covers CDD identity/control records and copies of presented ID, transaction documentation, account overviews, business correspondence and investigation records. The five-year clock runs from relationship end or the occasional transaction, not merely the last CDD update. Section 30(3) requires secure, confidential responses to competent-authority queries about current and past-five-year relationships. 'At least five years' is not permission to retain personal data indefinitely.
Applicability
Business lines
all
Customer types
all
Stages
onboarding, ongoing, investigation, offboarding
Supporting provision
LBK 433/2026 section 16(1)-(2), p. 7; section 30(1)-(3), p. 11
Downloaded original: data/country-handbook-evidence/dk/lbk-433-2026.pdf, 35 pages; inspected with pdftotext. Current reference is supported by the live Finanstilsynet index. The consolidation includes the amendment to section 38 b from Act 1638/2025 and explains the revoked, unincorporated amendment from Act 712/2025. Publication on 21 April 2026 is NOT treated as the commencement of all provisions. The JavaScript landing page did not expose amendment-status metadata. The bounded follow-up verified promulgated Act 764/2026 and its 15 September commencement; see the promulgated Act 764/2026 and the dated governance-review limitation. Danish original governs; English summaries are editorial, not an official translation.
Recent document checks
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
Conditions
Only section 1 obliged activities. The advance customer-information duty in section 16(1) is for natural-person customers; the personal-data purpose restriction also protects natural persons recorded for entity customers.
Data items are evidence/retention categories, not a requirement to collect documents never used or relevant to the case.
Exceptions
Another law may require different personal-data retention; identify that legal basis before extending retention. A generic internal policy or business interest is not the exception stated in section 30(2).
Evidence diagnostics
Record ID
dk-data-retention
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
requirements
Status when reviewed
current
Review status
source checked
Effective from
Not recorded
Effective to
Not recorded
Maintain transfer controls, records and protected reporting channelslegislation
Maintain transfer controls, records and protected reporting channels
What this requires
Implement Union and national restrictive-measures controls, respond promptly to authorised requests and protect transfer information throughout its retention and use.
RegCanary explanation
Article 23 requires internal policies, procedures and controls to implement Union and national restrictive measures for covered transfers. Article 24 requires full and immediate responses, in accordance with national procedural requirements, exclusively to requests from the competent domestic AML/TF authorities for information under the regulation. Article 25 applies the GDPR, restricts processing under this regulation to AML/TF prevention, prohibits commercial use of those data and requires clear advance information to new customers before a relationship or occasional transaction. Transfers of personal data must comply with the GDPR. Article 26 requires the payer's and payee's providers to retain the Article 4-7 records, and the originator's and beneficiary's crypto providers to retain the Article 14-16 records, for five years and then delete personal data unless a justified national retention rule applies; the permitted additional period cannot exceed five years. Do not infer an automatic ten-year retention period. Article 32(2) requires suitable internal procedures, in cooperation with competent authorities, allowing employees or persons in a comparable position to report infringements through a secure, independent, specific and anonymous channel proportionate to the provider's nature and size.
Applicability
Business lines
all
Customer types
all
Stages
onboarding, ongoing, investigation, offboarding
Supporting provision
Regulation 2023/1113 Articles 23-26, 32(2), pp. 25-27, 29
Retained original: data/country-handbook-evidence/dk/eu-tfr-2023-1113-da-20260911.pdf; 771970 bytes. Capture timestamp records original-file acquisition in UTC (11 September 2026 local time). Authentic Danish OJ. Inspected Articles 2-13, 23-26, 32(2), 35 and 39-40, pp. 13-21, 25-30, 36. Live document-information original retained as 32023R1113-currentness-20260911.html. German/Spanish corrigenda and the future Article 38 change do not amend the mapped Danish payment-provider provisions. Article 4(2)(c) contains a payer/payee wording issue in Danish; no universal natural-person LEI duty is inferred. EBA/GL/2024/11 and technical message implementation remain separate review items.
Recent document checks
: unchanged, document 523a600af229
: unchanged, document 523a600af229
: unchanged, document 523a600af229
: unchanged, document 523a600af229
: failed, document 523a600af229
Conditions
The five-year rule stated here covers payer/payee providers and originator/beneficiary crypto providers under Article 26(1). Determine any additional Danish retention basis separately and reconcile it with existing AML records; this is not a new invented retention start date.
Operational fields are evidence aids, not a universal statutory report template. The internal anonymous channel is not an FIU submission engine.
Apply only when the undertaking acts in the provider role specified here for a covered transfer. The same rule covers individual, company and trust customers; an activity label alone does not establish that role.
Exceptions
No bank's GDPR transfer mechanism, retention scheduler, authority-response channel or control effectiveness is validated by this mapping.
Evidence diagnostics
Record ID
dk-tfr-controls-records-privacy
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
requirements
Status when reviewed
current
Review status
source checked
Effective from
30 Dec 2024
Effective to
Not recorded
Apply the specific cash and anonymous prepaid restrictionslegislation
Apply the specific cash and anonymous prepaid restrictions
What this requires
Do not redeem anonymous third-country prepaid cards or use EUR 500 notes in Denmark; handle suspected counterfeit cash under its own rule.
RegCanary explanation
Section 5a prohibits redemption in Denmark of payments made with anonymous prepaid cards issued in third countries, including cash redemption of residual value and cash withdrawals of the card's value. Section 6a prohibits using, issuing, depositing, exchanging, paying with or transferring EUR 500 notes in Denmark. Businesses handling and distributing notes and coins must remove known or suspected counterfeits from circulation and immediately hand them to police under section 6; euro cash follows the EU rule identified in subsection 2. These specific controls do not mean every cash transaction is suspicious. Section 5's DKK 15,000 cash-receipt prohibition applies to businesses outside section 1(1), not as a general bank deposit ceiling.
Applicability
Business lines
all
Customer types
all
Stages
onboarding, ongoing, investigation, offboarding
Supporting provision
LBK 433/2026 sections 1(2)-(4), p. 2; 5, 5a, 6(1)-(2), 6a, p. 4
Downloaded original: data/country-handbook-evidence/dk/lbk-433-2026.pdf, 35 pages; inspected with pdftotext. Current reference is supported by the live Finanstilsynet index. The consolidation includes the amendment to section 38 b from Act 1638/2025 and explains the revoked, unincorporated amendment from Act 712/2025. Publication on 21 April 2026 is NOT treated as the commencement of all provisions. The JavaScript landing page did not expose amendment-status metadata. The bounded follow-up verified promulgated Act 764/2026 and its 15 September commencement; see the promulgated Act 764/2026 and the dated governance-review limitation. Danish original governs; English summaries are editorial, not an official translation.
Recent document checks
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
Conditions
Apply each rule to its stated activity and territorial scope; the EUR 500 note rule applies to all natural and legal persons in Denmark. No automated cash-handling or fraud engine is part of this handbook.
Evidence diagnostics
Record ID
dk-cash-and-anonymous-prepaid-controls
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
requirements
Status when reviewed
current
Review status
source checked
Effective from
Not recorded
Effective to
Not recorded
No exceptions are recorded. This does not establish that none apply.
Maintain AML, proliferation-risk and sanctions controls from 15 September 2026legislation
Maintain AML, proliferation-risk and sanctions controls from 15 September 2026
What this requires
From 15 September 2026, retain the AML framework and add the enacted proliferation-risk assessment, financial-sanctions controls and applicable independent-testing branch.
RegCanary explanation
Read LBK 433/2026 with Act 764/2026 section 1. Section 7(1) retains the documented, continuously updated business-model ML/TF assessment across customers, products, services, transactions, delivery channels and geographies, and adds risk of potential breaches, non-implementation or circumvention of proliferation-financing obligations in laws/regulations concerning countries, persons, groups, legal entities or bodies and section 34a(3). New section 4a defines proliferation financing as supplying funds or financial services for the listed nuclear, chemical or biological weapon activities for illegitimate purposes contrary to national law or international obligations. Section 8(1) retains written AML risk-management, CDD, investigation, recording, reporting, retention, employee-screening and internal controls and adds adequate written policies, procedures and controls for financial-sanctions compliance, including section 34a(3). Proliferation-compliance controls must also follow the section 7 assessment, taking business size into account. Section 8(2) approval and section 8(6) staff/management training, including relevant data protection, continue. Under existing section 8(4) sentence 1, boards of section 1(1) nos. 1-7 businesses that have internal audit (excluding their domestic branches, distributors and agents), and boards of other covered businesses legally required to have internal audit, ensure internal audit assesses the design and functioning of the framework. Added sentences 2-3 require covered businesses/persons outside that first branch, excluding their domestic branches, distributors and agents, to have their policies, procedures and controls tested by an independent audit function; if none exists, an external expert may perform the test.
Applicability
Business lines
all
Customer types
all
Stages
all
Supporting provision
LBK 433/2026 sections 7(1)-(2), 8(1)-(2), 8(4), 8(6), pp. 4-5; Act 764/2026 section 1 nos. 1-4 (new section 4a and amended sections 7/8), p. 1, section 20(1)-(2) and section 21, p. 8
Downloaded original: data/country-handbook-evidence/dk/lbk-433-2026.pdf, 35 pages; inspected with pdftotext. Current reference is supported by the live Finanstilsynet index. The consolidation includes the amendment to section 38 b from Act 1638/2025 and explains the revoked, unincorporated amendment from Act 712/2025. Publication on 21 April 2026 is NOT treated as the commencement of all provisions. The JavaScript landing page did not expose amendment-status metadata. The bounded follow-up verified promulgated Act 764/2026 and its 15 September commencement; see the promulgated Act 764/2026 and the dated governance-review limitation. Danish original governs; English summaries are editorial, not an official translation.
Recent document checks
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
Baseline document
Retsinformation / Skatte- og Vaekstministeriet
Source diagnostics
Lifecycle
Not recorded
Language
da
Retrieved
10 Sept 2026
Extraction
captured
Latest automated check
20 Sept 2026
Check outcome
unchanged
Evidence review
unvalidated
Type
legislation
Version
LOV nr 764 af 08/09/2026; Lovtidende A published 09/09/2026
Original data/country-handbook-evidence/dk/lov-764-2026.pdf. Royal assent/publication verified on p. 1 and signature p. 8; Folketinget L9 page identifies this Act. Inspected section 1 nos. 1-8, pp. 1-2; section 7, p. 5; section 20, p. 8. Relevant AML additions commence 15 September 2026 under section 20(1); only section 8 no. 1 and section 16 no. 1 defer to 20 November. The successor dk-governance-risk-20260915 maps selected governance duties effective from 15 September 2026 and is classified current from that commencement date. The baseline's dated review boundary remains; this does not establish a complete or independently reviewed current legal position. No change to mapped AML identity/reporting/offboarding sections or consumer Payment Accounts Act sections 11/13 was found in these amendment provisions. Not an exhaustive audit of all legislation.
Recent document checks
: unchanged, document e4d520035310
: unchanged, document e4d520035310
: unchanged, document e4d520035310
: unchanged, document e4d520035310
: unchanged, document e4d520035310
Conditions
The existing AML policies, controls and procedures must be based on the section 7 risk assessment, taking the size of the business into account, under the retained second sentence of section 8(1). This duty is separate from the added proliferation-control duty and does not create a risk-based exemption from financial-sanctions prohibitions.
All means only financial activities actually in section 1: banking, covered investment activities, payment services under Payment Act Annex 1 nos. 1-7 and e-money, and defined cryptoasset service providers. Funds/managers in section 1(1) nos. 9-10 require direct customer contact; statutory exemptions must be checked.
Approval under section 8(2) is by the section 7(2) designated person where that designation duty applies; domestic branches, distributors and agents are excluded from section 7(2)'s designation duty.
Versioned successor for the selected governance duties only. Section 20(1) brought these section 1 amendments into force on 15 September 2026; section 20(2)'s 20 November deferral concerns section 8 no. 1 and section 16 no. 1 of the amending Act, not its AML section 1.
These additions are not operative before 15 September 2026. This explanation covers the inspected provisions, not every governance duty or later amendment.
Financial-sanctions control duties do not themselves supply an asset-release authorisation, a complete regime/list inventory or evidence that an operational control has been implemented. Denmark only: section 21 excludes automatic application to Greenland and the Faroe Islands.
Exceptions
Section 7(3) permits rules creating exemptions; this entry does not establish eligibility for any exemption.
Apply the two section 8(4) branches using the firm's actual perimeter and audit arrangements. The added branch is not a universal duty to hire an external auditor. No annual testing interval, prescribed vendor or risk-based exemption from the added testing duty is stated in the inspected amendment.
Evidence diagnostics
Record ID
dk-governance-risk-20260915
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
requirements
Status when reviewed
current
Review status
source checked
Effective from
15 Sept 2026
Effective to
Not recorded
Determine AML scope from the financial activitylegislation
Determine AML scope from the financial activity
What this requires
Apply shared AML controls to the covered activity, not merely to a banking, wealth or fintech label.
RegCanary explanation
Section 1 covers banks, mortgage lenders, investment firms, life insurers and relevant intermediaries, e-money issuers and payment services in Payment Act Annex 1 nos. 1-7, other professional Annex 1 financial activities and defined cryptoasset service providers. Investment managers, AIF managers, Danish UCITS and AIFs in nos. 9-10 require direct customer contact. Annex 1 includes lending, financial leasing, customer securities transactions, portfolio management and advice, securities custody and safe-deposit services. A software supplier is not automatically an obliged payment or crypto provider. Identify the actual service, contracting entity and establishment; Danish branches, distributors and agents are included where section 1 applies.
Applicability
Business lines
all
Customer types
all
Stages
all
Supporting provision
LBK 433/2026 section 1(1), (5), (7), pp. 1-2; section 2(3)-(4), pp. 2-3; Annex 1, p. 33
Downloaded original: data/country-handbook-evidence/dk/lbk-433-2026.pdf, 35 pages; inspected with pdftotext. Current reference is supported by the live Finanstilsynet index. The consolidation includes the amendment to section 38 b from Act 1638/2025 and explains the revoked, unincorporated amendment from Act 712/2025. Publication on 21 April 2026 is NOT treated as the commencement of all provisions. The JavaScript landing page did not expose amendment-status metadata. The bounded follow-up verified promulgated Act 764/2026 and its 15 September commencement; see the promulgated Act 764/2026 and the dated governance-review limitation. Danish original governs; English summaries are editorial, not an official translation.
Recent document checks
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
Conditions
Applies only to activities within section 1 of the Danish AML Act; the firm's activity and legal form determine applicability.
Exceptions
Limited financial activity exemptions require their own legal basis and facts; section 1(7) is a rule-making power, not a blanket exemption. This is AML scope, not a licensing opinion or an extension of consumer account rights to corporate customers.
Evidence diagnostics
Record ID
dk-activity-perimeter
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
requirements
Status when reviewed
current
Review status
source checked
Effective from
Not recorded
Effective to
Not recorded
Assign the legally required AML responsibilitieslegislation
Assign the legally required AML responsibilities
What this requires
Distinguish the designated decision-maker, conditional compliance officer and relevant executive responsibility.
RegCanary explanation
Section 7(2) requires management of undertakings in section 1(1) nos. 1-8, 9, 10, 18 and 22 to designate an employee authorised for decisions under sections 8(2), 17(2) no. 5, 18(3) and 19(1) no. 3. The employee may be in daily management, must understand the undertaking's ML/TF exposure and satisfy reputation and conduct requirements. Under section 8(3), undertakings in nos. 1-7 which must have a compliance function under other legislation must designate a management-level compliance officer to assess procedure and remediation effectiveness and check FIU reporting. Section 8(5) requires an executive-board member responsible for AML implementation where relevant. Under section 8(4), boards of undertakings in nos. 1-7 with internal audit, excluding their domestic branches, distributors and agents, and other obliged undertakings legally required to have internal audit must ensure that audit assesses whether AML policies, procedures and controls are properly designed and operating.
Downloaded original: data/country-handbook-evidence/dk/lbk-433-2026.pdf, 35 pages; inspected with pdftotext. Current reference is supported by the live Finanstilsynet index. The consolidation includes the amendment to section 38 b from Act 1638/2025 and explains the revoked, unincorporated amendment from Act 712/2025. Publication on 21 April 2026 is NOT treated as the commencement of all provisions. The JavaScript landing page did not expose amendment-status metadata. The bounded follow-up verified promulgated Act 764/2026 and its 15 September commencement; see the promulgated Act 764/2026 and the dated governance-review limitation. Danish original governs; English summaries are editorial, not an official translation.
Recent document checks
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
Conditions
The three designation provisions exclude the undertakings' domestic branches, distributors and agents. This does not exempt those establishments from AML controls.
The compliance-function condition in section 8(3) must not be imposed on every obliged business. Existing and future audit requirements remain in the dated governance framework; this row does not change the 15 September boundary.
Evidence diagnostics
Record ID
dk-designated-governance-roles
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
requirements
Status when reviewed
current
Review status
source checked
Effective from
Not recorded
Effective to
Not recorded
No exceptions are recorded. This does not establish that none apply.
Apply group controls and address conflicting foreign lawlegislation
Apply group controls and address conflicting foreign law
What this requires
Maintain group AML information-sharing policies and manage weaker or conflicting host-country requirements.
RegCanary explanation
Section 9 requires group data-protection and AML information-sharing policies and procedures, which group undertakings must follow in addition to their own controls. Section 31(1) requires establishments in another EU/EEA state to comply with that state's AML rules. For a branch or majority-owned subsidiary outside the EU/EEA where requirements are weaker, subsection 2 requires Danish AML and data-protection standards insofar as host law permits. Where host law prevents implementation, subsection 3 requires additional risk-mitigation measures and notification to the undertaking's Danish AML supervisor. Section 32 requires group sharing where funds are suspected criminal proceeds or linked to terrorist financing and a section 26 report has been made, limited to necessary personal data. Read this with the separate section 38 confidentiality permissions.
Applicability
Business lines
all
Customer types
all
Stages
all
Supporting provision
LBK 433/2026 section 9, p. 5; section 31(1)-(3), pp. 11-12; section 32, p. 12; section 38(3)-(4), p. 13
Downloaded original: data/country-handbook-evidence/dk/lbk-433-2026.pdf, 35 pages; inspected with pdftotext. Current reference is supported by the live Finanstilsynet index. The consolidation includes the amendment to section 38 b from Act 1638/2025 and explains the revoked, unincorporated amendment from Act 712/2025. Publication on 21 April 2026 is NOT treated as the commencement of all provisions. The JavaScript landing page did not expose amendment-status metadata. The bounded follow-up verified promulgated Act 764/2026 and its 15 September commencement; see the promulgated Act 764/2026 and the dated governance-review limitation. Danish original governs; English summaries are editorial, not an official translation.
Recent document checks
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
Conditions
Conditional on group membership or relevant foreign establishments. Group sharing is not general permission to disclose suspicion to the customer or unrelated affiliates.
Exceptions
This row does not establish international data-transfer safeguards or permission to open branches in high-risk countries; sections 31a-31b have separate establishment controls.
Evidence diagnostics
Record ID
dk-group-cross-border-controls
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
requirements
Status when reviewed
current
Review status
source checked
Effective from
Not recorded
Effective to
Not recorded
Protect internal reporting and provide the required channellegislation
Protect internal reporting and provide the required channel
What this requires
Apply the sector-specific anonymous breach-reporting duty and protect employees who report ML/TF suspicions.
RegCanary explanation
Section 35 requires undertakings in section 1(1) nos. 5, 8, 10 as regards AIFs, 12-19, 21 and 22 with more than five employees to provide a special independent autonomous channel accepting anonymous reports of actual or potential AML breaches. Establish it within three months of hiring the sixth employee, follow up and document the response. Section 36(1) protects breach reporters in those specified sectors; subsection 2 separately protects employees and former employees of all obliged businesses who report ML/TF suspicions internally or to the FIU, including in variable remuneration decisions. These protections cannot be contracted away. Section 37 protects good-faith section 26 reports and specified transaction stoppages against liability and confidentiality claims.
Applicability
Business lines
all
Customer types
all
Stages
all
Supporting provision
LBK 433/2026 sections 35(1)-(4), pp. 12-13; 36(1)-(4), 37, p. 13
Downloaded original: data/country-handbook-evidence/dk/lbk-433-2026.pdf, 35 pages; inspected with pdftotext. Current reference is supported by the live Finanstilsynet index. The consolidation includes the amendment to section 38 b from Act 1638/2025 and explains the revoked, unincorporated amendment from Act 712/2025. Publication on 21 April 2026 is NOT treated as the commencement of all provisions. The JavaScript landing page did not expose amendment-status metadata. The bounded follow-up verified promulgated Act 764/2026 and its 15 September commencement; see the promulgated Act 764/2026 and the dated governance-review limitation. Danish original governs; English summaries are editorial, not an official translation.
Recent document checks
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
Conditions
Section 35's sector and headcount conditions are not universal bank exemptions from whistleblowing law. Other financial legislation and the separate TFR Article 32(2) duty may apply.
A collective agreement may establish the section 35 channel; the supervisor may grant the specific subsection 4 exemption. This row does not decide eligibility.
Evidence diagnostics
Record ID
dk-protected-internal-reporting
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
requirements
Status when reviewed
current
Review status
source checked
Effective from
Not recorded
Effective to
Not recorded
No exceptions are recorded. This does not establish that none apply.
CDD & KYC
United Kingdom
Include and verify required payment-transfer informationlegislation
Include and verify required payment-transfer information
What this requires
The payer's payment service provider must send required payer and payee information and verify the payer information before executing the transfer, subject to the precise domestic and low-value derogations.
RegCanary explanation
The standard fields are payer name, account number and one of address, official personal-document number, customer identifier or date and place of birth; payee name and account number are also required. Use a unique transaction identifier where no payment account is involved. An entirely UK/Gibraltar chain may carry account numbers or an identifier, with further information supplied on request within three working days. The current UK text retains EUR 1,000 thresholds for the specified low-value rules.
Original downloaded to data/country-handbook-evidence/uk/uk-funds-transfer-2015-847-20260910.xml and parsed with ElementTree. Articles 2 and 4-16 checked in the UK-amended national version, not the repealed EU-only version. UK/Gibraltar scope and EUR 1,000 thresholds remain in the inspected text. Article 16(2) retains national-law qualifications; no generic ten-year permission is inferred. Web XHTML extraction failed but the official XML download succeeded.
Recent document checks
: unchanged, document 2d9221b2e9e3
: unchanged, document 2d9221b2e9e3
: unchanged, document 2d9221b2e9e3
: unchanged, document 2d9221b2e9e3
: unchanged, document 2d9221b2e9e3
Evidence diagnostics
Record ID
uk-payment-transfer-payer
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
cdd
Status when reviewed
current
Review status
source checked
Effective from
Not recorded
Effective to
Not recorded
No conditions are recorded. This does not establish that none apply.
No exceptions are recorded. This does not establish that none apply.
Separate individual information from verification evidence · review pendingguidance / Review pending
Separate individual information from verification evidence
What this requires
JMLSG guidance says to obtain an individual's full name, residential address and date of birth; its standard documentary route verifies the name plus either the address or date of birth.
RegCanary explanation
MLR regulation 28 requires identification and reliable, independent verification when CDD applies, but does not prescribe a universal document set. JMLSG Part I 5.3.71 says firms should obtain full name, residential address and date of birth. Paragraphs 5.3.72-5.3.75 describe reliable documentary, electronic or combined evidence and two documentary routes. Paragraph 5.3.112 confirms that the standard verification is name plus a choice of address or date of birth, rather than address verification in every case. This remains guidance supporting risk-based verification, not a statutory passport-and-utility-bill checklist.
Applicability
Business lines
all
Customer types
individual
Stages
onboarding
Supporting provision
JMLSG Part I paragraphs 5.3.69-5.3.75 and 5.3.112 (PDF pages 88 and 96 in the retained August 2025 Part I)
Baseline document
Joint Money Laundering Steering Group
Source diagnostics
Lifecycle
Not recorded
Language
en
Retrieved
10 Sept 2026
Extraction
captured
Latest automated check
12 Oct 2026
Check outcome
unchanged
Evidence review
unvalidated
Type
guidance
Version
June 2023, updated August 2025, as linked from Current Guidance; read with later revisions
Original downloaded to data/country-handbook-evidence/uk/jmlsg-part-i-aug-2025.pdf. Paragraphs 5.3.69-5.3.75 inspected via web text and PDF page 88 via pdftotext. Current means publisher-listed base guidance, not that all text reflects 2026 law. No wholesale republication; original is a local research capture subject to publisher rights. Core-control expansion checked paragraphs 6.32 and 8.21-8.23 using pdftotext on the retained original. The five-year suspicion-report retention statement is guidance, not a new statutory period.
Recent document checks
: unchanged, document 5ddd575e79e3
: unchanged, document 5ddd575e79e3
: unchanged, document 5ddd575e79e3
: unchanged, document 5ddd575e79e3
: unchanged, document 5ddd575e79e3
Review pending
Joint Money Laundering Steering Group
Source diagnostics
Lifecycle
Not recorded
Language
en
Retrieved
11 Sept 2026
Extraction
captured
Latest automated check
12 Oct 2026
Check outcome
unchanged
Evidence review
requires-revalidation
Type
guidance
Version
Publisher current-guidance index captured 11 September 2026; 2026 MLR update in progress
Web-fetched index. Publisher warns that guidance is being updated for SI 2026/621 and must be read with the Revisions tab. Part III is under review. The index is evidence of publication state, not the basis for a source_checked substantive requirement. Delivery original captured from https://www.jmlsg.org.uk/guidance/current-guidance/ at 2026-09-11T07:29:04.998Z to data/country-handbook-evidence/uk/uk-jmlsg-current-delivery-20260911.html; SHA-256 8fce48f4def8f87d362136ca75e6d79dbfa77e7e2452add8293f3be115119879. Timestamp records local download completion. Official publisher English, not a translation. The original's text was inspected; capture does not imply every provision is verified.
Recent document checks
: unchanged, document 2ea97bb47583
: unchanged, document 2ea97bb47583
: unchanged, document 2ea97bb47583
: unchanged, document 2ea97bb47583
: unchanged, document 2ea97bb47583
Review pending
Joint Money Laundering Steering Group
Source diagnostics
Lifecycle
Not recorded
Language
en
Retrieved
11 Sept 2026
Extraction
captured
Latest automated check
12 Oct 2026
Check outcome
unchanged
Evidence review
requires-revalidation
Type
guidance
Version
Live revision register including September and February 2026
Web content checked. September and February 2026 revisions are labelled awaiting HMT approval; June 2025 revisions are labelled HMT approval received. Neither consultation nor board approval is represented as ministerial approval. Delivery original captured from https://www.jmlsg.org.uk/revisions/ at 2026-09-11T07:29:05.634Z to data/country-handbook-evidence/uk/uk-jmlsg-revisions-delivery-20260911.html; SHA-256 a3a317d1672497cfb1b510a492b42c729bcd586a9624e62eb5b342029e81d9be. Timestamp records local download completion. Official publisher English, not a translation. The original's text was inspected; capture does not imply every provision is verified.
Recent document checks
: unchanged, document 6a006e15e117
: unchanged, document 6a006e15e117
: unchanged, document 6a006e15e117
: unchanged, document 6a006e15e117
: unchanged, document 6a006e15e117
Information and evidence
Information items
Structured information items
Information
Classification
Condition
Provision
Full name
guidance information
Initial individual onboarding within the relevant JMLSG Part II sector scope.
JMLSG Part I paragraph 5.3.71
Residential address
guidance information
Initial individual onboarding within the relevant JMLSG Part II sector scope.
JMLSG Part I paragraph 5.3.71
Date of birth
guidance information
Initial individual onboarding within the relevant JMLSG Part II sector scope.
JMLSG Part I paragraph 5.3.71
Reliable, independent evidence of identity
statutory outcome
When regulation 27 requires CDD; JMLSG guidance assists the evidence assessment but does not replace the statutory outcome.
MLR 2017 regulation 28(2)(b) and (18)-(19)
Documentary evidence for the name plus either residential address or date of birth
evidence option
If the standard JMLSG documentary route is selected; it is not a universal document pack.
JMLSG Part I paragraph 5.3.112
Reliable electronic or combined evidence route
evidence option
Where the selected evidence remains reliable, independent and appropriate to the risk.
JMLSG Part I paragraphs 5.3.72-5.3.75
Evidence diagnostics
Record ID
uk-jmlsg-individual-evidence
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
verification
Baseline review status
source checked
Review status
needs review
Effective from
Not recorded
Effective to
Not recorded
No conditions are recorded. This does not establish that none apply.
No exceptions are recorded. This does not establish that none apply.
Assess pooled accounts and distinguish holder duties · review pendinglegislation / Review pending
Assess pooled accounts and distinguish holder duties
What this requires
A credit or financial institution providing a qualifying new pooled account must understand its purpose and proposed use and assess the risks of the customer's use of it.
RegCanary explanation
Check consistency with knowledge of the customer and update CDD if necessary. Assess appropriate account controls and be able to justify the measures to the supervisor. Separately, the account customer must supply underlying-person and beneficial-owner identities on request, keep accurate written inflow and outflow records for five years from each payment's completion, and answer qualifying law-enforcement requests.
Official original downloaded from https://www.legislation.gov.uk/uksi/2017/692/data.xml to data/country-handbook-evidence/uk/mlr-2017-revised.xml; parsed with Python ElementTree. Web reader rejected XHTML; direct XML succeeded. Inspected provisions and unapplied-effects metadata. Future reg. 34A and Sch. 6 para. 7(ga) are not current duties; metadata also identifies an obsolete 2019 reg. 3(1) effect that requires no application. English official legislative text, not a translation. Version dates are not assigned as commencement dates to compound requirements. Fresh read-only download completed 2026-09-10T19:02:53Z at data/country-handbook-evidence/uk/mlr-2017-entity-expansion-20260910.xml; SHA-256 is identical to the first capture. Entity expansion checked regulations 5, 6, 28, 30(6)-(7), 30A, 30ZA(5), 42-45 (selected information paragraphs) and Schedule 3AZA. See docs/country-handbooks/uk-entity-expansion.md. Core-control re-download at data/country-handbook-evidence/uk/mlr-2017-core-controls-20260910.xml completed 2026-09-10T20:35:30Z with the same SHA-256. Further inspected regulations 19A, 20, 21, 24, 29, 34, 38-41 and 64A-64H. See docs/country-handbooks/uk-coverage-completion.md. Delivery original captured from https://www.legislation.gov.uk/uksi/2017/692/data.xml at 2026-09-11T07:33:37.592Z to data/country-handbook-evidence/uk/mlr-2017-delivery-20260911.xml; SHA-256 694f11c106b2b5328a4bcabf5a2d6f48ac39ec06670302b4e19c20bcfdb70811. Timestamp records local download completion. Official publisher English, not a translation. The original's text was inspected; capture does not imply every provision is verified. Fresh XML parsed with ElementTree: legislative body and commentary are identical to the prior retained original; differences are confined to metadata. Prior originals remain retained.
Recent document checks
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
Evidence diagnostics
Record ID
uk-pooled-account-controls
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
cdd
Baseline review status
source checked
Review status
needs review
Effective from
Not recorded
Effective to
Not recorded
No conditions are recorded. This does not establish that none apply.
No exceptions are recorded. This does not establish that none apply.
Apply the e-money derogation only within its limits · review pendinglegislation / Review pending
Apply the e-money derogation only within its limits
What this requires
CDD relief for qualifying e-money depends on every statutory product condition and continued monitoring for unusual or suspicious transactions.
RegCanary explanation
The maximum stored value is GBP 150. The instrument must be non-reloadable or subject to a GBP 150 monthly transaction limit usable only in the UK; it must be used exclusively for goods or services and cannot be funded with anonymous e-money. Apply the cash-redemption, cash-withdrawal and remote-payment limits in regulation 38(2). An acquirer accepting an anonymous prepaid card issued in a third country must establish equivalent national requirements and that the card satisfies them.
Official original downloaded from https://www.legislation.gov.uk/uksi/2017/692/data.xml to data/country-handbook-evidence/uk/mlr-2017-revised.xml; parsed with Python ElementTree. Web reader rejected XHTML; direct XML succeeded. Inspected provisions and unapplied-effects metadata. Future reg. 34A and Sch. 6 para. 7(ga) are not current duties; metadata also identifies an obsolete 2019 reg. 3(1) effect that requires no application. English official legislative text, not a translation. Version dates are not assigned as commencement dates to compound requirements. Fresh read-only download completed 2026-09-10T19:02:53Z at data/country-handbook-evidence/uk/mlr-2017-entity-expansion-20260910.xml; SHA-256 is identical to the first capture. Entity expansion checked regulations 5, 6, 28, 30(6)-(7), 30A, 30ZA(5), 42-45 (selected information paragraphs) and Schedule 3AZA. See docs/country-handbooks/uk-entity-expansion.md. Core-control re-download at data/country-handbook-evidence/uk/mlr-2017-core-controls-20260910.xml completed 2026-09-10T20:35:30Z with the same SHA-256. Further inspected regulations 19A, 20, 21, 24, 29, 34, 38-41 and 64A-64H. See docs/country-handbooks/uk-coverage-completion.md. Delivery original captured from https://www.legislation.gov.uk/uksi/2017/692/data.xml at 2026-09-11T07:33:37.592Z to data/country-handbook-evidence/uk/mlr-2017-delivery-20260911.xml; SHA-256 694f11c106b2b5328a4bcabf5a2d6f48ac39ec06670302b4e19c20bcfdb70811. Timestamp records local download completion. Official publisher English, not a translation. The original's text was inspected; capture does not imply every provision is verified. Fresh XML parsed with ElementTree: legislative body and commentary are identical to the prior retained original; differences are confined to metadata. Prior originals remain retained.
Recent document checks
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
Evidence diagnostics
Record ID
uk-emoney-derogation
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
cdd
Baseline review status
source checked
Review status
needs review
Effective from
Not recorded
Effective to
Not recorded
No conditions are recorded. This does not establish that none apply.
No exceptions are recorded. This does not establish that none apply.
Do not establish anonymous accounts or safe-deposit boxes · review pendinglegislation / Review pending
Do not establish anonymous accounts or safe-deposit boxes
What this requires
A credit or financial institution must not establish an anonymous account, passbook or safe-deposit box for a new or existing customer.
RegCanary explanation
Apply CDD to the legacy anonymous accounts, passbooks and safe-deposit boxes covered by the regulation, and in any event before they are used. A product label or customer preference does not displace the prohibition.
Official original downloaded from https://www.legislation.gov.uk/uksi/2017/692/data.xml to data/country-handbook-evidence/uk/mlr-2017-revised.xml; parsed with Python ElementTree. Web reader rejected XHTML; direct XML succeeded. Inspected provisions and unapplied-effects metadata. Future reg. 34A and Sch. 6 para. 7(ga) are not current duties; metadata also identifies an obsolete 2019 reg. 3(1) effect that requires no application. English official legislative text, not a translation. Version dates are not assigned as commencement dates to compound requirements. Fresh read-only download completed 2026-09-10T19:02:53Z at data/country-handbook-evidence/uk/mlr-2017-entity-expansion-20260910.xml; SHA-256 is identical to the first capture. Entity expansion checked regulations 5, 6, 28, 30(6)-(7), 30A, 30ZA(5), 42-45 (selected information paragraphs) and Schedule 3AZA. See docs/country-handbooks/uk-entity-expansion.md. Core-control re-download at data/country-handbook-evidence/uk/mlr-2017-core-controls-20260910.xml completed 2026-09-10T20:35:30Z with the same SHA-256. Further inspected regulations 19A, 20, 21, 24, 29, 34, 38-41 and 64A-64H. See docs/country-handbooks/uk-coverage-completion.md. Delivery original captured from https://www.legislation.gov.uk/uksi/2017/692/data.xml at 2026-09-11T07:33:37.592Z to data/country-handbook-evidence/uk/mlr-2017-delivery-20260911.xml; SHA-256 694f11c106b2b5328a4bcabf5a2d6f48ac39ec06670302b4e19c20bcfdb70811. Timestamp records local download completion. Official publisher English, not a translation. The original's text was inspected; capture does not imply every provision is verified. Fresh XML parsed with ElementTree: legislative body and commentary are identical to the prior retained original; differences are confined to metadata. Prior originals remain retained.
Recent document checks
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
Evidence diagnostics
Record ID
uk-anonymous-account-prohibition
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
cdd
Baseline review status
source checked
Review status
needs review
Effective from
Not recorded
Effective to
Not recorded
No conditions are recorded. This does not establish that none apply.
No exceptions are recorded. This does not establish that none apply.
Use simplified CDD only on a supported low-risk basis · review pendinglegislation / Review pending
Use simplified CDD only on a supported low-risk basis
What this requires
Simplified diligence adjusts measures for demonstrated low risk; it does not remove CDD or monitoring.
RegCanary explanation
Consider the business assessment, supervisor information and relevant risk factors. Continue the requirements identified in regulation 37(2), while adjusting permitted measures. Monitoring must still detect unusual or suspicious transactions. Stop simplified treatment when identity doubts, suspicion, higher risk or a regulation 33(1) condition arises.
Applicability
Business lines
all
Customer types
all
Stages
onboarding, ongoing
Supporting provision
MLR 2017 regulation 37(1)-(4) and (8)
Review pending
HM Treasury / legislation.gov.uk
Source diagnostics
Lifecycle
Not recorded
Language
en
Retrieved
11 Sept 2026
Extraction
captured
Latest automated check
12 Oct 2026
Check outcome
unchanged
Evidence review
requires-revalidation
Type
legislation
Version
Revised XML retrieved 2026-09-11; document RestrictStartDate 2026-06-30; individual provisions have different amendment histories
Official original downloaded from https://www.legislation.gov.uk/uksi/2017/692/data.xml to data/country-handbook-evidence/uk/mlr-2017-revised.xml; parsed with Python ElementTree. Web reader rejected XHTML; direct XML succeeded. Inspected provisions and unapplied-effects metadata. Future reg. 34A and Sch. 6 para. 7(ga) are not current duties; metadata also identifies an obsolete 2019 reg. 3(1) effect that requires no application. English official legislative text, not a translation. Version dates are not assigned as commencement dates to compound requirements. Fresh read-only download completed 2026-09-10T19:02:53Z at data/country-handbook-evidence/uk/mlr-2017-entity-expansion-20260910.xml; SHA-256 is identical to the first capture. Entity expansion checked regulations 5, 6, 28, 30(6)-(7), 30A, 30ZA(5), 42-45 (selected information paragraphs) and Schedule 3AZA. See docs/country-handbooks/uk-entity-expansion.md. Core-control re-download at data/country-handbook-evidence/uk/mlr-2017-core-controls-20260910.xml completed 2026-09-10T20:35:30Z with the same SHA-256. Further inspected regulations 19A, 20, 21, 24, 29, 34, 38-41 and 64A-64H. See docs/country-handbooks/uk-coverage-completion.md. Delivery original captured from https://www.legislation.gov.uk/uksi/2017/692/data.xml at 2026-09-11T07:33:37.592Z to data/country-handbook-evidence/uk/mlr-2017-delivery-20260911.xml; SHA-256 694f11c106b2b5328a4bcabf5a2d6f48ac39ec06670302b4e19c20bcfdb70811. Timestamp records local download completion. Official publisher English, not a translation. The original's text was inspected; capture does not imply every provision is verified. Fresh XML parsed with ElementTree: legislative body and commentary are identical to the prior retained original; differences are confined to metadata. Prior originals remain retained.
Recent document checks
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
Evidence diagnostics
Record ID
uk-simplified-diligence
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
cdd
Baseline review status
source checked
Review status
needs review
Effective from
Not recorded
Effective to
Not recorded
No conditions are recorded. This does not establish that none apply.
No exceptions are recorded. This does not establish that none apply.
Apply CDD at the relevant trigger · review pendinglegislation / Review pending
Apply CDD at the relevant trigger
What this requires
For a UK MLR relevant person, a business relationship, suspicion or identity doubts can trigger CDD irrespective of transaction value. Occasional-transaction thresholds depend on the activity; crypto transfers and crypto ATM transactions have specific tests rather than a universal banking threshold.
RegCanary explanation
The checked amended text uses GBP: funds transfers exceeding GBP 800; general occasional transactions of GBP 12,000 or more, including linked operations, subject to sector exclusions. Crypto transfers of at least GBP 800 equivalent include linked transfers; crypto ATM transactions have no minimum CDD threshold. Relationship, suspicion and doubt triggers are not displaced by transaction thresholds.
Applicability
Business lines
all
Customer types
all
Stages
all
Supporting provision
MLR 2017 regulation 27(1)-(2), (7D)-(7E) and (10), read with regulations 8, 14A and 15
Review pending
HM Treasury / legislation.gov.uk
Source diagnostics
Lifecycle
Not recorded
Language
en
Retrieved
11 Sept 2026
Extraction
captured
Latest automated check
12 Oct 2026
Check outcome
unchanged
Evidence review
requires-revalidation
Type
legislation
Version
Revised XML retrieved 2026-09-11; document RestrictStartDate 2026-06-30; individual provisions have different amendment histories
Official original downloaded from https://www.legislation.gov.uk/uksi/2017/692/data.xml to data/country-handbook-evidence/uk/mlr-2017-revised.xml; parsed with Python ElementTree. Web reader rejected XHTML; direct XML succeeded. Inspected provisions and unapplied-effects metadata. Future reg. 34A and Sch. 6 para. 7(ga) are not current duties; metadata also identifies an obsolete 2019 reg. 3(1) effect that requires no application. English official legislative text, not a translation. Version dates are not assigned as commencement dates to compound requirements. Fresh read-only download completed 2026-09-10T19:02:53Z at data/country-handbook-evidence/uk/mlr-2017-entity-expansion-20260910.xml; SHA-256 is identical to the first capture. Entity expansion checked regulations 5, 6, 28, 30(6)-(7), 30A, 30ZA(5), 42-45 (selected information paragraphs) and Schedule 3AZA. See docs/country-handbooks/uk-entity-expansion.md. Core-control re-download at data/country-handbook-evidence/uk/mlr-2017-core-controls-20260910.xml completed 2026-09-10T20:35:30Z with the same SHA-256. Further inspected regulations 19A, 20, 21, 24, 29, 34, 38-41 and 64A-64H. See docs/country-handbooks/uk-coverage-completion.md. Delivery original captured from https://www.legislation.gov.uk/uksi/2017/692/data.xml at 2026-09-11T07:33:37.592Z to data/country-handbook-evidence/uk/mlr-2017-delivery-20260911.xml; SHA-256 694f11c106b2b5328a4bcabf5a2d6f48ac39ec06670302b4e19c20bcfdb70811. Timestamp records local download completion. Official publisher English, not a translation. The original's text was inspected; capture does not imply every provision is verified. Fresh XML parsed with ElementTree: legislative body and commentary are identical to the prior retained original; differences are confined to metadata. Prior originals remain retained.
Recent document checks
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
Evidence diagnostics
Record ID
uk-cdd-triggers
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
cdd
Baseline review status
source checked
Review status
needs review
Effective from
Not recorded
Effective to
Not recorded
No conditions are recorded. This does not establish that none apply.
No exceptions are recorded. This does not establish that none apply.
Verify the customer and assess the purpose of the relationship. Where a person purports to act on the customer's behalf, separately verify authority to act, identify that person and verify their identity using a source independent of both the person and the customer.
RegCanary explanation
In company or trust scenarios, a board-member name, beneficial-owner identity and authority to instruct are different matters. Regulation 28(3)(b)(ii) concerns reasonable determination and verification of directors' and senior personnel's full names; it is not itself a direction to obtain a passport for every director. Paragraph (10) applies when someone purports to act for the customer. Beneficial-owner verification under (4) does not establish that person's authority to act. Paragraphs (18)-(19) allow reliable independent documentary/information evidence and qualifying electronic identification; no universal document pair is prescribed.
Applicability
Business lines
all
Customer types
all
Stages
all
Supporting provision
MLR 2017 regulation 28(1)-(4), (10), (12)-(15) and (18)-(19), read with regulation 30
Review pending
HM Treasury / legislation.gov.uk
Source diagnostics
Lifecycle
Not recorded
Language
en
Retrieved
11 Sept 2026
Extraction
captured
Latest automated check
12 Oct 2026
Check outcome
unchanged
Evidence review
requires-revalidation
Type
legislation
Version
Revised XML retrieved 2026-09-11; document RestrictStartDate 2026-06-30; individual provisions have different amendment histories
Official original downloaded from https://www.legislation.gov.uk/uksi/2017/692/data.xml to data/country-handbook-evidence/uk/mlr-2017-revised.xml; parsed with Python ElementTree. Web reader rejected XHTML; direct XML succeeded. Inspected provisions and unapplied-effects metadata. Future reg. 34A and Sch. 6 para. 7(ga) are not current duties; metadata also identifies an obsolete 2019 reg. 3(1) effect that requires no application. English official legislative text, not a translation. Version dates are not assigned as commencement dates to compound requirements. Fresh read-only download completed 2026-09-10T19:02:53Z at data/country-handbook-evidence/uk/mlr-2017-entity-expansion-20260910.xml; SHA-256 is identical to the first capture. Entity expansion checked regulations 5, 6, 28, 30(6)-(7), 30A, 30ZA(5), 42-45 (selected information paragraphs) and Schedule 3AZA. See docs/country-handbooks/uk-entity-expansion.md. Core-control re-download at data/country-handbook-evidence/uk/mlr-2017-core-controls-20260910.xml completed 2026-09-10T20:35:30Z with the same SHA-256. Further inspected regulations 19A, 20, 21, 24, 29, 34, 38-41 and 64A-64H. See docs/country-handbooks/uk-coverage-completion.md. Delivery original captured from https://www.legislation.gov.uk/uksi/2017/692/data.xml at 2026-09-11T07:33:37.592Z to data/country-handbook-evidence/uk/mlr-2017-delivery-20260911.xml; SHA-256 694f11c106b2b5328a4bcabf5a2d6f48ac39ec06670302b4e19c20bcfdb70811. Timestamp records local download completion. Official publisher English, not a translation. The original's text was inspected; capture does not imply every provision is verified. Fresh XML parsed with ElementTree: legislative body and commentary are identical to the prior retained original; differences are confined to metadata. Prior originals remain retained.
Recent document checks
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
Information and evidence
Information items
Structured information items
Information
Classification
Condition
Provision
Reliable, independent verification of the customer's identity
statutory outcome
When regulation 27 requires CDD, subject to the timing rules and safeguards in regulation 30.
MLR 2017 regulation 28(2)(b) and (18)-(19)
Assessment of the relationship's purpose and intended nature
conditional information
Obtain information where appropriate to the risk-based CDD assessment.
MLR 2017 regulation 28(2)(c)
Evidence diagnostics
Record ID
uk-independent-verification
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
verification
Baseline review status
source checked
Review status
needs review
Effective from
Not recorded
Effective to
Not recorded
No conditions are recorded. This does not establish that none apply.
No exceptions are recorded. This does not establish that none apply.
Control third-party reliance and retain responsibility · review pendinglegislation / Review pending
Control third-party reliance and retain responsibility
What this requires
Use permitted third-party reliance only with immediate access to the necessary CDD and register information; the firm remains liable for failures.
RegCanary explanation
Immediately obtain the information needed for the specified customer, beneficial-owner, acting-on-behalf and register measures. Arrange immediate access on request to copies of identification and verification material and retention for the statutory period. Assess the third party's eligibility and, where overseas, equivalent requirements and supervision.
Official original downloaded from https://www.legislation.gov.uk/uksi/2017/692/data.xml to data/country-handbook-evidence/uk/mlr-2017-revised.xml; parsed with Python ElementTree. Web reader rejected XHTML; direct XML succeeded. Inspected provisions and unapplied-effects metadata. Future reg. 34A and Sch. 6 para. 7(ga) are not current duties; metadata also identifies an obsolete 2019 reg. 3(1) effect that requires no application. English official legislative text, not a translation. Version dates are not assigned as commencement dates to compound requirements. Fresh read-only download completed 2026-09-10T19:02:53Z at data/country-handbook-evidence/uk/mlr-2017-entity-expansion-20260910.xml; SHA-256 is identical to the first capture. Entity expansion checked regulations 5, 6, 28, 30(6)-(7), 30A, 30ZA(5), 42-45 (selected information paragraphs) and Schedule 3AZA. See docs/country-handbooks/uk-entity-expansion.md. Core-control re-download at data/country-handbook-evidence/uk/mlr-2017-core-controls-20260910.xml completed 2026-09-10T20:35:30Z with the same SHA-256. Further inspected regulations 19A, 20, 21, 24, 29, 34, 38-41 and 64A-64H. See docs/country-handbooks/uk-coverage-completion.md. Delivery original captured from https://www.legislation.gov.uk/uksi/2017/692/data.xml at 2026-09-11T07:33:37.592Z to data/country-handbook-evidence/uk/mlr-2017-delivery-20260911.xml; SHA-256 694f11c106b2b5328a4bcabf5a2d6f48ac39ec06670302b4e19c20bcfdb70811. Timestamp records local download completion. Official publisher English, not a translation. The original's text was inspected; capture does not imply every provision is verified. Fresh XML parsed with ElementTree: legislative body and commentary are identical to the prior retained original; differences are confined to metadata. Prior originals remain retained.
Recent document checks
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
Evidence diagnostics
Record ID
uk-third-party-reliance
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
cdd
Baseline review status
source checked
Review status
needs review
Effective from
Not recorded
Effective to
Not recorded
No conditions are recorded. This does not establish that none apply.
No exceptions are recorded. This does not establish that none apply.
Denmark
Carry out authorised domestic consumer account switchinglegislation
Carry out authorised domestic consumer account switching
What this requires
Use the consumer's recorded consent to coordinate the sending and receiving providers, preserve payment continuity and apply the statutory working-day deadlines.
RegCanary explanation
For consumer payment accounts in the same currency between Danish providers, the receiving provider starts the process on paper or durable-medium consent from all account holders. Record the tasks, recurring payments and chosen date. Under section 4(4), the chosen date must be at least six working days after the date on which the receiving provider is due to receive the list under section 5(1) no. 1, not six working days after a late actual response. Section 4(5) uses a different anchor: if the chosen date is more than six working days after actual receipt of that list, the receiving provider's section 5(1) deadline for requesting the sending provider's tasks must be shifted by the corresponding number of days. Keep that actual-receipt adjustment separate from section 4(4)'s due-receipt minimum; a late response does not silently reset the minimum chosen-date rule. Subject to section 4(5), the receiving provider requests the tasks within two working days of receiving the consumer's consent or transfer request. The sending provider must send the list within five working days of receiving that request. Section 6(1)'s specified receiving-provider setup and payer/payee tasks run from actual receipt of the list, with a five-working-day deadline and the stated information-availability conditions, including NemKonto changes where applicable. On request, review the preceding 13 months to identify recurring transactions. Transfer the positive balance as authorised and notify the consumer no later than transfer. Close only after the specified tasks are completed, applicable notice is observed and no outstanding obligation prevents closure; immediately explain any such obstacle.
Applicability
Business lines
retail banking
Customer types
individual
Stages
onboarding, offboarding
Supporting provision
BEK 1761/2021 sections 1, 3-8 and commencement section 9, PDF pp. 1-3; LBK 463/2026 section 75(1), (3)-(5), pp. 22-23
Baseline document
Retsinformation / Erhvervsministeriet
Source diagnostics
Lifecycle
Not recorded
Language
da
Retrieved
10 Sept 2026
Extraction
captured
Latest automated check
20 Sept 2026
Check outcome
unchanged
Evidence review
unvalidated
Type
legislation
Version
BEK nr 1761 af 01/09/2021; commencement 01/10/2021
Downloaded original: data/country-handbook-evidence/dk/bek-1761-2021-switching.pdf. 3 pages, 166,507 bytes. Native Retsinformation text marked Gaeldende; full sections 1-9 inspected. Maps domestic consumer same-currency consent, provider tasks, deadlines, continuity, information, costs and closure conditions. Section 2's borrowed definitions and section 6's direct-debit-rights cross-reference do not establish a full payments-law map. No operational switching calendar or provider test was performed.
Downloaded original: data/country-handbook-evidence/dk/lbk-463-2026-payments.pdf. 49 pages, 617,829 bytes. Inspected sections 72(3) and 75(1)-(5), pp. 22-23, for consumer framework notice, termination fees and proportional prepaid-fee refunds. The statute preserves separate basic-account rules and the AML exception. Amendment impact check: retained Act 711/2025 section 2, Act 729/2026 section 16 and future Act 764/2026 section 3 do not amend these selected provisions. This is not an exhaustive Payments Act/currentness audit or an inferred common historical commencement date.
Recent document checks
: unchanged, document 7bd57c83efe3
: unchanged, document 7bd57c83efe3
: unchanged, document 7bd57c83efe3
: unchanged, document 7bd57c83efe3
: unchanged, document 7bd57c83efe3
Conditions
Only consumer payment accounts within the domestic same-currency perimeter. Obtain all holders' consent and identify each sending/receiving provider responsibility. The working-day clock and later chosen date must be calculated under the order, not an unqualified calendar-day target.
Section 5(2) protects availability of payment instruments during switching, subject to lawful security blocking. Section 6(3) provides standard letters within five working days where the consumer elects to notify payers or recipients.
Under section 7, customer access to existing standing-order/direct-debit information and inter-provider list provision are free; other switching charges must be reasonable and reflect actual costs. Section 8 requires advance information on tasks, deadlines, fees, customer information and complaints, free on paper or durable medium at premises and online.
Under section 6(4), an early-arriving balance requires immediate performance of the listed receiving-provider tasks; execution before receipt of the balance requires reimbursement of resulting consumer costs.
Exceptions
Switching consent does not authorise a prohibited or frozen closing payment, waive AML/FIU controls, or extinguish outstanding debt. Cross-border assistance and basic-account termination have separate rules.
Evidence diagnostics
Record ID
dk-domestic-account-switching
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
cdd
Status when reviewed
current
Review status
source checked
Effective from
1 Oct 2021
Effective to
Not recorded
Start CDD at onboarding and repeat it on relevant changes or doubtslegislation
Start CDD at onboarding and repeat it on relevant changes or doubts
What this requires
Establishing a covered business relationship requires CDD without a minimum transaction amount. Repeat CDD on relevant changes, appropriate occasions, suspicion or identity doubts.
RegCanary explanation
Section 10 no. 1 covers establishing a relationship, changed relevant circumstances and appropriate times. Nos. 4-5 independently trigger CDD for ML/TF suspicion and doubts about the accuracy or adequacy of previous identity information. For occasional transactions, no. 2 distinguishes EUR 15,000 generally, more than EUR 1,000 for money transfers, EUR 500 or more for currency exchange including crypto/fiat, and EUR 1,000 or more for specified crypto activities, including linked transactions. These activity-specific thresholds do not exempt an ongoing business relationship from CDD.
Applicability
Business lines
all
Customer types
all
Stages
onboarding, ongoing, investigation
Supporting provision
LBK 433/2026 section 10 nos. 1, 2(a)-(d), 4-5, p. 5
Downloaded original: data/country-handbook-evidence/dk/lbk-433-2026.pdf, 35 pages; inspected with pdftotext. Current reference is supported by the live Finanstilsynet index. The consolidation includes the amendment to section 38 b from Act 1638/2025 and explains the revoked, unincorporated amendment from Act 712/2025. Publication on 21 April 2026 is NOT treated as the commencement of all provisions. The JavaScript landing page did not expose amendment-status metadata. The bounded follow-up verified promulgated Act 764/2026 and its 15 September commencement; see the promulgated Act 764/2026 and the dated governance-review limitation. Danish original governs; English summaries are editorial, not an official translation.
Recent document checks
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
Conditions
Applies only to obliged activities under section 1; apply each occasional-transaction threshold to its own activity and aggregate linked transactions.
Exceptions
Sector-specific exemptions are not established by this entry; gaming thresholds are outside the mapped financial journey.
Evidence diagnostics
Record ID
dk-cdd-triggers
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
cdd
Status when reviewed
current
Review status
source checked
Effective from
Not recorded
Effective to
Not recorded
Identify representatives and relevant beneficial ownerslegislation
Identify representatives and relevant beneficial owners
What this requires
Check who is acting for the customer, independently verify that person's identity and establish authority; identify and reasonably verify relevant beneficial owners.
RegCanary explanation
A representative or uncertainty about whether someone acts on their own behalf triggers section 11(2). This is relevant to an individual account operated through an authorised person. Section 11(1) no. 3 separately requires beneficial-owner identification and reasonable verification, and ownership/control analysis for entities and arrangements. Do not collect a company ownership chart for every individual acting solely for themselves. The related requirements explain entity identification, company beneficial owners and qualified management fallback, and conditional ERST register checks separately. Trust/foundation role-specific identification remains incomplete.
Applicability
Business lines
all
Customer types
all
Stages
onboarding, ongoing, investigation
Supporting provision
LBK 433/2026 section 11(1) no. 3 and section 11(2), p. 6
Downloaded original: data/country-handbook-evidence/dk/lbk-433-2026.pdf, 35 pages; inspected with pdftotext. Current reference is supported by the live Finanstilsynet index. The consolidation includes the amendment to section 38 b from Act 1638/2025 and explains the revoked, unincorporated amendment from Act 712/2025. Publication on 21 April 2026 is NOT treated as the commencement of all provisions. The JavaScript landing page did not expose amendment-status metadata. The bounded follow-up verified promulgated Act 764/2026 and its 15 September commencement; see the promulgated Act 764/2026 and the dated governance-review limitation. Danish original governs; English summaries are editorial, not an official translation.
Recent document checks
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
Conditions
Only for obliged activities under section 1. Representative checks apply when someone acts for a customer or there is doubt about own-behalf action; ownership/control checks depend on the actual customer structure.
Exceptions
Section 11(2) exempts an advocate admitted in Denmark or another EU/EEA state from the authority-to-act check, not from representative identity verification.
Corporate daily-management fallback is explained separately under company beneficial owners. Trust/foundation beneficiary definitions and timing still need case-specific treatment under sections 2 no. 9(b)-(c) and 11(1) no. 3; do not apply the corporate fallback to them.
Evidence diagnostics
Record ID
dk-representatives-owners
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
cdd
Status when reviewed
current
Review status
source checked
Effective from
Not recorded
Effective to
Not recorded
Control third-party reliance and outsourced customer checkslegislation
Control third-party reliance and outsourced customer checks
What this requires
Using another organisation's CDD does not transfer the obliged undertaking's responsibility. Establish eligibility, access to evidence and continuing oversight before relying on another party.
RegCanary explanation
Sections 22-23 permit reliance for the identity, beneficial-owner and purpose components in section 11(1) nos. 1-4, not for ongoing monitoring. Section 22 limits eligible third parties to the specified obliged entities, equivalent supervised entities and qualifying associations; obtain enough information about equivalent CDD and retention, and an undertaking to provide identification, verification and other relevant records immediately on request. Group reliance under section 23 has its own equivalent group procedures and group-supervision conditions. Section 24 separately permits outsourcing under a contract, after checking capability, capacity and any necessary permission; check performance and continuing suitability during the arrangement. The obliged undertaking remains responsible under each route. The duty to appoint the person with authority under section 7(2) cannot be outsourced.
Applicability
Business lines
all
Customer types
all
Stages
onboarding, ongoing
Supporting provision
LBK 433/2026 sections 22(1)-(5), 23 and 24(1)-(4), p. 9
Downloaded original: data/country-handbook-evidence/dk/lbk-433-2026.pdf, 35 pages; inspected with pdftotext. Current reference is supported by the live Finanstilsynet index. The consolidation includes the amendment to section 38 b from Act 1638/2025 and explains the revoked, unincorporated amendment from Act 712/2025. Publication on 21 April 2026 is NOT treated as the commencement of all provisions. The JavaScript landing page did not expose amendment-status metadata. The bounded follow-up verified promulgated Act 764/2026 and its 15 September commencement; see the promulgated Act 764/2026 and the dated governance-review limitation. Danish original governs; English summaries are editorial, not an official translation.
Recent document checks
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
Conditions
Applies to individual, company and trust customers of section 1 obliged undertakings. Determine whether the arrangement is statutory reliance, group reliance or outsourcing; a referral, shared account history or vendor contract alone does not establish eligibility.
For section 22 reliance, secure the subsection 3 undertaking for immediate provision of copies on request. The obliged undertaking must still satisfy itself that the CDD is sufficient and perform its own ongoing monitoring.
Exceptions
Section 22(5) prohibits reliance on third parties established in Commission-listed high-risk third countries, except qualifying branches and majority-owned subsidiaries fully complying with EU/EEA group policies and procedures. This is not a general country-risk waiver.
Evidence diagnostics
Record ID
dk-third-party-cdd
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
cdd
Status when reviewed
current
Review status
source checked
Effective from
Not recorded
Effective to
Not recorded
Identify and verify life and pension insurance beneficiarieslegislation
Identify and verify life and pension insurance beneficiaries
What this requires
Add policy-beneficiary checks to ordinary customer CDD where life or pension insurance is offered.
RegCanary explanation
Section 12 requires the beneficiary's name. For an unnamed beneficiary or a class, obtain enough information to identify the beneficiaries at payout. Verify their identity through documents, data or information from a reliable independent source before payout, irrespective of PEP status. Section 18(1) requires procedures to determine whether the beneficiary or its beneficial owner is a PEP or a defined family member or close associate. Only where the beneficiary or its beneficial owner is a person covered by section 18(1), subsection 5 requires risk-based clarification of the insurance circumstances and notification to the person designated under section 7(2) that payout is planned and in the event of a full or partial policy transfer. This is notification, not a universal requirement to obtain payout approval. These are additional duties, not a substitute for customer and beneficial-owner CDD.
Applicability
Business lines
all
Customer types
all
Stages
onboarding, ongoing, investigation, offboarding
Supporting provision
LBK 433/2026 section 12(1)-(2), p. 6; section 18(1), (5), p. 8
Downloaded original: data/country-handbook-evidence/dk/lbk-433-2026.pdf, 35 pages; inspected with pdftotext. Current reference is supported by the live Finanstilsynet index. The consolidation includes the amendment to section 38 b from Act 1638/2025 and explains the revoked, unincorporated amendment from Act 712/2025. Publication on 21 April 2026 is NOT treated as the commencement of all provisions. The JavaScript landing page did not expose amendment-status metadata. The bounded follow-up verified promulgated Act 764/2026 and its 15 September commencement; see the promulgated Act 764/2026 and the dated governance-review limitation. Danish original governs; English summaries are editorial, not an official translation.
Recent document checks
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
Conditions
Only where the undertaking offers the life or pension insurance product within the statutory perimeter. A securities portfolio or ordinary bank account is not an insurance policy.
The special section 18(5) clarification and designated-person notification are triggered by the beneficiary or its beneficial owner being a PEP, defined family member or close associate under section 18(1). Ordinary section 12 identification and independent verification before payout still apply when that trigger is absent.
Evidence diagnostics
Record ID
dk-insurance-beneficiary-cdd
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
cdd
Status when reviewed
current
Review status
source checked
Effective from
Not recorded
Effective to
Not recorded
No exceptions are recorded. This does not establish that none apply.
Assist a consumer moving a payment account abroad · review pendinglegislation / Review pending
Assist a consumer moving a payment account abroad
What this requires
Provide the prescribed free information, transfer the available positive balance when the receiving account is identified and close the account when the statutory conditions are met.
RegCanary explanation
Section 8 applies when a consumer wants to open a payment account with a provider in another EU Member State or a country with the relevant EU financial agreement and that provider has no branch in Denmark. On request, provide free lists of active standing orders and debtor-initiated direct-debit mandates, together with available recurring credits and creditor-initiated direct debits from the preceding 13 months. Transfer the positive balance once the new provider and account are identified, and close the account. Subject to the agreed notice under the Payments Act, use the consumer's chosen date, at least six working days after the request unless otherwise agreed. If outstanding obligations prevent closure, immediately inform the consumer.
Applicability
Business lines
retail banking
Customer types
individual
Stages
onboarding, offboarding
Supporting provision
LBK 1462/2025 section 8(1)-(2), printed p. 4 (PDF p. 5); LBK 463/2026 section 75(1), p. 22
Review pending
Retsinformation / Erhvervsministeriet
Source diagnostics
Lifecycle
Not recorded
Language
da
Retrieved
10 Sept 2026
Extraction
captured
Latest automated check
20 Sept 2026
Check outcome
changed
Evidence review
requires-revalidation
Type
legislation
Version
LBK nr 1462 af 18/11/2025; read with Act 1638/2025 section 9
Original data/country-handbook-evidence/dk/lbk-1462-2025-payment-accounts.pdf. Printed pp. 1, 4-6 (PDF pp. 2, 5-7): section 1(2), section 2 nos. 1-2, sections 9-13. Consumer basic payment accounts are chapter 4, not basic deposit accounts or chapter 4a business accounts. Cover lists Act 1638/2025 section 9 (adds non-discrimination section 8a, separately captured) and Act 764/2026 section 7 (only section 19 supervisory-publication amendments, inspected). Neither changes sections 11/13. Other chapters and detailed account-switching mechanics are not fully mapped. This expansion additionally inspected section 8(1)-(2), printed p. 4/PDF p. 5, for consumer cross-border switching assistance; domestic implementation is separately sourced to BEK 1761/2021. No complete payment-account or basic-business-account regime is claimed.
Downloaded original: data/country-handbook-evidence/dk/lbk-463-2026-payments.pdf. 49 pages, 617,829 bytes. Inspected sections 72(3) and 75(1)-(5), pp. 22-23, for consumer framework notice, termination fees and proportional prepaid-fee refunds. The statute preserves separate basic-account rules and the AML exception. Amendment impact check: retained Act 711/2025 section 2, Act 729/2026 section 16 and future Act 764/2026 section 3 do not amend these selected provisions. This is not an exhaustive Payments Act/currentness audit or an inferred common historical commencement date.
Recent document checks
: unchanged, document 7bd57c83efe3
: unchanged, document 7bd57c83efe3
: unchanged, document 7bd57c83efe3
: unchanged, document 7bd57c83efe3
: unchanged, document 7bd57c83efe3
Conditions
Applies to the specified consumer cross-border account-opening situation, not every international transfer or domestic switch. Check the receiving provider's country, absence of a Danish branch, account details, selected date and outstanding obligations.
Apply AML transaction holds and applicable sanctions to any balance payment; the account-switching rule is not a release authorisation.
Exceptions
This assistance rule does not promise that the foreign provider will accept the customer or copy every service. Outstanding obligations may prevent closure.
Evidence diagnostics
Record ID
dk-cross-border-account-switching
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
cdd
Baseline review status
source checked
Review status
needs review
Effective from
Not recorded
Effective to
Not recorded
Identify and independently verify the individual customer · review pendinglegislation / Review pending
Identify and independently verify the individual customer
What this requires
Obtain name and CPR number or equivalent; if neither exists obtain date of birth. Verify identity using a reliable, independent source.
RegCanary explanation
Customer-provided details must be checked against independent documents, data or information, including recognised secure electronic identification processes. The general guidance section 9.3 explains that photo ID is not universally mandatory and that alternative reliable sources may be needed for customers unable to supply standard documents. Its passport, driving-licence, public-authority and residence-document examples are alternatives to assess, not a cumulative statutory checklist. A utility bill or Danish address is not made a universal identity requirement by section 11(1) no. 1(a).
Applicability
Business lines
all
Customer types
individual
Stages
onboarding, ongoing, investigation
Supporting provision
LBK 433/2026 section 11(1) nos. 1(a), 2, pp. 5-6; VEJ 9864/2020 section 9.3, printed pp. 59-60 (PDF pp. 60-61)
Downloaded original: data/country-handbook-evidence/dk/lbk-433-2026.pdf, 35 pages; inspected with pdftotext. Current reference is supported by the live Finanstilsynet index. The consolidation includes the amendment to section 38 b from Act 1638/2025 and explains the revoked, unincorporated amendment from Act 712/2025. Publication on 21 April 2026 is NOT treated as the commencement of all provisions. The JavaScript landing page did not expose amendment-status metadata. The bounded follow-up verified promulgated Act 764/2026 and its 15 September commencement; see the promulgated Act 764/2026 and the dated governance-review limitation. Danish original governs; English summaries are editorial, not an official translation.
Downloaded original: data/country-handbook-evidence/dk/vej-9864-2020.pdf. Retsinformation's generated cover marks it Gaeldende on 10 September 2026 and the live supervisor index still links it. This guidance describes the 2020 law: use only inspected, cross-checked passages, not its old scope numbering, NemID guidance or reporting references. Inspected introduction, sections 9.1 (legal entities), 9.3, 9.6 and 9.6.1-9.6.3, 17.1-17.2 and 18-18.1. MitID-specific guidance below takes precedence for the mapped MitID interpretation. Guidance examples are not mandatory document checklists.
Recent document checks
: changed, document 83bf1654e4f2
: changed, document 0c28b1486859
: changed, document 56be2e927b70
: changed, document bf45282bf5bc
: changed, document e7b3dba5f084
Conditions
Use the customer's risk and available reliable evidence to select the verification method; higher risk may require additional controls.
When section 10 re-triggers CDD during an investigation, this entry covers the same identity task; an investigation label alone is not a new identity-data request.
Data items describe fields or evidence categories, not a duty to collect every listed alternative.
Exceptions
No CPR/equivalent: date of birth is the statutory fallback. Lack of standard photo ID does not by itself establish failed CDD.
Evidence diagnostics
Record ID
dk-individual-identity
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
verification
Baseline review status
source checked
Review status
needs review
Effective from
Not recorded
Effective to
Not recorded
Resolve CDD gaps and terminate where mandatory CDD cannot be completed · review pendinglegislation / Review pending
Resolve CDD gaps and terminate where mandatory CDD cannot be completed
What this requires
If specified CDD requirements cannot be met, interrupt or wind down an existing relationship, stop further transactions and consider reporting; first assess reasonable alternative ways to complete CDD.
RegCanary explanation
Section 14(5) applies when section 11(1) nos. 1-4 and section 11(2)-(3) cannot be satisfied: interrupt/wind down the relationship, do not perform further transactions and consider a section 26 report. Section 15 separately requires appropriate mitigation, including considering termination, when information is insufficient and cannot be updated. Guidance section 18.1 interprets the AML termination duty as requiring both exhaustion of all ways to complete CDD and an assessed ML/TF risk; absence of the firm's preferred ID or refusal of one information request is not sufficient by itself. Document that interpretive risk condition, rather than silently deleting it or treating it as a statutory exemption: section 14(5) does not expressly state a separate risk exception and remains controlling. Section 18.1 then distinguishes an existing fixed loan, which is to run down on its agreed repayment profile, from further customer transactions/activities, which must stop; the credit facility must be withdrawn, including adjustment in relation to the run-off agreement where relevant. This supports qualified servicing of an existing fixed obligation, not new lending, redraws or continued payment-account use. Apply separate AML holds and sanctions restrictions to repayments and any closing balance. For consumer basic payment accounts, also apply the access and termination rows; a notice period or complaint is not permission to transact contrary to AML or sanctions law.
Applicability
Business lines
all
Customer types
all
Stages
onboarding, ongoing, investigation, offboarding
Supporting provision
LBK 433/2026 section 14(5)-(6), section 15, p. 7; VEJ 9864/2020 sections 18-18.1, printed pp. 108-109 (PDF pp. 109-110)
Downloaded original: data/country-handbook-evidence/dk/lbk-433-2026.pdf, 35 pages; inspected with pdftotext. Current reference is supported by the live Finanstilsynet index. The consolidation includes the amendment to section 38 b from Act 1638/2025 and explains the revoked, unincorporated amendment from Act 712/2025. Publication on 21 April 2026 is NOT treated as the commencement of all provisions. The JavaScript landing page did not expose amendment-status metadata. The bounded follow-up verified promulgated Act 764/2026 and its 15 September commencement; see the promulgated Act 764/2026 and the dated governance-review limitation. Danish original governs; English summaries are editorial, not an official translation.
Downloaded original: data/country-handbook-evidence/dk/vej-9864-2020.pdf. Retsinformation's generated cover marks it Gaeldende on 10 September 2026 and the live supervisor index still links it. This guidance describes the 2020 law: use only inspected, cross-checked passages, not its old scope numbering, NemID guidance or reporting references. Inspected introduction, sections 9.1 (legal entities), 9.3, 9.6 and 9.6.1-9.6.3, 17.1-17.2 and 18-18.1. MitID-specific guidance below takes precedence for the mapped MitID interpretation. Guidance examples are not mandatory document checklists.
Recent document checks
: changed, document 83bf1654e4f2
: changed, document 0c28b1486859
: changed, document 56be2e927b70
: changed, document bf45282bf5bc
: changed, document e7b3dba5f084
Conditions
Only section 1 obliged financial activities. Distinguish new-customer verification gates, section 15 mitigation and section 14(5) impossibility. Document missing CDD components, exhausted alternatives, the guidance's ML/TF risk assessment and the legal basis of the decision.
This can arise during an investigation when a section 10 trigger exposes CDD that cannot be completed; do not defer the statutory transaction stop until an offboarding workflow begins.
Obtain case-specific Danish legal/compliance review where the guidance's risk condition or fixed-loan servicing appears to conflict with the statutory stop rule. This source reconciliation is not an executable legal exception or permission for a customer to keep transacting.
For an existing fixed loan, separately record the original repayment profile, servicing-only scope, withdrawn credit limit and approval of any proposed repayment mechanics. No universal accelerated-repayment duty, debt cancellation, set-off power or free release of collateral is established here.
Exceptions
Section 14(6)'s legal-professional exception does not exempt a retail bank.
The fixed-loan passage is supervisory guidance, not a general statutory exception. It does not override a sanctions freeze, FIU approval gate or other payment prohibition.
Evidence diagnostics
Record ID
dk-cdd-failure-offboarding
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
cdd
Baseline review status
source checked
Review status
needs review
Effective from
Not recorded
Effective to
Not recorded
Verification
United Kingdom
Separate individual information from verification evidence · review pendingguidance / Review pending
Separate individual information from verification evidence
What this requires
JMLSG guidance says to obtain an individual's full name, residential address and date of birth; its standard documentary route verifies the name plus either the address or date of birth.
RegCanary explanation
MLR regulation 28 requires identification and reliable, independent verification when CDD applies, but does not prescribe a universal document set. JMLSG Part I 5.3.71 says firms should obtain full name, residential address and date of birth. Paragraphs 5.3.72-5.3.75 describe reliable documentary, electronic or combined evidence and two documentary routes. Paragraph 5.3.112 confirms that the standard verification is name plus a choice of address or date of birth, rather than address verification in every case. This remains guidance supporting risk-based verification, not a statutory passport-and-utility-bill checklist.
Applicability
Business lines
all
Customer types
individual
Stages
onboarding
Supporting provision
JMLSG Part I paragraphs 5.3.69-5.3.75 and 5.3.112 (PDF pages 88 and 96 in the retained August 2025 Part I)
Baseline document
Joint Money Laundering Steering Group
Source diagnostics
Lifecycle
Not recorded
Language
en
Retrieved
10 Sept 2026
Extraction
captured
Latest automated check
12 Oct 2026
Check outcome
unchanged
Evidence review
unvalidated
Type
guidance
Version
June 2023, updated August 2025, as linked from Current Guidance; read with later revisions
Original downloaded to data/country-handbook-evidence/uk/jmlsg-part-i-aug-2025.pdf. Paragraphs 5.3.69-5.3.75 inspected via web text and PDF page 88 via pdftotext. Current means publisher-listed base guidance, not that all text reflects 2026 law. No wholesale republication; original is a local research capture subject to publisher rights. Core-control expansion checked paragraphs 6.32 and 8.21-8.23 using pdftotext on the retained original. The five-year suspicion-report retention statement is guidance, not a new statutory period.
Recent document checks
: unchanged, document 5ddd575e79e3
: unchanged, document 5ddd575e79e3
: unchanged, document 5ddd575e79e3
: unchanged, document 5ddd575e79e3
: unchanged, document 5ddd575e79e3
Review pending
Joint Money Laundering Steering Group
Source diagnostics
Lifecycle
Not recorded
Language
en
Retrieved
11 Sept 2026
Extraction
captured
Latest automated check
12 Oct 2026
Check outcome
unchanged
Evidence review
requires-revalidation
Type
guidance
Version
Publisher current-guidance index captured 11 September 2026; 2026 MLR update in progress
Web-fetched index. Publisher warns that guidance is being updated for SI 2026/621 and must be read with the Revisions tab. Part III is under review. The index is evidence of publication state, not the basis for a source_checked substantive requirement. Delivery original captured from https://www.jmlsg.org.uk/guidance/current-guidance/ at 2026-09-11T07:29:04.998Z to data/country-handbook-evidence/uk/uk-jmlsg-current-delivery-20260911.html; SHA-256 8fce48f4def8f87d362136ca75e6d79dbfa77e7e2452add8293f3be115119879. Timestamp records local download completion. Official publisher English, not a translation. The original's text was inspected; capture does not imply every provision is verified.
Recent document checks
: unchanged, document 2ea97bb47583
: unchanged, document 2ea97bb47583
: unchanged, document 2ea97bb47583
: unchanged, document 2ea97bb47583
: unchanged, document 2ea97bb47583
Review pending
Joint Money Laundering Steering Group
Source diagnostics
Lifecycle
Not recorded
Language
en
Retrieved
11 Sept 2026
Extraction
captured
Latest automated check
12 Oct 2026
Check outcome
unchanged
Evidence review
requires-revalidation
Type
guidance
Version
Live revision register including September and February 2026
Web content checked. September and February 2026 revisions are labelled awaiting HMT approval; June 2025 revisions are labelled HMT approval received. Neither consultation nor board approval is represented as ministerial approval. Delivery original captured from https://www.jmlsg.org.uk/revisions/ at 2026-09-11T07:29:05.634Z to data/country-handbook-evidence/uk/uk-jmlsg-revisions-delivery-20260911.html; SHA-256 a3a317d1672497cfb1b510a492b42c729bcd586a9624e62eb5b342029e81d9be. Timestamp records local download completion. Official publisher English, not a translation. The original's text was inspected; capture does not imply every provision is verified.
Recent document checks
: unchanged, document 6a006e15e117
: unchanged, document 6a006e15e117
: unchanged, document 6a006e15e117
: unchanged, document 6a006e15e117
: unchanged, document 6a006e15e117
Information and evidence
Information items
Structured information items
Information
Classification
Condition
Provision
Full name
guidance information
Initial individual onboarding within the relevant JMLSG Part II sector scope.
JMLSG Part I paragraph 5.3.71
Residential address
guidance information
Initial individual onboarding within the relevant JMLSG Part II sector scope.
JMLSG Part I paragraph 5.3.71
Date of birth
guidance information
Initial individual onboarding within the relevant JMLSG Part II sector scope.
JMLSG Part I paragraph 5.3.71
Reliable, independent evidence of identity
statutory outcome
When regulation 27 requires CDD; JMLSG guidance assists the evidence assessment but does not replace the statutory outcome.
MLR 2017 regulation 28(2)(b) and (18)-(19)
Documentary evidence for the name plus either residential address or date of birth
evidence option
If the standard JMLSG documentary route is selected; it is not a universal document pack.
JMLSG Part I paragraph 5.3.112
Reliable electronic or combined evidence route
evidence option
Where the selected evidence remains reliable, independent and appropriate to the risk.
JMLSG Part I paragraphs 5.3.72-5.3.75
Evidence diagnostics
Record ID
uk-jmlsg-individual-evidence
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
verification
Baseline review status
source checked
Review status
needs review
Effective from
Not recorded
Effective to
Not recorded
No conditions are recorded. This does not establish that none apply.
No exceptions are recorded. This does not establish that none apply.
Identify and verify long-term insurance beneficiaries
What this requires
When a credit or financial institution provides a customer with a long-term insurance contract, identify designated beneficiaries and verify them before payment.
RegCanary explanation
Record the full name of a named beneficiary or legal arrangement. For beneficiaries designated by class or characteristics, obtain enough information to establish identity before payment. When rights are assigned to a new beneficiary receiving value for its own benefit, identify that beneficiary as soon as possible after awareness and in any event before payment. For a life insurance policy, consider the beneficiary's nature and identity in the risk assessment; where a beneficiary is a high-risk legal person or arrangement, take reasonable measures to identify and verify its beneficial owner before payment. For long-term insurance, take reasonable measures to determine beneficiary or beneficiary-owner PEP, family-member or known-close-associate status before payment or assignment. Where the beneficiary is a PEP or such a connected person, inform senior management before payout and apply enhanced ongoing scrutiny to the entire policyholder relationship, even if the policyholder is not politically exposed.
Official original downloaded from https://www.legislation.gov.uk/uksi/2017/692/data.xml to data/country-handbook-evidence/uk/mlr-2017-revised.xml; parsed with Python ElementTree. Web reader rejected XHTML; direct XML succeeded. Inspected provisions and unapplied-effects metadata. Future reg. 34A and Sch. 6 para. 7(ga) are not current duties; metadata also identifies an obsolete 2019 reg. 3(1) effect that requires no application. English official legislative text, not a translation. Version dates are not assigned as commencement dates to compound requirements. Fresh read-only download completed 2026-09-10T19:02:53Z at data/country-handbook-evidence/uk/mlr-2017-entity-expansion-20260910.xml; SHA-256 is identical to the first capture. Entity expansion checked regulations 5, 6, 28, 30(6)-(7), 30A, 30ZA(5), 42-45 (selected information paragraphs) and Schedule 3AZA. See docs/country-handbooks/uk-entity-expansion.md. Core-control re-download at data/country-handbook-evidence/uk/mlr-2017-core-controls-20260910.xml completed 2026-09-10T20:35:30Z with the same SHA-256. Further inspected regulations 19A, 20, 21, 24, 29, 34, 38-41 and 64A-64H. See docs/country-handbooks/uk-coverage-completion.md. Delivery original captured from https://www.legislation.gov.uk/uksi/2017/692/data.xml at 2026-09-11T07:33:37.592Z to data/country-handbook-evidence/uk/mlr-2017-delivery-20260911.xml; SHA-256 694f11c106b2b5328a4bcabf5a2d6f48ac39ec06670302b4e19c20bcfdb70811. Timestamp records local download completion. Official publisher English, not a translation. The original's text was inspected; capture does not imply every provision is verified. Fresh XML parsed with ElementTree: legislative body and commentary are identical to the prior retained original; differences are confined to metadata. Prior originals remain retained.
Recent document checks
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
Evidence diagnostics
Record ID
uk-insurance-beneficiary-checks
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
verification
Baseline review status
source checked
Review status
needs review
Effective from
Not recorded
Effective to
Not recorded
No conditions are recorded. This does not establish that none apply.
No exceptions are recorded. This does not establish that none apply.
Verify the customer and assess the purpose of the relationship. Where a person purports to act on the customer's behalf, separately verify authority to act, identify that person and verify their identity using a source independent of both the person and the customer.
RegCanary explanation
In company or trust scenarios, a board-member name, beneficial-owner identity and authority to instruct are different matters. Regulation 28(3)(b)(ii) concerns reasonable determination and verification of directors' and senior personnel's full names; it is not itself a direction to obtain a passport for every director. Paragraph (10) applies when someone purports to act for the customer. Beneficial-owner verification under (4) does not establish that person's authority to act. Paragraphs (18)-(19) allow reliable independent documentary/information evidence and qualifying electronic identification; no universal document pair is prescribed.
Applicability
Business lines
all
Customer types
all
Stages
all
Supporting provision
MLR 2017 regulation 28(1)-(4), (10), (12)-(15) and (18)-(19), read with regulation 30
Review pending
HM Treasury / legislation.gov.uk
Source diagnostics
Lifecycle
Not recorded
Language
en
Retrieved
11 Sept 2026
Extraction
captured
Latest automated check
12 Oct 2026
Check outcome
unchanged
Evidence review
requires-revalidation
Type
legislation
Version
Revised XML retrieved 2026-09-11; document RestrictStartDate 2026-06-30; individual provisions have different amendment histories
Official original downloaded from https://www.legislation.gov.uk/uksi/2017/692/data.xml to data/country-handbook-evidence/uk/mlr-2017-revised.xml; parsed with Python ElementTree. Web reader rejected XHTML; direct XML succeeded. Inspected provisions and unapplied-effects metadata. Future reg. 34A and Sch. 6 para. 7(ga) are not current duties; metadata also identifies an obsolete 2019 reg. 3(1) effect that requires no application. English official legislative text, not a translation. Version dates are not assigned as commencement dates to compound requirements. Fresh read-only download completed 2026-09-10T19:02:53Z at data/country-handbook-evidence/uk/mlr-2017-entity-expansion-20260910.xml; SHA-256 is identical to the first capture. Entity expansion checked regulations 5, 6, 28, 30(6)-(7), 30A, 30ZA(5), 42-45 (selected information paragraphs) and Schedule 3AZA. See docs/country-handbooks/uk-entity-expansion.md. Core-control re-download at data/country-handbook-evidence/uk/mlr-2017-core-controls-20260910.xml completed 2026-09-10T20:35:30Z with the same SHA-256. Further inspected regulations 19A, 20, 21, 24, 29, 34, 38-41 and 64A-64H. See docs/country-handbooks/uk-coverage-completion.md. Delivery original captured from https://www.legislation.gov.uk/uksi/2017/692/data.xml at 2026-09-11T07:33:37.592Z to data/country-handbook-evidence/uk/mlr-2017-delivery-20260911.xml; SHA-256 694f11c106b2b5328a4bcabf5a2d6f48ac39ec06670302b4e19c20bcfdb70811. Timestamp records local download completion. Official publisher English, not a translation. The original's text was inspected; capture does not imply every provision is verified. Fresh XML parsed with ElementTree: legislative body and commentary are identical to the prior retained original; differences are confined to metadata. Prior originals remain retained.
Recent document checks
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
Information and evidence
Information items
Structured information items
Information
Classification
Condition
Provision
Reliable, independent verification of the customer's identity
statutory outcome
When regulation 27 requires CDD, subject to the timing rules and safeguards in regulation 30.
MLR 2017 regulation 28(2)(b) and (18)-(19)
Assessment of the relationship's purpose and intended nature
conditional information
Obtain information where appropriate to the risk-based CDD assessment.
MLR 2017 regulation 28(2)(c)
Evidence diagnostics
Record ID
uk-independent-verification
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
verification
Baseline review status
source checked
Review status
needs review
Effective from
Not recorded
Effective to
Not recorded
No conditions are recorded. This does not establish that none apply.
No exceptions are recorded. This does not establish that none apply.
Control verification timing and failed CDD · review pendinglegislation / Review pending
Control verification timing and failed CDD
What this requires
Normally complete verification before the relationship or transaction; restrict or end activity when required CDD cannot be completed.
RegCanary explanation
Limited timing relief requires the statutory safeguards. If regulation 28 CDD cannot be applied, regulation 31 prohibits specified transactions/new relationships, requires termination of existing relationships and requires consideration of a POCA/TACT disclosure. Termination or returning funds is not automatically authorised by a SAR.
Applicability
Business lines
all
Customer types
all
Stages
all
Supporting provision
MLR 2017 regulations 30(1)-(5) and 31(1)-(5)
Review pending
HM Treasury / legislation.gov.uk
Source diagnostics
Lifecycle
Not recorded
Language
en
Retrieved
11 Sept 2026
Extraction
captured
Latest automated check
12 Oct 2026
Check outcome
unchanged
Evidence review
requires-revalidation
Type
legislation
Version
Revised XML retrieved 2026-09-11; document RestrictStartDate 2026-06-30; individual provisions have different amendment histories
Official original downloaded from https://www.legislation.gov.uk/uksi/2017/692/data.xml to data/country-handbook-evidence/uk/mlr-2017-revised.xml; parsed with Python ElementTree. Web reader rejected XHTML; direct XML succeeded. Inspected provisions and unapplied-effects metadata. Future reg. 34A and Sch. 6 para. 7(ga) are not current duties; metadata also identifies an obsolete 2019 reg. 3(1) effect that requires no application. English official legislative text, not a translation. Version dates are not assigned as commencement dates to compound requirements. Fresh read-only download completed 2026-09-10T19:02:53Z at data/country-handbook-evidence/uk/mlr-2017-entity-expansion-20260910.xml; SHA-256 is identical to the first capture. Entity expansion checked regulations 5, 6, 28, 30(6)-(7), 30A, 30ZA(5), 42-45 (selected information paragraphs) and Schedule 3AZA. See docs/country-handbooks/uk-entity-expansion.md. Core-control re-download at data/country-handbook-evidence/uk/mlr-2017-core-controls-20260910.xml completed 2026-09-10T20:35:30Z with the same SHA-256. Further inspected regulations 19A, 20, 21, 24, 29, 34, 38-41 and 64A-64H. See docs/country-handbooks/uk-coverage-completion.md. Delivery original captured from https://www.legislation.gov.uk/uksi/2017/692/data.xml at 2026-09-11T07:33:37.592Z to data/country-handbook-evidence/uk/mlr-2017-delivery-20260911.xml; SHA-256 694f11c106b2b5328a4bcabf5a2d6f48ac39ec06670302b4e19c20bcfdb70811. Timestamp records local download completion. Official publisher English, not a translation. The original's text was inspected; capture does not imply every provision is verified. Fresh XML parsed with ElementTree: legislative body and commentary are identical to the prior retained original; differences are confined to metadata. Prior originals remain retained.
Recent document checks
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
Evidence diagnostics
Record ID
uk-verification-timing
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
verification
Baseline review status
source checked
Review status
needs review
Effective from
Not recorded
Effective to
Not recorded
No conditions are recorded. This does not establish that none apply.
No exceptions are recorded. This does not establish that none apply.
Validate and supervise remote identity verification
What this requires
Remote onboarding needs risk-based eligibility, tested technology, reliable identity evidence, fraud safeguards and documented intervention when checks fail. These are supervisory guidelines, not a universal demand for a particular document or biometric.
RegCanary explanation
The EBA guidelines call for approved procedures, pre-implementation assessment and testing, and ongoing review when risks, defects, fraud or legal requirements change. Define the required customer information and reliable sources; preserve readable, time-stamped evidence securely. Interrupt and restart the process or redirect to face-to-face verification where poor quality or ambiguity prevents adequate checks. Document-based checks address authenticity, tampering and accurate extraction. Unattended photo or video identification includes liveness and reliable matching; attended sessions need trained staff and adequate audiovisual quality. Assess the effect of material deficiencies on existing customers and take proportionate remedial action. Control third-party access, security and responsibilities. Non-traditional identity evidence may call for additional or human checks, not automatic exclusion.
Applicability
Business lines
retail banking
Customer types
individual
Stages
onboarding, ongoing
Supporting provision
EBA/GL/2022/15, section 3 (application), PDF p. 4; section 4 paras. 9-28, 33-45, 46-54, PDF pp. 5-17; LBK 433/2026 sections 11 and 14; VEJ 9426/2023, MitID conditions
Downloaded original: data/country-handbook-evidence/dk/lbk-433-2026.pdf, 35 pages; inspected with pdftotext. Current reference is supported by the live Finanstilsynet index. The consolidation includes the amendment to section 38 b from Act 1638/2025 and explains the revoked, unincorporated amendment from Act 712/2025. Publication on 21 April 2026 is NOT treated as the commencement of all provisions. The JavaScript landing page did not expose amendment-status metadata. The bounded follow-up verified promulgated Act 764/2026 and its 15 September commencement; see the promulgated Act 764/2026 and the dated governance-review limitation. Danish original governs; English summaries are editorial, not an official translation.
Downloaded original: data/country-handbook-evidence/dk/eba-remote-onboarding-2022-da.pdf. 17 pages, 223,817 bytes. Actual Danish link discovered on the official EBA publication page after an incorrect candidate returned 404 and was not retained. Current Finanstilsynet AML index links the guidelines. Inspected legal status, scope/application and section 4 paras. 9-28, 33-54; entity-specific paras. 29-32 are not part of this individual delta. Qualifying eID/trust-service treatment is paragraph-specific (15, 25, 45); paragraph 44 additional controls are examples. Article 16 guidance, not a statutory universal biometric rule. No vendor, privacy or technical-assurance validation.
Downloaded and fully text-inspected original: data/country-handbook-evidence/dk/vej-9426-2023-mitid.pdf. Generated cover marks it Gaeldende and current index links it. A web-tool PDF request errored, but curl successfully captured the actual PDF. Guidance anticipated a possible review in 2024; that statement is not evidence of replacement. Applies to MitID at substantial assurance, subject to customer-specific risk and no enhanced-CDD trigger; not a blanket CDD exemption.
Recent document checks
: changed, document 7cb305206cca
: changed, document 857e3c8dc93e
: changed, document bf228e9eee2d
: changed, document 42dd9aae19a2
: changed, document 251f69e4e0e7
Conditions
Mapped for retail banks onboarding individual customers remotely within the EBA guideline scope. The guidelines apply from 2 October 2023; their Article 16 supervisory status is distinct from the Danish Act. Finanstilsynet links them, but its formal EBA compliance notification was not independently checked.
Qualifying notified electronic identification at substantial or high assurance, or qualified trust services, receive only the specific deemed-compliance treatment in paragraphs 15, 25 and 45. These provisions do not remove all CDD, customer-risk or monitoring duties. Apply the separate Danish MitID conditions.
Paragraph 44 gives non-exhaustive, risk-proportionate additional controls, with one or more controls or an equivalent measure where proportionate to the relationship's ML/TF risk. Its first-funding example is a payment from an account held solely or jointly by the customer at an EEA-regulated credit or financial institution, or at a third-country credit or financial institution subject to AML/TF requirements no less stringent than Directive 2015/849. One-time codes, further biometric comparison, telephone contact or direct mail are other examples, not a mandatory cumulative checklist. The first-funding example is not required for every customer.
Exceptions
No particular vendor, biometric method or two-document rule is mandated by this summary. No implementation, privacy impact assessment or fraud-performance test is certified here.
Evidence diagnostics
Record ID
dk-remote-onboarding-controls
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
verification
Baseline review status
source checked
Review status
needs review
Effective from
2 Oct 2023
Effective to
Not recorded
Identify and independently verify the individual customer · review pendinglegislation / Review pending
Identify and independently verify the individual customer
What this requires
Obtain name and CPR number or equivalent; if neither exists obtain date of birth. Verify identity using a reliable, independent source.
RegCanary explanation
Customer-provided details must be checked against independent documents, data or information, including recognised secure electronic identification processes. The general guidance section 9.3 explains that photo ID is not universally mandatory and that alternative reliable sources may be needed for customers unable to supply standard documents. Its passport, driving-licence, public-authority and residence-document examples are alternatives to assess, not a cumulative statutory checklist. A utility bill or Danish address is not made a universal identity requirement by section 11(1) no. 1(a).
Applicability
Business lines
all
Customer types
individual
Stages
onboarding, ongoing, investigation
Supporting provision
LBK 433/2026 section 11(1) nos. 1(a), 2, pp. 5-6; VEJ 9864/2020 section 9.3, printed pp. 59-60 (PDF pp. 60-61)
Downloaded original: data/country-handbook-evidence/dk/lbk-433-2026.pdf, 35 pages; inspected with pdftotext. Current reference is supported by the live Finanstilsynet index. The consolidation includes the amendment to section 38 b from Act 1638/2025 and explains the revoked, unincorporated amendment from Act 712/2025. Publication on 21 April 2026 is NOT treated as the commencement of all provisions. The JavaScript landing page did not expose amendment-status metadata. The bounded follow-up verified promulgated Act 764/2026 and its 15 September commencement; see the promulgated Act 764/2026 and the dated governance-review limitation. Danish original governs; English summaries are editorial, not an official translation.
Downloaded original: data/country-handbook-evidence/dk/vej-9864-2020.pdf. Retsinformation's generated cover marks it Gaeldende on 10 September 2026 and the live supervisor index still links it. This guidance describes the 2020 law: use only inspected, cross-checked passages, not its old scope numbering, NemID guidance or reporting references. Inspected introduction, sections 9.1 (legal entities), 9.3, 9.6 and 9.6.1-9.6.3, 17.1-17.2 and 18-18.1. MitID-specific guidance below takes precedence for the mapped MitID interpretation. Guidance examples are not mandatory document checklists.
Recent document checks
: changed, document 83bf1654e4f2
: changed, document 0c28b1486859
: changed, document 56be2e927b70
: changed, document bf45282bf5bc
: changed, document e7b3dba5f084
Conditions
Use the customer's risk and available reliable evidence to select the verification method; higher risk may require additional controls.
When section 10 re-triggers CDD during an investigation, this entry covers the same identity task; an investigation label alone is not a new identity-data request.
Data items describe fields or evidence categories, not a duty to collect every listed alternative.
Exceptions
No CPR/equivalent: date of birth is the statutory fallback. Lack of standard photo ID does not by itself establish failed CDD.
Evidence diagnostics
Record ID
dk-individual-identity
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
verification
Baseline review status
source checked
Review status
needs review
Effective from
Not recorded
Effective to
Not recorded
Use MitID as a conditional identity control, not complete CDD · review pendingguidance / Review pending
Use MitID as a conditional identity control, not complete CDD
What this requires
MitID at substantial assurance may stand alone for identity verification in suitable low- or medium-risk cases, including remote customers, but not as a sole control for enhanced-CDD cases.
RegCanary explanation
The guidance permits a process in which the customer gives name and CPR number and confirms identity through MitID, subject to assessment of the individual customer. Add other verification sources where the circumstances require them. MitID verifies identity only: it does not establish the relationship's purpose, risk classification, source of funds or the adequacy of monitoring. The old general guidance's NemID-only restrictions must not be mechanically applied to MitID.
Applicability
Business lines
all
Customer types
individual
Stages
onboarding, ongoing
Supporting provision
VEJ 9426/2023 'Sammenfatning', printed p. 1; 'Baggrund', printed pp. 2-3; 'Hvornaar kan MitID bruges som en kontrolkilde til identifikation, og hvilken betydning har det?', printed p. 3 (PDF pp. 2-4); LBK 433/2026 section 11(1) no. 2
Downloaded and fully text-inspected original: data/country-handbook-evidence/dk/vej-9426-2023-mitid.pdf. Generated cover marks it Gaeldende and current index links it. A web-tool PDF request errored, but curl successfully captured the actual PDF. Guidance anticipated a possible review in 2024; that statement is not evidence of replacement. Applies to MitID at substantial assurance, subject to customer-specific risk and no enhanced-CDD trigger; not a blanket CDD exemption.
Downloaded original: data/country-handbook-evidence/dk/lbk-433-2026.pdf, 35 pages; inspected with pdftotext. Current reference is supported by the live Finanstilsynet index. The consolidation includes the amendment to section 38 b from Act 1638/2025 and explains the revoked, unincorporated amendment from Act 712/2025. Publication on 21 April 2026 is NOT treated as the commencement of all provisions. The JavaScript landing page did not expose amendment-status metadata. The bounded follow-up verified promulgated Act 764/2026 and its 15 September commencement; see the promulgated Act 764/2026 and the dated governance-review limitation. Danish original governs; English summaries are editorial, not an official translation.
Recent document checks
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
Conditions
Only section 1 obliged activities. Verify the assurance level actually achieved and suitability for the customer. No enhanced-CDD trigger may be ignored merely because MitID succeeded.
Exceptions
MitID alone is not the guidance's route for high-risk customers. A customer-specific concern can require supplementary sources even at low or medium risk.
Evidence diagnostics
Record ID
dk-mitid-verification
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
verification
Baseline review status
source checked
Review status
needs review
Effective from
Not recorded
Effective to
Not recorded
Gate relationship establishment and transactions on identity verification · review pendinglegislation / Review pending
Gate relationship establishment and transactions on identity verification
What this requires
Verify the customer and beneficial owners before establishing the relationship or executing a transaction, subject only to defined exceptions.
RegCanary explanation
Section 14(2) permits verification during establishment only where necessary not to interrupt normal business and ML/TF risk is limited; complete it as soon as possible after first contact. General guidance section 17.1 explains that preliminary account creation does not allow a transaction before identification and verification. The securities-account exception in section 14(3) requires safeguards preventing transactions until verification is complete. The 30-day temporary gaming-account rule is not a retail banking grace period.
Applicability
Business lines
all
Customer types
all
Stages
onboarding
Supporting provision
LBK 433/2026 section 14(1)-(4), pp. 6-7; VEJ 9864/2020 sections 17.1-17.2, printed pp. 107-108 (PDF pp. 108-109)
Downloaded original: data/country-handbook-evidence/dk/lbk-433-2026.pdf, 35 pages; inspected with pdftotext. Current reference is supported by the live Finanstilsynet index. The consolidation includes the amendment to section 38 b from Act 1638/2025 and explains the revoked, unincorporated amendment from Act 712/2025. Publication on 21 April 2026 is NOT treated as the commencement of all provisions. The JavaScript landing page did not expose amendment-status metadata. The bounded follow-up verified promulgated Act 764/2026 and its 15 September commencement; see the promulgated Act 764/2026 and the dated governance-review limitation. Danish original governs; English summaries are editorial, not an official translation.
Downloaded original: data/country-handbook-evidence/dk/vej-9864-2020.pdf. Retsinformation's generated cover marks it Gaeldende on 10 September 2026 and the live supervisor index still links it. This guidance describes the 2020 law: use only inspected, cross-checked passages, not its old scope numbering, NemID guidance or reporting references. Inspected introduction, sections 9.1 (legal entities), 9.3, 9.6 and 9.6.1-9.6.3, 17.1-17.2 and 18-18.1. MitID-specific guidance below takes precedence for the mapped MitID interpretation. Guidance examples are not mandatory document checklists.
Recent document checks
: changed, document 83bf1654e4f2
: changed, document 0c28b1486859
: changed, document 56be2e927b70
: changed, document bf45282bf5bc
: changed, document e7b3dba5f084
Conditions
Only section 1 obliged activities. Document both section 14(2) conditions before any deferral; no general numerical banking deadline is specified.
Exceptions
Section 14(3) applies to the described securities account/depot structure with transaction safeguards; section 14(4) is gaming-specific and excluded from this financial journey.
Apply EDD and enhanced monitoring when regulation 33 triggers are met.
RegCanary explanation
Triggers include assessed high risk, specified correspondent and PEP cases, false identity evidence where dealing continues, unusual transactions and countries on FATF's call-for-action list. For the country trigger, obtain additional customer/owner and relationship information, source of funds/wealth, transaction reasons and senior-management approval, with increased monitoring. Unusual transactions require examination of background and purpose. False or stolen identification triggers this specific duty when the firm proposes to continue dealing; a fraud concern does not by itself establish the separate POCA or TACT disclosure threshold.
Applicability
Business lines
all
Customer types
all
Stages
all
Supporting provision
MLR 2017 regulation 33(1)-(4), (5)-(7)
Review pending
HM Treasury / legislation.gov.uk
Source diagnostics
Lifecycle
Not recorded
Language
en
Retrieved
11 Sept 2026
Extraction
captured
Latest automated check
12 Oct 2026
Check outcome
unchanged
Evidence review
requires-revalidation
Type
legislation
Version
Revised XML retrieved 2026-09-11; document RestrictStartDate 2026-06-30; individual provisions have different amendment histories
Official original downloaded from https://www.legislation.gov.uk/uksi/2017/692/data.xml to data/country-handbook-evidence/uk/mlr-2017-revised.xml; parsed with Python ElementTree. Web reader rejected XHTML; direct XML succeeded. Inspected provisions and unapplied-effects metadata. Future reg. 34A and Sch. 6 para. 7(ga) are not current duties; metadata also identifies an obsolete 2019 reg. 3(1) effect that requires no application. English official legislative text, not a translation. Version dates are not assigned as commencement dates to compound requirements. Fresh read-only download completed 2026-09-10T19:02:53Z at data/country-handbook-evidence/uk/mlr-2017-entity-expansion-20260910.xml; SHA-256 is identical to the first capture. Entity expansion checked regulations 5, 6, 28, 30(6)-(7), 30A, 30ZA(5), 42-45 (selected information paragraphs) and Schedule 3AZA. See docs/country-handbooks/uk-entity-expansion.md. Core-control re-download at data/country-handbook-evidence/uk/mlr-2017-core-controls-20260910.xml completed 2026-09-10T20:35:30Z with the same SHA-256. Further inspected regulations 19A, 20, 21, 24, 29, 34, 38-41 and 64A-64H. See docs/country-handbooks/uk-coverage-completion.md. Delivery original captured from https://www.legislation.gov.uk/uksi/2017/692/data.xml at 2026-09-11T07:33:37.592Z to data/country-handbook-evidence/uk/mlr-2017-delivery-20260911.xml; SHA-256 694f11c106b2b5328a4bcabf5a2d6f48ac39ec06670302b4e19c20bcfdb70811. Timestamp records local download completion. Official publisher English, not a translation. The original's text was inspected; capture does not imply every provision is verified. Fresh XML parsed with ElementTree: legislative body and commentary are identical to the prior retained original; differences are confined to metadata. Prior originals remain retained.
Recent document checks
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
Evidence diagnostics
Record ID
uk-enhanced-diligence
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
risk
Baseline review status
source checked
Review status
needs review
Effective from
Not recorded
Effective to
Not recorded
No conditions are recorded. This does not establish that none apply.
No exceptions are recorded. This does not establish that none apply.
Identify PEP exposure, assess its risk and apply the required approval, source-of-funds/wealth and monitoring controls.
RegCanary explanation
Check customers and beneficial owners for PEP, family-member and known-close-associate exposure. For domestic PEPs and connected persons, the starting point is lower risk than non-domestic PEPs; absent enhanced risk factors, EDD is less extensive. This is not an exemption from PEP controls.
Applicability
Business lines
all
Customer types
all
Stages
all
Supporting provision
MLR 2017 regulation 35(1)-(5), (9)-(15)
Review pending
HM Treasury / legislation.gov.uk
Source diagnostics
Lifecycle
Not recorded
Language
en
Retrieved
11 Sept 2026
Extraction
captured
Latest automated check
12 Oct 2026
Check outcome
unchanged
Evidence review
requires-revalidation
Type
legislation
Version
Revised XML retrieved 2026-09-11; document RestrictStartDate 2026-06-30; individual provisions have different amendment histories
Official original downloaded from https://www.legislation.gov.uk/uksi/2017/692/data.xml to data/country-handbook-evidence/uk/mlr-2017-revised.xml; parsed with Python ElementTree. Web reader rejected XHTML; direct XML succeeded. Inspected provisions and unapplied-effects metadata. Future reg. 34A and Sch. 6 para. 7(ga) are not current duties; metadata also identifies an obsolete 2019 reg. 3(1) effect that requires no application. English official legislative text, not a translation. Version dates are not assigned as commencement dates to compound requirements. Fresh read-only download completed 2026-09-10T19:02:53Z at data/country-handbook-evidence/uk/mlr-2017-entity-expansion-20260910.xml; SHA-256 is identical to the first capture. Entity expansion checked regulations 5, 6, 28, 30(6)-(7), 30A, 30ZA(5), 42-45 (selected information paragraphs) and Schedule 3AZA. See docs/country-handbooks/uk-entity-expansion.md. Core-control re-download at data/country-handbook-evidence/uk/mlr-2017-core-controls-20260910.xml completed 2026-09-10T20:35:30Z with the same SHA-256. Further inspected regulations 19A, 20, 21, 24, 29, 34, 38-41 and 64A-64H. See docs/country-handbooks/uk-coverage-completion.md. Delivery original captured from https://www.legislation.gov.uk/uksi/2017/692/data.xml at 2026-09-11T07:33:37.592Z to data/country-handbook-evidence/uk/mlr-2017-delivery-20260911.xml; SHA-256 694f11c106b2b5328a4bcabf5a2d6f48ac39ec06670302b4e19c20bcfdb70811. Timestamp records local download completion. Official publisher English, not a translation. The original's text was inspected; capture does not imply every provision is verified. Fresh XML parsed with ElementTree: legislative body and commentary are identical to the prior retained original; differences are confined to metadata. Prior originals remain retained.
Recent document checks
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
Evidence diagnostics
Record ID
uk-peps
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
risk
Baseline review status
source checked
Review status
needs review
Effective from
Not recorded
Effective to
Not recorded
No conditions are recorded. This does not establish that none apply.
No exceptions are recorded. This does not establish that none apply.
Apply sanctions ownership and control tests, not MLR thresholds · review pendinglegislation / Review pending
Apply sanctions ownership and control tests, not MLR thresholds
What this requires
For the Russia asset-freeze framework, assess both ownership and control of a non-individual person. An entity can be caught without being separately named on the sanctions list.
RegCanary explanation
Regulation 7 covers more than 50% of shares or voting rights, or the right to appoint or remove a majority of the board, directly or indirectly. Separately, regulation 7(4) asks whether, having regard to all the circumstances, it is reasonable to expect that another person could, if they chose, make the entity's affairs follow their wishes in most cases or in significant respects, by whatever means, directly or indirectly. This is a test of ability if chosen; demonstrated exercise of control is not required. Schedule 1 addresses joint interests and arrangements, indirect chains, nominees and control of rights. This is not the MLR corporate beneficial-owner test, which includes more than 25% and separate control routes.
Original downloaded to data/country-handbook-evidence/uk/russia-sanctions-revised-20260911.xml. ElementTree extraction checked regulations 2-3, 5, 7-8, 10-15, 19, 58, 64, 66-67, 70-71 and 79(3), (6), Schedule 1 and selected Schedule 5 paragraphs. No future RestrictStartDate nodes or Unapplied metadata elements found in the downloaded snapshot; this is not a comprehensive amendment/legal-perimeter audit. These source_checked additions map only the stated Russia-regime provisions, not all sectoral sanctions or all UK regimes. Native English statutory original, not a translation. Freeze recheck: official original recaptured unchanged at data/country-handbook-evidence/uk/russia-sanctions-freeze-20260911.xml, 2026-09-11T07:50:08.614Z; SHA-256 146f749d478109c2e8c72d7620eaab8dbe1352d270d35828e95566935573e99f matches the retained source. Further inspected regulations 18A, 70(1ZA)-(1ZB), (3)-(4), (7), 71 and 79(3), (5)-(6).
Recent document checks
: unchanged, document 146f749d4781
: unchanged, document 146f749d4781
: unchanged, document 146f749d4781
: unchanged, document 146f749d4781
: unchanged, document 146f749d4781
Review pending
HM Treasury / legislation.gov.uk
Source diagnostics
Lifecycle
Not recorded
Language
en
Retrieved
11 Sept 2026
Extraction
captured
Latest automated check
12 Oct 2026
Check outcome
unchanged
Evidence review
requires-revalidation
Type
legislation
Version
Revised XML retrieved 2026-09-11; document RestrictStartDate 2026-06-30; individual provisions have different amendment histories
Official original downloaded from https://www.legislation.gov.uk/uksi/2017/692/data.xml to data/country-handbook-evidence/uk/mlr-2017-revised.xml; parsed with Python ElementTree. Web reader rejected XHTML; direct XML succeeded. Inspected provisions and unapplied-effects metadata. Future reg. 34A and Sch. 6 para. 7(ga) are not current duties; metadata also identifies an obsolete 2019 reg. 3(1) effect that requires no application. English official legislative text, not a translation. Version dates are not assigned as commencement dates to compound requirements. Fresh read-only download completed 2026-09-10T19:02:53Z at data/country-handbook-evidence/uk/mlr-2017-entity-expansion-20260910.xml; SHA-256 is identical to the first capture. Entity expansion checked regulations 5, 6, 28, 30(6)-(7), 30A, 30ZA(5), 42-45 (selected information paragraphs) and Schedule 3AZA. See docs/country-handbooks/uk-entity-expansion.md. Core-control re-download at data/country-handbook-evidence/uk/mlr-2017-core-controls-20260910.xml completed 2026-09-10T20:35:30Z with the same SHA-256. Further inspected regulations 19A, 20, 21, 24, 29, 34, 38-41 and 64A-64H. See docs/country-handbooks/uk-coverage-completion.md. Delivery original captured from https://www.legislation.gov.uk/uksi/2017/692/data.xml at 2026-09-11T07:33:37.592Z to data/country-handbook-evidence/uk/mlr-2017-delivery-20260911.xml; SHA-256 694f11c106b2b5328a4bcabf5a2d6f48ac39ec06670302b4e19c20bcfdb70811. Timestamp records local download completion. Official publisher English, not a translation. The original's text was inspected; capture does not imply every provision is verified. Fresh XML parsed with ElementTree: legislative body and commentary are identical to the prior retained original; differences are confined to metadata. Prior originals remain retained.
Recent document checks
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
Evidence diagnostics
Record ID
uk-russia-ownership-control
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
risk
Baseline review status
source checked
Review status
needs review
Effective from
Not recorded
Effective to
Not recorded
No conditions are recorded. This does not establish that none apply.
No exceptions are recorded. This does not establish that none apply.
Tailor the extent and manner of CDD to the firm's business risk assessment and the risk in the particular customer or transaction case.
RegCanary explanation
Assess the purpose of the account, transaction or relationship, the assets to be deposited or transaction size, and the relationship's regularity and duration. Be able to demonstrate to the supervisor that the measures are appropriate, including against supervisor-identified risks. Consider the statutory customer, product, delivery-channel and geographical EDD factors. Private banking, personal-asset vehicles and complex ownership are factors to evaluate, not automatic identical risk classifications.
Applicability
Business lines
all
Customer types
all
Stages
all
Supporting provision
MLR 2017 regulation 28(12)-(13), (16)-(17), read with 18(1) and 33(6)-(7)
Review pending
HM Treasury / legislation.gov.uk
Source diagnostics
Lifecycle
Not recorded
Language
en
Retrieved
11 Sept 2026
Extraction
captured
Latest automated check
12 Oct 2026
Check outcome
unchanged
Evidence review
requires-revalidation
Type
legislation
Version
Revised XML retrieved 2026-09-11; document RestrictStartDate 2026-06-30; individual provisions have different amendment histories
Official original downloaded from https://www.legislation.gov.uk/uksi/2017/692/data.xml to data/country-handbook-evidence/uk/mlr-2017-revised.xml; parsed with Python ElementTree. Web reader rejected XHTML; direct XML succeeded. Inspected provisions and unapplied-effects metadata. Future reg. 34A and Sch. 6 para. 7(ga) are not current duties; metadata also identifies an obsolete 2019 reg. 3(1) effect that requires no application. English official legislative text, not a translation. Version dates are not assigned as commencement dates to compound requirements. Fresh read-only download completed 2026-09-10T19:02:53Z at data/country-handbook-evidence/uk/mlr-2017-entity-expansion-20260910.xml; SHA-256 is identical to the first capture. Entity expansion checked regulations 5, 6, 28, 30(6)-(7), 30A, 30ZA(5), 42-45 (selected information paragraphs) and Schedule 3AZA. See docs/country-handbooks/uk-entity-expansion.md. Core-control re-download at data/country-handbook-evidence/uk/mlr-2017-core-controls-20260910.xml completed 2026-09-10T20:35:30Z with the same SHA-256. Further inspected regulations 19A, 20, 21, 24, 29, 34, 38-41 and 64A-64H. See docs/country-handbooks/uk-coverage-completion.md. Delivery original captured from https://www.legislation.gov.uk/uksi/2017/692/data.xml at 2026-09-11T07:33:37.592Z to data/country-handbook-evidence/uk/mlr-2017-delivery-20260911.xml; SHA-256 694f11c106b2b5328a4bcabf5a2d6f48ac39ec06670302b4e19c20bcfdb70811. Timestamp records local download completion. Official publisher English, not a translation. The original's text was inspected; capture does not imply every provision is verified. Fresh XML parsed with ElementTree: legislative body and commentary are identical to the prior retained original; differences are confined to metadata. Prior originals remain retained.
Recent document checks
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
Evidence diagnostics
Record ID
uk-customer-risk-assessment
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
risk
Baseline review status
source checked
Review status
needs review
Effective from
Not recorded
Effective to
Not recorded
No conditions are recorded. This does not establish that none apply.
No exceptions are recorded. This does not establish that none apply.
Denmark
Establish relationship purpose and a defensible customer risk assessmentlegislation
Establish relationship purpose and a defensible customer risk assessment
What this requires
Assess the relationship's purpose and intended nature and calibrate CDD to its purpose, scale, regularity and duration. Simplified CDD needs an established low-risk basis.
RegCanary explanation
Section 11(1) no. 4 requires assessing and, where relevant, obtaining information on purpose and intended nature. Section 11(3)-(4) requires all CDD components and evidence that knowledge is sufficient for the risk, considering at least Annexes 2 and 3. Section 21(1) permits simplified measures only after determining low risk. Record expected use of the particular services provided, with relevant scale, frequency and geographical exposure; these must fit the customer's actual activity rather than a universal banking questionnaire. A sector-wide rating alone is not an individual risk decision. Annex 2's potentially lower-risk factors include certain limited financial-inclusion products and spending or transparency controls. Annex 3's potentially higher-risk factors include unusual relationship circumstances, private banking, products favouring anonymity, remote relationships without adequate safeguards, unknown or unconnected third-party payments, new technology and relevant geographical exposure. These non-exhaustive factors must be assessed in combination; a remote channel or nationality alone does not determine the outcome.
Applicability
Business lines
all
Customer types
all
Stages
onboarding, ongoing, investigation
Supporting provision
LBK 433/2026 section 11(1) no. 4, section 11(3)-(4), p. 6; section 21(1), p. 8; Annexes 2-3, pp. 34-35
Downloaded original: data/country-handbook-evidence/dk/lbk-433-2026.pdf, 35 pages; inspected with pdftotext. Current reference is supported by the live Finanstilsynet index. The consolidation includes the amendment to section 38 b from Act 1638/2025 and explains the revoked, unincorporated amendment from Act 712/2025. Publication on 21 April 2026 is NOT treated as the commencement of all provisions. The JavaScript landing page did not expose amendment-status metadata. The bounded follow-up verified promulgated Act 764/2026 and its 15 September commencement; see the promulgated Act 764/2026 and the dated governance-review limitation. Danish original governs; English summaries are editorial, not an official translation.
Recent document checks
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
Conditions
Only section 1 obliged activities; simplified CDD must remain sufficient for the actual customer and cannot override an enhanced-CDD trigger.
When section 10 re-triggers CDD during an investigation, reassess the relationship purpose and risk only to the extent needed for that trigger; the stage label does not prescribe a universal refresh.
Exceptions
Low risk permits reduced extent, not no CDD. The separate e-money exemption-making power in section 21(2) is not an exemption established by this row.
Evidence diagnostics
Record ID
dk-customer-purpose-risk
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
risk
Status when reviewed
current
Review status
source checked
Effective from
Not recorded
Effective to
Not recorded
Apply enhanced CDD for higher risk and listed high-risk third countrieslegislation
Apply enhanced CDD for higher risk and listed high-risk third countries
What this requires
Higher ML/TF risk requires additional CDD. A customer based in a Commission-listed high-risk third country triggers specified additional information, approval and monitoring.
RegCanary explanation
Section 17(1) requires consideration of Annex 3 and other relevant high-risk factors. Section 17(2) requires extra customer/owner and intended-relationship information, source of funds and wealth, transaction reasons, designated-person approval for establishing or continuing the relationship and enhanced monitoring. For transactions involving Commission-listed high-risk third countries, section 17(3) expressly requires the measures in subsection 2 plus one or more additional measures: supplementary CDD measures; enhanced reporting mechanisms or systematic reporting of financial transactions; or restrictions on business relationships or transactions involving those countries. The transaction-country trigger is distinct from the customer-location trigger, but its additional measures do not replace the subsection 2 information, approval or monitoring requirements. A Danish-based customer transacting with a listed country is therefore not outside subsection 3 merely because of the customer's location. Record both the subsection 2 measures and the additional measure selected. In addition to subsection 3, section 17(4), where relevant, requires the first payment through an account in the customer's name at a credit institution subject to CDD requirements at least equivalent to those in the Danish Act. No current country list is embedded here.
Applicability
Business lines
all
Customer types
all
Stages
onboarding, ongoing, investigation, offboarding
Supporting provision
LBK 433/2026 section 17(1)-(5), pp. 7-8; Annex 3, p. 35
Downloaded original: data/country-handbook-evidence/dk/lbk-433-2026.pdf, 35 pages; inspected with pdftotext. Current reference is supported by the live Finanstilsynet index. The consolidation includes the amendment to section 38 b from Act 1638/2025 and explains the revoked, unincorporated amendment from Act 712/2025. Publication on 21 April 2026 is NOT treated as the commencement of all provisions. The JavaScript landing page did not expose amendment-status metadata. The bounded follow-up verified promulgated Act 764/2026 and its 15 September commencement; see the promulgated Act 764/2026 and the dated governance-review limitation. Danish original governs; English summaries are editorial, not an official translation.
Recent document checks
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
Conditions
Only section 1 obliged activities. Distinguish customer location under section 17(2) from transactions involving a listed country under section 17(3). Check the Commission list applicable to the decision date, not just a FATF list or an internal score.
At offboarding, use this entry only where a listed-country or other higher-risk condition applies to an uncompleted relationship or final transaction; offboarding alone is not a fresh EDD trigger.
Exceptions
Section 17(5) allows a risk-based exception to subsection 2 for specified compliant branches or majority-owned subsidiaries of EU/EEA-established legal persons; not a general exception for retail individuals.
Evidence diagnostics
Record ID
dk-enhanced-cdd
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
risk
Status when reviewed
current
Review status
source checked
Effective from
Not recorded
Effective to
Not recorded
Identify PEP connections and approve higher-risk relationshipslegislation
Identify PEP connections and approve higher-risk relationships
What this requires
Maintain procedures to detect PEPs, relatives and close associates and apply source-of-funds/wealth measures, approval and enhanced monitoring where required.
RegCanary explanation
Section 18(1) covers the customer and beneficial owner, and relevant life-insurance beneficiaries. For an individual PEP, relative or close associate, subsections 2-4 require appropriate measures to establish the origin of relevant funds and wealth, approval by the section 7(2) designated person and enhanced monitoring. After a PEP leaves office, subsection 6 requires risk assessment for at least 12 months and enhanced CDD until the person no longer presents increased risk. Twelve months is not automatic declassification.
Applicability
Business lines
all
Customer types
all
Stages
onboarding, ongoing
Supporting provision
LBK 433/2026 section 2 nos. 6-8, pp. 2-3; section 18(1)-(4), (6), p. 8
Downloaded original: data/country-handbook-evidence/dk/lbk-433-2026.pdf, 35 pages; inspected with pdftotext. Current reference is supported by the live Finanstilsynet index. The consolidation includes the amendment to section 38 b from Act 1638/2025 and explains the revoked, unincorporated amendment from Act 712/2025. Publication on 21 April 2026 is NOT treated as the commencement of all provisions. The JavaScript landing page did not expose amendment-status metadata. The bounded follow-up verified promulgated Act 764/2026 and its 15 September commencement; see the promulgated Act 764/2026 and the dated governance-review limitation. Danish original governs; English summaries are editorial, not an official translation.
Recent document checks
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
Conditions
Only section 1 obliged activities. Apply statutory definitions, including foreign roles and family/close-associate connections; do not treat a Danish domestic list as exhaustive.
Corporate/trust customer tags refer to identifying relevant natural persons, not labelling an entity itself a PEP.
Exceptions
The separate insurance-beneficiary process in section 18(5) is outside the individual retail-account reference; it is not replaced by this row.
Evidence diagnostics
Record ID
dk-pep-controls
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
risk
Status when reviewed
current
Review status
source checked
Effective from
Not recorded
Effective to
Not recorded
Justify simplified CDD and assess relevant higher-risk featureslegislation
Justify simplified CDD and assess relevant higher-risk features
What this requires
Establish low risk before simplifying checks; private banking and complex ownership are risk factors, not automatic exclusions.
RegCanary explanation
Section 21 permits simplified CDD only after assessing that the relationship or transaction presents limited ML/TF risk, considering Annex 2 and other relevant factors. Section 11(3)-(4) still requires all CDD components and demonstrably sufficient customer knowledge. Annex 3 requires consideration of private banking, personal asset-holding vehicles, nominee shareholders or bearer shares, cash-intensive businesses, unusually complex ownership, anonymity, unknown third-party payments and new technology where relevant. These factors inform the assessment; enhanced CDD follows the higher-risk finding under section 17(1), while listed-country and PEP triggers have their own mandatory rules. A low-risk product label alone does not establish simplified CDD eligibility.
Applicability
Business lines
all
Customer types
all
Stages
onboarding, ongoing
Supporting provision
LBK 433/2026 section 11(3)-(4), p. 6; sections 17(1), 21(1)-(2), pp. 7-8; Annexes 2-3, pp. 34-35
Downloaded original: data/country-handbook-evidence/dk/lbk-433-2026.pdf, 35 pages; inspected with pdftotext. Current reference is supported by the live Finanstilsynet index. The consolidation includes the amendment to section 38 b from Act 1638/2025 and explains the revoked, unincorporated amendment from Act 712/2025. Publication on 21 April 2026 is NOT treated as the commencement of all provisions. The JavaScript landing page did not expose amendment-status metadata. The bounded follow-up verified promulgated Act 764/2026 and its 15 September commencement; see the promulgated Act 764/2026 and the dated governance-review limitation. Danish original governs; English summaries are editorial, not an official translation.
Recent document checks
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
Conditions
Applies only to activities within section 1 of the Danish AML Act; the firm's activity and legal form determine applicability.
Exceptions
Section 21(2) empowers e-money exemptions; no exemption is inferred from that power. Section 13's risk-based derogation is confined to assistance with an isolated activity without a transaction, not an ongoing advisory relationship.
Evidence diagnostics
Record ID
dk-simplified-cdd-risk-factors
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
risk
Status when reviewed
current
Review status
source checked
Effective from
Not recorded
Effective to
Not recorded
Assess respondents and prohibit shell-bank relationshipslegislation
Assess respondents and prohibit shell-bank relationships
What this requires
Apply correspondent due diligence where triggered, including respondent crypto authorisation and payable-through safeguards.
RegCanary explanation
Before a cross-border correspondent relationship involving payments with a respondent outside the Union where the Union has no financial agreement with the relevant country, section 19(1) requires information on the respondent's business, public reputation and supervision; sufficient information to ensure effective AML controls; designated-person approval; and documented allocation of AML responsibilities. Section 19(2) requires the correspondent to establish whether the respondent is authorised or registered in the relevant country before cryptoasset services. For direct customer access to funds at the correspondent, subsection 3 requires assurance that the respondent conducts CDD and can supply it on request. Section 20 prohibits establishing or maintaining shell-bank correspondence and requires reasonable measures to avoid respondents publicly known to let shell banks use their accounts.
Applicability
Business lines
all
Customer types
all
Stages
onboarding, ongoing, offboarding
Supporting provision
LBK 433/2026 section 2(4), pp. 2-3; section 2(11), p. 3; sections 19(1)-(3), 20(1)-(2), p. 8
Downloaded original: data/country-handbook-evidence/dk/lbk-433-2026.pdf, 35 pages; inspected with pdftotext. Current reference is supported by the live Finanstilsynet index. The consolidation includes the amendment to section 38 b from Act 1638/2025 and explains the revoked, unincorporated amendment from Act 712/2025. Publication on 21 April 2026 is NOT treated as the commencement of all provisions. The JavaScript landing page did not expose amendment-status metadata. The bounded follow-up verified promulgated Act 764/2026 and its 15 September commencement; see the promulgated Act 764/2026 and the dated governance-review limitation. Danish original governs; English summaries are editorial, not an official translation.
Recent document checks
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
Conditions
Apply only to a correspondent/respondent arrangement under section 2(4), which includes relevant securities and crypto relationships as well as bank services. Not every customer payment creates a correspondent relationship.
The shell-bank definition requires the section 2(11) characteristics, including absence of physical presence and local management and not belonging to a regulated financial group.
Evidence diagnostics
Record ID
dk-correspondent-controls
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
risk
Status when reviewed
current
Review status
source checked
Effective from
Not recorded
Effective to
Not recorded
No exceptions are recorded. This does not establish that none apply.
Payee and intermediary payment service providers must detect missing or inadmissible transfer information and operate risk-based procedures to execute, reject or suspend affected transfers.
RegCanary explanation
Request required information or reject the transfer on a risk-sensitive basis. Repeated failures require escalation, potentially restriction or termination, and a report to the competent authority. Consider missing information when assessing suspicion. For transfers exceeding EUR 1,000, including apparently linked transfers, the payee provider must verify the accuracy of the payee information using documents, data or information from a reliable and independent source before crediting the payee's payment account or making the funds available. Article 8's risk-based timing for information requests does not relax this separate verification deadline. Below or at that threshold the cash/anonymous-e-money payout and suspicion conditions remove verification relief. Under Article 7(5), verification is deemed to have occurred where identity was verified under MLR regulation 28 and the information retained under regulation 40, or where regulation 27(8) applies to the payee. Intermediaries must retain received information with the transfer.
Original downloaded to data/country-handbook-evidence/uk/uk-funds-transfer-2015-847-20260910.xml and parsed with ElementTree. Articles 2 and 4-16 checked in the UK-amended national version, not the repealed EU-only version. UK/Gibraltar scope and EUR 1,000 thresholds remain in the inspected text. Article 16(2) retains national-law qualifications; no generic ten-year permission is inferred. Web XHTML extraction failed but the official XML download succeeded.
Recent document checks
: unchanged, document 2d9221b2e9e3
: unchanged, document 2d9221b2e9e3
: unchanged, document 2d9221b2e9e3
: unchanged, document 2d9221b2e9e3
: unchanged, document 2d9221b2e9e3
Evidence diagnostics
Record ID
uk-payment-transfer-recipient
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
monitoring
Status when reviewed
current
Review status
source checked
Effective from
Not recorded
Effective to
Not recorded
No conditions are recorded. This does not establish that none apply.
No exceptions are recorded. This does not establish that none apply.
Prevent prohibited provision of funds and economic resourceslegislation
Prevent prohibited provision of funds and economic resources
What this requires
Under the Russia regime, do not make funds or economic resources available to, or for the benefit of, an asset-freeze designated person when the applicable statutory conditions are met.
RegCanary explanation
Funds made available directly or indirectly are covered by regulation 12. For economic resources, regulation 14 also requires knowledge or reasonable cause to suspect that the designated person would likely exchange or use them for funds, goods or services. Provision for a designated person's benefit under regulations 13 and 15 requires a significant financial benefit, including discharge of an obligation. Owned or controlled entities are expressly included. Intentional participation knowing that the object or effect circumvents or facilitates breach is separately prohibited.
Applicability
Business lines
all
Customer types
all
Stages
all
Supporting provision
Russia Regulations 3, 10, 12(1)-(4), 13(1)-(4), 14(1)-(4), 15(1)-(4), 19(1)-(2)
Baseline document
Secretary of State / legislation.gov.uk
Source diagnostics
Lifecycle
Not recorded
Language
en
Retrieved
10 Sept 2026
Extraction
captured
Latest automated check
12 Oct 2026
Check outcome
unchanged
Evidence review
unvalidated
Type
legislation
Version
Official revised XML captured 11 September 2026 London time; document RestrictStartDate 2026-05-20
Original downloaded to data/country-handbook-evidence/uk/russia-sanctions-revised-20260911.xml. ElementTree extraction checked regulations 2-3, 5, 7-8, 10-15, 19, 58, 64, 66-67, 70-71 and 79(3), (6), Schedule 1 and selected Schedule 5 paragraphs. No future RestrictStartDate nodes or Unapplied metadata elements found in the downloaded snapshot; this is not a comprehensive amendment/legal-perimeter audit. These source_checked additions map only the stated Russia-regime provisions, not all sectoral sanctions or all UK regimes. Native English statutory original, not a translation. Freeze recheck: official original recaptured unchanged at data/country-handbook-evidence/uk/russia-sanctions-freeze-20260911.xml, 2026-09-11T07:50:08.614Z; SHA-256 146f749d478109c2e8c72d7620eaab8dbe1352d270d35828e95566935573e99f matches the retained source. Further inspected regulations 18A, 70(1ZA)-(1ZB), (3)-(4), (7), 71 and 79(3), (5)-(6).
Recent document checks
: unchanged, document 146f749d4781
: unchanged, document 146f749d4781
: unchanged, document 146f749d4781
: unchanged, document 146f749d4781
: unchanged, document 146f749d4781
Evidence diagnostics
Record ID
uk-russia-making-available
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
monitoring
Status when reviewed
current
Review status
source checked
Effective from
Not recorded
Effective to
Not recorded
No conditions are recorded. This does not establish that none apply.
No exceptions are recorded. This does not establish that none apply.
Make the Russia annual frozen-asset return and required nil follow-uplegislation
Make the Russia annual frozen-asset return and required nil follow-up
What this requires
A person who knows or has reasonable cause to suspect that it holds funds or economic resources owned, held or controlled by a Russia asset-freeze designated person must report the 30 September position to the Treasury by 30 November each year.
RegCanary explanation
Report the nature and amount or quantity of the property held at the statutory snapshot date. This includes property held through an entity owned or controlled by the designated person. If a report was made but by 30 September in the following year the person no longer holds such property, report that fact by 30 November of that year. This annual obligation is separate from prompt relevant-firm reporting.
Applicability
Business lines
all
Customer types
all
Stages
all
Supporting provision
Russia Regulations 3(4)-(7), 70(4A)-(4D), (6A)-(7), 79(3), (6)
Baseline document
Secretary of State / legislation.gov.uk
Source diagnostics
Lifecycle
Not recorded
Language
en
Retrieved
10 Sept 2026
Extraction
captured
Latest automated check
12 Oct 2026
Check outcome
unchanged
Evidence review
unvalidated
Type
legislation
Version
Official revised XML captured 11 September 2026 London time; document RestrictStartDate 2026-05-20
Original downloaded to data/country-handbook-evidence/uk/russia-sanctions-revised-20260911.xml. ElementTree extraction checked regulations 2-3, 5, 7-8, 10-15, 19, 58, 64, 66-67, 70-71 and 79(3), (6), Schedule 1 and selected Schedule 5 paragraphs. No future RestrictStartDate nodes or Unapplied metadata elements found in the downloaded snapshot; this is not a comprehensive amendment/legal-perimeter audit. These source_checked additions map only the stated Russia-regime provisions, not all sectoral sanctions or all UK regimes. Native English statutory original, not a translation. Freeze recheck: official original recaptured unchanged at data/country-handbook-evidence/uk/russia-sanctions-freeze-20260911.xml, 2026-09-11T07:50:08.614Z; SHA-256 146f749d478109c2e8c72d7620eaab8dbe1352d270d35828e95566935573e99f matches the retained source. Further inspected regulations 18A, 70(1ZA)-(1ZB), (3)-(4), (7), 71 and 79(3), (5)-(6).
Recent document checks
: unchanged, document 146f749d4781
: unchanged, document 146f749d4781
: unchanged, document 146f749d4781
: unchanged, document 146f749d4781
: unchanged, document 146f749d4781
Evidence diagnostics
Record ID
uk-russia-annual-frozen-assets
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
monitoring
Status when reviewed
current
Review status
source checked
Effective from
Not recorded
Effective to
Not recorded
No conditions are recorded. This does not establish that none apply.
No exceptions are recorded. This does not establish that none apply.
Report holdings for Russia-regime prohibited personslegislation
Report holdings for Russia-regime prohibited persons
What this requires
A relevant firm must inform the Treasury as soon as practicable when it knows or has reasonable cause to suspect that it holds funds or economic resources for a prohibited person and that information arose in its business. A separate annual report applies after notification while the firm continues to hold those assets.
RegCanary explanation
Regulation 70(7) defines prohibited persons through regulation 18A(1), not by a general Russian nationality or political-exposure test. Regulation 18A concerns financial services for foreign-exchange reserve and asset management for the Russian Central Bank, National Wealth Fund, Ministry of Finance, their directly or indirectly owned/controlled persons, and persons acting on their behalf or direction, with its knowledge/reasonable-suspicion condition and Part 7 exceptions/licences. For the reporting duty, the trigger is holding funds or economic resources for the prohibited person; the firm need not itself have provided the prohibited management service. If that person is a customer, regulation 70(3)-(4) additionally requires the nature and amount or quantity held at first knowledge or suspicion. After a 70(1ZA) notification, where holdings continue, 70(1ZB) requires the nature and amount or quantity held as at 30 September to be reported by 30 November each calendar year.
Applicability
Business lines
all
Customer types
all
Stages
all
Supporting provision
Russia Regulations 18A(1)-(3), 70(1ZA)-(1ZB), (3)-(4), (6)-(7), 71(1), (3A)-(3C), (4), 79(3), (5)-(6); regulation 7 for ownership/control
Baseline document
Secretary of State / legislation.gov.uk
Source diagnostics
Lifecycle
Not recorded
Language
en
Retrieved
10 Sept 2026
Extraction
captured
Latest automated check
12 Oct 2026
Check outcome
unchanged
Evidence review
unvalidated
Type
legislation
Version
Official revised XML captured 11 September 2026 London time; document RestrictStartDate 2026-05-20
Original downloaded to data/country-handbook-evidence/uk/russia-sanctions-revised-20260911.xml. ElementTree extraction checked regulations 2-3, 5, 7-8, 10-15, 19, 58, 64, 66-67, 70-71 and 79(3), (6), Schedule 1 and selected Schedule 5 paragraphs. No future RestrictStartDate nodes or Unapplied metadata elements found in the downloaded snapshot; this is not a comprehensive amendment/legal-perimeter audit. These source_checked additions map only the stated Russia-regime provisions, not all sectoral sanctions or all UK regimes. Native English statutory original, not a translation. Freeze recheck: official original recaptured unchanged at data/country-handbook-evidence/uk/russia-sanctions-freeze-20260911.xml, 2026-09-11T07:50:08.614Z; SHA-256 146f749d478109c2e8c72d7620eaab8dbe1352d270d35828e95566935573e99f matches the retained source. Further inspected regulations 18A, 70(1ZA)-(1ZB), (3)-(4), (7), 71 and 79(3), (5)-(6).
Recent document checks
: unchanged, document 146f749d4781
: unchanged, document 146f749d4781
: unchanged, document 146f749d4781
: unchanged, document 146f749d4781
: unchanged, document 146f749d4781
Evidence diagnostics
Record ID
uk-russia-prohibited-person-reporting
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
monitoring
Status when reviewed
current
Review status
source checked
Effective from
Not recorded
Effective to
Not recorded
No conditions are recorded. This does not establish that none apply.
No exceptions are recorded. This does not establish that none apply.
Keep activity and CDD under review · review pendinglegislation / Review pending
Keep activity and CDD under review
What this requires
Scrutinise relationship transactions and keep customer information current on a risk-sensitive basis.
RegCanary explanation
Compare transactions with knowledge of the customer, business and risk profile, considering source of funds where necessary. Refresh records and apply CDD at appropriate times and when relevant circumstances change, including the specified beneficial-ownership and tax-contact triggers.
Applicability
Business lines
all
Customer types
all
Stages
all
Supporting provision
MLR 2017 regulations 27(8)-(9) and 28(11)-(13)
Review pending
HM Treasury / legislation.gov.uk
Source diagnostics
Lifecycle
Not recorded
Language
en
Retrieved
11 Sept 2026
Extraction
captured
Latest automated check
12 Oct 2026
Check outcome
unchanged
Evidence review
requires-revalidation
Type
legislation
Version
Revised XML retrieved 2026-09-11; document RestrictStartDate 2026-06-30; individual provisions have different amendment histories
Official original downloaded from https://www.legislation.gov.uk/uksi/2017/692/data.xml to data/country-handbook-evidence/uk/mlr-2017-revised.xml; parsed with Python ElementTree. Web reader rejected XHTML; direct XML succeeded. Inspected provisions and unapplied-effects metadata. Future reg. 34A and Sch. 6 para. 7(ga) are not current duties; metadata also identifies an obsolete 2019 reg. 3(1) effect that requires no application. English official legislative text, not a translation. Version dates are not assigned as commencement dates to compound requirements. Fresh read-only download completed 2026-09-10T19:02:53Z at data/country-handbook-evidence/uk/mlr-2017-entity-expansion-20260910.xml; SHA-256 is identical to the first capture. Entity expansion checked regulations 5, 6, 28, 30(6)-(7), 30A, 30ZA(5), 42-45 (selected information paragraphs) and Schedule 3AZA. See docs/country-handbooks/uk-entity-expansion.md. Core-control re-download at data/country-handbook-evidence/uk/mlr-2017-core-controls-20260910.xml completed 2026-09-10T20:35:30Z with the same SHA-256. Further inspected regulations 19A, 20, 21, 24, 29, 34, 38-41 and 64A-64H. See docs/country-handbooks/uk-coverage-completion.md. Delivery original captured from https://www.legislation.gov.uk/uksi/2017/692/data.xml at 2026-09-11T07:33:37.592Z to data/country-handbook-evidence/uk/mlr-2017-delivery-20260911.xml; SHA-256 694f11c106b2b5328a4bcabf5a2d6f48ac39ec06670302b4e19c20bcfdb70811. Timestamp records local download completion. Official publisher English, not a translation. The original's text was inspected; capture does not imply every provision is verified. Fresh XML parsed with ElementTree: legislative body and commentary are identical to the prior retained original; differences are confined to metadata. Prior originals remain retained.
Recent document checks
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
: unchanged, document 0a7d582b83ce
Evidence diagnostics
Record ID
uk-ongoing-monitoring
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
monitoring
Baseline review status
source checked
Review status
needs review
Effective from
Not recorded
Effective to
Not recorded
No conditions are recorded. This does not establish that none apply.
No exceptions are recorded. This does not establish that none apply.
Prepare a clear SAR through the current portal · review pendingguidance / Review pending
Prepare a clear SAR through the current portal
What this requires
Use the NCA SAR Portal and explain the suspicion, relevant parties, property and events clearly.
RegCanary explanation
Select applicable current portal glossary codes and explain their relevance. Describe who is involved, the chronology, why the activity is suspicious and the suspected criminal/terrorist property. A DAML/DATF request concerns specified future activity, is not a CDD tool and does not establish that funds are legitimate.
Applicability
Business lines
all
Customer types
all
Stages
all
Supporting provision
NCA SAR page: Submitting a SAR; UKFIU Chapter 2, Section 4 Glossary codes (p.16) and Section 5 Reason for suspicion (pp.18-20); Chapter 3 FAQ Q10 (p.19) and Q36 (p.30)
Web-fetched content, including Submitting a SAR and links to current guidance chapters. No authenticated portal accessed and no SAR submitted. Delivery original captured from https://www.nationalcrimeagency.gov.uk/what-we-do/crime-threats/money-laundering-and-illicit-finance/suspicious-activity-reports?delivery=20260911 at 2026-09-11T07:33:58.942Z to data/country-handbook-evidence/uk/nca-sars-delivery-20260911.html; SHA-256 96aa8fcf42c2b9c22c32b0d2e5fb9877a28d4ab6d5577318649d57efcaf42747. Timestamp records local download completion. Official publisher English, not a translation. The original's text was inspected; capture does not imply every provision is verified.
PDF text successfully fetched by web tool; pages 16 and 18-20 checked. Earlier direct download returned HTTP 403; the delivery capture below resolves that original-file gap. Delivery original captured from https://www.nationalcrimeagency.gov.uk/who-we-are/publications/775-ukfiu-chapter-2-submitting-a-sar/file?download=1 at 2026-09-11T07:33:38.098Z to data/country-handbook-evidence/uk/nca-sar-ch2-delivery-20260911.pdf; SHA-256 ed8efef20f0415a7d6358cb2bbd39fee08a521893845bd615b022ea93a34530d. Timestamp records local download completion. Official publisher English, not a translation. The original's text was inspected; capture does not imply every provision is verified.
Web-extracted PDF; FAQ Q10 and Q36 checked for the distinction between a specific defence request, CDD and legitimising funds. The earlier capture was web-only. This guidance source does not itself establish the separately mapped statutory notice periods, exceptions or reporting offences. Delivery original captured from https://www.nationalcrimeagency.gov.uk/who-we-are/publications/776-ukfiu-chapter-3-understanding-damls-and-datfs/file?download=1 at 2026-09-11T07:33:58.542Z to data/country-handbook-evidence/uk/nca-sar-ch3-delivery-20260911.pdf; SHA-256 d41c0fa70c5e0ed09e4327c5902d208feff0d9d161aa003f3617f31cece70f58. Timestamp records local download completion. Official publisher English, not a translation. The original's text was inspected; capture does not imply every provision is verified.
Recent document checks
: unchanged, document a7067b61c8e7
: unchanged, document a7067b61c8e7
: unchanged, document a7067b61c8e7
: unchanged, document a7067b61c8e7
: unchanged, document a7067b61c8e7
Evidence diagnostics
Record ID
uk-sar-submission
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
monitoring
Baseline review status
source checked
Review status
needs review
Effective from
Not recorded
Effective to
Not recorded
No conditions are recorded. This does not establish that none apply.
No exceptions are recorded. This does not establish that none apply.
Use current sanctions references and assess ownership/control · review pendingguidance / Review pending
Use current sanctions references and assess ownership/control
What this requires
Use the FCDO UK Sanctions List, assess ownership/control and apply relevant freezing and reporting controls.
RegCanary explanation
OFSI explains immediate freezing, dealing restrictions and relevant-firm reporting as soon as practicable. A name-only check is insufficient where an unlisted entity is owned or controlled by a designated person. SAR submission does not replace reporting to OFSI.
Applicability
Business lines
all
Customer types
all
Stages
all
Supporting provision
OFSI general guidance sections 2.2, 3.1.1-3.1.2, 4.1, 5.1.1-5.1.2, 5.3, 5.9 and 6; FCDO UK Sanctions List update dated 28 January 2026
Review pending
Office of Financial Sanctions Implementation / HM Treasury
Web-fetched official English guidance; chapters 2-6 inspected selectively. The earlier capture was web-only. Underlying sanctions instruments, particular licences and individual designations are not exhaustively checked. Original HTML now captured at data/country-handbook-evidence/uk/ofsi-general-20260911.html on 11 September 2026 London time (2026-09-10T23:43:04Z UTC). Parsed using HTMLParser excluding scripts/styles. The hash is of the original response bytes, not extracted text. Rechecked the cryptoasset/dealing definitions, reporting and frozen-account/exception passages supporting the bounded Russia additions.
Recent document checks
: unchanged, document cb2c88de51e0
: unchanged, document cb2c88de51e0
: unchanged, document cb2c88de51e0
: unchanged, document cb2c88de51e0
: unchanged, document cb2c88de51e0
Review pending
Foreign, Commonwealth & Development Office
Source diagnostics
Lifecycle
Not recorded
Language
en
Retrieved
10 Sept 2026
Extraction
captured
Latest automated check
12 Oct 2026
Check outcome
unchanged
Evidence review
requires-revalidation
Type
sanctions
Version
Live publication page; 28 January 2026 change notice confirms OFSI Consolidated List closure
Publication-page evidence only, not a downloaded designation dataset. UK Sanctions List is the current designation source; the old OFSI Consolidated List is no longer updated. List-change date is not a commencement date for sanctions prohibitions. Original HTML now captured at data/country-handbook-evidence/uk/fcdo-sanctions-list-20260911.html on 11 September 2026 London time (2026-09-10T23:43:05Z UTC). Parsed using HTMLParser excluding scripts/styles. The hash is of the original response bytes, not extracted text. Rechecked the single-list notice and separate Russia financial/investment-list notice; this capture is the publication page, not a downloaded designation dataset or case-match verification.
Recent document checks
: unchanged, document 6cdec4038406
: unchanged, document 6cdec4038406
: changed, document 6cdec4038406
: changed, document 313c54fb15e8
: changed, document b5ee89013398
Evidence diagnostics
Record ID
uk-sanctions-controls
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
monitoring
Baseline review status
source checked
Review status
needs review
Effective from
Not recorded
Effective to
Not recorded
No conditions are recorded. This does not establish that none apply.
No exceptions are recorded. This does not establish that none apply.
Report knowledge, suspicion or reasonable grounds of money laundering · review pendinglegislation / Review pending
Report knowledge, suspicion or reasonable grounds of money laundering
What this requires
A person receiving relevant information in regulated-sector business must make the required disclosure as soon as practicable when the statutory money-laundering reporting conditions are met; there is no minimum monetary threshold.
RegCanary explanation
Section 330 covers actual knowledge or suspicion and reasonable grounds for either, together with the statutory identification or assistance condition. Disclose to the nominated officer or authorised NCA recipient the known identity, known property whereabouts and supporting information. A nominated officer receiving a section 330 disclosure has a separate onward-reporting duty under section 331 when its conditions are met.
Original downloaded unchanged to data/country-handbook-evidence/uk/poca-part-7-delivery-20260911.xml. SHA-256 a4b5f9ad5ebf63c86e39a89a6b2ca1c08cfbe9acec717d1df9f22f834116f4fa; capture completion 2026-09-11T07:39:46.896Z. English national original, not a translation. Selected mapped text matches the corresponding full revised XML provisions at the same version. ElementTree reference check found no missing commentary targets; current extractCountrySource returned extracted-text, source-provision-identifiers and no warnings. This scoped original avoids, but does not resolve or approve, the full-document section 195S annotation defect. No effective date inferred from the root version or capture date.
Recent document checks
: unchanged, document 8204b9bb6342
: unchanged, document 8204b9bb6342
: unchanged, document 8204b9bb6342
: unchanged, document 8204b9bb6342
: unchanged, document 8204b9bb6342
Review pending
UK Parliament / legislation.gov.uk
Source diagnostics
Lifecycle
Not recorded
Language
en
Retrieved
11 Sept 2026
Extraction
captured
Latest automated check
12 Oct 2026
Check outcome
unchanged
Evidence review
requires-revalidation
Type
legislation
Version
Official provision-scoped revised XML; root RestrictStartDate 2026-06-30; captured 11 September 2026
Original downloaded unchanged to data/country-handbook-evidence/uk/poca-schedule-9-delivery-20260911.xml. SHA-256 eebc2b24518990b7ea1d25c26a10c1f31cbfe2b08600d52ec353b355a3b5d1a7; capture completion 2026-09-11T07:39:47.607Z. English national original, not a translation. Selected mapped text matches the corresponding full revised XML provisions at the same version. ElementTree reference check found no missing commentary targets; current extractCountrySource returned extracted-text, source-provision-identifiers and no warnings. This scoped original avoids, but does not resolve or approve, the full-document section 195S annotation defect. No effective date inferred from the root version or capture date.
Recent document checks
: unchanged, document 48f459125dca
: unchanged, document 48f459125dca
: unchanged, document 48f459125dca
: unchanged, document 48f459125dca
: unchanged, document 48f459125dca
Evidence diagnostics
Record ID
uk-poca-sar-duty
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
monitoring
Baseline review status
source checked
Review status
needs review
Effective from
Not recorded
Effective to
Not recorded
No conditions are recorded. This does not establish that none apply.
No exceptions are recorded. This does not establish that none apply.
In regulated-sector business, disclose information as soon as practicable where there is knowledge, suspicion or reasonable grounds to know or suspect that another person has committed or attempted a terrorist-financing offence under sections 15 to 18.
RegCanary explanation
Make the disclosure to a constable, an authorised NCA officer or a nominated officer through the statutory employer procedure. Section 21A applies to the information received by the person, including a nominated officer assessing it. Unlike the POCA reporting test, this provision does not add POCA's person/property-identification condition.
Official English national text downloaded to data/country-handbook-evidence/uk/terrorism-act-2000-revised-20260910.xml and parsed with ElementTree. Checked sections 14-19, 21A, 21ZA-21ZC, 21D-21G and Schedule 3A. No POCA low-value or moratorium rule is inferred for TACT. This is not a complete counter-terrorism legislation review. Delivery original captured from https://www.legislation.gov.uk/ukpga/2000/11/data.xml at 2026-09-11T07:35:03.872Z to data/country-handbook-evidence/uk/terrorism-act-2000-delivery-20260911.xml; SHA-256 af439550aa1bb4268f5546db1ed3b7f935811fdf331dd564449876ffeaa4f0fc. Timestamp records local download completion. Official publisher English, not a translation. The original's text was inspected; capture does not imply every provision is verified. Fresh XML parsed with ElementTree: legislative body and commentary are identical to the prior retained original; differences are confined to metadata. Prior originals remain retained.
Recent document checks
: unchanged, document be84ca199962
: unchanged, document be84ca199962
: unchanged, document be84ca199962
: unchanged, document be84ca199962
: unchanged, document be84ca199962
Evidence diagnostics
Record ID
uk-tact-sar-duty
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
monitoring
Baseline review status
source checked
Review status
needs review
Effective from
Not recorded
Effective to
Not recorded
No conditions are recorded. This does not establish that none apply.
No exceptions are recorded. This does not establish that none apply.
Observe DAML notice and moratorium periods · review pendinglegislation / Review pending
Observe DAML notice and moratorium periods
What this requires
Before a proposed prohibited money-laundering act, make an authorised disclosure and obtain appropriate consent or establish that the statutory deemed-consent conditions are satisfied.
RegCanary explanation
The notice period is seven working days starting with the first working day after disclosure. A refusal triggers a 31-day moratorium starting with the day refusal is notified. Courts may extend the moratorium, generally by up to 31 days per order and no more than 186 additional days in total; pending applications and appeals can also extend it. A nominated officer's permission must satisfy section 336.
Applicability
Business lines
all
Customer types
all
Stages
all
Supporting provision
POCA 2002 sections 335(1)-(7), 336(1)-(9), 336A(1)-(8), 336C and 338(1)-(4)
Review pending
UK Parliament / legislation.gov.uk
Source diagnostics
Lifecycle
Not recorded
Language
en
Retrieved
11 Sept 2026
Extraction
captured
Latest automated check
12 Oct 2026
Check outcome
unchanged
Evidence review
requires-revalidation
Type
legislation
Version
Official provision-scoped revised XML; root RestrictStartDate 2026-06-30; captured 11 September 2026
Original downloaded unchanged to data/country-handbook-evidence/uk/poca-part-7-delivery-20260911.xml. SHA-256 a4b5f9ad5ebf63c86e39a89a6b2ca1c08cfbe9acec717d1df9f22f834116f4fa; capture completion 2026-09-11T07:39:46.896Z. English national original, not a translation. Selected mapped text matches the corresponding full revised XML provisions at the same version. ElementTree reference check found no missing commentary targets; current extractCountrySource returned extracted-text, source-provision-identifiers and no warnings. This scoped original avoids, but does not resolve or approve, the full-document section 195S annotation defect. No effective date inferred from the root version or capture date.
Recent document checks
: unchanged, document 8204b9bb6342
: unchanged, document 8204b9bb6342
: unchanged, document 8204b9bb6342
: unchanged, document 8204b9bb6342
: unchanged, document 8204b9bb6342
Evidence diagnostics
Record ID
uk-daml-consent-periods
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
monitoring
Baseline review status
source checked
Review status
needs review
Effective from
Not recorded
Effective to
Not recorded
No conditions are recorded. This does not establish that none apply.
No exceptions are recorded. This does not establish that none apply.
Apply the terrorist-property consent rules separately
What this requires
For proposed involvement in a transaction or arrangement involving suspected terrorist property, assess the offences in sections 15 to 18 and obtain the applicable defence before proceeding.
RegCanary explanation
Terrorist property includes funds likely to be used for terrorism, not only criminal proceeds. Prior disclosure to an authorised NCA officer and consent can protect the specified involvement; consent is deemed if no refusal is received within seven working days starting with the first working day after disclosure. A refusal does not begin a POCA-style 31-day moratorium.
Applicability
Business lines
all
Customer types
all
Stages
all
Supporting provision
Terrorism Act 2000 sections 14-18 and 21ZA(1)-(6), 21ZB(1)-(5), 21ZC
Review pending
UK Parliament / legislation.gov.uk
Source diagnostics
Lifecycle
Not recorded
Language
en
Retrieved
11 Sept 2026
Extraction
captured
Latest automated check
12 Oct 2026
Check outcome
unchanged
Evidence review
requires-revalidation
Type
legislation
Version
Revised XML retrieved 10 September 2026; cited provisions checked individually
Official English national text downloaded to data/country-handbook-evidence/uk/terrorism-act-2000-revised-20260910.xml and parsed with ElementTree. Checked sections 14-19, 21A, 21ZA-21ZC, 21D-21G and Schedule 3A. No POCA low-value or moratorium rule is inferred for TACT. This is not a complete counter-terrorism legislation review. Delivery original captured from https://www.legislation.gov.uk/ukpga/2000/11/data.xml at 2026-09-11T07:35:03.872Z to data/country-handbook-evidence/uk/terrorism-act-2000-delivery-20260911.xml; SHA-256 af439550aa1bb4268f5546db1ed3b7f935811fdf331dd564449876ffeaa4f0fc. Timestamp records local download completion. Official publisher English, not a translation. The original's text was inspected; capture does not imply every provision is verified. Fresh XML parsed with ElementTree: legislative body and commentary are identical to the prior retained original; differences are confined to metadata. Prior originals remain retained.
Recent document checks
: unchanged, document be84ca199962
: unchanged, document be84ca199962
: unchanged, document be84ca199962
: unchanged, document be84ca199962
: unchanged, document be84ca199962
Evidence diagnostics
Record ID
uk-datf-consent
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
monitoring
Baseline review status
source checked
Review status
needs review
Effective from
Not recorded
Effective to
Not recorded
No conditions are recorded. This does not establish that none apply.
No exceptions are recorded. This does not establish that none apply.
Avoid disclosures likely to prejudice an investigation · review pendinglegislation / Review pending
Avoid disclosures likely to prejudice an investigation
What this requires
Control communications about SARs and contemplated or actual investigations where disclosure is likely to prejudice the relevant investigation and the information came from regulated-sector business.
RegCanary explanation
POCA and TACT each define the offence and permitted disclosures. The rules are not a blanket prohibition on all customer contact. Limited intra-undertaking, group, institution-to-institution, supervisor and enforcement disclosures have statutory conditions; assess the purpose, recipient and likely prejudice before sharing.
Original downloaded unchanged to data/country-handbook-evidence/uk/poca-part-7-delivery-20260911.xml. SHA-256 a4b5f9ad5ebf63c86e39a89a6b2ca1c08cfbe9acec717d1df9f22f834116f4fa; capture completion 2026-09-11T07:39:46.896Z. English national original, not a translation. Selected mapped text matches the corresponding full revised XML provisions at the same version. ElementTree reference check found no missing commentary targets; current extractCountrySource returned extracted-text, source-provision-identifiers and no warnings. This scoped original avoids, but does not resolve or approve, the full-document section 195S annotation defect. No effective date inferred from the root version or capture date.
Recent document checks
: unchanged, document 8204b9bb6342
: unchanged, document 8204b9bb6342
: unchanged, document 8204b9bb6342
: unchanged, document 8204b9bb6342
: unchanged, document 8204b9bb6342
Review pending
UK Parliament / legislation.gov.uk
Source diagnostics
Lifecycle
Not recorded
Language
en
Retrieved
11 Sept 2026
Extraction
captured
Latest automated check
12 Oct 2026
Check outcome
unchanged
Evidence review
requires-revalidation
Type
legislation
Version
Revised XML retrieved 10 September 2026; cited provisions checked individually
Official English national text downloaded to data/country-handbook-evidence/uk/terrorism-act-2000-revised-20260910.xml and parsed with ElementTree. Checked sections 14-19, 21A, 21ZA-21ZC, 21D-21G and Schedule 3A. No POCA low-value or moratorium rule is inferred for TACT. This is not a complete counter-terrorism legislation review. Delivery original captured from https://www.legislation.gov.uk/ukpga/2000/11/data.xml at 2026-09-11T07:35:03.872Z to data/country-handbook-evidence/uk/terrorism-act-2000-delivery-20260911.xml; SHA-256 af439550aa1bb4268f5546db1ed3b7f935811fdf331dd564449876ffeaa4f0fc. Timestamp records local download completion. Official publisher English, not a translation. The original's text was inspected; capture does not imply every provision is verified. Fresh XML parsed with ElementTree: legislative body and commentary are identical to the prior retained original; differences are confined to metadata. Prior originals remain retained.
Recent document checks
: unchanged, document be84ca199962
: unchanged, document be84ca199962
: unchanged, document be84ca199962
: unchanged, document be84ca199962
: unchanged, document be84ca199962
Evidence diagnostics
Record ID
uk-tipping-off-controls
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
monitoring
Baseline review status
source checked
Review status
needs review
Effective from
Not recorded
Effective to
Not recorded
No conditions are recorded. This does not establish that none apply.
No exceptions are recorded. This does not establish that none apply.
Apply the Russia asset freeze to covered property · review pendinglegislation / Review pending
Apply the Russia asset freeze to covered property
What this requires
Under the Russia regime, do not deal with funds or economic resources owned, held or controlled by an asset-freeze designated person where the statutory knowledge or reasonable-cause-to-suspect condition is met.
RegCanary explanation
The prohibition covers using, moving or transferring funds, allowing access, portfolio changes enabling use, and exchanging or using economic resources for funds, goods or services. It includes legal or equitable interests, including jointly held interests, and property held through an entity owned or controlled by the designated person. OFSI explains that the broad funds and economic-resources definitions cover cryptoassets; the prohibition is not restricted to cash or bank deposits.
Applicability
Business lines
all
Customer types
all
Stages
all
Supporting provision
Russia Regulations 3, 10, 11(1)-(8); SAMLA 2018 sections 21 and 60(1)-(4); OFSI general guidance section 3.1.2, 'Cryptoassets' and dealing definitions
Baseline document
Secretary of State / legislation.gov.uk
Source diagnostics
Lifecycle
Not recorded
Language
en
Retrieved
10 Sept 2026
Extraction
captured
Latest automated check
12 Oct 2026
Check outcome
unchanged
Evidence review
unvalidated
Type
legislation
Version
Official revised XML captured 11 September 2026 London time; document RestrictStartDate 2026-05-20
Original downloaded to data/country-handbook-evidence/uk/russia-sanctions-revised-20260911.xml. ElementTree extraction checked regulations 2-3, 5, 7-8, 10-15, 19, 58, 64, 66-67, 70-71 and 79(3), (6), Schedule 1 and selected Schedule 5 paragraphs. No future RestrictStartDate nodes or Unapplied metadata elements found in the downloaded snapshot; this is not a comprehensive amendment/legal-perimeter audit. These source_checked additions map only the stated Russia-regime provisions, not all sectoral sanctions or all UK regimes. Native English statutory original, not a translation. Freeze recheck: official original recaptured unchanged at data/country-handbook-evidence/uk/russia-sanctions-freeze-20260911.xml, 2026-09-11T07:50:08.614Z; SHA-256 146f749d478109c2e8c72d7620eaab8dbe1352d270d35828e95566935573e99f matches the retained source. Further inspected regulations 18A, 70(1ZA)-(1ZB), (3)-(4), (7), 71 and 79(3), (5)-(6).
Recent document checks
: unchanged, document 146f749d4781
: unchanged, document 146f749d4781
: unchanged, document 146f749d4781
: unchanged, document 146f749d4781
: unchanged, document 146f749d4781
Review pending
UK Parliament / legislation.gov.uk
Source diagnostics
Lifecycle
Not recorded
Language
en
Retrieved
10 Sept 2026
Extraction
captured
Latest automated check
12 Oct 2026
Check outcome
unchanged
Evidence review
requires-revalidation
Type
legislation
Version
Official revised XML captured 11 September 2026 London time; document RestrictStartDate 2025-10-16
Original downloaded to data/country-handbook-evidence/uk/samla-2018-revised-20260911.xml. ElementTree extraction checked sections 1(1), 3(1), 21 and 60. The enabling framework is distinguished from the actual prohibitions in regime regulations. No source publication, snapshot or capture date is assigned as commencement of a compound requirement. Native English statutory original; not a complete SAMLA review.
Recent document checks
: unchanged, document 23c852a64b23
: unchanged, document 23c852a64b23
: unchanged, document 23c852a64b23
: unchanged, document 23c852a64b23
: unchanged, document 23c852a64b23
Review pending
Office of Financial Sanctions Implementation / HM Treasury
Web-fetched official English guidance; chapters 2-6 inspected selectively. The earlier capture was web-only. Underlying sanctions instruments, particular licences and individual designations are not exhaustively checked. Original HTML now captured at data/country-handbook-evidence/uk/ofsi-general-20260911.html on 11 September 2026 London time (2026-09-10T23:43:04Z UTC). Parsed using HTMLParser excluding scripts/styles. The hash is of the original response bytes, not extracted text. Rechecked the cryptoasset/dealing definitions, reporting and frozen-account/exception passages supporting the bounded Russia additions.
Recent document checks
: unchanged, document cb2c88de51e0
: unchanged, document cb2c88de51e0
: unchanged, document cb2c88de51e0
: unchanged, document cb2c88de51e0
: unchanged, document cb2c88de51e0
Evidence diagnostics
Record ID
uk-russia-asset-freeze
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
monitoring
Baseline review status
source checked
Review status
needs review
Effective from
Not recorded
Effective to
Not recorded
No conditions are recorded. This does not establish that none apply.
No exceptions are recorded. This does not establish that none apply.
Report Russia sanctions knowledge or suspicion promptly · review pendinglegislation / Review pending
Report Russia sanctions knowledge or suspicion promptly
What this requires
A relevant firm must inform the Treasury as soon as practicable when the Russia regime's designated-person or specified breach reporting conditions are met and the information arose in the relevant business activity.
RegCanary explanation
State the grounds and information identifying the person, together with related maritime oil information where applicable. Where the designated person is a customer, also report the nature and amount or quantity of funds or economic resources held when knowledge or suspicion first arose. The relevant-firm definition includes Part 4A-authorised persons, specified money transmission/currency businesses, cryptoasset exchange providers and custodian wallet providers. Information received by a Part 4A firm must arise in the activity for which that permission is required.
Applicability
Business lines
all
Customer types
all
Stages
all
Supporting provision
Russia Regulations 3(4)-(7), 70(1)-(4), (6)-(7), 71(1)(a)-(b), (h)-(i), (3A)-(3C), (4)-(5), 79(3), (6); OFSI general guidance sections 5.1, 5.3 and 5.9
Baseline document
Secretary of State / legislation.gov.uk
Source diagnostics
Lifecycle
Not recorded
Language
en
Retrieved
10 Sept 2026
Extraction
captured
Latest automated check
12 Oct 2026
Check outcome
unchanged
Evidence review
unvalidated
Type
legislation
Version
Official revised XML captured 11 September 2026 London time; document RestrictStartDate 2026-05-20
Original downloaded to data/country-handbook-evidence/uk/russia-sanctions-revised-20260911.xml. ElementTree extraction checked regulations 2-3, 5, 7-8, 10-15, 19, 58, 64, 66-67, 70-71 and 79(3), (6), Schedule 1 and selected Schedule 5 paragraphs. No future RestrictStartDate nodes or Unapplied metadata elements found in the downloaded snapshot; this is not a comprehensive amendment/legal-perimeter audit. These source_checked additions map only the stated Russia-regime provisions, not all sectoral sanctions or all UK regimes. Native English statutory original, not a translation. Freeze recheck: official original recaptured unchanged at data/country-handbook-evidence/uk/russia-sanctions-freeze-20260911.xml, 2026-09-11T07:50:08.614Z; SHA-256 146f749d478109c2e8c72d7620eaab8dbe1352d270d35828e95566935573e99f matches the retained source. Further inspected regulations 18A, 70(1ZA)-(1ZB), (3)-(4), (7), 71 and 79(3), (5)-(6).
Recent document checks
: unchanged, document 146f749d4781
: unchanged, document 146f749d4781
: unchanged, document 146f749d4781
: unchanged, document 146f749d4781
: unchanged, document 146f749d4781
Review pending
Office of Financial Sanctions Implementation / HM Treasury
Web-fetched official English guidance; chapters 2-6 inspected selectively. The earlier capture was web-only. Underlying sanctions instruments, particular licences and individual designations are not exhaustively checked. Original HTML now captured at data/country-handbook-evidence/uk/ofsi-general-20260911.html on 11 September 2026 London time (2026-09-10T23:43:04Z UTC). Parsed using HTMLParser excluding scripts/styles. The hash is of the original response bytes, not extracted text. Rechecked the cryptoasset/dealing definitions, reporting and frozen-account/exception passages supporting the bounded Russia additions.
Recent document checks
: unchanged, document cb2c88de51e0
: unchanged, document cb2c88de51e0
: unchanged, document cb2c88de51e0
: unchanged, document cb2c88de51e0
: unchanged, document cb2c88de51e0
Evidence diagnostics
Record ID
uk-russia-relevant-firm-reporting
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
monitoring
Baseline review status
source checked
Review status
needs review
Effective from
Not recorded
Effective to
Not recorded
No conditions are recorded. This does not establish that none apply.
No exceptions are recorded. This does not establish that none apply.
Preserve investigation material and avoid prejudicial disclosure · review pendinglegislation / Review pending
Preserve investigation material and avoid prejudicial disclosure
What this requires
When the statutory investigation trigger is met, avoid prejudicial disclosures and prohibited interference with relevant records or material.
RegCanary explanation
POCA section 342 applies when a person knows or suspects that the specified official is acting or proposing to act in connection with a listed investigation that is being or is about to be conducted; it prohibits disclosures likely to prejudice it and specified dealings with relevant documents. TACT section 39 has separate knowledge or reasonable-cause-to-suspect triggers for terrorist investigations and specified disclosures already made or to be made. Its interference prohibition includes falsifying, concealing, destroying or disposing of relevant material, including causing or permitting another to do so.
Original downloaded unchanged to data/country-handbook-evidence/uk/poca-section-342-delivery-20260911.xml. SHA-256 be2b1584e29fa97d37b0d54fd8a493331b21d87e948158db27f1a86873005ce7; capture completion 2026-09-11T07:39:48.187Z. English national original, not a translation. Selected mapped text matches the corresponding full revised XML provisions at the same version. ElementTree reference check found no missing commentary targets; current extractCountrySource returned extracted-text, source-provision-identifiers and no warnings. This scoped original avoids, but does not resolve or approve, the full-document section 195S annotation defect. No effective date inferred from the root version or capture date.
Recent document checks
: unchanged, document f807cdd0a7ff
: unchanged, document f807cdd0a7ff
: unchanged, document f807cdd0a7ff
: unchanged, document f807cdd0a7ff
: unchanged, document f807cdd0a7ff
Review pending
UK Parliament / legislation.gov.uk
Source diagnostics
Lifecycle
Not recorded
Language
en
Retrieved
11 Sept 2026
Extraction
captured
Latest automated check
12 Oct 2026
Check outcome
unchanged
Evidence review
requires-revalidation
Type
legislation
Version
Revised XML retrieved 10 September 2026; cited provisions checked individually
Official English national text downloaded to data/country-handbook-evidence/uk/terrorism-act-2000-revised-20260910.xml and parsed with ElementTree. Checked sections 14-19, 21A, 21ZA-21ZC, 21D-21G and Schedule 3A. No POCA low-value or moratorium rule is inferred for TACT. This is not a complete counter-terrorism legislation review. Delivery original captured from https://www.legislation.gov.uk/ukpga/2000/11/data.xml at 2026-09-11T07:35:03.872Z to data/country-handbook-evidence/uk/terrorism-act-2000-delivery-20260911.xml; SHA-256 af439550aa1bb4268f5546db1ed3b7f935811fdf331dd564449876ffeaa4f0fc. Timestamp records local download completion. Official publisher English, not a translation. The original's text was inspected; capture does not imply every provision is verified. Fresh XML parsed with ElementTree: legislative body and commentary are identical to the prior retained original; differences are confined to metadata. Prior originals remain retained.
Recent document checks
: unchanged, document be84ca199962
: unchanged, document be84ca199962
: unchanged, document be84ca199962
: unchanged, document be84ca199962
: unchanged, document be84ca199962
Evidence diagnostics
Record ID
uk-investigation-integrity
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
monitoring
Baseline review status
source checked
Review status
needs review
Effective from
Not recorded
Effective to
Not recorded
No conditions are recorded. This does not establish that none apply.
No exceptions are recorded. This does not establish that none apply.
Separate crime and safeguarding escalation from SAR reporting · review pendingguidance / Review pending
Separate crime and safeguarding escalation from SAR reporting
What this requires
A SAR reports the relevant money-laundering or terrorist-financing suspicion; it is not a substitute for reporting fraud or other crime, or an immediate safeguarding risk, through the appropriate route.
RegCanary explanation
UKFIU guidance distinguishes crime reports from SARs and directs urgent risks to the police or emergency services as appropriate. Where related reporting has occurred, include the reference and relevant safeguarding steps in the SAR. Separately assess the POCA or TACT reporting trigger rather than treating every fraud concern as a mandatory SAR or assuming that a SAR handles the underlying crime.
Applicability
Business lines
all
Customer types
all
Stages
all
Supporting provision
UKFIU SARs Best Practice Guidance, Chapter 2, December 2025 version 1.1, printed page 4, 'A note about crime reporting', and pages 16-17
PDF text successfully fetched by web tool; pages 16 and 18-20 checked. Earlier direct download returned HTTP 403; the delivery capture below resolves that original-file gap. Delivery original captured from https://www.nationalcrimeagency.gov.uk/who-we-are/publications/775-ukfiu-chapter-2-submitting-a-sar/file?download=1 at 2026-09-11T07:33:38.098Z to data/country-handbook-evidence/uk/nca-sar-ch2-delivery-20260911.pdf; SHA-256 ed8efef20f0415a7d6358cb2bbd39fee08a521893845bd615b022ea93a34530d. Timestamp records local download completion. Official publisher English, not a translation. The original's text was inspected; capture does not imply every provision is verified.
Recent document checks
: unchanged, document c2f86fb72953
: unchanged, document c2f86fb72953
: unchanged, document c2f86fb72953
: unchanged, document c2f86fb72953
: unchanged, document c2f86fb72953
Evidence diagnostics
Record ID
uk-fraud-crime-escalation
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
monitoring
Baseline review status
source checked
Review status
needs review
Effective from
Not recorded
Effective to
Not recorded
No conditions are recorded. This does not establish that none apply.
No exceptions are recorded. This does not establish that none apply.
Denmark
Apply Russian deposit and payment-service restrictions separatelylegislation
Apply Russian deposit and payment-service restrictions separately
What this requires
Check the deposit limit, restricted payment services and nationality/residence exceptions independently; a deposit exception is not sanctions clearance.
RegCanary explanation
Regulation 833/2014 Article 5b(1) prohibits accepting deposits exceeding the EUR 100,000 total from the specified Russian nationals or persons resident in Russia. Article 5b(2)(b)-(c) separately prohibits direct or indirect provision of payment-instrument issuance, acquiring, payment-initiation services and electronic-money issuance to the specified persons; this is not a EUR 100,000 service threshold. Article 5b(3) excludes EU, EEA or Swiss nationals and natural persons with temporary or permanent residence permits in those jurisdictions from these prohibitions. Article 5c(1a) narrowly preserves provision of personalised security credentials necessary to access an account at a credit or e-money institution established in a Member State or an Annex VIII partner country. Articles 5c and 5d provide competent-authority authorisation routes, including basic needs, legal fees, qualifying maintenance, extraordinary expenses, permitted cross-border trade, humanitarian purposes and specified civil-society activities, subject to their own conditions. Article 5g(1)(a) required an initial list of the specified deposits above EUR 100,000 by 27 May 2022 and updates of amounts every 12 months; Article 5g(1)(b) separately requires information about such deposits held by Russian nationals or residents who obtained Member State citizenship or residence through investor schemes.
Retained original: data/country-handbook-evidence/dk/eu-russia-833-2026-da-20260911.pdf; 8783539 bytes. Capture timestamp records original-file acquisition in UTC (11 September 2026 local time). Selected Articles 5b-5d and 5g, pp. 105-110; broader transaction restrictions inventoried, not fully mapped. Authentic amendments 2022/328, 2022/1269, 2023/2878 and 2025/2033 retained. Current-version metadata retained. Account-access credentials are a narrow exception, not permission to issue every payment instrument. No exhaustive annex/list or derogation audit.
Recent document checks
: unchanged, document 0e7661571d62
: unchanged, document 0e7661571d62
: unchanged, document 0e7661571d62
: unchanged, document 0e7661571d62
: failed, document 0e7661571d62
Conditions
Determine nationality, residence and qualifying permit evidence rather than infer a ban from a Russian name. The wider legal-person branches are not converted into mandatory company onboarding in this individual product.
The deposit test concerns the relevant total, not each individual incoming transfer. Apply the current deposit definition and aggregation rules; this row is not a tested currency or joint-account calculator.
The annual deposit report is to the competent national authority or Commission as Article 5g specifies; it is not an automatic FIU suspicion report. Confirm the current Danish reporting channel before operational use.
Exceptions
Article 5c(1a) account-access credentials do not exempt every payment instrument. A qualifying service/deposit exception does not override a listed-party freeze, separate transaction ban or AML hold.
The corporate Article 5g(1)(aa) reporting branch is not mapped for this individual customer product. Other transaction prohibitions, including provider/counterparty annex restrictions, remain separately applicable and not exhaustively mapped.
The 2022 date is a historical initial reporting deadline, not a new deadline for a 2026 customer. No blanket mandatory rejection or automatic freezing of every Russian customer's existing balance is asserted.
Evidence diagnostics
Record ID
dk-russia-retail-service-restrictions
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
monitoring
Status when reviewed
current
Review status
source checked
Effective from
Not recorded
Effective to
Not recorded
Investigate unusual transactions and record the resultlegislation
Investigate unusual transactions and record the result
What this requires
Examine the background and purpose of qualifying unusual transactions and activities, extend monitoring where relevant and retain a written investigation result.
RegCanary explanation
Section 25(1) covers transactions that are complex, unusually large, follow an unusual pattern, or lack an apparent economic or lawful purpose; it separately covers unusual activities lacking such a purpose. Do not wait for proof of money laundering before investigating. Section 25(2) requires expanded monitoring where relevant to determine suspicion, and subsection 3 requires findings to be recorded and retained under section 30. Document why an alert is cleared as well as why it is escalated. Apply this assessment during onboarding where the customer's proposed activity or transaction meets the statutory conditions; a completed relationship is not a prerequisite. The separate reporting duty also covers attempts and approaches by prospective customers.
Applicability
Business lines
all
Customer types
all
Stages
onboarding, ongoing, investigation, offboarding
Supporting provision
LBK 433/2026 section 25(1)-(3), p. 9; section 30(1) no. 3, p. 11
Downloaded original: data/country-handbook-evidence/dk/lbk-433-2026.pdf, 35 pages; inspected with pdftotext. Current reference is supported by the live Finanstilsynet index. The consolidation includes the amendment to section 38 b from Act 1638/2025 and explains the revoked, unincorporated amendment from Act 712/2025. Publication on 21 April 2026 is NOT treated as the commencement of all provisions. The JavaScript landing page did not expose amendment-status metadata. The bounded follow-up verified promulgated Act 764/2026 and its 15 September commencement; see the promulgated Act 764/2026 and the dated governance-review limitation. Danish original governs; English summaries are editorial, not an official translation.
Recent document checks
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
Conditions
Only section 1 obliged activities. Evaluate background and purpose in context; unusual does not automatically equal suspicious, but report promptly once the section 26 threshold is met.
Exceptions
No monetary floor for this investigation duty is specified in section 25.
Evidence diagnostics
Record ID
dk-investigate-record
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
monitoring
Status when reviewed
current
Review status
source checked
Effective from
Not recorded
Effective to
Not recorded
Apply the correct transaction hold and FIU approval rulelegislation
Apply the correct transaction hold and FIU approval rule
What this requires
Hold unexecuted suspected-ML transactions until reporting; larger/specially suspicious ML transactions and suspected-TF transactions require reporting and FIU approval.
RegCanary explanation
Section 26(3) covers the ordinary ML hold. Subsections 4 and 6 require FIU approval as well as reporting for the specified larger/specially suspicious ML and TF cases. BEK 431 section 1 places a reportable transaction involving deposited funds of DKK 1 million or more before execution within subsection 4. That is not a DKK 1 million minimum for all suspicious reporting. The FIU is to arrange the seizure decision as soon as possible and by the end of the following banking day; this deadline must not be treated as automatic permission to release funds without the required approval.
Applicability
Business lines
all
Customer types
all
Stages
onboarding, ongoing, investigation, offboarding
Supporting provision
LBK 433/2026 section 26(3)-(6), p. 10; BEK 431/2023 sections 1-2, p. 1
Downloaded original: data/country-handbook-evidence/dk/lbk-433-2026.pdf, 35 pages; inspected with pdftotext. Current reference is supported by the live Finanstilsynet index. The consolidation includes the amendment to section 38 b from Act 1638/2025 and explains the revoked, unincorporated amendment from Act 712/2025. Publication on 21 April 2026 is NOT treated as the commencement of all provisions. The JavaScript landing page did not expose amendment-status metadata. The bounded follow-up verified promulgated Act 764/2026 and its 15 September commencement; see the promulgated Act 764/2026 and the dated governance-review limitation. Danish original governs; English summaries are editorial, not an official translation.
Downloaded and fully text-inspected original: data/country-handbook-evidence/dk/bek-431-2023-fast-track.pdf, 1 page. Current supervisor index links it. Section 1 concerns a reportable transaction involving deposited funds of DKK 1 million or more BEFORE execution, not a general reporting threshold or simply the amount transferred. Section 2 expressly commences the order on 1 June 2023.
Recent document checks
: unchanged, document 287f052f45bb
: unchanged, document 287f052f45bb
: unchanged, document 287f052f45bb
: unchanged, document 287f052f45bb
: unchanged, document 287f052f45bb
Conditions
Only section 1 obliged activities. Classify ML versus TF and assess the fast-track deposited-funds condition before allowing any suspicious exit payment. FIU approval under this requirement does not authorise release of sanctions-frozen assets; separately apply the sanctions freezing, release and reporting requirements and any other applicable instrument.
BEK 431 commenced on 1 June 2023 under section 2; no common commencement date is inferred for the combined rule.
Exceptions
Under section 26(3), if non-execution is impossible or would harm the investigation, report immediately after execution. Do not generalise that exception to the distinct subsection 4 or 6 approval requirements.
Already executed transactions still require reporting where the threshold is met.
Evidence diagnostics
Record ID
dk-transaction-holds
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
monitoring
Status when reviewed
current
Review status
source checked
Effective from
Not recorded
Effective to
Not recorded
Provide accurate account information through the statutory mechanismlegislation
Provide accurate account information through the statutory mechanism
What this requires
Covered account and safe-deposit providers must respond promptly to FIU or tax-authority requests through the central mechanism.
RegCanary explanation
Order 1114 covers providers of IBAN-identified bank/payment accounts and safe-deposit boxes, including Danish branches of foreign providers. Sections 2-3 require the central mechanism and its operator, with each provider responsible as controller for its submitted personal data. On an FIU or tax-authority request, provide information immediately and no later than three banking days after the request was sent; urgent cases have an immediate, one-banking-day maximum. Account information comprises customer and representative identity, beneficial-owner identity, registration/account number or IBAN, and opening and any closing date. Box information comprises renter identity and opening/closing dates. Providers must submit correct, current information. The operator's activity logs have five-year retention followed by deletion; requests and responses in the mechanism have the separate five-banking-day retention after the response deadline. These periods do not replace ordinary AML record retention.
Applicability
Business lines
all
Customer types
all
Stages
onboarding, ongoing, investigation, offboarding
Supporting provision
BEK 1114/2023 sections 1-3, p. 1; sections 3(4), 4-5, 7, p. 2; LBK 433/2026 section 30a, p. 11
Baseline document
Retsinformation / Finanstilsynet
Source diagnostics
Lifecycle
Not recorded
Language
da
Retrieved
11 Sept 2026
Extraction
captured
Latest automated check
19 Sept 2026
Check outcome
unchanged
Evidence review
unvalidated
Type
legislation
Version
BEK nr 1114 af 25/08/2023; section 7 commencement 01/09/2023
Actual Danish official PDF retained at data/country-handbook-evidence/dk/bek-1114-2023-account-mechanism-20260911.pdf (147774 bytes, 2 pages). Sections 1-7 inspected; linked by the live Finanstilsynet AML legislation index checked on 11 September 2026. Provider and operator duties, response deadlines and the distinct log/request retention periods are not interchangeable. No connection to the mechanism was attempted.
Downloaded original: data/country-handbook-evidence/dk/lbk-433-2026.pdf, 35 pages; inspected with pdftotext. Current reference is supported by the live Finanstilsynet index. The consolidation includes the amendment to section 38 b from Act 1638/2025 and explains the revoked, unincorporated amendment from Act 712/2025. Publication on 21 April 2026 is NOT treated as the commencement of all provisions. The JavaScript landing page did not expose amendment-status metadata. The bounded follow-up verified promulgated Act 764/2026 and its 15 September commencement; see the promulgated Act 764/2026 and the dated governance-review limitation. Danish original governs; English summaries are editorial, not an official translation.
Recent document checks
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
: unchanged, document 4a9a0064d70e
Conditions
Activity-specific: not every investment firm, e-money issuer or crypto provider offers an account or box within section 1. Operator logging, retention and system-error responsibility are distinct from the provider's reporting responsibility.
This explains statutory information and deadlines; building or connecting the central mechanism is outside the handbook product.
Evidence diagnostics
Record ID
dk-account-information-mechanism
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
monitoring
Status when reviewed
current
Review status
source checked
Effective from
1 Sept 2023
Effective to
Not recorded
No exceptions are recorded. This does not establish that none apply.
Apply the transfer guidelines to identity fields and linked transfersguidance
Apply the transfer guidelines to identity fields and linked transfers
What this requires
Use complete, meaningful transfer information, assess linked payments and preserve the correct provider role and cross-border character.
RegCanary explanation
Identify the undertaking's role for each transfer and document effective information-handling procedures. If the conditions for an Article 2 exclusion cannot be established, apply the transfer rules. Detect potentially linked fund transfers using the same payer or payee, including one-to-many and many-to-one patterns, with a proportionate short time window; assess values without fees. Use full natural-person names and registered legal-person names, and the required information for all joint account or address holders. Use the prescribed postal address rather than a post-office box or virtual address alone; the guidelines accommodate people without a fixed address and lawful protective alternatives for vulnerable people. An equivalent legal-person identifier must meet all paragraph 41 criteria: unique, publicly registered, issued by a public authority on establishment in the home jurisdiction, identifying name and address, with its type described in the message. The corrected Danish heading expressly covers payer and payee as well as crypto originator and beneficiary. Do not relabel a cross-border customer transfer as a domestic transfer or own-account liquidity movement to avoid information requirements. Preserve information integrity through message conversion and notify the next provider of corrections.
Applicability
Business lines
all
Customer types
all
Stages
onboarding, ongoing, investigation, offboarding
Supporting provision
EBA/GL/2024/11 paras. 12-20, 21-41, corrected Danish PDF pp. 6-13; Regulation 2023/1113 Articles 2 and 4-6
Retained original: data/country-handbook-evidence/dk/eu-tfr-2023-1113-da-20260911.pdf; 771970 bytes. Capture timestamp records original-file acquisition in UTC (11 September 2026 local time). Authentic Danish OJ. Inspected Articles 2-13, 23-26, 32(2), 35 and 39-40, pp. 13-21, 25-30, 36. Live document-information original retained as 32023R1113-currentness-20260911.html. German/Spanish corrigenda and the future Article 38 change do not amend the mapped Danish payment-provider provisions. Article 4(2)(c) contains a payer/payee wording issue in Danish; no universal natural-person LEI duty is inferred. EBA/GL/2024/11 and technical message implementation remain separate review items.
Recent document checks
: unchanged, document 523a600af229
: unchanged, document 523a600af229
: unchanged, document 523a600af229
: unchanged, document 523a600af229
: failed, document 523a600af229
Baseline document
European Banking Authority
Source diagnostics
Lifecycle
Not recorded
Language
da
Retrieved
11 Sept 2026
Extraction
captured
Latest automated check
19 Sept 2026
Check outcome
unchanged
Evidence review
unvalidated
Type
guidance
Version
EBA/GL/2024/11, 4 July 2024; corrected Danish text; applies 30 December 2024
Retained original: data/country-handbook-evidence/dk/eba-travel-rule-2024-da-20260911.pdf; 376419 bytes, 26 pages. All paragraphs 1-94 inspected. Live EBA publication page and Finanstilsynet index checked on 11 September 2026; the EBA index original is retained separately. Paragraph 24 relief ended 31 July 2025. Danish Article 4(2)(c) and paragraph 81 wording qualifications are expressly reconciled, not represented as statutory corrigenda.
Recent document checks
: unchanged, document 57bad43838db
: unchanged, document 57bad43838db
: unchanged, document 57bad43838db
: unchanged, document 57bad43838db
: unchanged, document 57bad43838db
Conditions
Applies according to PSP, intermediary PSP, CASP or intermediary CASP role; linked-funds rules and crypto rules must not be interchanged.
LEI or equivalent fields remain conditional on the statutory message-field and supplied-identifier conditions. These are not demands that individual customers obtain an LEI.
Paragraph 24's temporary technical allowance ended on 31 July 2025. Abbreviation and joint-holder concessions expressly dependent on that allowance are not a current general exemption.
Exceptions
The Danish statutory Article 4(2)(c) payer/payee wording discrepancy is retained as a textual qualification. The corrected Danish supervisory guidance supports the conditional payee-identifier implementation; no statutory corrigendum is claimed.
Evidence diagnostics
Record ID
dk-tfr-guideline-fields-linked-transfers
Lifecycle
Not recorded
Scenario applicability
Not recorded
Topic
monitoring
Status when reviewed
current
Review status
source checked
Effective from
30 Dec 2024
Effective to
Not recorded
Coverage limitations
United Kingdom
The core FCA AML binding-rule routes are now mapped by Handbook firm class, activity and territory under SYSC 1 Annex 1, including SYSC 6 and the insurer/SYSC 3 route. Detailed registration applications, fitness/propriety, complete trust-register filings and wider outsourcing/prudential governance remain separately scoped extensions, not omissions from these two core AML rule routes.
The statutory customer-level risk assessment and selected official 2025 ML/TF and 2021 PF context are mapped. Full sector ratings, all typologies and a dated FATF list snapshot are not mapped. National context does not replace a firm's assessment; no numerical customer-risk algorithm is prescribed.
Core POCA/TACT reporting, consent, selected low-value/mixed-property exceptions, tipping-off and investigation-integrity offences are mapped; NCA crime/SAR distinctions now have retained originals. Case law, all delegated overseas-conduct/excluded-business exceptions, court procedure and wider information-sharing powers remain outside the bounded review.
Selected Russia-regime statutory controls now include the distinct prohibited-person initial and annual reporting branch. Other sanctions regimes, Russia sectoral/oil involved-person duties and designated-person self-reporting remain explicit extensions outside this bounded financial-firm core. Live designation matching is an excluded product function, not a content delivery gate.
Current correspondent, pooled-account, e-money, transfer and long-term insurance beneficiary controls are mapped, including life-policy high-risk beneficiary ownership and insurance PEP measures. Insolvent-bank transfer timing and specialist investment-fund/distribution rules remain optional extensions to this bounded core. Crypto correspondent duties commencing 1 February 2027 and remaining control changes commencing 25 October 2027 require later reconciliation.
JMLSG base guidance must be read with current legislation and subsequent revisions. Full Part II and Part III sector review, unresolved HMT approval of later revisions and all specialist entity/acting-on-behalf scenarios remain outstanding. No universal identity-document package is prescribed.
FCA Handbook FCG 3.2 Themes requires an evidence review. Affected explanations are not confirmed as current. Previously checked explanations may be read separately with their baseline date; rejected evidence is not displayed.
FCA Handbook Glossary: authorised person requires an evidence review. Affected explanations are not confirmed as current. Previously checked explanations may be read separately with their baseline date; rejected evidence is not displayed.
FCA Handbook Glossary: firm requires an evidence review. Affected explanations are not confirmed as current. Previously checked explanations may be read separately with their baseline date; rejected evidence is not displayed.
FCA Handbook SYSC 3.2: Areas covered by systems and controls could not be checked. This does not establish that the law changed. Affected explanations are not confirmed as current. Previously checked explanations may be read separately with their baseline date; rejected evidence is not displayed.
FCA Handbook SYSC 6.1: Compliance requires an evidence review. Affected explanations are not confirmed as current. Previously checked explanations may be read separately with their baseline date; rejected evidence is not displayed.
FCA Handbook SYSC 6.3 Financial crime requires an evidence review. Affected explanations are not confirmed as current. Previously checked explanations may be read separately with their baseline date; rejected evidence is not displayed.
FCA Handbook SYSC 1: Application and purpose, including Annex 1 requires an evidence review. Affected explanations are not confirmed as current. Previously checked explanations may be read separately with their baseline date; rejected evidence is not displayed.
The UK Sanctions List requires an evidence review. Affected explanations are not confirmed as current. Previously checked explanations may be read separately with their baseline date; rejected evidence is not displayed.
JMLSG Current Guidance requires an evidence review. Affected explanations are not confirmed as current. Previously checked explanations may be read separately with their baseline date; rejected evidence is not displayed.
JMLSG Revisions requires an evidence review. Affected explanations are not confirmed as current. Previously checked explanations may be read separately with their baseline date; rejected evidence is not displayed.
Money Laundering, Terrorist Financing and Transfer of Funds (Information on the Payer) Regulations 2017, SI 2017/692 requires an evidence review. Affected explanations are not confirmed as current. Previously checked explanations may be read separately with their baseline date; rejected evidence is not displayed.
Money Laundering and Terrorist Financing (Amendment) Regulations 2026, SI 2026/621 requires an evidence review. Affected explanations are not confirmed as current. Previously checked explanations may be read separately with their baseline date; rejected evidence is not displayed.
UKFIU SARs Best Practice Guidance, Chapter 2: Submitting a SAR requires an evidence review. Affected explanations are not confirmed as current. Previously checked explanations may be read separately with their baseline date; rejected evidence is not displayed.
UKFIU SARs Best Practice Guidance, Chapter 3: Understanding DAMLs and DATFs requires an evidence review. Affected explanations are not confirmed as current. Previously checked explanations may be read separately with their baseline date; rejected evidence is not displayed.
Suspicious Activity Reports requires an evidence review. Affected explanations are not confirmed as current. Previously checked explanations may be read separately with their baseline date; rejected evidence is not displayed.
National risk assessment of money laundering and terrorist financing 2025 requires an evidence review. Affected explanations are not confirmed as current. Previously checked explanations may be read separately with their baseline date; rejected evidence is not displayed.
UK financial sanctions general guidance requires an evidence review. Affected explanations are not confirmed as current. Previously checked explanations may be read separately with their baseline date; rejected evidence is not displayed.
National risk assessment of proliferation financing requires an evidence review. Affected explanations are not confirmed as current. Previously checked explanations may be read separately with their baseline date; rejected evidence is not displayed.
Proceeds of Crime Act 2002, revised UK text requires an evidence review. Affected explanations are not confirmed as current. Previously checked explanations may be read separately with their baseline date; rejected evidence is not displayed.
Proceeds of Crime Act 2002, Part 7: Money laundering requires an evidence review. Affected explanations are not confirmed as current. Previously checked explanations may be read separately with their baseline date; rejected evidence is not displayed.
Proceeds of Crime Act 2002, Schedule 9: Regulated sector and supervisory authorities requires an evidence review. Affected explanations are not confirmed as current. Previously checked explanations may be read separately with their baseline date; rejected evidence is not displayed.
Proceeds of Crime Act 2002, Section 342: Offences of prejudicing investigation requires an evidence review. Affected explanations are not confirmed as current. Previously checked explanations may be read separately with their baseline date; rejected evidence is not displayed.
Sanctions and Anti-Money Laundering Act 2018, revised UK text requires an evidence review. Affected explanations are not confirmed as current. Previously checked explanations may be read separately with their baseline date; rejected evidence is not displayed.
Terrorism Act 2000, revised UK text requires an evidence review. Affected explanations are not confirmed as current. Previously checked explanations may be read separately with their baseline date; rejected evidence is not displayed.
No source-checked verification requirements have been mapped for this selection. This does not mean no obligations apply.
No source-checked risk and edd requirements have been mapped for this selection. This does not mean no obligations apply.
This handbook explains selected requirements reviewed through 11 September 2026. It is not an exhaustive statement of UK financial-crime law or confirmation of a firm's compliance.
Apply each requirement's activity, customer and territorial conditions. Selecting a business line does not establish that a firm is within the legal perimeter.
Legislation, supervisory guidance and suggested evidence serve different purposes. Information held by a trustee is not automatically information that every financial firm must collect.
A source publication date is not necessarily the date its requirements take effect. Future provisions, unconfirmed dates and remaining evidence gaps are identified separately.
The statutory sanctions additions reviewed on 11 September 2026 cover selected Russia-regime controls. They are not a complete account of that regime or a substitute for checking other sanctions regimes and the actual licence or designation.
Denmark
The inspected Act 764/2026 governance additions commence on 15 September and remain separately versioned with the existing review boundary. This review does not establish the complete future legal position; no currentness guard or end date has been changed.
The FIU still links its 2022 money-laundering assessment, with a horizon ending in 2025. The June 2026 annual report announces a replacement, but publication was not verified. PET's January 2024 terrorist-financing assessment is now mapped for selected retail-bank risks; refreshed supranational evidence and the adequacy of the combined risk picture for an actual institution remain unverified. The large older NRA is retained and hashed but exceeds the bounded offline import limit.
The core sanctions map now covers shared ownership/control, Danish authority routing, Belarus asset freezing, corporate deposits and reporting, enumerated payment/e-money/crypto services, provider ownership, securities/CSD, issuer/lending, financial-counterparty and crypto-platform prohibitions. It is not an exhaustive catalogue of every geographic or trade regime. Article 5aa/5ac/5ad counterparty-specific and trade-purpose derogations remain an exposure-based inventory rather than a complete specialist manual. The ERST original-capture 403 remains; the Foreign Ministry and Finanstilsynet provide retained primary authority alternatives, while ERST's national UN notification instruction remains explicitly web-evidenced. No live list, trade-form or customer-clearance engine is part of this product.
The core map now includes trust/foundation beneficial-owner roles, conditional insurance beneficiaries, correspondent and group controls, and shared reliance across customer types. Foreign legal-form/register interpretation, nominee arrangements beyond the mapped risk factor, and acting as a professional trustee remain outside the bounded customer map. Consumer basic-account and switching protections must not be applied to corporate, investment or crypto products. Minors, incapacity, deceased customers, the separate basic-deposit-account regime and loan/security mechanics remain excluded special cases; the existing fixed-loan qualification is unchanged.
The corrected Danish remote-onboarding guidelines now cover legal-person eligibility, identity, representative authority, beneficial owners and purpose before completion. Formal national EBA compliance notification is not asserted, but is not a missing statutory customer control. A bank's implementation, customer evidence, vendor performance and fraud testing remain outside this explanatory handbook, not source-delivery gates.
The corrected Danish EBA transfer guidelines now map provider roles, linked transfers, complete joint-holder fields, missing-information deadlines, repeated-failure supervisor reports, self-hosted verification and direct debits. The conditional payee identifier and instant-payment reservation are reconciled for handbook interpretation using native guidance and authentic legislation, with the literal Danish discrepancies retained and no statutory corrigendum claimed. The separate national territorial route under EU Article 35 remains unverified and excluded; ordinary Denmark scope does not depend on that exemption. XML/taxonomy integration, FIU submission, list operation and bank-engine execution are excluded product functions.
Historical commencement dates have not been reconstructed for every inherited requirement. The existing 15 September governance boundary and staged future record remain unchanged. New source captures and provision mappings support the bounded core handbook, not country-wide legal certification or future-currentness approval. Independent review of the new conditional sanctions and transfer deltas remains outstanding.
The 27 September public re-audit reported eight changed sources requiring revalidation and additional failed or unvalidated checks whose IDs were not resolved. Named source baselines remain in the package; unmatched failures are deliberately not assigned to guessed records.
Finanstilsynet states its Denmark PEP list was updated on 22 September 2026. The list itself is not retained or reconciled, and the PEP reporting order and operational screening route remain unmapped. This is not evidence of a complete PEP control.
The retained Regulation 269/2014 consolidation is dated 7 August 2026 and predates Regulation 2026/2160 of 22 September. The amendment is recorded as an unresolved annex delta; no complete current list, live feed or customer-clearance result is available.
The 2022 Danish AML NRA states a 2022-2025 horizon. The 2026 replacement announced in the FIU annual report has not been verified in this package; a current AML NRA is not claimed.
Known Finanstilsynet-indexed orders, applicable and scoped-out sectors, shared EU instruments and retained sources now have structured dispositions. Several applicable instruments and categories remain uncaptured or unmapped, and the register has not undergone independent completeness review.
Legal-position, plain-language and practical-application draft layers were added for the 12 newly classified requirements. They lack trusted independent review artifacts and are withheld from public requirement details.
No hosted end-to-end acceptance evidence was added. The selector is not proof of onboarding, failed-CDD escalation, sanctions holds, FIU reporting or offboarding journey execution.
Vejledning til virksomheder omfattet af hvidvaskloven requires an evidence review. Affected explanations are not confirmed as current. Previously checked explanations may be read separately with their baseline date; rejected evidence is not displayed.
Pengeinstitutter: basic payment accounts, MitID and complaints requires an evidence review. Affected explanations are not confirmed as current. Previously checked explanations may be read separately with their baseline date; rejected evidence is not displayed.
Vejledning om indefrysning requires an evidence review. Affected explanations are not confirmed as current. Previously checked explanations may be read separately with their baseline date; rejected evidence is not displayed.
Forordning (EF) 765/2006, udvalgte detailbankrestriktioner requires an evidence review. Affected explanations are not confirmed as current. Previously checked explanations may be read separately with their baseline date; rejected evidence is not displayed.
Council Implementing Regulation (EU) 2026/2160 of 22 September 2026 could not be checked. This does not establish that the law changed. Affected explanations are not confirmed as current. Previously checked explanations may be read separately with their baseline date; rejected evidence is not displayed.
Hvordan sender man en underretning? requires an evidence review. Affected explanations are not confirmed as current. Previously checked explanations may be read separately with their baseline date; rejected evidence is not displayed.
Risikovurdering af hvidvask requires an evidence review. Affected explanations are not confirmed as current. Previously checked explanations may be read separately with their baseline date; rejected evidence is not displayed.
Sanktioner mod Rusland og Belarus requires an evidence review. Affected explanations are not confirmed as current. Previously checked explanations may be read separately with their baseline date; rejected evidence is not displayed.
Finanstilsynets vejledning om lov om forebyggende foranstaltninger mod hvidvask og finansiering af terrorisme (hvidvaskloven) requires an evidence review. Affected explanations are not confirmed as current. Previously checked explanations may be read separately with their baseline date; rejected evidence is not displayed.
L 9 as adopted: amendments strengthening Denmark's implementation of FATF recommendations, including proliferation financing requires an evidence review. Affected explanations are not confirmed as current. Previously checked explanations may be read separately with their baseline date; rejected evidence is not displayed.
Vejledning om anvendelse af MitID som kontrolkilde i kundekendskabsprocedurer requires an evidence review. Affected explanations are not confirmed as current. Previously checked explanations may be read separately with their baseline date; rejected evidence is not displayed.
Hvidvaskomraadet requires an evidence review. Affected explanations are not confirmed as current. Previously checked explanations may be read separately with their baseline date; rejected evidence is not displayed.
Bekendtgoerelse af lov om betalingskonti og basale erhvervskonti requires an evidence review. Affected explanations are not confirmed as current. Previously checked explanations may be read separately with their baseline date; rejected evidence is not displayed.
Ansvarlige myndigheder requires an evidence review. Affected explanations are not confirmed as current. Previously checked explanations may be read separately with their baseline date; rejected evidence is not displayed.
No source-checked verification requirements have been mapped for this selection. This does not mean no obligations apply.
PUBLIC RESEARCH PREVIEW - ASSURANCE HOLD (27 September 2026). The independent country release gate is incomplete. This page is not a complete or independently assured statement of Danish AML/CTF requirements.
Selected requirements, source counts and the selected as-of date describe the reader selection. They are not independent review counts, a last-verified-through date or a legal completeness measure.
Eight production sources were reported changed and require revalidation; additional failed or unvalidated checks were not identified by source ID in the audit. Review Source diagnostics and the prominent assurance warning.
The Finanstilsynet Denmark PEP list page states it was updated on 22 September 2026; the list itself is not retained or reconciled in this package. No live screening is evidenced.
The 2022 AML NRA states a 2022-2025 horizon. A current 2026 AML NRA or replacement is not established; do not treat the 2022 assessment as current.
The Regulation 269/2014 consolidation dated 7 August 2026 predates Council Implementing Regulation 2026/2160 of 22 September. Neither record provides a complete sanctions list, live feed or customer-clearance result.
The 15 September 2026 commencement of the mapped Act 764/2026 additions is reflected. The change does not close source-universe, currentness, applicability, content-review or operational-journey gaps.
Draft content layers are not displayed until a trusted independent review resolves them. This handbook is not proof that any firm has implemented a control or completed a customer journey.
Country scope is Denmark, not automatically Greenland or the Faroe Islands. AML duties, consumer payment-account protections and sanctions rules have different application conditions.
