Skip to content
FonteumPublic-records evidence
Fonteum Data GlossaryRegulatory

What is customer due diligence (CDD)?

Customer due diligence (CDD) is the process financial institutions use to understand a customer's identity, beneficial ownership, and the purpose of the relationship, and to monitor activity on an ongoing basis. It is an evidence workflow rather than a one-time search: strong programs document sources, dates, limitations, and the reasoning used to clear or escalate a record.

Source file
Not reported
Published
Not reported
Retrieved
Not reported
Snapshot
Not retained for this reference page
Data as of
Not reported

Full name: Third-Party and KYC Due Diligence

Short explanation

In a third-party or KYC context, due diligence means collecting and assessing enough information to understand the counterparty, the purpose of the relationship, ownership and control, sanctions or exclusion exposure, and changes over time. It is an evidence workflow, not a one-time search. Strong programs preserve sources, dates, limitations, and the reasoning used to clear or escalate a record.

Related use case: Exclusion & sanctions screening

Last updated: 2026-07-11Reviewed by: Fonteum data standards deskSource-provenance editorial review. Definitions checked against primary federal sources.

How it’s used

  • KYC programs: financial institutions use customer due diligence to understand customer identity, beneficial ownership, relationship purpose, and monitoring needs.
  • Vendor screening: procurement and compliance teams check sanctions, exclusions, corporate registries, and ownership records before and during a relationship.
  • Fonteum supports due diligence by preserving source, date, limitation, and identity-resolution context for each public-record fact it displays.

Frequently asked questions

What does due diligence mean in KYC?
It means collecting and assessing information about a customer, ownership, relationship purpose, and ongoing activity so a firm can understand and monitor the relationship.
What is third-party due diligence?
Third-party due diligence is the process of checking vendors, contractors, suppliers, or partners against public records and internal requirements before and during a business relationship.
Is due diligence a one-time lookup?
No. It usually includes onboarding checks, documented decisions, periodic refreshes, and event-driven follow-up when a source record changes.

Explore in Fonteum

How Fonteum sources, resolves, and publishes data tied to this term.

What’s on file, by the numbers

Platform snapshot · 2026-08-12

13.4Mproviders & companiesProviders, organizations, owners, and facilities on file
26.2Msource-linked factsSource-linked field facts in the dated platform snapshot
90sources with dataDistinct snapshot source IDs with at least one positive record count
73fresh sourcesDistinct source IDs whose latest positive-data snapshot falls within the preceding 45 days
111sources integratedActive registry rows; integration does not establish a load
13state Medicaid jurisdictionsDistinct states represented in the state-exclusions serving table

Integrated, with-data, and fresh-observation counts are separate. No platform-wide source-completeness count is published. Completeness is source-specific and must be evaluated against the named source's expected scope. State coverage is a separate jurisdiction measure.

Source authority is record-specific

Use the issuer named on the record.

Fonteum spans federal, state, and global public publishers. A source page or returned record identifies its issuer and dataset where that metadata is available. A platform registry count does not assign every page to one authority or establish loaded, fresh, or complete coverage.

Browse source records and their stated limitations →

Reproducible by design

Inspect the evidence each published figure actually supplies.

Source and date

Research pages expose the named public file and observation date where those fields are available. Source-file SHA-256 coverage is separate; facts do not currently link deterministically to signatures.

Available derivation

Studies with a retained release and committed derivation link the SQL or method used. Other studies state the evidence and reproduction limits they actually have.

Daily observations

Dated table row-count observations can detect local drift. They do not imply that an upstream publisher released or Fonteum ingested new data that day.

Named medical review

Reviewed by Jennifer Montecillo, MD, medical reviewer. Non-practicing medical reviewer.

Read the full provenance and attestation methodology →

Request access