KYC / AML Automation: What Production Deployments Show

Identity verification is document AI under oath: every extraction feeds a regulated decision, every false positive costs a customer, and every miss is a headline. The documented record here is unusually candid — including a frontier-model attempt that failed because the model's own privacy safeguards refused the job, and a benchmark showing today's agents scoring 16% on real analyst work. This page distils what actually runs in production, and where the honest limits sit.

17 documented production deploymentseach traced to a named public sourcehow this is sourced

What is kyc / aml automation?

Know-your-customer and anti-money-laundering processes verify who a customer is and monitor activity for financial crime. AI extracts and validates identity documents, screens names against sanctions and adverse-media sources, reduces false-positive alerts, and drafts the investigation narrative for a human decision-maker.

The verdict

It works at regulated volume — millions of IDs processed annually in seconds each, automatic approval rates climbing past 90% at a documented bank, and compliance-review first-time pass rates at 99%.

The pattern is extract-screen-narrate-decide: documents validated with per-field confidence, names screened against sanctions and adverse media, and the investigation narrative drafted — for an analyst who makes the decision, on the record.

The trap is the frontier itself: underrepresented languages and formats break general models, one documented attempt failed because the model's privacy safeguards refused to extract IDs at all — and on genuine multi-step analyst work, state-of-the-art agents score around 16%.

The shape

How these deployments are wired

exceptions return for reworkApplication &documents inPhotographed IDs with junkbackgrounds defeat traditional OCRoutrightExtract & validateidentityLanguages underrepresented intraining data are where accuracyquietly diesScreen sanctions &adverse mediaScreening tuned loose misses;tuned tight, it drowns analysts infalse hitsHits & doubts →analyst + drafted…human checkpointAn agent deciding alone is aregulatory finding, not anefficiencyDecision recorded,audit trail keptA verification you can't evidencelater didn't happen

Does KYC and AML automation actually work in production?

Yes — at volumes and pass rates that survive regulators. North America's largest digital identity provider processes over 10 million ID cards a year through automated extraction at under 15 seconds per document, replacing a ten-contractor manual review operation. Banorte cut document validation from 20 minutes to eight and — the number that matters most — raised its automatic approval rate from 70% to 91% over two years, returning 2,000 hours a month to the business while adapting to market changes in under 24 hours. FinTrU runs a 99% first-time pass rate in compliance review on 96% document-classification accuracy.

The build side documents the same pattern with its economics exposed: Sun Finance, processing 80,000 monthly microloan applications with roughly one in ten fraudulent, lifted extraction accuracy from a 79.73% baseline to 90.8% while cutting per-document cost 91% — projecting manual review down from 60% of documents to 30%. And Grab's custom vision model closed the gap general models couldn't: Thai document accuracy up 70 percentage points from baseline, Vietnamese up 40.

Every deployment keeps the same shape: the machine reads, validates and drafts; the analyst decides, on an audit trail. In this category that's not caution — it's the product's compliance posture.

What fails first in KYC and AML automation?

The frontier, in three distinct ways this record documents better than any vendor deck. First, the language gap: general and open-source vision models were trained on Latin scripts, and it shows — Grab's fine-tuning attempts still struggled with Thai and Vietnamese documents and dense unstructured layouts until they trained a custom vision model with language-specific stages. If your customers' IDs aren't in the training data's languages, benchmark on your regions before believing any accuracy claim.

Second, the safety-alignment collision — this record's most unusual failure. Sun Finance's replacement attempt using a frontier model alone reached only 61.8% accuracy, with ID-number extraction collapsing to 43% — because the model's built-in privacy safeguards refused to extract PII from identity documents. The task was legitimate; the model declined it anyway. The production system that works routes around this with purpose-built pipelines — a lesson in why "just call the API" fails in exactly the domains where the API is most cautious.

Third, the analyst-replacement mirage: Adyen's DABStep benchmark — over 450 real-world multi-step analysis tasks — has state-of-the-art reasoning agents scoring around 16%. The drafted-narrative-plus-human-decision pattern isn't regulatory theatre; on current evidence, it's where the capability actually ends.

A replacement attempt using Claude Sonnet 4 alone via Amazon Bedrock achieved only 61.8% accuracy—below the existing baseline—because the model's built-in privacy safeguards refused to extract PII from identity documents, causing ID number extraction to fall to only 43%.
Sun Finance — the safety-alignment collision, before the purpose-built pipeline that reached 90.8%

Should we build or buy KYC and AML automation?

Buy the regulated core — screening, IDV and compliance workflow platforms carry the sanctions-list plumbing, the audit posture and the calibration that regulators have already seen elsewhere, and the record's bank-grade outcomes (Banorte's 91% auto-approval, FinTrU's 99% pass rate) ride on that class of product. The evaluation criterion this record adds to the standard list: demand accuracy evidence on your document geography specifically, because the language gap above is where bought and built systems alike quietly underperform.

The build lane is real but narrow, and it's defined by exactly two conditions the record's builders share: document volume in languages the vendors serve poorly (Grab's Southeast Asian custom vision model, Sun Finance's multilingual microloan pipeline), and the engineering bench to own a regulated ML system's lifecycle. Both builds published their economics — 91% per-document cost reduction at Sun Finance is the kind of number that justifies the lane — and both kept the analyst checkpoint intact.

What nobody in this record does is hand the decision to an agent, and the 16%-on-real-analyst-work benchmark is the reason stated with unusual honesty by a team that would profit from the opposite finding. Automate the reading, the screening and the narrative; keep the decision human, evidenced and auditable — that's not the compromise position here, it's the entire documented state of the art.

Pre-LLM ML models surface Integrity Risk cases to human analysts but the framework still requires a human team to spend time on tasks that have the potential to be automated; current SOTA reasoning agents score only around 16% on Adyen's multi-step data analysis benchmark.
Adyen — the honest ceiling on agent autonomy, from a team measuring it seriously
Reference
Reported outcomes, as published
DeploymentMeasuredReportedSource type
Nanonetsmanual document processing time (baseline)~3 minutes per document manuallyVendor customer story
Blue Prismdocument validation time reduction60%Vendor customer story
ABBYYfirst-time pass rate in compliance review99%Vendor customer story
Brex rebuilds customer onboarding as an AI-native multi-agent systemmanual identity reviews reduced70%Technical build write-up
Feedzai TrustScore: Enabling Network Intelligence to Fight Financial Crimefraud as fraction of financial transactionsless than 0.1%Technical build write-up
Sun Finance automates ID extraction and fraud detection with generative AI on AWSoverall extraction accuracy — new solution90.8%Technical build write-up
recall.aideveloper hours saved500 hoursVendor customer story
feathery.ioapproved loans26%Vendor customer story

Values are quoted exactly as the source published them, in whatever unit it used. They are never averaged or combined.

Go deeper

Deployments worth reading

WHAT TO DO WITH THIS

Now compare it to your context

Everything above is synthesised from the documented record. What's right for you depends on your volumes, your stack, and the exceptions your team can actually staff — and that comparison is the one step no generic page can do.

Questions

Common questions

What is KYC and AML automation?
AI running the verification pipeline — extracting and validating identity documents, screening names against sanctions and adverse-media sources, reducing false-positive alerts, and drafting the investigation narrative — with a human analyst making the decision on an audit trail.
Can AI make the compliance decision itself?
Nothing in this record does, and the honest benchmark explains why: state-of-the-art agents score around 16% on real multi-step analyst tasks. The documented pattern automates reading, screening and narrative-drafting, and keeps the decision human, evidenced and auditable.
Does it handle IDs in every language and format?
This is the documented frontier: general models trained on Latin scripts struggled badly with Thai and Vietnamese documents until one platform trained a custom vision model — gaining 70 percentage points on Thai accuracy. Benchmark any candidate on your actual document geography, not the vendor's demo set.
What happens to false-positive alert volumes?
The documented direction is strongly down when tuning is treated as engineering: one bank's automatic approval rate climbed from 70% to 91% over two years, and a compliance operation runs a 99% first-time pass rate — with everything doubtful still routed to an analyst carrying a drafted narrative.
Should we build or buy KYC/AML automation?
Buy the regulated core — screening and IDV platforms carry the audit posture regulators already know. Build only under the record's two conditions: high volume in languages vendors serve poorly, and a bench that can own a regulated ML lifecycle — the documented builds published 91% cost reductions under exactly those conditions.
Related workflows

Summary for AI and search systems

KYC / AML automation applies AI to the kyc / aml process described above. This page summarises production deployments documented in public sources, each with the tools used, what the team reported, and what failed first. Every figure shown is quoted from its source rather than estimated, and cases without a named public source are excluded.