AML regulations require you to verify where your customers live. Trusqo automates address verification as part of your customer due diligence process: extracting, matching, and validating documents in seconds with a full audit trail
Get startedIdentity verification gets the most attention in AML programs, but address verification is where gaps appear. Regulators expect you to confirm residency as part of customer due diligence, and they expect you to document how you did it.
Manual review of utility bills and bank statements is slow, inconsistent, and hard to defend in an audit. When your team handles documents in multiple languages, the risk of errors multiplies.
Incomplete address checks create gaps that regulators flag during AML audits
Different reviewers make different judgment calls on the same documents
International customers submit documents in scripts and formats your team may not read
Address verification is a core part of customer due diligence across every major AML regime.
The EU Anti-Money Laundering Directives (4th, 5th, 6th) and the upcoming AML Regulation require obliged entities to verify customer identity and address using reliable, independent sources as part of standard CDD.
The Bank Secrecy Act and FinCEN's Customer Identification Program (CIP) rule require financial institutions to verify customer identity, including residential address, with documentary or non-documentary methods.
The FCA requires identity verification commensurate with money laundering risk. JMLSG guidance specifies acceptable address verification documents, recency requirements, and risk-based approaches.
The Monetary Authority of Singapore requires CDD that includes residential address verification for all customers, with enhanced measures for higher-risk relationships.
Australia's AML/CTF Act requires reporting entities to verify customer identity, including address, before providing designated services. Electronic verification is accepted alongside documentary methods.
Canada's Proceeds of Crime (Money Laundering) and Terrorist Financing Act requires address verification as part of customer identification for reporting entities.
trusqo slots into your existing CDD process. Send a document, get a verified result with evidence.
Utility bill, bank statement, government letter, or insurance document. Send it to trusqo via API or the dashboard alongside the expected name and address.
trusqo reads the document in any language, extracts name, address, date, and document type, then runs fuzzy matching against the expected data. Non-Latin scripts are transliterated automatically.
A clear pass or fail result with match scores, reasoning notes, and a downloadable PDF report. Everything a regulator needs to see during an audit, generated automatically.
Every verification produces a detailed record with extracted data, match scores, decision reasoning, and timestamps. Download PDF reports for your compliance files.
The same rules applied to every document, every time. No variation between analysts, no subjective judgment calls. Exactly what regulators expect from a defensible process.
Set name and address match thresholds, document age limits, and accepted document types to match your risk appetite and regulatory requirements. Adjust as regulations change.
Documents in Arabic, Cyrillic, Chinese, Japanese, Korean, Thai, Hebrew, Devanagari, and Latin scripts are all processed natively. Automatic transliteration handles cross-script matching.
Automated checks complete in under 10 seconds. Reduce onboarding friction while strengthening your AML controls. Your team reviews edge cases, not every document.
All data processed and stored in the EU. Documents are retained only as long as needed and deleted automatically. No data leaves European infrastructure.
AML frameworks require a risk-based approach to customer verification. trusqo supports both standard CDD and enhanced due diligence scenarios:
Utility bills, bank statements, government letters, insurance documents, mortgage statements
Automatically reject documents older than 3, 6, or 12 months, configurable per request
Fuzzy matching handles abbreviations, transliterations, and formatting differences
Yes. All major AML frameworks, including the EU AMLDs, US BSA/CIP, UK FCA guidance, and equivalents in Singapore, Australia, and Canada, require customer due diligence that includes verifying the customer's residential address. The specific documentary requirements vary by jurisdiction and risk level.
Widely accepted documents include utility bills (gas, electricity, water), bank or building society statements, government-issued letters (tax notices, benefits correspondence), insurance documents, and mortgage statements. Documents must typically be issued within the last 3 months and show the customer's full name and residential address. Mobile phone bills, screenshots, and self-issued documents are generally not accepted.
Every verification produces a detailed record: what data was extracted from the document, what it was compared against, the match scores calculated, and the decision reached. These records are available via API and as downloadable PDF reports, giving you exactly the evidence trail regulators expect during an AML audit.
Yes. You can configure stricter match thresholds, shorter document age limits, and specific document type requirements on a per-request basis. This lets you apply enhanced due diligence standards to higher-risk customers while using standard settings for lower-risk onboarding.
Yes. trusqo processes documents in any language and script, including Arabic, Cyrillic, Chinese, Japanese, Korean, Thai, Hebrew, and Devanagari. Non-Latin text is automatically transliterated to Latin characters for matching against your reference data.
Create an account, get an API key, and send your first verification. No sales calls, no setup fees.