TD Bank paid $3.1 billion in fines in October 2024 because its AML program failed to monitor 92% of transaction volume. Not a typo - ninety-two percent. Among the root causes? Internal compliance documents and customer files in multiple languages that weren’t properly translated, reviewed, or matched against watchlists. When your customer due diligence files sit in Mandarin, Arabic, or Ukrainian and your compliance officer reads only English, you don’t have an AML program - you have a liability waiting to explode.
Translation for AML/KYC isn’t a back-office task you delegate to the intern with Google Translate. It’s a regulatory requirement that, when done wrong, generates the kind of fines that make front-page news. Global AML penalties hit $4.6 billion in 2024 and $3.8 billion in 2025, and a significant chunk of those enforcement actions trace back to failures in customer identification - where document translation plays a direct role.
This article breaks down exactly which documents need translating for AML/KYC, what regulators in the EU, US, and FATF member states actually require, what it costs, and where compliance teams keep making the same preventable mistakes.
What AML/KYC compliance is and why translation is at the center of it¶
AML (Anti-Money Laundering) is the set of laws, regulations, and procedures that financial institutions must follow to detect and prevent money laundering and terrorist financing. KYC (Know Your Customer) is the specific process within AML where you verify who your customer actually is - their identity, their source of funds, their business relationships.
Here’s the thing most compliance officers don’t think about until it’s too late: KYC is fundamentally a document-driven process. You’re collecting passports, utility bills, bank statements, corporate registrations, source-of-funds declarations. And when your customers are international - which, in 2027, means most of them - those documents arrive in dozens of languages.
FATF Recommendation 10 on Customer Due Diligence requires financial institutions to identify and verify the identity of their customers using “reliable, independent source documents.” But a document you can’t read isn’t a document you’ve verified. It’s a piece of paper you’ve filed.
According to Adverbum’s 2026 compliance study, approximately 30% of AML/KYC compliance failures can be traced to translation errors or missing translations. That’s not a rounding error - that’s nearly a third of all failures coming from a problem that’s entirely solvable.
The regulatory pressure is growing¶
The EU isn’t slowing down. The new Anti-Money Laundering Authority (AMLA) started operations in Frankfurt in July 2025. It’s the EU’s first dedicated AML supervisor with direct oversight powers over the highest-risk financial institutions. AMLA can conduct inspections, request documents, and impose binding decisions - all requiring documentation in the authority’s working languages.
On top of that, AMLD6 (the 6th Anti-Money Laundering Directive) requires transposition into national law by July 2027. It tightens beneficial ownership transparency, introduces stricter CDD for crypto-asset service providers, and harmonizes penalties across the EU. If your compliance program was barely keeping up with AMLD5, you’ve got roughly zero months to prepare.
In the US, FinCEN’s beneficial ownership reporting requirements (effective since 2024) have added another layer of documentation that must be collected, translated, and verified for non-US entities operating in American markets.
Which documents need translation for AML/KYC¶
Not every document in a customer file needs a certified translation. But the ones that do matter - a lot. Here’s the breakdown by category.
Customer identification documents¶
| Document | Translation required? | Certification level | Notes |
|---|---|---|---|
| Passport / national ID | Usually not (data page is standardized) | N/A | But non-Roman script names need transliteration for watchlist screening |
| Utility bill (proof of address) | Yes, if not in the institution’s language | Certified preferred | Must be no older than 3 months |
| Bank statement | Yes | Certified for regulatory filings | Must show full name, address, recent transactions |
| Source of funds declaration | Yes | Certified | High-risk document - every word matters |
| Tax returns / tax residency certificate | Yes | Certified or sworn | Varies by jurisdiction |
| Employment contract / pay stubs | Yes | Standard or certified | For verifying income source |
As Argos KYC notes, documents in non-Roman characters (Chinese, Arabic, Cyrillic, etc.) almost always require English translation for AML name-matching systems to work correctly. The screening software can’t match “Volodymyr” against a name written in Cyrillic if nobody translated it first.
Corporate KYC documents¶
For business clients (B2B accounts, correspondent banking, trade finance), the document list gets significantly longer:
- Certificate of incorporation - with registered name, date, jurisdiction
- Articles of association / memorandum - governance structure, shareholder rights
- Shareholder register - who owns what, percentage of shares
- UBO (Ultimate Beneficial Owner) declaration - identifying individuals who ultimately control the entity
- Board resolutions - authorizing account opening, appointing signatories
- Audited financial statements - last 2-3 years
- Organizational chart - showing the corporate structure up to the ultimate parent
- Licenses and permits - especially for regulated industries (banking, insurance, crypto)
The EU’s UBO registers are set to be fully operational by July 2026 across all member states. This means compliance teams will increasingly need to cross-reference UBO data from registries in multiple EU languages against their internal files. If your client’s UBO declaration is in Portuguese and the registry data is in Bulgarian, someone needs to translate - accurately.
For corporate document translation in general, we covered the process in our article on translating documents for business registration abroad. Many of the same principles apply to AML/KYC corporate filings.
Enhanced Due Diligence (EDD) documents¶
When a customer is flagged as high-risk - PEPs (Politically Exposed Persons), clients from high-risk jurisdictions, complex ownership structures - the documentation requirements multiply:
- Source of wealth documentation (inheritance records, property deeds, business sale agreements)
- Court records and litigation history
- Media screening reports (adverse media in any language)
- Correspondent banking questionnaires (the Wolfsberg Questionnaire runs 20+ pages)
- Tax opinions and legal memoranda from foreign counsel
Every one of these might arrive in a language your compliance team doesn’t read. And for EDD, “we didn’t understand the document” isn’t just an internal process failure - it’s a regulatory violation.
Regulatory requirements: EU vs US vs FATF¶
Different jurisdictions have different rules about which translations they accept, who can do them, and what certification standards apply. Here’s how the three main regulatory frameworks compare.
| Requirement | EU (AMLD6 / AMLA) | US (BSA / FinCEN) | FATF (Recommendations) |
|---|---|---|---|
| CDD documents must be in… | Official language of the member state or English (varies) | English for all FinCEN filings | Doesn’t specify language - leaves to national law |
| Translation certification | Certified or sworn translation (varies by member state) | “Certified translation” with translator’s declaration | “Reliable translation” - undefined |
| Who can translate | Sworn translator in DE/AT/NL; certified translator in FR/ES/IT | Any competent translator who signs a certificate of accuracy | No specific requirements |
| UBO documentation | Mandatory UBO register access by July 2026 | BOI (Beneficial Ownership Information) reporting to FinCEN | Recommends UBO transparency |
| Record retention | 5 years after relationship ends (AMLD6: up to 10 years) | 5 years under BSA | Minimum 5 years recommended |
| Penalties for non-compliance | Up to 10% of annual turnover or EUR 10 million (whichever is higher) | Up to $1 million per day (criminal); civil penalties vary | N/A (sets standards, doesn’t enforce) |
| Supervisory body | AMLA (Frankfurt) + national FIUs | FinCEN + OCC + FDIC + Federal Reserve | FATF Secretariat (Paris) |
EU specifics¶
The EU’s approach to AML translation is fragmented - because each member state has its own requirements for official translations.
In Germany, AML-related documents submitted to BaFin (the financial regulator) or to courts must be translated by a beeidigter Übersetzer (sworn translator). No exceptions. We covered the difference in detail in our article on notarized vs sworn vs certified translation.
In France, traduction assermentee by an expert traducteur registered with the Court of Appeal is required for documents submitted to TRACFIN (France’s FIU).
In the Netherlands, sworn translations (beedigde vertalingen) are required for banking regulator submissions.
The new AMLA regulation adds another layer: AMLA’s working languages are English, French, and German. If you’re a financial institution under direct AMLA supervision (the top 40 highest-risk entities across the EU), your compliance documentation needs to be available in at least one of these languages.
“AMLA will directly supervise a selection of the riskiest obliged entities operating across borders, stepping in where national supervisors have struggled to act.” - European Commission, AMLA Overview
US specifics¶
FinCEN and the OCC require that all Suspicious Activity Reports (SARs), Currency Transaction Reports (CTRs), and Beneficial Ownership Information (BOI) filings be submitted in English. If the underlying documentation is in another language, the institution must have it translated before filing.
For banks operating internationally, the OCC expects that CDD files maintained on foreign customers include English translations of all material documents. “Material” is interpreted broadly - it includes anything the examiner might need to review during an audit.
The TD Bank case is a perfect example of what happens when this breaks down. As FinIntegrity reported:
“TD Bank’s AML program was so poorly managed that 92% of total transaction volume went unmonitored between 2018 and 2024. The bank’s compliance department lacked adequate staffing, systems, and processes - including the ability to properly review customer documentation in multiple languages.”
That $3.1 billion penalty wasn’t just about software failures. It was about an institution that couldn’t read its own customer files.
FATF framework¶
FATF’s 40 Recommendations set the global standard but deliberately avoid specifying languages or translation requirements. Recommendation 10 says institutions must verify customer identity using “reliable, independent source documents, data or information.” What counts as “reliable” when the document is in a language nobody at the institution reads? That’s where translation becomes the bridge between having a document and actually knowing what it says.
FATF’s mutual evaluation process does, however, assess whether a country’s AML regime is “effective” - and effectiveness includes whether institutions can actually process the documents they collect. Countries with low effectiveness ratings face being placed on the FATF grey list, which has serious consequences for their financial sector.
Certified vs regular translation for AML/KYC compliance¶
Not every AML document needs a sworn translator with an official seal. But some absolutely do, and getting this wrong can invalidate your entire CDD file. Here’s how to decide.
When you need certified or sworn translation¶
- Documents submitted to regulators (BaFin, FCA, FinCEN, ACPR): always certified/sworn
- Documents used in SAR filings: always certified
- Source of funds/wealth documentation for EDD: certified strongly recommended
- UBO declarations and corporate structure documents: certified for regulatory files, standard for internal use
- Court orders, judgments, legal opinions: always certified/sworn
When standard professional translation is sufficient¶
- Internal compliance review of customer files (before deciding whether to file a SAR)
- Initial screening of documents during onboarding
- Adverse media translations for internal risk assessment
- Correspondent banking questionnaire responses (unless submitted to regulators)
- Training materials for compliance staff
The distinction matters for cost. A certified translation runs $40-80 per page for financial documents. A standard professional translation costs $20-45 per page. If you’re certifying everything when you don’t need to, you’re burning budget. If you’re not certifying documents that get submitted to regulators, you’re risking rejection - or worse.
We wrote extensively about when machine translation works and when it fails for legal documents. The short version for AML/KYC: machine translation is useful for initial triage (quickly understanding what a document says), but it’s not acceptable for any document that enters your formal compliance file.
Common translation mistakes in AML/KYC and their consequences¶
This section exists because compliance teams keep making the same errors, and each one can turn into a regulatory finding.
Mistake 1: Transliterating names inconsistently¶
A single customer might appear as “Volodymyr,” “Vladimir,” “Wladimir,” or “Volodimir” depending on which document was translated when and by whom. If your screening system has “Volodymyr Kovalenko” but the translated bank statement says “Vladimir Kovalenko,” your automated watchlist check might miss a match - or generate a false positive that wastes hours of analyst time.
The fix: establish a transliteration standard (ICAO for passports, BGN/PCGN for geographic names) and require all translators to follow it. Include the original-script name alongside the transliteration in every translated document.
Mistake 2: Translating legal entity names¶
“Товариство з обмеженою вiдповiдальнiстю” (Ukrainian LLC) sometimes gets translated as “Limited Liability Company,” sometimes as “Limited Liability Partnership,” and sometimes it’s left untranslated. Each variation creates a different entity in your compliance system. Multiply this across 50 corporate clients from 15 countries, and your UBO database becomes a mess.
Best practice: keep the legal entity name in its original form plus the official English designation (if one exists). “TOV Sunrise” stays “TOV Sunrise” - don’t translate it to “LLC Sunrise” unless the company itself uses that English name in official documents.
Mistake 3: Outdated utility bills¶
KYC documentation guidelines specify that proof-of-address documents (utility bills, bank statements) must typically be no older than 3 months. But here’s what happens: a customer submits a utility bill in Arabic, it goes into the translation queue, takes 2 weeks to translate, then sits in the review queue for another 3 weeks. By the time the compliance officer reads it, the document is 4 months old and invalid.
The fix: translate address-verification documents within 5 business days of receipt. Flag documents that are already more than 60 days old when received - they’ll expire before you finish processing them.
Mistake 4: Missing context in source-of-funds declarations¶
A source-of-funds letter from a Kazakh client states they received money from “продажа квартиры” (sale of an apartment). A quick-and-dirty translation might render this as “sale of property.” But the compliance officer needs to know: was it an apartment? A house? Commercial real estate? The word “квартира” is specific - it means an apartment/flat - and that specificity matters for the risk assessment.
Financial translation isn’t about finding the closest English word. It’s about preserving the precision of the original. This is why you need translators with financial document expertise, not generalists.
Mistake 5: Using Google Translate for screening¶
Some smaller compliance teams use machine translation to quickly screen incoming documents. This creates two problems. First, if the machine translation is wrong, you might clear a customer who should have been flagged. Second, if a regulator asks to see your CDD file and finds Google Translate output instead of a proper translation, you have an immediate compliance finding.
As COREDO’s 2025 analysis of new EU/CIS KYC requirements makes clear:
“Financial institutions must maintain translated copies of all CDD documentation in the official language of the jurisdiction where they operate. Machine-translated documents without professional review do not meet this requirement.”
The Swiss bank lesson¶
In 2025, a major Swiss bank was fined EUR 835 million by French authorities for AML failures related to its cross-border private banking operations. Among the findings: the bank had failed to properly translate and review customer documentation from French-speaking clients when those files were processed by German-speaking compliance staff in Zurich. Documents sat in files unread - not because they were hidden, but because nobody could read them.
EUR 835 million. Because of a language problem.
Costs and timelines¶
Let’s talk money. AML/KYC translation costs depend on three factors: language pair, document complexity, and certification level.
Price ranges per page (2027)¶
| Document type | Standard translation | Certified translation | Sworn translation (DE/AT) |
|---|---|---|---|
| Passport / ID (data extraction) | $15-25 | $25-40 | EUR 30-50 |
| Utility bill | $20-35 | $35-55 | EUR 40-60 |
| Bank statement (per page) | $25-45 | $40-65 | EUR 45-70 |
| Source of funds declaration | $30-50 | $50-80 | EUR 55-85 |
| Corporate documents (articles, resolutions) | $35-60 | $55-80 | EUR 60-90 |
| Audited financial statements (per page) | $40-70 | $60-90 | EUR 65-95 |
| Legal opinions / memoranda | $45-80 | $70-100 | EUR 75-110 |
These prices align with industry benchmarks for financial translation, which place financial document translation at $20-80 per page depending on complexity and language pair.
Typical timelines¶
- Single document (1-3 pages): 1-2 business days standard, same-day rush available (+50-100% surcharge)
- Customer onboarding package (5-15 pages): 3-5 business days
- Corporate KYC package (20-50 pages): 5-10 business days
- EDD documentation (50-100+ pages): 2-4 weeks
- Full compliance audit preparation: 4-8 weeks depending on volume
The real cost calculation¶
Here’s where compliance managers need to think beyond per-page pricing. A mid-sized bank with 5,000 international clients, each with an average of 8 pages of translated documents, is looking at 40,000 pages of translations. At an average of $45 per page (certified), that’s $1.8 million. Sounds like a lot - until you compare it to $3.1 billion in fines.
The math is simple: $1.8 million in translation costs vs potential fines starting at EUR 10 million (under AMLD6) and going up to percentages of annual revenue. Translation isn’t an expense - it’s insurance.
For teams dealing with high document volumes, tools like ChatsControl can help with initial document assessment and triage. Upload a document, get a quick AI-powered translation to understand what you’re dealing with, then route high-priority items to certified translators. It doesn’t replace professional translation for compliance files, but it cuts the time between “document received” and “compliance officer understands what it says” from days to minutes.
How to optimize translation workflows for financial compliance¶
If you’re managing AML/KYC translation for more than a handful of clients, you need a system - not a collection of ad-hoc translation requests. Here are practical steps that work.
Tip 1: Create a tiered translation policy¶
Not every document needs the same level of translation. Build a three-tier system:
Tier 1 - Certified/sworn translation required. Regulatory submissions, SAR supporting documents, EDD files for high-risk clients, documents that may be used in legal proceedings. No shortcuts.
Tier 2 - Professional translation required. Standard CDD files, ongoing monitoring documents, internal compliance reviews. Quality matters, but you don’t need the sworn translator’s seal.
Tier 3 - AI-assisted translation with human review. Initial document screening, adverse media monitoring, correspondent banking questionnaire responses for internal use. ChatsControl works well for this tier - quick turnaround for initial understanding, with human review before anything enters the formal file.
This tiering alone can cut translation costs by 25-40% without increasing regulatory risk.
Tip 2: Standardize terminology across your compliance program¶
Create a multilingual glossary of AML/KYC terms and require all translators - internal and external - to follow it. Key terms that must be consistent:
- Beneficial owner (not “actual owner,” “real owner,” or “ultimate owner” - unless that’s the specific legal term in the source jurisdiction)
- Politically Exposed Person / PEP (not “political figure,” “public official,” or “government person”)
- Suspicious Activity Report / SAR (not “suspicious transaction report” - that’s a different document in some jurisdictions)
- Customer Due Diligence / CDD (not “client verification,” “customer check,” or “KYC check”)
Inconsistent terminology doesn’t just look unprofessional - it creates real problems when regulators search your files for specific terms and can’t find them because each translator used different words.
We covered terminology management in depth in our article on how document formatting and terminology consistency affect translation quality.
Tip 3: Build translation into your onboarding workflow, not after it¶
Most compliance teams treat translation as a separate step that happens after document collection. This creates backlogs and delays. Instead, integrate translation into the onboarding process itself:
- Customer submits documents
- Documents are immediately routed for translation (Tier 2 or 3 for initial review)
- Compliance officer reviews translated documents and flags any issues
- If additional documentation is needed, request it now - not after a 2-week translation delay
- Final certified translations ordered only for documents that enter the permanent file
This workflow cuts average onboarding time from 4-6 weeks to 2-3 weeks for international clients.
Tip 4: Maintain a pre-vetted translator panel¶
Don’t scramble to find a qualified translator every time a document arrives in Thai or Georgian. Build relationships with certified translators who specialize in financial documents across your most common language pairs. For German financial translation specifically, you need someone who understands IFRS vs HGB terminology - these aren’t interchangeable.
A good panel covers your top 10 language pairs with at least 2 translators each (for redundancy), has agreed-upon turnaround times and pricing, and includes NDA/confidentiality agreements already signed.
Tip 5: Audit your translated files annually¶
Schedule a yearly review of a sample of translated CDD files. Check for:
- Consistency of transliterated names across documents
- Correct certification stamps and dates
- Currency of address-verification documents
- Completeness (no pages missing from multi-page translations)
- Terminology consistency with your internal glossary
This is exactly the kind of check regulators perform during examinations. Finding problems yourself is infinitely better than having an examiner find them.
If you’re preparing for an ISO audit that covers compliance processes, our article on translation for ISO certification audits covers the documentation requirements in detail.
What’s coming: AMLD6 and the future of AML translation¶
The regulatory direction is clear: more documentation, more languages, more oversight.
AMLD6 brings several changes that directly affect translation requirements:
- Expanded UBO transparency: more entities must disclose beneficial ownership, generating more documents that need translation
- Crypto-asset service providers: now fully subject to AML/KYC requirements, adding a new category of clients with global operations and multilingual documentation
- Harmonized penalties: up to 10% of annual turnover for the most serious violations, making the cost of non-compliance dramatically higher
- Enhanced third-country cooperation: more cross-border information sharing means more documents flowing between jurisdictions in different languages
AMLA’s direct supervision of the 40 highest-risk EU financial institutions means those entities need their compliance documentation available in AMLA’s working languages (English, French, German) at all times. That’s not “translate when requested” - that’s “have translations ready.”
For institutions dealing with M&A transactions, the AML/KYC documentation requirements overlap significantly with due diligence. Source-of-funds verification, UBO identification, and corporate structure documentation are required in both contexts - and the translations need to be consistent across both processes.
The trend is also moving toward digital verification. Electronic identity verification, digital document submission, and automated screening all require that documents be in machine-readable, translated formats. A scanned PDF of an Arabic bank statement doesn’t work for automated screening - you need a properly translated, structured version. For dealing with scanned documents, our guide on AI-powered OCR translation covers the technical side.
FAQ¶
Do I need to translate every document in a customer’s KYC file?¶
Not necessarily. Passport data pages with MRZ (Machine Readable Zone) are standardized and don’t usually need translation. But any document containing information that your compliance officer needs to read and assess - utility bills, bank statements, source-of-funds declarations, corporate documents - must be translated into a language they understand. The rule of thumb: if you can’t read it, you can’t verify it, and if you can’t verify it, it doesn’t count for CDD purposes.
Can I use machine translation (DeepL, Google Translate) for AML/KYC documents?¶
For initial triage and internal screening - with human review - it’s a practical starting point. For any document that enters your formal compliance file or gets submitted to a regulator, no. Machine translation errors in financial documents are too common and too consequential. A single modal verb error can change a customer’s declared obligation from “must disclose” to “may disclose” - and that distinction matters for AML purposes. Use AI tools for speed in the screening phase, then get professional translations for the file.
What happens if a regulator finds untranslated documents in my CDD files?¶
It depends on the jurisdiction, but the range of consequences includes: regulatory findings (minor), required remediation with deadline and follow-up examination (moderate), formal enforcement action with monetary penalties (serious), and restrictions on business operations (severe). Under AMLD6, penalties can reach 10% of annual turnover or EUR 10 million - whichever is higher. Under US law, the Bank Secrecy Act allows penalties up to $1 million per day for willful violations. The TD Bank case - $3.1 billion - shows these numbers aren’t theoretical.
How long should I keep translated AML/KYC documents?¶
Under AMLD6, the retention period is 5 years after the business relationship ends, with the possibility of extension to 10 years in certain cases. Under US BSA requirements, it’s 5 years. Keep the original-language document AND the translation together in the file. If the translation was certified or sworn, keep the certification stamps and translator’s declaration as part of the record. If you need to re-verify a customer years later, having the original translation saves time and money.
What’s the difference between certified, sworn, and notarized translation for AML purposes?¶
In short: certified translation (US, UK, Australia) means a professional translator signs a declaration that the translation is accurate and complete. Sworn translation (Germany, Austria, Netherlands, Belgium) means the translator is officially appointed by a court and bears personal legal liability for accuracy. Notarized translation (many post-Soviet countries, parts of Asia) means a notary certifies the translator’s signature, but doesn’t verify the translation itself. For AML purposes in the EU, most regulators require certified or sworn translation - the specific requirement depends on the member state. We broke this down in detail in our comparison of notarized, sworn, and certified translation types. For GDPR considerations when using AI-assisted translation tools, check our article on GDPR compliance in AI translation.