Pricing
Language

18-11-2026

What the AMLA–OLAF Agreement Means for Compliance Teams

What the AMLA and OLAF working arrangement covers and how fraud and AML teams can connect ownership evidence with an unusual payment.

Share

On 21 October 2026, the EU Anti-Money Laundering Authority (AMLA) and the European Anti-Fraud Office (OLAF) signed a working arrangement. It sets out how they can share information and bring OLAF's anti-fraud expertise into selected analyses involving national financial intelligence units (FIUs). One focus is money laundering linked to fraud involving EU funds.1

For a compliance team, consider the same problem at the firm level. A fraud analyst may know that an invoice does not fit a funded project. An AML analyst may know that the recipient is connected to the customer. The two findings only become useful together if the team can show what connects them.

What AMLA and OLAF agreed to do

The signed text sets out strategic cooperation, such as exchanging risk indicators and patterns seen in cases. It also provides for operational cooperation within the agencies' mandates, including exchanging relevant case information and coordinating their respective work where needed.2

AMLA may invite OLAF to participate in a joint analysis when its involvement is relevant and falls within its mandate. The participating FIUs must consent and OLAF must agree. The text also describes a mechanism for identifying possible links early by checking information from a joint analysis against information made available by OLAF. A hit tells analysts where to look next. The published text does not establish that every case is automatically checked against all OLAF records.2

Article 94 of Regulation (EU) 2024/1620 provides the cooperation framework. A working arrangement under that article cannot itself supply the legal basis for exchanging personal data. Any such exchange needs its own legal basis and must follow the applicable safeguards.32

What the agreement means for firms

The arrangement governs cooperation between the authorities. It creates no new screening requirement, filing channel or access to OLAF or FIU systems for a bank or fintech. A firm's due diligence and reporting decisions still depend on the laws that apply to its business and the facts of the case.23

A practical question for firms is whether a reviewer can trace a payment back to the underlying customer, contract and ownership evidence. If that information sits in different teams' files, start by agreeing on the facts to record and who can access them under existing permissions. A short referral with source references can be more useful than copying the entire customer file.

A fictional case involving an EU-funded project

A payment institution handles an account for a company carrying out an EU-funded infrastructure project. The company pays a new overseas logistics supplier. The payment references the project, but the invoice gives no delivery location and the supplier is absent from the project documents the firm has obtained. The fraud analyst asks for the contract, evidence that the work was delivered and any approval for the supplier change.

Meanwhile, the AML analyst compares the supplier's registration number and directors with the customer's due diligence records. One name resembles a director connected to the customer through an intermediate holding company. A registry extract confirms the person held roles in both businesses, but the dates overlap only briefly. The available documents do not establish who ultimately owns the supplier or whether that director approved the payment.

Together, the analysts can narrow their inquiry. They record the overlapping roles, the invoice and the gap in the project documents, then assign someone to verify the supplier's ownership and check who approved the expense. A subcontract or an approved change might explain the payment. If the applicable reporting threshold is met, the firm follows its reporting procedure and records why. It should not wait to prove an underlying offence where the applicable law requires reporting on suspicion.

The value of the handoff is that the second reviewer can see exactly what was verified. A shared director is evidence of a relationship. The contract, approval record and payment evidence help determine whether that relationship matters to the transaction.

What to record when fraud and AML compare findings

  • The parties and roles. Record who paid, who received the funds, and the date and source for each ownership or management link. Use the guide to screening owners and related parties to structure that part of the review.
  • The payment context. Link the invoice, payment record and supporting documents. Explain what differs from the expected activity and which explanations were checked.
  • The decision and open questions. Record who will obtain missing evidence, who assessed escalation, and which facts supported that assessment. Keep access limited to the people who need the record for their role.

Checklynx can help teams map supplied ownership and related-party relationships and review structured screening profiles with available identifiers and source context. Contracts, grant conditions and payment approvals need their own evidence. Those are the records that let a reviewer explain why the payment warranted a closer look.

Official sources

Footnotes

  1. AMLA and OLAF announcement, 21 October 2026. ↩

  2. AMLA and OLAF Working Arrangement on Cooperation, sections 2, 4 and 8–10. ↩ ↩2 ↩3 ↩4

  3. Regulation (EU) 2024/1620, Articles 40 and 94. ↩ ↩2

Share
Blog

Footer