Almost nobody plans to become a deputy. It happens to them, usually because the appointed officer wanted cover for annual leave.
That is a wasted opportunity. Handled deliberately, the deputy role is the single most efficient way to acquire the four exposures a reporting appointment interview tests, set out under Deputy MLRO versus MLRO below, and that no amount of analyst work will give you.
The Deputy MLRO role at a glance
Key point: it is a delegation of authority, not a title. If no authority is delegated, it is not the role.
The table below sets out what the position is and is not. The row that matters most is the authority row, because a great many people hold the title without ever being given anything to decide. If you are offered a deputy appointment, that row is the one to negotiate before you accept, since a deputy who never decides anything gains nothing an analyst does not already have.
| Attribute | What it means in practice |
| What the role is | A named individual holding delegated authority to perform the appointed officer's duties, and to act in their absence |
| Authority delegated | Typically the reporting decision, alert escalation sign-off, and the ability to respond to the supervisor or the Financial Intelligence Unit |
| Where the accountability sits | With the appointed Compliance Officer, which is what makes the role a safe place to learn |
| Is it required? | Depends on the supervisor. Federal law does not require a deputy |
| Who it typically goes to | A senior analyst, a compliance manager, or the second most senior person in a small function |
| What it is not | A promotion in title only, a cover arrangement with no delegated authority, or an assistant to the officer |
| Why it matters | It is the only role that gives you reporting decisions with a safety net |
Is a Deputy MLRO required in the UAE?
Key point: federal law does not require one. Some supervisors do. Check yours rather than assuming.
Cabinet Resolution No. 134 of 2025, the Executive Regulations to the UAE AML law, requires, in Article 22, the appointment of a Compliance Officer at management level, with independence in decision-making and appropriate competence and experience. It says nothing about a deputy.
That means the requirement, where it exists, comes from your supervisor rather than from the federal framework. Some UAE supervisory regimes require or expect a deputy or an alternate, particularly those operating an approved person or authorised individual process. Others do not address it. The regulator comparison page sets out each supervisor's position, with the date its rulebook was checked.
There is also a practical requirement that no rulebook states. Article 22 requires the Compliance Officer to receive, examine and assess suspicious transaction data and decide whether to notify the Financial Intelligence Unit. Federal Decree-Law No. 10 of 2025, Article 18(1) requires that notification be made without delay. A firm whose only decision maker is on a flight cannot satisfy both, which is why most well-run firms appoint a deputy whether or not anyone obliges them to.
Deputy MLRO responsibilities: what you actually take on
Key point: three things, and the third one is the one people underestimate.
Delegated reporting decisions
The core of the delegation. You receive escalations, assess them, and decide whether the matter goes to the Financial Intelligence Unit or is retained. Article 22 requires the reasons to be stated where the decision is to retain, and that obligation attaches to whoever makes the call. Your first properly documented decision not to report is the single most valuable artefact in your career at this stage.
Ask what the delegation actually covers before you rely on it. Some firms delegate the whole decision. Some delegate the decision to report but reserve the decision to retain, which is an odd arrangement and worth questioning. Some have never written it down at all, which is the most common position and the least comfortable one to be in when a case lands.
Cover during the appointed officer's absence
For the period of cover you are the reporting function. Not a channel to it, the function itself. That includes responding to a supervisor request or a Financial Intelligence Unit query if one arrives while you hold the role, which is exactly when they tend to arrive.
Two practical things make that survivable. Know before the cover starts where the live cases are and what state each is in, because inheriting a queue you have never seen is how deadlines get missed. And agree how you reach the appointed officer if something genuinely cannot wait, along with what counts as genuinely.
The firm stays obliged throughout. Nothing about the officer being away reduces what the business has to do, which is exactly why the arrangement exists in the first place.
Standing capacity, the Deputy MLRO responsibility firms never write down
The third responsibility is not an activity. It is availability. A deputy exists so that the firm always has someone who can decide. That means you have to stay current on cases you are not working, on framework changes you did not make, and on the firm's risk profile as it moves. A deputy who is briefed only when the officer goes on leave is not a deputy, and will make a poor decision the first time it counts.
Deputy MLRO versus MLRO: what is genuinely different
Key point: not the task list. Accountability, relationships, and exposure to consequence.
On a day when both are in the office, the task lists look similar. The differences appear in four places, and all four are things you should deliberately seek out while you are the deputy rather than discovering them after appointment.
Accountability. The appointed officer answers for the programme. A deputy contributes to it. This is why the deputy role is a safe place to make your first hard call, and why it is not a substitute for having made one.
The board relationship. Article 22 requires periodic reports submitted directly to senior management, including their observations and decisions. That relationship belongs to the appointed officer, and a deputy who has never presented to the board arrives at their first appointment missing the skill that matters most.
The supervisor relationship. Cooperating with the supervisory authority and the Financial Intelligence Unit is one of the Compliance Officer's statutory duties under Article 22. Deputies are often kept away from it, which is a firm mistake and a gap you should close.
The resourcing conversation. The appointed officer is the person who has to say the function is under-resourced to the people who control the budget. Nobody enjoys it, and nobody is good at it the first time.
What gets you appointed Deputy MLRO
Key point: four capability gates, and firms assess all four whether or not they say so.
There is no published standard, because the position is not usually a regulated appointment in its own right. What firms actually look for is consistent, and it is narrower than most senior analysts expect.
You have made escalation decisions and been right about the reasoning, not merely about the outcome. Firms look at whether your escalations were well reasoned, including the ones that went nowhere.
You can be independent of the business. If you have a commercial relationship, a revenue target, or a close working dependency on the people whose customers you would report, you are not a candidate.
You write well enough to be relied on. The appointed officer, an auditor, and possibly a supervisor read a deputy's decisions. Sloppy reasoning is disqualifying at this level in a way it is not at analyst level.
You know the framework, not just your part of it. You should be able to describe the firm's risk assessment, policy, monitoring arrangement, and reporting process without looking any of them up.
Three things a senior analyst has never done that a Deputy MLRO must
Key point: this is the most useful section on this page. Close these three before you are offered the role.
I have watched capable senior analysts struggle in a deputy role for the same three reasons every time. None of them is about technical knowledge.
That is worth saying plainly, because people prepare for this role by revising. They read the policy again, they refresh on the framework, they take another course. All of that is useful and none of it touches the three things below, which are about position rather than knowledge.
Deciding a case with nobody to escalate to
An analyst always has somewhere to send a hard case. A deputy holding cover does not. The first time you sit with a genuinely balanced case and realise the decision stops with you is a distinct professional experience, and it is uncomfortable.
You can rehearse it. Before you escalate your next difficult case, write down what you would decide if nobody senior existed, and why. Then compare it to what the officer actually decided. Do that ten times and the first real decision is far less alarming.
Defending a decision the appointed officer made
A deputy inherits the officer's decisions. When an auditor asks why a case was closed six months ago, you have to reconstruct and defend reasoning that is not yours. This is why documentation quality matters so much at this level, and why a deputy quickly becomes the loudest advocate for it in the firm.
When the reasoning is not recoverable, say so. Defending a decision you cannot explain is worse than reporting that the record was inadequate and saying what has changed since. Auditors and supervisors have seen both, and they treat them very differently.
Saying no on behalf of the compliance function, not yourself
An analyst who declines something is expressing a view. A deputy who declines something is the compliance function declining it. The words are the same and the weight is not, and people who have not made that shift either soften until the position is meaningless or harden until the relationship breaks.
What works is separating the person from the position out loud. Saying that the function cannot support this, and that you would happily look at an alternative that would work, gives the other side somewhere to go. Saying no and stopping does not, and it makes the next conversation harder than it needed to be.
How to prepare before a Deputy MLRO appointment
Key point: four things to ask for, in this order, starting a year out.
Each is an ordinary request most compliance officers will grant because it reduces their workload.
Ask to draft a section of the enterprise-wide risk assessment. It explains why the whole framework is shaped the way it is, and most analysts have never read it, let alone written part of it.
Ask to run one control test and present the result. Article 21 of the Executive Regulations requires an independent audit function to test the effectiveness of the internal policies and controls. Being on the receiving end of that test teaches you something. Running one teaches you more.
Ask to take one item to the management meeting yourself. Not to attend. To present, and to answer the questions.
Ask to be in the room for a supervisor or auditor interaction. Even silently. The tone of those conversations is not something you can learn from a document.
What I would ask a Deputy MLRO candidate
Key point: all three questions are about what happens when the officer is unavailable.
The officer is uncontactable, and you have a case you are genuinely unsure about. Walk me through the next two hours.
You disagree with a decision the appointed officer made last month. What do you do?
A weak answer either overrides it or says nothing. A strong answer raises it directly with the officer, records the discussion, and accepts the outcome unless something material was missed; in that case, it states the escalation route. What I am testing is whether you understand that a deputy holds delegated authority rather than parallel authority.
There is a version of this answer that is too deferential, and it fails as well. A deputy who would never raise a disagreement at all is not exercising independent judgement, which is the quality the whole function rests on. The right posture is to raise it once, properly, and then either be satisfied or escalate.
What would you want in writing before you accepted this role?
Almost nobody has an answer, and the ones who do stand out immediately. A strong answer asks for the scope of the delegation in writing, the circumstances in which it activates, the escalation route when the officer is unavailable, and confirmation that no part of your other responsibilities conflicts with the reporting decision.
The reason the question works is that it reveals whether the candidate has thought about the role as an accountability or as a promotion. Someone who has only thought about the title asks about reporting lines and pay. Someone who has thought about the accountability asks what happens when it goes wrong.
Would you decide? A Deputy MLRO cover scenario
Key point: this is a labelled hypothetical. It describes no real person, customer, case or institution.
You are covering for two weeks. An analyst escalates a customer whose activity has changed shape: the overall volume is the same, but the counterparties have shifted to a set of new entities over about six weeks. The customer has an explanation, a change of supplier, and it is plausible. The analyst is uneasy but cannot say why.
Nothing here is time-critical. No sanctions issue arises. The appointed officer returns in nine days.
The tempting answer is to hold it for nine days. It is not obviously wrong, and it is what most deputies do.
The better answer treats holding as a decision requiring a reason. What would nine days give you that you do not have? If the answer is more data, say so and name what data. If the answer is only that you would rather someone else decided, that is not a reason, and the file should not record it as one.
The other thing a strong deputy does here is interrogate the analyst's unease. An experienced analyst who cannot articulate why they are uncomfortable is often responding to something real that they have not yet put into words. Asking what specifically changed, and when, frequently surfaces it. That question is one of the more useful things a reporting officer does, and the deputy role is where you learn to ask it.
Deputy MLRO readiness checklist
Key point: seven of nine means ready. Six means nearly there, and worth one more cycle. Fewer than six means keep preparing.
I have made escalation decisions and can explain the reasoning on the ones that came to nothing.
I have documented a decision not to escalate, with reasons.
I can describe my firm's risk assessment, policy, monitoring arrangement and reporting process without looking them up.
I have contributed to the enterprise-wide risk assessment.
I have run or been closely involved in a control test.
I have presented to senior management and answered questions.
I have been present for a supervisor, auditor or correspondent bank interaction.
I have no commercial responsibility or dependency that would conflict with a reporting decision.
I know what I would ask for in writing before accepting the role.
How this article was researched and verified
Federal Decree-Law No. 10 of 2025 and Cabinet Resolution No. 134 of 2025 were read directly in their published texts on 1 September 2026. Article 18(1) of the Decree-Law and Articles 21 and 22 of the Executive Regulations are described from those texts and nothing else.
No experience period is stated as a requirement for a deputy appointment, because the position is not usually a regulated appointment in its own right and no federal instrument addresses it.
No salary figure appears on this page. Pay is covered on the dedicated Dubai and UAE salary guide.
The four capability gates, the three gaps, the preparation list, the interview questions and the case are mine. They come from working with people in and around this role, and reflect professional judgement rather than regulatory requirements.
Build the framework exposure a Deputy MLRO appointment assumes
Key point: the gap between senior analyst and deputy is governance, not casework.
Frequently asked questions
