top of page

MiCA · AIFMD II ready

AMLR 2027 ready

+370 600 26147

Vilnius · Lithuania

Pink Poppy Flowers

AML Teams · Audit · MiCA

· Backlogs · Payment Rails

MLRO · MSB Canada

· Access EU Market

MiCA · Casino · Bank & EMI

· iGaming · Immigration

Soft Costs of Hiring in AML Teams | The Real Cost to Hire, Part 7

Nov 5
7 min read

Most of what a hire costs fits on a spreadsheet. The soft costs of hiring do not, because they arrive as something else: a case the reviewer sends back, a doubt that stays in someone's head for three days, an analyst who resigns without ever having said what was wrong. In an anti-money laundering (AML) team those three things are rework, late escalation and attrition, and each has a price.

This is Part 7 of The Real Cost to Hire, the second of two parts on culture. Part 6 compared what the law makes you pay in five countries. This one is about how people work together once they are hired, and it sticks to documented cases and published research rather than claims about what any nationality is like.


Where soft costs show up

There is no "culture" line in the budget. It shows up in quality assurance (QA) returns, when analyst and reviewer read the same procedure differently. It shows up as escalation lag, when someone sees a source-of-funds story that does not add up and waits because they are new, or the decision-maker is asleep in another time zone, or the last escalation got a cool reception. And it shows up as quiet exits. Part 5 put an illustrative price of about EUR 15,000 on replacing one analyst.

None of this is caused by where someone was born. It gets worse when people bring different assumptions about hierarchy, directness and who may raise a problem, and nobody writes the local rules down.


Danske Bank Estonia: distance, language and a warning that travelled slowly

The best-documented example of what distance does to a compliance chain is Danske Bank's Estonian branch. In 2018 the bank published an investigation by the law firm Bruun & Hjejle, the Report on the Non-Resident Portfolio at Danske Bank's Estonian branch. The investigation covered approximately 15,000 customers and 9.5 million payments, with a flow the report puts at approximately EUR 200 billion.

Several of its findings are about structure and communication rather than a single bad actor. The branch had its own IT platform, and Group "did not have the same insight into the branch as other parts of Group". "Many documents at the Estonian branch, including information about customers, were written in Estonian or Russian." When an inspection report was issued in August 2007, it was written in Estonian, and the branch sent an English translation of the summary. In 2009, Group Compliance & AML was again working from an English summary the branch provided. Copenhagen was reading other people's summaries of the problem.

Then the escalation itself. On 27 December 2013 an employee of the Estonian branch filed a whistleblower report. According to the investigation, the Executive Board was informed at its meeting on 7 January 2014, "without receiving copy of the whistleblower report", and the allegations "were not properly investigated". The bank's own press release on the findings said the branch had "operated too independently from the rest of the Group with its own culture and systems".

The lesson is not about how Estonians or Danes communicate. A separate system, a different working language and a habit of passing on summaries instead of source material can filter bad news until it no longer sounds urgent. A fintech with onboarding in one country, monitoring in another and a board in a third has the same ingredients in smaller quantities.


Speaking up is a team habit, not a personality trait

Whether an analyst flags a doubt early depends heavily on the team. Google studied 180 teams (115 engineering project teams and 65 sales pods) to find out what made some more effective than others. Its re:Work summary of the research lists five dynamics in order of importance, and psychological safety comes first. The page quotes Harvard's Amy Edmondson, who defined it as "a shared belief held by members of a team that the team is safe for interpersonal risk taking".

Those were engineers and salespeople, not AML analysts, so treat it as direction rather than proof. The mechanism carries over, though. Someone who comes from a workplace where questioning a senior colleague was unusual, or where a returned file counted against you, will often wait to be asked. In a know your customer (KYC) queue, waiting means the doubtful file gets closed or sits.

EU law already assumes that problems reach the top. Recital 38 of the Anti-Money Laundering Regulation, (EU) 2024/1624, says responsibility for compliance with AML and counter-terrorist financing requirements "should rest ultimately with the management body". An escalation path that works on paper but not in practice leaves the management body carrying a risk it cannot see.


Distributed teams lose the corridor

Remote and cross-border teams are normal in compliance now. Researchers from Microsoft and the University of California, Berkeley studied the collaboration data of over 61,000 Microsoft employees when the company moved to firm-wide remote work in 2020. According to Berkeley Haas, remote work caused collaboration networks to become "less interconnected and more siloed", and workers spent about 25% less of their time collaborating with colleagues across groups. They also shifted towards email and messaging. The Microsoft Research summary suggests the move to less rich media may have made complex information harder to convey and process.

It is one company in an unusual year, so we would not build a model on the 25%. The direction matches what we see, though. In AML the useful questions often cross teams: the monitoring analyst who spots an onboarding pattern, the know your business (KYB) reviewer who asks fraud whether a director's name has come up before. Distributed teams keep the formal handoffs and lose those conversations unless someone schedules them back in.


Founders building EU teams from outside the EU

Founders from the US, the UK or Asia bring their own defaults about response times, sign-off and how directly disagreement is voiced. None of them is wrong. The cost appears when they go unstated and a team in Vilnius or Warsaw works to different ones. A founder who expects to approve every exception slows a queue built on delegated thresholds. A team that expects close direction stalls when the founder expects autonomy. And if the evidence is in Lithuanian or Polish while the decision-maker reads English, someone has to decide in advance what gets translated. As we said in Part 6, a founder's home-country instinct is not a policy.


An illustrative cost model

Illustrative, with assumptions stated. A team of four KYC analysts closes 480 reviews a month. Using the fully loaded cost from Part 1 (about EUR 56,300 a year) and roughly 1,650 productive hours, an analyst hour costs about EUR 34.

  • If 8% of files come back from QA and each takes 40 minutes to fix, that is about 26 hours a month, or roughly EUR 10,400 a year in rework.

  • At a 3% return rate, it is about 10 hours a month, or roughly EUR 3,900 a year.

  • The gap, around EUR 6,500 a year, does not count the reviewer's time or the cost of a delayed escalation.

  • If one analyst leaves because the team never felt safe raising problems, add about EUR 15,000 from the Part 5 model.

The exact number matters less than the pattern: soft costs compound, and they are cheaper to prevent than to measure.


What to put in place

  • Escalation thresholds with deadlines: what goes to the Team Lead, what goes to the money laundering reporting officer (MLRO), and within how many hours.

  • QA returns treated as calibration, not blame, with return reasons tracked and shared.

  • A working language for case files, and a rule for translating source documents a decision depends on.

  • A short weekly cross-team case review for distributed teams, plus agreed overlap hours with decision-makers in other time zones.

  • Exit interviews that ask whether people felt able to raise concerns.

In our case study on clearing 10,279 merchant alerts, recording one complete review taught the team the judgement calls a procedure leaves out. That kind of shared reference matters most when a queue is already behind, which is when AML backlogs get expensive.


Where outsourced analysts fit

An outsourced team still needs clear escalation rules, but it arrives with working habits already set. CAML's analysts have more than five years of AML experience, Team Leads are ACAMS-certified, and every critical task gets a four-eyes review. The one-week onboarding period that opens each engagement is where we agree the key performance indicator (KPI) baseline, the escalation thresholds and the working language with the client, before the volume starts.


Frequently asked questions

What are the soft costs of hiring?

Costs that never appear on a payroll or recruiter's invoice: rework, slow escalation and avoidable attrition caused by how people work together. In AML teams they show up in QA return rates, ageing alerts and exit interviews.

Does remote work hurt AML teams?

Not by itself, but published research on remote collaboration found networks became more siloed and cross-group collaboration fell. Scheduled cross-team case reviews and clear escalation channels help offset that.


The part that does not fit on a payslip

Firms rarely lose money on culture in one dramatic moment. They lose it a file at a time, and notice when a regulator or auditor adds it up. If you want experienced AML capacity with the working rules already written down, talk to CAML.

About this series. The Real Cost to Hire is an eight-part series on what AML hiring decisions leave out. Part 1 set out the fully loaded cost of an AML analyst, Part 2 what an empty AML seat costs, Part 3 how long a new AML analyst takes to become productive, Part 4 the cost of a bad AML hire, Part 5 what AML staff turnover and counter-offers cost and Part 6 how AML hiring costs differ by country. Part 8 brings it together: build, borrow or blend, with an in-house, outsourced and hybrid cost comparison.

Comments


bottom of page