AML Compliance Software & PEP Screening

What Is AML Compliance Software?

Diliguard’s AML Compliance Software cross-references an individual or entity name against consolidated sanctions lists, politically exposed persons registers, Interpol Red Notices, regulatory enforcement records, adverse media, and offshore leak databases in a single query. It returns a match-scored, source-attributed result rather than a single aggregated risk number.

How AML Compliance Software Works

• Sanctions and Watchlist Screening: Cross-references the target against the OFAC, UN, EU, and UK consolidated sanctions collection, which aggregates 90 designating sources covering roughly 215 countries of origin.
• PEP and Interpol Detection: Checks the target against a dedicated Politically Exposed Persons dataset covering 28 countries plus a separate EU-wide and a global collection, and against Interpol Red Notices, which are global.
• Regulatory Enforcement Screening: Cross-references the target against the OpenSanctions Crime dataset to surface regulatory fines and enforcement actions.
• Adverse Media Analysis: Searches global and local news via Google News, automatically translating risk terms into the target’s local official language so non-English coverage is not missed.
• Offshore Leaks Correlation: Cross-references the target against the ICIJ Offshore Leaks database, covering the Panama Papers, Pandora Papers, and Paradise Papers investigations.

What Diliguard Returns

A clean result returns a green “Clear: Screening Passed” banner. A match returns a red “Alert: Match Found” banner with one card per hit, containing the Entity Match Name, the Database List the match came from (for example OFAC SDN, EU Consolidated, or UN Security Council), a Match Score (for example “92% Match”), and, where available, Birth Date and Nationality. Regulatory enforcement and offshore leaks results follow the same card format, with the specific enforcement action or leaked entity detail shown instead of a sanctions designation.

Data Sources and Coverage

Sanctions screening draws on OFAC, UN, EU, and UK consolidated lists spanning approximately 215 countries of origin. PEP screening draws on a dataset covering 28 countries plus a separate EU-wide and a global collection, not the full 215-country sanctions scope. Interpol Red Notices are checked globally. Regulatory enforcement draws on the OpenSanctions Crime dataset. Adverse media draws on Google News with local-language query translation. Offshore leaks draws on ICIJ’s Panama Papers, Pandora Papers, and Paradise Papers datasets.

Frequently Asked Questions

Does Diliguard screen PEPs in every country?

No. Sanctions screening covers roughly 215 countries, but the dedicated PEP dataset covers 28 countries plus a separate EU-wide and a global collection. Interpol Red Notice checks, run alongside PEP screening, are global.

What happens when a screening result returns a false positive?

A match score below full confidence is shown alongside the record’s available details (birth date, nationality, database source) specifically so a compliance officer can rule out a name-string coincidence rather than accepting or rejecting the match blind.

Is a Diliguard AML screening report defensible in a regulatory audit?

Every match card carries a source database attribution and a match score, and every screening run is timestamped in scan history, so the basis for a clear or flagged outcome is documented at the time the check was performed.

Can this be run as a one-time check or does it need to repeat?

Both. A screening can run once at onboarding, or be added to continuous monitoring on a daily, weekly, monthly, quarterly, or yearly schedule so a previously clear entity is re-checked automatically as sanctions, PEP, and adverse media data changes.

Where This Fits

AML Compliance Software is the primary screening layer behind Legal & Compliance, Accountants & Tax Advisors, Lawyers & Notaries, and Investment Migration Operators, where PEP exposure and sanctions status are checked before a client relationship or transaction is confirmed.

Architecture and Integration

Diliguard operates on a heavy-lifting OSINT and compliance architecture designed for data density. Teams access these intelligence tools through the Diliguard portal, or integrate the logic directly into backend systems via the Developer API at api.diliguard.com, authenticated with an API key created from the portal’s Settings page. Usage is credit-metered, with success rate and latency visible on the API Metrics page, and the same capability is available to AI agents through the @sluxia/diliguard-mcp MCP server.