Customer due diligence · ComplifyADV
One case, one workflow, from the branch to audit.
ComplifyADV is the platform for customer due diligence. It gathers the information, calculates the risk, takes the case through to approval and keeps it under monitoring. It becomes active when a customer's risk changes, and leaves a trace of every step. Artificial intelligence analyses the cases, recognises the patterns of positions at high risk and flags in advance those heading the same way.
The three forms
How deep to go is decided by the risk.
Ordinary
For most customers: identification, verification of identity, purpose and nature of the relationship, monitoring over time.
Simplified
Where the risk is low, for example with public bodies or supervised intermediaries: reduced checks, but documented.
Enhanced
Where the risk is high, as with politically exposed persons or high-risk third countries: more information on the origin of funds, more frequent checks, additional documents.
What it does
Gathers, assesses, monitors, anticipates.
Gathering of information
- The data the bank already has.
- The official information on the company and the individual.
- Financial statements and sources of income.
- Beneficial ownership.
- Reputational information.
Risk assessment
- Pledge, usufruct, real estate ownership.
- Trusts, trust companies (fiduciarie) and public bodies in the shareholding structure.
- Foreign companies and opaque chains beyond three levels.
- Lists, sanctions, adverse media, politically exposed persons.
- Protesti, pregiudizievoli and proceedings.
- Sectors and territories at risk.
- Shareholders and positions changed in the last two years.
- Authority requests and seizures.
Continuous monitoring
- Every day the changes on monitored customers arrive.
- Beneficial owner, politically exposed persons, activity, chamber of commerce status, office, shareholders.
- Lists, sanctions, adverse media, adverse records.
- Chain of control and changes in assets.
- A change that matters reopens the case.
Artificial intelligence
High risk leaves a pattern. Artificial intelligence recognises it sooner.
ComplifyADV uses artificial intelligence at two points. In the analysis of customer due diligence files, to read the cases and line up what carries weight. And on the data of positions with high money laundering risk, to recognise the patterns they share and flag in advance the positions that are heading the same way.
01
Analysis of customer due diligence files
AI reads the cases, lines up the information that matters and prepares the assessment for whoever has to sign it.
02
The patterns of high risk
On positions with high money laundering risk it recognises what repeats in the data, even where the naked eye does not see it.
03
Money laundering risk prediction
Flags in advance the positions heading the same way, so that enhanced customer due diligence arrives when needed, not after.
Artificial intelligence flags and prepares; the assessment and the decision stay with the bank.
The workflow
From the branch to the head office, with the levels needed.
The workflow adapts to the way the bank works and is distributed across all the offices involved, with the hierarchical and authorisation levels of each.
01
Access
With SSO or with credentials and two-factor authentication, from any device.
02
New case
Generated by the bank's systems or uploaded by hand.
03
Dashboard
The cases to be worked on, according to each user's level.
04
Detail
All the customer due diligence files for the same counterparty, available online.
05
Interview
The branch operator gathers the information from the counterparty.
06
Document
The customer due diligence document, with a chat to the consultant for difficult cases.
07
Approval
Authorisation and closing of the case.
08
Monitoring
Once the case is closed, surveillance follows the risk level.
09
Changes
When something that matters changes, the case is reopened.
10
History
What is done outside the platform is also recorded in the case.
11
Audit
Internal departments and supervisory inspectors retrace every step.
12
Statistics
The figures of the process, for those who manage it.
From 10 July 2027 · article 28 of the AMLR
What the AMLA technical standards will require, and where ComplifyADV already does it.
Regulation (EU) 2024/1624 entrusts AMLA with the regulatory technical standards on customer due diligence (article 28, paragraph 1). The final report is dated 30 September 2026 and has been sent to the Commission for adoption; the standards apply six months after entry into force. Seven points of the text, and for each the step in Complify or ComplifyADV that carries it out.
Identifying is not verifying
The data to be gathered and the documents to verify them with.
What the RTS require. For a natural person: all forenames and surnames, place and date of birth, nationality, address of residence. For a legal person: name, legal form, registration number, registered office, beneficial owners. Identification gathers; verification compares with an identity document, a passport or an equivalent, or with an official register. Without a document, reliable and independent means for the missing data.
Where ComplifyADV does it. The new case starts with data from the bank's systems or uploaded by hand; the interview gathers what is missing; the official information on the company and the individual comes from the Register with its date, and the beneficial owner from the beneficial ownership document. The case says which datum was verified against what.
The quality of the source is part of the verification
Reliable and independent sources, assessed against the risk.
What the RTS require. The information for customer due diligence comes from reliable and independent sources, and the source is assessed: credibility and reputation, official status, how up to date it is, accuracy, possibility of falsification. For a legal person, the public registers, the constitutive documents, the financial statements; for the beneficial owner, the business registers, the registers of beneficial owners and the land registers, and the central register is not enough on its own. Conflicting sources are resolved, and the resolution is kept in writing.
Where ComplifyADV does it. Every item in the case carries the source and the date to which it refers: Italian and foreign business registers, filed financial statements, land registry, registers of protesti, sanctions lists. Where two sources diverge, the document says so and the analyst notes the choice.
Remotely, with the same safeguards
Electronic identification and qualified trust services.
What the RTS require. When the customer and the obliged entity are not present, verification goes through the electronic identification means and qualified trust services of the eIDAS regulation; alternative solutions are allowed only if the customer cannot appear in person or use those means, with safeguards on actual presence, integrity, clear images and data, interruption in case of doubt, retention with a time stamp, and they must be justified to the authority.
Where ComplifyADV does it. Access is by SSO or by credentials and two-factor authentication; the case records by what means identity was verified and keeps the outcome with the date. The means of identification is the bank's choice, and the case keeps a record of it whichever it is.
Proportionate to risk, in both directions
Do not ask again for what is already known.
What the RTS require. Verification is not a checklist that is the same for everyone: the nature, extent and intensity of the measures follow the risk. Where it is low, a natural person is identified by name, place and date of birth and nationality, and the address need not be verified; where it is high, further information on the customer, on the beneficial owner, on the ownership and control structure, on the origin of funds and of wealth. And if the obliged entity already holds useful information, including from another entity in the group, it assesses it before asking for it again.
Where ComplifyADV does it. The form of verification follows the risk profile, and the case asks the operator only for what the form requires. All the customer due diligence files for the same counterparty can be consulted online, and monitoring brings into the case what has changed, not everything from scratch.
Purpose and nature of the relationship
The expected operating profile, written at opening.
What the RTS require. At opening, the information is gathered that explains why the customer is entering into the relationship and how it will use it: the activity it carries out, the expected operations and volumes, the origin and destination of funds. It is not the same list for everyone: the extent follows the risk, and the information the obliged entity already holds counts too. That profile becomes the yardstick for ongoing monitoring: operations that depart from it must be explained, or lead to the profile being reviewed.
Where Complify and ComplifyADV do it. The company arrives with its context already written: activity and ATECO code, financial statements and size, local units, group and countries of the associated companies. The case interview gathers what only the customer knows, and monitoring flags when the subject changes from that starting point.
Who acts on behalf of the customer
Identity is not enough: the power and its scope are needed.
What the RTS require. For the person acting in the customer's name (the esecutore, in Italian law: the legal representative, a signatory, an attorney or procuratore), identity, the existence of the power of representation and its scope in relation to the requested transaction are verified. A limited delegation is not full representation. And the person who represents should not be confused with the person who owns: the nominee is a question of beneficial ownership, not of powers.
Where Complify does it. Next to each officer the file says who can sign for the company and how, alone, separately or jointly, in three colours: verified, to be read in the text of the powers, not verifiable. Powers of attorney that the Business Register does not record remain to be requested from the customer.
Exposed persons and sanctions, not just once
Before the start, and again when something changes.
What the RTS require. The status of politically exposed person is verified before the relationship is started, and then again over time, according to the risk. Sanctions screening covers the customer, the beneficial owners and those who control; it is done at the start, when the lists change, when the data of the customer or of the beneficial owner change, and periodically. For sanctions there is no graduated risk-based approach: checks are always made.
Where Complify does it. Screening against sanctions lists and politically exposed persons covers the company, the directors, the shareholders and the beneficial owners, with the matches told apart from namesakes by name and date of birth. With monitoring, the subject is re-read at the chosen frequency, and a change of shareholders or beneficial owners is flagged and, in ComplifyADV, reopens the case.
Sources. Regulation (EU) 2024/1624, articles 20, 22, 26 and 28 (Official Journal of the European Union); AMLA, final report on the regulatory technical standards under article 28, paragraph 1, 30 September 2026; Regulation (EU) No 910/2014 (eIDAS). Checked on 9 October 2026, the three new points on 20 October 2026 (AMLA press release of 1 October 2026). The technical standards are awaiting adoption by the Commission and may change.
Technology
It builds on what the bank already has.
- It integrates with SSO and the general customer register, without complex connections to the bank's other systems.
- It is built on microservices and offered in the cloud; those with a private cloud can keep the data in a local archive.
- It is designed for large volumes of cases and data.
The assessment and the decision remain with the bank: ComplifyADV prepares and documents them.
Complify Yourself!
A briefing, a meeting, a trial or a demo: tell us what you need. A person will write to you.