Start hereDefine the product change and assess legal scope
~17 days leftOpen step
Guide library
Evaluation Europe

Andorra MONEYVAL 2018 follow-up

Andorra AML risk assessment for new products and technology

Prepare the money laundering and terrorist financing risk assessment for a new product, delivery method or technology. Use the 2018 MONEYVAL follow-up to understand why the assessment belongs in the launch process.

Issuing authority
Council of Europe MONEYVAL
Timing
Article 9(6) addresses risk analysis before introducing or allowing use of new products, practices and technologies. Assign review time before the planned release. The effort estimates in this guide are planning inputs.
Reviewed
Inside this guide
4 steps · 4 templates

Who it applies to

Product, risk and compliance teams at entities subject to Andorra’s AML/CFT law. Apply the current local rules to the actual entity, activity and proposed change.

What you’ll produce

A dated scope decision, a product risk assessment, evidence that controls passed testing and a signed launch decision with review triggers.

The 2018 technical re-rating for Recommendation 15 predates the revised standard covering virtual assets. Local counsel should confirm the operative law and applicable UIFAND guidance for each launch.

TEAM KICKOFF

Run the project

Go to the roadmap

Decisions for leadership

Which risks will we reduce and how will we measure it?
Set a target for each priority service or outcome. Use a current baseline to decide the investment needed, what can be phased in, and who accepts remaining risk.
Who will do the work and who can sign?
Appoint a sponsor, a day-to-day lead and a named owner for every workstream. Set aside their time and decide who can approve the outcome, accept remaining risk or authorize a filing.
Which deadlines can we promise?
Separate fixed external dates from internal targets. Confirm dependencies such as a vendor, test lab or assessor, and approve a backup plan if their dates slip.

How to spend the first week

  1. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work.
  2. Select one service and test a high-impact control with its owner. Record what actually happened, what failed and the proposed target.
  3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.

What to review each week

Monitor progress against the target, failed control tests and gaps that leave a critical service exposed.

Kickoff brief to share with your team

Fill this in with your sponsor and send it to the people who own the work.

Andorra MONEYVAL 2018 follow-up kickoff brief
Business reason and required outcome  [Contract, obligation or approval]
Scope and exclusions  [Entities, systems or activities, and reasons]
Fixed deadlines and internal milestones  [Date, source and owner]
Executive sponsor and authorized signer  [Names]
Project lead and backup  [Names]
First workstream  Define the product change and assess legal scope · Product owner + local counsel [Name and due date]
People, effort and external costs  [Estimate, owner and contingency]
Evidence folder and reviewer access  [Location, access owner and review date]
Decisions and blockers  [Item, options, owner and decision date]

First week
1. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work.
2. Select one service and test a high-impact control with its owner. Record what actually happened, what failed and the proposed target.
3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.
How to hand off evidence
  1. Record the requirement or claim, the person responsible, the period and the result. Link to the original report, configuration, test or case record.
  2. Include the version, system or product, date, and how you gathered the record. When a report covers a group of items, retain its filters and reconcile the count to the source.
  3. Ask the reviewer to open the evidence and reproduce the key check. Record their decision and date. Keep missing items or failures visible with an owner, a due date and a retest when needed.
  4. Share through the agreed channel. Keep sensitive originals in a restricted location and link any redacted copies to the corresponding originals.
BEFORE YOU START

How this works in practice

Two questions to check scope

  • What changes about customer identification, service access or movement of funds when this product launches?
  • Which test results should the risk owner see before approving production access?

Worked scenario

A fictional payment provider proposes remote onboarding for business customers. Its product owner maps the proposed workflow. Compliance assesses ownership and identity verification, and the release owner waits for evidence that referrals reach the AML review queue.

What to read next

FROM THE SOURCE

Cases and numbers

MONEYVAL · first enhanced follow-up

12Technical compliance upgrades in the 2018 report

12 technical recommendations were upgraded

The upgrades included Recommendation 15 on new technologies. MONEYVAL pointed to Article 9(6), which required covered entities to assess relevant risks before launch and take appropriate steps to address them.

What to check Put the AML review on the release checklist early enough for the product team to fix issues and retest.

2018 MONEYVAL report, paragraphs 28 and 71 (opens in a new tab)

MONEYVAL · third enhanced follow-up

A revised standard changed the Recommendation 15 rating

The November 2021 report assessed obligations related to virtual assets under the revised Recommendation 15 and lowered the technical rating to partially compliant.

What to check Keep the version of each requirement next to the rating. Use the current legal sources to determine what your business must do.

2021 MONEYVAL report, Recommendation 15 (opens in a new tab)
DATES AND TRIGGERS

Official milestones

See the deadline calendar
The whole journeyabout 17 days across 4 steps
  1. 01Define the product change and assess legal scope, Product owner + local counsel, about 3 days
  2. 02Assess the risks before release, AML risk analyst + product and operations leads, about 7 days
  3. 03Test referrals and control decisions, Quality assurance + onboarding operations + AML reviewer, about 5 days
  4. 04Record the decision and monitor change, Release owner + AML officer + accountable approver, about 2 days
IMPLEMENTATION ROADMAP

Step by step

Checklist, instructions and 4 templates.

View plan as a table
Project roadmap with current target dates and completion status
StepOwnerWhen to actEstimated targetDeliverablesStatus
Define the product change and assess legal scopeProduct owner + local counselWhen the change is first proposedSet a start dateAndorra AML product change intakeOpen
Assess the risks before releaseAML risk analyst + product and operations leadsBefore introducing the product or allowing use of the technologySet a start dateAndorra pre-launch AML risk assessmentOpen
Test referrals and control decisionsQuality assurance + onboarding operations + AML reviewerAfter controls are configured and before go-live approvalSet a start dateAndorra AML release test fileOpen
Record the decision and monitor changeRelease owner + AML officer + accountable approverAt release approval and when scope or applicable law changesSet a start dateAndorra AML launch decision recordOpen
0 of 4 completeOpen workspace

Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.

  1. 01

    Define the product change and assess legal scope

    Who Product owner + local counsel When When the change is first proposed

    Describe the entity, target customers, service and delivery channel. Document how it changes the way customers are identified, served or monitored. Have counsel cite the operative law and decide whether further diligence is required before launch.

    What to produce

    Andorra AML product change intakeDecision memo

    Gather first

    • Product proposal
    • Accountable entity and customer types
    • Process diagram
    • Current legal text and applicable UIFAND guidance

    How to prepare it

    1. Describe the current and proposed customer journeys. Record the entity, product owner, proposed date, channel, jurisdictions and parties performing due diligence.
    2. List changes that affect risk, including identity verification, handling of ownership data and the transaction path. Record any unresolved scope questions for legal review.
    3. Ask local compliance or counsel to sign the scope decision with the version of the law used and any further checks needed before release.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Fictional change
    The payments team proposes switching from in-person business onboarding to a remote flow. Ownership review remains assigned to the AML operations team.
    Fictional scope decision
    Counsel records the regulated legal entity and directs the product manager to complete a pre-launch risk assessment before enabling the remote flow.

    Check before handing it over

    The change, launch scope and applicable legal basis are clear enough for a different reviewer to reproduce the scope decision.

    Send the signed intake to the analyst, product owner and person accountable for release.

  2. 02

    Assess the risks before release

    Who AML risk analyst + product and operations leads When Before introducing the product or allowing use of the technology

    Walk through the customer journey and map risk scenarios to the processes that prevent, detect or escalate them. Evaluate each control’s evidence and remaining exposure. Assign treatment and decision owners.

    What to produce

    Andorra pre-launch AML risk assessmentSpreadsheet

    Gather first

    • Approved intake
    • Product and data flows
    • AML policy and control inventory
    • UIFAND sector risk material
    • Product design and vendor evidence

    How to prepare it

    1. Use one row per risk scenario. Include the affected journey step, observed or anticipated exposure, existing control, evidence reference, remaining risk and assigned owner.
    2. Record how each mitigation will work in the actual journey. Assign test cases and a due date. Where the process depends on a vendor, identify who reviews the evidence and owns performance.
    3. Confirm the remaining risks and proposed treatments with the AML officer. Make critical issues visible in the launch decision and attach the signed assessment.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Fictional risk row
    The customer declaration and company records disagree about control of a business. The proposed workflow sends the file to a named reviewer for a documented decision.
    Fictional evidence
    The case owner links the synthetic referral test, reviewer permissions and retention review to the control row before readiness sign-off.

    Check before handing it over

    Each material risk has an evidenced control or an open action with a decision owner. The assessment predates production enablement.

    Give the final assessment and unresolved actions to the test lead and release approver.

  3. 03

    Test referrals and control decisions

    Who Quality assurance + onboarding operations + AML reviewer When After controls are configured and before go-live approval

    Use synthetic cases covering incomplete, contradictory and complete records. Check whether the workflow routes each decision to an authorised reviewer and retains the activity log. Track failures to retest.

    What to produce

    Andorra AML release test fileControl test worksheet

    Gather first

    • Risk rows
    • Approved policy and process
    • Test environment and synthetic cases
    • Reviewer role and referral queue configuration

    How to prepare it

    1. For each selected risk, specify test input, expected decision, reviewer role and expected record or log. Include both standard onboarding and cases requiring human review.
    2. Run the journey with synthetic data. Save the build version, timestamp, result, reviewer assignment and decision evidence. Record each difference from the expected result.
    3. Assign owners to fix failures and retest them. Have the AML lead sign the results and state which cases the test did not cover.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Fictional expected result
    Case AD-NP-04 includes inconsistent ownership documents. The case enters manual review with both evidence references retained and no approval before an authorised decision.
    Fictional retest
    A referral initially had no assignee. Operations corrects the routing configuration and the reviewer reproduces the expected assignment with a new test record.

    Check before handing it over

    An independent reviewer can tie each tested scenario to a risk, the release version and the result, including any retests.

    Send the signed test file, open issues and supporting evidence to the release owner.

  4. 04

    Record the decision and monitor change

    Who Release owner + AML officer + accountable approver When At release approval and when scope or applicable law changes

    Review the signed assessment and test results. Record the authorised scope and unresolved issues. Assign source monitoring and set triggers for another review if a product, service provider, channel or customer group changes.

    What to produce

    Andorra AML launch decision recordDecision memo

    Gather first

    • Signed intake and assessment
    • Completed control tests and open defects
    • Rollout plan
    • Incident and source monitoring owners

    How to prepare it

    1. Record the responsible entity, release version, date, authorised scope and decision maker. Link the assessment and test evidence directly to the decision.
    2. Record the decision to proceed, restrict or defer. If there are unresolved actions, specify their scope, owner and deadline and assign follow-up before enabling additional customer journeys.
    3. Set a review date and event triggers for expanding scope, changing an identity supplier or receiving new legal guidance. Share the decision and operating limitations with the relevant teams.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Fictional launch decision
    The release owner approves the tested business onboarding flow after verifying referral assignment. Expansion to another customer group needs a new scope and risk review.
    Fictional follow-up
    Compliance logs the latest UIFAND amendment review and records the people who will reassess the workflow if the law or vendor changes.

    Check before handing it over

    The date, permitted scope and unresolved issues are clear. The approver can trace the decision to work completed before deployment.

    Send the signed decision to product, operations and compliance, with review tasks in the compliance calendar.

PRIMARY REFERENCES

Official sources

How we build these guides

Keyboard shortcuts

⌘K or /
Search everything
?
This list
g h
Home
g l
Guide library
g f
Find my path
g t
Templates
g p
Playbooks
g w
My workspace
g d
Deadline calendar
g c
Regulatory changes