AMLR Reference

Customer data fields for AMLR due diligence

A growing, field-level dictionary of the data points to collect, verify, store and screen. Each entry states the definition, the format, whether it is mandatory, and the legal basis where one applies.

Working draft. Legal basis references point to Regulation (EU) 2024/1624 (AMLR) as published in the Official Journal; verify against the final text before use in production systems.

Company name (legal entity)

The name attributes to capture when identifying a corporate customer. AMLR Article 22(1)(b) requires, for legal entities, the name, legal form, registered/head office address, and registration number, so the name block below is built around that core plus the operational fields needed to make screening and matching reliable.

  • legal_name

    Mandatory

    Free text, UTF-8, max 300 chars

    The full registered name of the entity exactly as recorded in the official company register of the country of incorporation, including the legal-form suffix.

    AMLR Art. 22(1)(b) — "the name"

    Store verbatim from the register, never a normalised or truncated version.

  • legal_form

    Mandatory

    Coded value (ISO 20275 ELF code) + free text

    The legal form of the entity (e.g. AB, GmbH, S.A., Ltd), captured as a separate attribute even when it is part of the legal name.

    AMLR Art. 22(1)(b) — "legal form"

  • legal_name_latin

    Conditional

    Free text, Latin script

    Transliteration of the legal name into Latin script when the register entry uses a non-Latin script (Cyrillic, Greek, Arabic, Chinese, etc.).

    Required for sanctions and PEP screening; both versions must be screened.

  • trading_names

    Recommended

    Array of free text

    Business, trading or brand names the entity uses commercially and that differ from the legal name (doing-business-as).

    Needed for transaction-monitoring alerts and adverse-media matching.

  • previous_names

    Recommended

    Array of {name, valid_from, valid_to}

    Former legal names with the date range each was in force, including names carried over through mergers.

    Frequent renaming is a risk indicator and old names may still appear on sanctions lists.

  • registration_number

    Mandatory

    Free text as printed by the register

    The identifier assigned to the entity in the official register, which binds the name to a unique entity.

    AMLR Art. 22(1)(b) — "registration number"

  • register_name_and_country

    Mandatory

    Free text + ISO 3166-1 alpha-2

    Which register the name was taken from and the country/jurisdiction of incorporation.

    Two entities can share a name across jurisdictions; the register plus country disambiguates them.

  • lei

    Conditional

    ISO 17442, 20 alphanumeric characters

    Legal Entity Identifier, where the entity has one.

    Strongest key for reconciling names across data sources.

  • euid

    Conditional

    EUID string

    European Unique Identifier from the Business Registers Interconnection System, for EU entities.

  • name_source

    Mandatory

    Coded value + document reference

    The document or data source the name was verified against (register extract, certificate of incorporation, register API).

    AMLR Art. 24 — verification against independent and reliable sources

  • name_verified_on

    Mandatory

    ISO 8601 date

    Date the name was verified, and the date it was last refreshed.

    Drives the ongoing-due-diligence refresh cycle.

  • name_screening_result

    Mandatory

    Coded result + list version + ISO 8601 timestamp

    Outcome of sanctions, PEP and adverse-media screening performed on each stored name variant, with list version and timestamp.

    Screen legal name, Latin transliteration, trading names and previous names — not just the legal name.

  • entity_status

    Recommended

    Coded value

    Register status of the entity (active, dissolved, in liquidation, struck off) as at the verification date.

    A name that resolves to a dissolved entity is a red flag for onboarding.

Legal entity — registration and identifiers

Beyond the name, AMLR Article 22(1)(b) requires the registration number and the address of the registered or head office. In practice you also need the identifiers that let you reconcile the customer across registers, screening lists and payment messages.

  • country_of_incorporation

    Mandatory

    ISO 3166-1 alpha-2

    Jurisdiction where the entity is legally registered.

    AMLR Art. 22(1)(b)

    Drives geographic risk scoring and the high-risk third-country checks under Art. 29.

  • date_of_incorporation

    Recommended

    ISO 8601 date

    Date the entity was entered in the register.

    Newly formed entities used for high-value activity are a risk indicator.

  • tax_identification_number

    Conditional

    Free text + ISO 3166-1 alpha-2

    National tax number(s) of the entity, with issuing country.

  • vat_number

    Recommended

    VIES format

    EU VAT identification number where the entity is VAT registered.

  • nace_code

    Mandatory

    NACE Rev. 2 code + description

    Principal economic activity of the entity.

    AMLR Art. 20(1)(c) — understanding the nature of the business

    Used for sector risk scoring and to test whether transactions match the stated business.

  • listed_status

    Conditional

    Boolean + market identifier (MIC)

    Whether the entity is listed on a regulated market and where, including whether it is subject to disclosure requirements ensuring adequate transparency of ownership.

    AMLR Art. 22(3)

    Affects the extent of beneficial ownership identification required.

  • regulated_status

    Conditional

    Coded value + licence reference

    Whether the entity is itself a supervised obliged entity, with regulator and licence number.

    Relevant to simplified due diligence eligibility under Art. 33.

  • group_affiliation

    Recommended

    Entity references + LEI

    Parent entity, ultimate parent and group identifier where the customer is part of a group.

Addresses and places of business

AMLR Article 22(1)(b) requires the address of the registered office and, where different, the head office. Operational addresses matter because a mismatch between the registered address and where business is actually conducted is a classic layering indicator.

  • registered_office_address

    Mandatory

    Structured address (street, number, postcode, city, region, ISO 3166-1 alpha-2)

    The address recorded in the official register.

    AMLR Art. 22(1)(b) — "address of the registered office"

  • head_office_address

    Conditional

    Structured address

    Address of the head office where this differs from the registered office.

    AMLR Art. 22(1)(b) — "and head office, if different"

  • principal_place_of_business

    Recommended

    Structured address

    Where the entity actually carries out its main activity.

    Flag when this sits in a different jurisdiction from incorporation.

  • correspondence_address

    Recommended

    Structured address

    Postal address used for communication where different from the above.

  • address_type_flags

    Recommended

    Coded value

    Whether the address is a serviced/virtual office, a registered-agent address, a c/o address or a PO box.

    Mass-registration addresses shared by hundreds of entities are a shell-company indicator.

  • address_verification

    Mandatory

    Coded source + document reference + ISO 8601 date

    Source and date of address verification (register extract, utility bill, government database).

    AMLR Art. 24 — verification against reliable, independent sources

  • address_history

    Recommended

    Array of {address, valid_from, valid_to}

    Previous addresses with the period each was in force.

Natural person — identification data

AMLR Article 22(1)(a) sets the identification data for a natural person: names, place and full date of birth, nationalities, residential address and identification number. These fields apply to individual customers, beneficial owners and persons acting on behalf of the customer alike.

  • given_names

    Mandatory

    Free text, UTF-8

    All first and middle names as printed on the identity document.

    AMLR Art. 22(1)(a) — "the first name(s) and surname"

  • surname

    Mandatory

    Free text, UTF-8

    Family name(s), including compound and maiden names.

    AMLR Art. 22(1)(a)

  • name_latin_transliteration

    Conditional

    Latin script

    Machine-readable-zone transliteration of the name for non-Latin scripts.

    Screen both the native and transliterated forms.

  • date_of_birth

    Mandatory

    ISO 8601 date

    Full date of birth, not just the year.

    AMLR Art. 22(1)(a) — "place and full date of birth"

  • place_of_birth

    Mandatory

    Free text + ISO 3166-1 alpha-2

    City/town and country of birth.

    AMLR Art. 22(1)(a)

  • nationalities

    Mandatory

    Array of ISO 3166-1 alpha-2

    All nationalities held, or statelessness, including recently acquired citizenships.

    AMLR Art. 22(1)(a) — "nationality or nationalities"

    Citizenship-by-investment nationalities are an explicit risk factor.

  • residential_address

    Mandatory

    Structured address

    Usual residential address; the country of residence at minimum where a full address is unavailable.

    AMLR Art. 22(1)(a)

  • national_identification_number

    Conditional

    Free text + ISO 3166-1 alpha-2

    National identity number, personal number or equivalent, with issuing country.

    AMLR Art. 22(1)(a)

    Where no such number exists, record the identity document number instead.

  • gender

    Recommended

    Coded value

    Gender as stated on the identity document, where captured.

    Only where needed for identity matching; minimise under data protection rules.

  • deceased_flag

    Recommended

    Boolean + ISO 8601 date

    Whether the person is recorded as deceased, with date and source.

Identity documents and verification evidence

AMLR Article 24 requires verification on the basis of documents, data or information from a reliable and independent source, including electronic identification means. Store what was checked, how, and when — not just the conclusion.

  • document_type

    Mandatory

    Coded value

    Type of document used to verify identity (passport, national ID, residence permit, driving licence).

    AMLR Art. 24

  • document_number

    Mandatory

    Free text

    Serial number of the document.

  • issuing_country_and_authority

    Mandatory

    ISO 3166-1 alpha-2 + free text

    Country and authority that issued the document.

  • issue_and_expiry_date

    Mandatory

    ISO 8601 dates

    Date of issue and date of expiry.

    Expired documents must trigger re-verification during ongoing due diligence.

  • verification_method

    Mandatory

    Coded value

    How identity was verified: physical presence, certified copy, remote video, eIDAS electronic identification, qualified trust service, or a supervised digital identity scheme.

    AMLR Art. 22(6) and Art. 24

    Remote/non-face-to-face onboarding is a risk factor in Annex III.

  • liveness_and_biometric_result

    Conditional

    Coded result + score + vendor reference

    Result of liveness detection and face match where remote identification was used, with vendor and score.

  • document_authenticity_check

    Recommended

    Coded result

    Outcome of chip/NFC read, MRZ checksum, hologram or database validation.

  • verification_performed_by

    Mandatory

    User/system identifier

    Person or system that performed and approved the verification.

    Needed for the audit trail and the record-keeping obligation.

  • document_image_reference

    Mandatory

    Document store reference + ISO 8601 date

    Pointer to the stored copy of the document, with retention date.

    AMLR Art. 77 — retention of CDD records for five years

Persons purporting to act on behalf of the customer

AMLR Article 25 requires you to verify the identity of any person purporting to act on behalf of the customer and to verify that they are authorised to do so. Capture both the person and the mandate.

  • representative_person

    Mandatory

    Reference to natural person record

    Full identification data of the representative, using the natural-person field set.

    AMLR Art. 25(1)

  • representative_role

    Mandatory

    Coded value

    Capacity in which the person acts: director, authorised signatory, power of attorney, guardian, legal representative.

  • authorisation_evidence

    Mandatory

    Document reference

    Document establishing the authorisation (board resolution, register extract of signatories, power of attorney).

    AMLR Art. 25(1) — verification of authorisation

  • authorisation_scope_and_limits

    Recommended

    Structured text + limits

    What the person may do, including monetary or product limits and joint-signature requirements.

  • authorisation_validity

    Mandatory

    ISO 8601 dates

    Start and end date of the mandate.

    Expired mandates must block instruction acceptance.

  • revocation_record

    Mandatory

    Boolean + ISO 8601 date + user reference

    Whether and when the mandate was revoked, and by whom.

Beneficial ownership and control

AMLR Chapter IV (Articles 51–62) sets the beneficial ownership rules. Article 51 defines the beneficial owner as the natural person who ultimately owns or controls the entity. The 25% ownership threshold in Article 52 is only an indication; Article 53 requires a separate, parallel assessment of control via other means. Where neither test identifies anyone, Article 54 points to the senior managing official as a fallback. Capture the full chain, the calculations and the rationale, not just the end names.

  • ubo_person

    Mandatory

    Array of natural person references

    Identification data for each beneficial owner, using the natural-person field set.

    AMLR Art. 22(1) and Chapter IV

  • basis_of_beneficial_ownership

    Mandatory

    Coded value

    Whether the person qualifies through ownership interest, through control via other means, or as a senior managing official where no owner is identified.

    AMLR Art. 51, Art. 52, Art. 53 and Art. 54

    Record explicitly when the senior-managing-official fallback is used, and why.

  • ownership_percentage

    Mandatory

    Decimal percentage, two decimals

    Direct and indirect share of capital and of voting rights held, calculated through the chain.

    AMLR Art. 51 — 25% threshold as an indication

    Store direct and effective (multiplied through the chain) percentages separately.

  • direct_ownership_percentage

    Mandatory

    Decimal percentage, two decimals

    Ownership interest held directly in the customer entity, before multiplying through intermediate layers.

    AMLR Art. 52

  • indirect_effective_percentage

    Mandatory

    Decimal percentage, two decimals

    Ownership interest calculated by multiplying each layer's stake along the chain and summing parallel chains.

    AMLR Art. 52

    Aggregation is required when several natural persons hold interests through the same intermediate entity.

  • voting_rights_percentage

    Mandatory

    Decimal percentage, two decimals

    Percentage of voting rights held directly and indirectly, which may differ from capital ownership.

    AMLR Art. 51 and Art. 52

    Control can exist with low or no capital stake if voting rights are concentrated.

  • ownership_interest_type

    Mandatory

    Coded value + free text

    The instrument through which ownership is held: shares, units, voting shares, non-voting shares, options, convertible instruments or other.

    AMLR Art. 52

  • control_other_means

    Conditional

    Structured text + coded categories

    Control not based on shareholding: shareholder agreements, veto rights, right to appoint or remove management, dominant influence, control through debt or contracts.

    AMLR Art. 51 and Art. 53

  • right_to_appoint_remove_body

    Conditional

    Boolean + document references

    Evidence that a natural person can appoint or remove a majority of the administrative, management or supervisory body, or senior management.

    AMLR Art. 53 — control via other means

  • shareholders_agreement_veto

    Conditional

    Document reference + summary of terms

    Shareholders' agreements, veto rights or similar arrangements that confer decisive influence over strategic decisions.

    AMLR Art. 53

  • significant_influence_indicators

    Conditional

    Structured text

    Other indicators of dominant or decisive influence, such as profit distribution rights, residual-asset claims or de facto decision-making.

    AMLR Art. 53

  • senior_managing_official_fallback

    Conditional

    Natural person reference + free-text justification

    Where no beneficial owner is identified under Articles 52 and 53, the natural person(s) holding the position of senior managing official and the record of steps taken.

    AMLR Art. 54

    This is a last-resort fallback, not a default. Document why ownership and control tests yielded no result.

  • ownership_chain

    Mandatory

    Graph of {entity, jurisdiction, stake, layer}

    Full chain of intermediate legal entities and arrangements between the customer and each beneficial owner.

    Number of layers and offshore jurisdictions in the chain are strong risk indicators.

  • bearer_share_or_nominee_identification

    Conditional

    Boolean + party references + evidence

    Where shares are bearer shares or held by nominees, the natural person who ultimately owns, controls or benefits from them.

    AMLR Chapter IV — transparency of ownership

    Bearer shares and nominee arrangements are classic opacity techniques.

  • nominee_arrangements

    Conditional

    Boolean + party references

    Whether nominee shareholders or nominee directors appear in the chain, and who the nominator is.

  • trust_roles

    Conditional

    Array of {role, person reference}

    For trusts and similar arrangements: settlor, trustee, protector, beneficiaries or class of beneficiaries, and any other person exercising ultimate control.

    AMLR Art. 58

    Each role must be identified separately, not collapsed into one "owner" field.

  • register_cross_check

    Mandatory

    Coded result + ISO 8601 date + register reference

    Result of consulting the central beneficial ownership register, including any discrepancy found.

    Discrepancies between register data and your findings must be reported to the register.

  • ubo_verification_evidence

    Mandatory

    Array of document references

    Documents or sources used to verify each beneficial owner and each link in the chain.

    AMLR Art. 24

  • ubo_as_of_date

    Mandatory

    ISO 8601 dates

    Date the ownership picture was established and the date it must next be refreshed.

  • source_of_funds_for_stake

    Conditional

    Coded value + evidence references

    How the beneficial owner acquired or funds the ownership stake, where enhanced due diligence or PEP considerations apply.

    AMLR Art. 34 (EDD) and Art. 42 (PEPs)

  • ubo_pep_status

    Conditional

    Boolean + coded PEP role + ISO 3166-1 alpha-2 + date range

    Whether the beneficial owner is a PEP, family member or known close associate, including function, country and dates.

    AMLR Art. 42

  • ownership_change_alerts

    Mandatory

    Array of {date, change, source, follow-up}

    Record of any subsequent change in shareholding, control rights or senior management that triggers a refresh of the beneficial ownership picture.

    AMLR Art. 26 — ongoing monitoring

Purpose and intended nature of the business relationship

AMLR Article 20(1)(c) requires obliged entities to assess and obtain information on the purpose and intended nature of the business relationship. This is the baseline against which later transaction monitoring is judged, so it must be captured as data, not free-text prose alone.

  • relationship_purpose

    Mandatory

    Coded value + free text

    Why the customer wants the relationship, in coded categories plus a narrative.

    AMLR Art. 20(1)(c)

  • products_and_services

    Mandatory

    Array of product codes

    The products and services the customer is expected to use.

  • expected_activity_volume

    Mandatory

    Numeric + currency + period

    Expected number and value of transactions per period, by product.

    Without this baseline, deviation-based monitoring cannot function.

  • expected_counterparty_countries

    Mandatory

    Array of ISO 3166-1 alpha-2

    Countries the customer expects to send funds to or receive funds from.

    Compare against the high-risk third-country list under Art. 29.

  • expected_transaction_types

    Mandatory

    Array of coded values

    Payment types expected: cash, card, wire, crypto, cheque, correspondent flows.

  • cash_usage_expectation

    Conditional

    Boolean + amount + currency

    Whether and to what extent the customer expects to use cash.

    AMLR Art. 80 — EUR 10 000 cash payment limit

  • employment_or_business_activity

    Mandatory

    Free text + NACE/ISCO code

    Occupation for individuals, or the actual business activity for entities, in the customer's own words plus a code.

  • relationship_start_date

    Mandatory

    ISO 8601 date

    Date the business relationship was established.

    AMLR Art. 23 — timing of verification

Source of funds and source of wealth

Source of funds concerns the money used in a specific transaction or relationship; source of wealth concerns how the customer's total wealth was built. AMLR Article 34 requires information on both as an enhanced due diligence measure, and Article 42 requires it for politically exposed persons.

  • source_of_funds_category

    Mandatory

    Coded value

    Origin of the funds entering the relationship: salary, business income, sale of assets, inheritance, loan, investment returns, gift.

  • source_of_funds_evidence

    Conditional

    Array of document references

    Supporting documentation: payslips, audited accounts, sale contract, loan agreement, tax return.

    AMLR Art. 34 — enhanced due diligence

    Mandatory in high-risk situations and for PEPs.

  • source_of_wealth_narrative

    Conditional

    Structured text + timeline entries

    How the customer's overall wealth was accumulated, with periods and amounts.

    AMLR Art. 42 — PEPs, family members and close associates

  • source_of_wealth_evidence

    Conditional

    Array of document references

    Independent evidence corroborating the wealth narrative.

  • plausibility_assessment

    Mandatory

    Coded conclusion + free text + user reference

    The analyst's conclusion on whether funds and wealth are consistent with the customer profile, with reasoning.

    Record the reasoning; an unexplained conclusion is not defensible to a supervisor.

  • funding_account_details

    Recommended

    IBAN/account reference/wallet address + holder name

    The account, wallet or instrument the funds arrive from, including holder name where available.

    Third-party funding that does not match the customer name is a red flag.

Sanctions, PEP and adverse media screening

AMLR Article 20 requires screening for targeted financial sanctions, and Articles 41–45 govern politically exposed persons, their family members and known close associates. Screening is a repeatable process, so store the inputs, the list version and the decision — never just a pass/fail flag.

  • sanctions_screening_result

    Mandatory

    Coded result + match score

    Outcome of screening against UN, EU and applicable national sanctions lists, for every name variant held.

    AMLR Art. 20(1)(d) — verification against targeted financial sanctions lists

  • list_version_and_timestamp

    Mandatory

    List identifier + version + ISO 8601 timestamp

    Which list version was used and exactly when the screening ran.

    Essential to prove what you could reasonably have known at a point in time.

  • pep_status

    Mandatory

    Boolean + coded function + ISO 3166-1 alpha-2 + date range

    Whether the person holds or has held a prominent public function, with the function, country and dates.

    AMLR Art. 2(1)(34) and Art. 42

  • pep_relationship_type

    Conditional

    Coded value

    Whether the person is a PEP themselves, a family member, or a known close associate.

    AMLR Art. 2(1)(35)–(36)

  • pep_declassification_date

    Conditional

    ISO 8601 dates

    When a former PEP ceased to hold the function and the date risk was reassessed.

    AMLR Art. 45 — measures applied for at least 12 months after ceasing the function

    Risk-based; do not auto-clear at 12 months without an assessment.

  • senior_management_approval

    Conditional

    Approver identity + ISO 8601 timestamp + decision

    Record of senior management approval to establish or continue the relationship where required.

    AMLR Art. 42(1)(a) — PEP relationships require senior management approval

  • adverse_media_findings

    Recommended

    Array of {source, date, category, assessment}

    Negative news hits with source, date, allegation category and materiality assessment.

  • match_disposition

    Mandatory

    Coded value + free text + user reference + timestamp

    True match, false positive or discounted, with the reason and the analyst who decided.

    Every discounted match needs a documented reason; this is a standard supervisory sampling point.

  • rescreening_frequency

    Mandatory

    Period + ISO 8601 timestamp

    How often the record is rescreened and when it last ran.

    AMLR Art. 26 — ongoing monitoring

Customer risk assessment and profile

AMLR Article 20(2) requires the extent of due diligence measures to be adjusted to the risk, and Annexes II and III list the factors indicating potentially lower and higher risk. Store the factors and the score, so the outcome can be reproduced and challenged.

  • risk_rating

    Mandatory

    Coded value (e.g. low / medium / high / unacceptable)

    Overall customer risk classification.

    AMLR Art. 20(2)

  • risk_factor_scores

    Mandatory

    Array of {factor, value, weight, score}

    Individual factor scores for customer, product/service, delivery channel, geography and transaction risk.

    AMLR Annexes II and III

  • risk_model_version

    Mandatory

    Version string

    Version of the scoring methodology applied.

    Needed to explain why the same customer scored differently at different times.

  • manual_override

    Conditional

    Coded direction + free text + user reference + ISO 8601 date

    Any manual change to the calculated rating, with justification, approver and date.

    Downward overrides are a supervisory focus area.

  • edd_applied

    Conditional

    Array of coded measures + trigger

    Which enhanced due diligence measures were applied and why.

    AMLR Arts. 34–36

  • sdd_applied

    Conditional

    Array of coded measures + justification

    Which simplified due diligence measures were applied and the lower-risk justification.

    AMLR Art. 33

  • high_risk_third_country_exposure

    Mandatory

    Boolean + ISO 3166-1 alpha-2 array

    Whether the customer, beneficial owner or counterparties are connected to a country identified as high-risk.

    AMLR Art. 29 — enhanced measures for high-risk third countries

  • next_review_date

    Mandatory

    ISO 8601 date

    When the profile must next be reviewed, derived from the risk rating.

    AMLR Art. 26 — keeping documents and information up to date

Ongoing monitoring and transaction data

AMLR Article 26 requires ongoing monitoring of the business relationship, including scrutiny of transactions to ensure they are consistent with the customer profile, and keeping documents and information up to date. The transaction record has to carry enough context to make that scrutiny possible.

  • transaction_identifier

    Mandatory

    String

    Unique reference for each transaction.

    AMLR Art. 77 — record keeping

  • amount_and_currency

    Mandatory

    Decimal + ISO 4217 + rate

    Value and currency of the transaction, plus the base-currency equivalent and the rate used.

  • value_and_booking_date

    Mandatory

    ISO 8601 timestamps

    Execution date/time and booking date.

  • counterparty_details

    Mandatory

    Free text + identifier + ISO 3166-1 alpha-2

    Name, account/wallet identifier and country of the counterparty.

    Regulation (EU) 2023/1113 (TFR) for transfers of funds and crypto-assets

  • payment_purpose_and_reference

    Recommended

    Free text

    Stated purpose and the free-text remittance reference.

    Retain unaltered; truncated references break downstream monitoring.

  • channel_and_instrument

    Mandatory

    Coded value

    How the transaction was initiated: branch, online, mobile, API, card, ATM, correspondent.

  • cash_indicator

    Conditional

    Boolean + decimal + ISO 4217

    Whether cash was involved and the amount.

    AMLR Art. 80 — limit of EUR 10 000 on cash payments

  • profile_deviation_flag

    Mandatory

    Boolean + deviation metric

    Whether the transaction deviates from the expected activity captured at onboarding, and by how much.

    AMLR Art. 26(1)

  • alert_reference

    Mandatory

    Array of {alert id, scenario, score, status, closure reason}

    Monitoring alerts raised, with scenario, score, assignee and outcome.

  • review_history

    Mandatory

    Array of {date, trigger, findings, user}

    Record of each periodic or event-driven review of the relationship, with trigger, findings and reviewer.

    AMLR Art. 26(2)

Suspicion, reporting and case data

AMLR Article 69 requires obliged entities to report suspicion to the FIU, and Article 73 governs the prohibition on disclosure. Keep the internal escalation, the decision and the report itself as distinct, linked records.

  • internal_escalation

    Mandatory

    {user, ISO 8601 timestamp, free text}

    Internal report raised by staff, with who raised it, when, and the concern described.

  • suspicion_decision

    Mandatory

    Coded decision + free text + user reference + timestamp

    Whether suspicion was confirmed or dismissed, by whom, with reasoning.

    AMLR Art. 69(1)

    Dismissed cases must be documented as thoroughly as reported ones.

  • str_reference

    Conditional

    String + ISO 8601 timestamp

    Reference number of the report submitted to the FIU and the submission timestamp.

    AMLR Art. 69

  • predicate_offence_indication

    Recommended

    Coded value

    Suspected underlying offence category where identifiable.

  • fiu_feedback_and_instructions

    Conditional

    Free text + document reference + timestamp

    Any response, request for information or instruction to refrain from executing a transaction.

    AMLR Art. 69(2) — abstaining from carrying out transactions

  • tipping_off_controls

    Mandatory

    Access control list + coded restriction

    Access restrictions applied to the case record to prevent disclosure to the customer.

    AMLR Art. 73 — prohibition of disclosure

  • relationship_exit_record

    Conditional

    Coded reason + user reference + ISO 8601 date

    Where the relationship was terminated or refused, the decision, the reason and the approver.

    AMLR Art. 21 — inability to comply with due diligence requirements

Record keeping, retention and audit trail

AMLR Article 77 requires retention of due diligence records and transaction records for five years after the end of the relationship or the date of the occasional transaction. Article 76 requires the processing of personal data to stay within the AML purpose, so retention has to be modelled per field.

  • record_created_and_modified

    Mandatory

    ISO 8601 timestamps + user references

    Creation timestamp, last modification timestamp and the user or system responsible for each change.

  • field_level_change_log

    Mandatory

    Append-only array of {field, old value, new value, user, timestamp}

    Immutable history of previous values for every due diligence field.

    Overwriting a CDD value without history destroys the evidence you would need in an inspection.

  • retention_expiry_date

    Mandatory

    ISO 8601 date

    Date each record becomes due for deletion, calculated from the end of the relationship.

    AMLR Art. 77 — five-year retention period

  • legal_hold_flag

    Conditional

    Boolean + reason + authority reference

    Whether deletion is suspended because of an ongoing investigation or a national extension of the retention period.

  • data_source_lineage

    Mandatory

    Source identifier + ISO 8601 timestamp

    For every stored value, which system or provider it came from and when it was last refreshed.

    Needed to answer "where did this come from" during supervision.

  • third_party_reliance_record

    Conditional

    Party reference + coded scope + agreement reference

    Where due diligence was performed by a third party, who it was, what was relied on, and confirmation that the underlying data is available on request.

    AMLR Arts. 48–50 — reliance on third parties

    Ultimate responsibility stays with the obliged entity relying on the third party.

  • outsourcing_record

    Conditional

    Party reference + coded functions + ISO 8601 date

    Functions outsourced to a service provider, with the agreement, the controls and the date of the last assurance review.

    AMLR Arts. 51–53 on outsourcing arrangements

Still to come — trusts and legal arrangements as customers in their own right, occasional transactions and crypto-asset transfer data under Regulation (EU) 2023/1113, and sector-specific fields for gambling, real estate and high-value goods dealers.