Posts

Vendor Questions Before the Business Case

AML Investigation in the UK and Europe: Six Questions for a Vendor Before the Business Case Is Written A business case built on a vendor's slide deck inherits the deck's gaps. These six questions are worth asking first. Can it show its sources for every statement? Ask for a live demonstration on a messy case. Explainable retrieval should let a reviewer open each source. Which problem does it address? Some tools improve detection and some improve what happens after the alert. The gap vendors leave in investigation quality is a useful lens. How does it handle rules still being written? Ask what changes when technical standards are finalised, and read what waiting on the final RTS can cost . What does it do when data is missing? It should say so. Who decides? The answer should be a named person. Will it support a pilot with a baseline? If not, the savings claim cannot be tested. Related: ten finance director questions and the question grid . For what a complete...

The Customer Context Checklist to Run Before You Close an Alert

Most AML reviews fail at the same point. The analyst has the flagged payment, the rule name and an account number, and starts pulling threads. Some of those threads lead somewhere. Some run out because the working day ran out. A short checklist at the front of the case removes the guesswork about what "enough context" means. This is a practical guide for UK and EU teams. It assumes you already have monitoring, screening and a case tool. It does not assume they talk to each other. If they do not, that is the point of the missing layer in the AML technology stack . The checklist follows the same logic as our customer-first investigation model : assemble the customer, then judge the payment. 1. Identity and onboarding Who is the customer, and what did they tell you at onboarding? Read the original note, not the current dropdown. Occupation, source of funds, expected geography and the stated purpose of the account are the baseline against which everything else is measure...

The Age of a Customer Record Is Part of Its Meaning By TechnoXander

The Age of a Customer Record Is Part of Its Meaning A customer record should not be treated as timeless simply because it remains available in a system. Information can be accurate when collected and still become misleading when circumstances change. Consider a business customer whose expected turnover was established during onboarding. Two years later, the business has entered a new market, changed its ownership structure and developed a different payment pattern. The original profile may still be factually correct as a historical record, but it may no longer be a reliable description of current activity. For an investigator, the distinction between what was known then and what is known now is essential. Without dates, provenance and review history, older information can appear more authoritative than it deserves. The FCA Financial Crime Guide describes ongoing monitoring as a risk-sensitive process that includes keeping customer information up to date. This makes record c...

The Retrieval Audit: 12 Checks for AML Teams in the UK and Europe

The Retrieval Audit: 12 Checks for AML Teams in the UK and Europe Before you buy investigation software, count what your analysts actually do. This is a one-day audit. Do it on five closed cases and one live one. Score each check yes or no. Anything you cannot answer is a finding. One login. Can an analyst see transactions, KYC, screening and prior cases without changing system? One timeline. Is there a single chronological view of the customer's activity, or four lists that must be merged by hand? Named sources. Can you list every system the case file draws from, with an owner for each? Gap warnings. When a source is missing, does the case say so, or does it look complete? Policy at the point of decision. Is the relevant rule visible inside the case, or in a PDF on a shared drive? Prior case recall. Can the analyst find similar past cases by fact pattern, not by customer name? Rationale capture. Is the reason for the decision recorded as a field, or reconstructed...

How to Measure AML Investigation Throughput in UK and European Firms by TechnoXander

How to Measure AML Investigation Throughput in UK and European Firms Most teams measure the wrong thing and then feel busy. Case count tells you how much work arrived. It does not tell you whether the team can absorb more. Throughput is a ratio, and if you are not measuring it as a ratio you are measuring activity. Here is the method I would use in a UK or European operation, in the order I would do it. 1. Fix the unit of work first A closed alert is not a closed case. A case with three linked entities is not one unit, it is three. Pick a unit and write it down. Most firms settle on "case closed to a documented rationale", because that is the only unit that maps to a regulatory outcome. 2. Count analyst hours, not headcount Headcount includes people in meetings, on leave, in training and on the investigations nobody wants to talk about. Use productive hours available for casework. If you cannot get that number, use 70 percent of contracted hours and say so in the ...

A Day in Two Workflows by TechnoXander

AML Investigation in the UK and Europe: One Analyst, Two Versions of the Same Day This is a hypothetical, written for illustration. The same analyst receives the same alert on the same Tuesday, once in a manual workflow and once in an assisted one. The point is where the time goes, which is the heart of AML investigation throughput . In short: the decision takes the same judgement either way. What changes is how long the analyst waits to start using it. Time Manual workflow Assisted workflow 09:00 Alert opens. Rule name and account number. Alert opens with customer history and earlier cases shown. 09:30 Searches three systems for earlier cases. Reviews the earlier cases and what they concluded. 11:00 Copies identifiers and builds a timeline in a spreadsheet. Checks a draft chronology against source records. 13:00 Starts to assess the activity. Already weighing whether the explanation holds. 15:00 Decides. Writes the note quickly. Decides. Writes the reasoning in full. ...

How a Reviewer Might Test Your Consistency by TechnoXander

AML Consistency Testing in the UK and Europe: A Mock Sample Imagine a reviewer pulls two closed cases. Same customer type, same pattern, two different outcomes. They ask one question: why? How well your records answer it says a great deal about your organisational memory . In short: different outcomes are fine when the facts differ. What a reviewer cannot accept is "we don't know why". Run the mock sample Pick two closed cases with similar profiles and different outcomes. For each, write one line: what was the question, and what evidence settled it? Mark whether either analyst could see the other case. Check dates: did circumstances change between the two? Note anything you could not answer from the record alone. What the results tell you If the difference is explained by facts, your decisions are consistent. If it is explained by "different analyst", you have a memory problem, and it will not show in a closure dashboard. The gap between ha...