Join our Newsletter — 33% off our NHI Course
Home› Guides› Customer Due Diligence vs Customer Identification Program: how…
Guide Fraud Prevention

Customer Due Diligence vs Customer Identification Program: how the US KYC layers fit together

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 14 November 2026 16 min read
On this page

Many onboarding teams treat a passed identity check as "KYC done", when under US rules that check is only the first of several layers and the one examiners find easiest to test. The Customer Identification Program (CIP) answers one question: is this person or entity who they claim to be? Customer due diligence (CDD) answers different ones: who really owns and controls the customer, what the relationship is for, how risky it is, and whether the activity still fits that picture months later. This guide is for fraud, compliance, identity and product teams building or reviewing onboarding at US banks, broker-dealers, fintechs and their partners. It sets out what each layer requires under the FinCEN rules, how they connect in a digital onboarding flow, where enhanced due diligence and ongoing monitoring fit, and the failure modes that sit in the gaps between them. Status checked 14 November 2026.

Key takeaways

  • CIP is identity, CDD is understanding. CIP under 31 CFR 1020.220 collects four data points and verifies them to form a reasonable belief in the customer's true identity; CDD builds a risk profile from the nature and purpose of the relationship and keeps it current.
  • Beneficial ownership is the bridge. For legal entity customers, 31 CFR 1010.230 requires identifying owners of 25% or more and one controlling individual, verified using at least the CIP data elements.
  • The 2026 relief changed repetition, not substance. FinCEN Order FIN-2026-R001 (13 February 2026) lets covered institutions stop re-collecting beneficial ownership at every new account, but risk-based updating and suspicious activity monitoring remain.
  • CDD updates are event-driven. The FFIEC manual says ongoing monitoring does not impose a categorical requirement to update on a fixed schedule; material changes in activity, ownership or adverse media should trigger review.
  • Passing CIP does not stop fraud. Synthetic identities, injected selfies and mule recruits can pass identity verification; the CDD layer is where purpose, expected activity and behaviour expose them.

The short answer

CIP is a narrow, prescriptive identity procedure performed at account opening. CDD is a broader, risk-based programme that starts at onboarding and runs for the life of the relationship. Enhanced due diligence (EDD) is the higher-intensity version of CDD for customers whose risk profile, product or status calls for it. In practice the three are one onboarding flow with three outputs: a verified identity record (CIP), a customer risk rating with beneficial ownership and expected activity (CDD), and for a subset, deeper evidence such as source of funds (EDD). The live CDD, EDD, PEP and sanctions screening guide covers screening and EDD in depth; this page focuses on the boundary between CIP and CDD and how to engineer it.

CIP and CDD compared

DimensionCustomer Identification ProgramCustomer due diligence
Primary US rule31 CFR 1020.220 for banks, with parallel CIP rules for broker-dealers, mutual funds, futures commission merchants and introducing brokersAML programme rule CDD element for banks, plus the beneficial ownership rule at 31 CFR 1010.230
Question answeredIs the customer who they claim to be?Who owns and controls them, why are they here, how risky are they, and does activity still fit?
Stated purposeForm a reasonable belief that the bank knows the true identity of each customer (FFIEC manual)Understand the nature and purpose of customer relationships to develop a customer risk profile, and monitor on an ongoing basis (FFIEC manual)
TimingCollect before the account is opened; verify within a reasonable time after openingAt onboarding, then for the life of the relationship
DataName, date of birth for individuals, address, identification numberPurpose, expected activity, occupation or business type, geography, products, beneficial owners; source of funds and wealth for higher risk
ApproachPrescribed minimum elements, risk-based verification proceduresRisk-based throughout; scope scales with the risk profile
OutputVerified identity record and verification evidenceCustomer risk rating, beneficial ownership record, baseline for monitoring
Typical failureWeak non-documentary verification, unresolved discrepanciesGeneric risk profile, stale data, no link between profile and monitoring
Record retentionIdentifying information five years after account closure; verification records five years after madeBeneficial ownership identification five years after closure; verification five years after made

What CIP actually requires

The bank CIP rule at 31 CFR 1020.220 requires a written, risk-based programme that forms part of the AML programme. Its minimum elements are:

  • Identifying information before opening: name; date of birth for an individual; an address (a residential or business street address for individuals, with an APO or FPO box or next of kin address as fall-backs, and a principal place of business or other physical location for entities); and an identification number. US persons provide a taxpayer identification number; non-US persons may provide a TIN, a passport number with country of issuance, an alien identification card number or similar government-issued document number.
  • Limited exceptions: an account may be opened for a customer who has applied for a TIN if the bank confirms the application and obtains the number within a reasonable period; for credit card accounts the identifying information may come from a third-party source before credit is extended.
  • Verification within a reasonable time: documentary methods (unexpired government-issued photo ID for individuals; articles of incorporation, business licence, partnership agreement or trust instrument for entities) and non-documentary methods (contacting the customer, checking consumer reporting agencies or public databases, references with other institutions, financial statements). Procedures must address accounts opened without an in-person visit, which covers most digital onboarding.
  • Lack of verification: the CIP must say when not to open an account, what the customer can do while verification is pending, when to close an account after failed attempts and when to file a suspicious activity report.
  • Records: identifying information, a description of documents relied on (type, number, place and date of issue, expiry), the methods and results of non-documentary checks, and how each substantive discrepancy was resolved.
  • Government list comparison and customer notice: check designated lists of known or suspected terrorists within a reasonable period, and give adequate notice before opening that identity information is being requested.
  • Reliance: another regulated financial institution may perform CIP if reliance is reasonable and it certifies annually under contract. Agents and service providers may perform CIP work, but the FFIEC manual is clear that the bank remains ultimately responsible.

The FFIEC manual also defines the scope that onboarding product teams often misread: a "customer" is a person opening a new account, and existing customers whose identity the bank already reasonably knows are excluded, as are applicants who are denied. One-off services with no formal relationship, such as cheque cashing or a wire transfer, are not "accounts".

What CDD adds

The FFIEC CDD overview sets out the minimum risk-based procedures: understand the nature and purpose of each relationship to build a customer risk profile; conduct ongoing monitoring to identify and report suspicious transactions; and, on a risk basis, maintain and update customer information, including beneficial ownership for legal entity customers. It expects the risk profile to consider products and services, customer types and geographies, with actual or expected activity as a key factor, and to distinguish meaningful differences within the same customer category.

Beneficial ownership

Under 31 CFR 1010.230, covered financial institutions must identify and verify the beneficial owners of legal entity customers when a new account is opened. There are two prongs: each individual who directly or indirectly owns 25% or more of the equity (up to four people), and one individual with significant responsibility to control, manage or direct the entity, such as a chief executive, chief financial officer, managing member or general partner. Verification uses risk-based procedures containing at least the CIP elements, and the institution may rely on the customer's information unless it knows facts that call its reliability into question. Some entities are excluded, and others, such as certain non-profits, are subject only to the control prong.

Two 2025 and 2026 changes are often confused. On 21 March 2025 FinCEN announced an interim final rule removing Corporate Transparency Act beneficial ownership reporting for US companies and US persons, so that only certain foreign-formed entities registered in a US state still report to FinCEN. A FinCEN final rule effective 14 August 2026 made those exemptions permanent (FinCEN BOI page, fincen.gov/boi, checked November 2026). That concerns reporting by companies; it does not remove the CDD rule's obligation on financial institutions to collect beneficial ownership from legal entity customers. Separately, FinCEN Order FIN-2026-R001 of 13 February 2026 granted exceptive relief so institutions may identify and verify beneficial owners only when a legal entity customer first opens an account, when they learn facts that reasonably call previous information into question, and as needed under risk-based ongoing CDD. Where they rely on earlier information they must obtain and record the customer's confirmation that it is up to date and accurate. Institutions may continue the old practice if they prefer.

Enhanced due diligence

For higher-risk customers, the FFIEC manual lists information banks may collect, including source of funds and wealth, occupation or business type, financial statements, principal place of business, expected domestic and international activity and transaction volumes, and major customers and suppliers. Specific EDD requirements apply to foreign correspondent accounts, payable-through accounts, private banking accounts, politically exposed persons and money services businesses.

Ongoing monitoring

The FFIEC manual describes updating as event-driven. Triggers include significant unexplained changes in activity, employment or business changes, ownership changes, suspicious activity red flags, law enforcement requests, negative media and the time since information was last gathered. Banks may still set risk-based periodic reviews. The Perpetual KYC guide covers building the trigger catalogue, and the AML programme and transaction monitoring guide covers scenarios and alert handling.

Threat models compared

ThreatWhich layer is meant to catch itWhy the other layer misses itSignals that help
Stolen identity used to open an accountCIP verification, liveness and document checksCDD sees a plausible profile because the identity is realDocument and selfie mismatch, device and phone tenure, contact data reused across applications
Synthetic identityCIP non-documentary checks, with CDD behaviour over timeThe identity can pass database checks once it has been built upThin credit files, identifiers that only recently appear, links to other applications
Recruited money mule with genuine IDCDD: purpose, expected activity, monitoringCIP is correct: the person is who they sayStated purpose does not fit inflows, rapid pass-through, many unrelated senders
Shell company hiding a controllerCDD beneficial ownership and EDDCIP verifies the entity exists, not who is behind itNominee directors, circular ownership, addresses shared with many entities
Account takeover after onboardingAuthentication and ongoing monitoringBoth identity checks were valid at openingNew device and contact changes followed by payment pattern changes

The pattern is that CIP stops impersonation and CDD stops misuse. A programme strong on one and weak on the other has a predictable hole. See the Synthetic Identity Fraud Guide and the Money Mule Detection Guide.

Architecture of a combined digital onboarding flow

  1. Notice and capture: show the CIP notice before data entry, then capture the four CIP elements plus device and session signals. For entities, capture formation documents and the beneficial ownership certification in the same session.
  2. Verify identity (CIP): run documentary verification (document authenticity, NFC chip read where available, face match with liveness) or non-documentary verification against authoritative data. Record method, result and evidence references. Treat injection-attack detection as part of verification; see Biometric Injection Attacks.
  3. Resolve discrepancies: route mismatches (date of birth differs, address not found) to a queue with documented resolution reasons, because the rule requires a record of how each substantive discrepancy was resolved.
  4. Screen: sanctions and other required list checks, with PEP and adverse media where the risk policy requires.
  5. Profile (CDD): ask purpose and expected activity in specific, checkable terms (expected monthly inflow band, main counterparties, countries), then compute the initial risk rating from customer, product, channel and geography factors.
  6. Escalate (EDD): for high ratings, collect source of funds or wealth and route to a reviewer before full functionality is enabled.
  7. Set the monitoring baseline: pass the expected activity and risk rating into transaction monitoring so that deviations from the stated purpose generate alerts.
  8. Restrict during pending verification: apply the CIP's terms for account use while verification is pending, for example no outbound payments until verification completes.

The assurance model in NIST SP 800-63A-4 (final, July 2025) is a useful engineering reference for the proofing step even though it is not a banking rule, and NIST SP 800-53 IA-12 Identity Proofing with enhancements IA-12(2) and IA-12(3) covers evidence collection and validation. The Identity Proofing and KYC Guide explains assurance levels.

Failure modes at the boundary

  • "Verified" treated as "low risk": the onboarding engine assigns the lowest risk rating to every customer who passes CIP, so CDD becomes a formality and monitoring has no meaningful baseline.
  • Purpose questions that cannot be tested: "personal use" or "business" tells monitoring nothing. Ask for ranges and counterparty types that a scenario can compare against.
  • Third-party verification without oversight: a fintech partner or identity vendor performs CIP, but the bank cannot show the methods, results or discrepancy records the rule requires, though it remains responsible.
  • Beneficial ownership collected once and never refreshed: the 2026 relief removed repetition at each account, not the duty to update on a risk basis, so a change in ownership seen in adverse media or a registry must still trigger review.
  • Pending verification with full functionality: accounts can receive and send funds before verification completes, which is exactly the window mule networks use.
  • Discrepancies overridden without reason codes: analysts clear mismatches to hit onboarding targets, leaving no record of resolution and no data on which checks are failing.

Worked scenario

A fintech offering business accounts through a sponsor bank sees rapid growth in sole-trader and small company accounts. CIP pass rates are high, document checks are clean and screening finds nothing. Within weeks, a cluster of newly formed companies receive many small inbound payments from unrelated individuals and forward the funds out the same day.

Review shows the CIP layer worked: the directors were real people with genuine documents. The gap was in CDD. Every company declared "consulting services" with no expected volume, so monitoring had no baseline; beneficial ownership was certified but not cross-checked against shared addresses; and the risk model weighted "verified identity" heavily. The fix was in CDD design: purpose questions with expected inflow bands and counterparty types; a network check for shared directors, addresses and devices across applications; a higher initial rating for newly formed entities with nominee-style structures; and limits on outbound payments until early activity matched the stated purpose. The sponsor bank also added contractual access to the fintech's verification evidence and discrepancy logs. The KYC vs KYB page covers business verification in more depth.

Decision guidance

SituationWhere to invest firstWhy
High remote onboarding volume, retail customersCIP verification quality and injection detectionImpersonation and synthetic identity scale with remote channels
Business accounts and payment productsBeneficial ownership quality and CDD purpose dataMisuse through genuine-looking entities is the main risk
Sponsor bank and fintech partner modelEvidence access, reliance terms and oversight testingThe bank stays responsible for CIP performed by others
Small institution with limited staffSimple, explicit risk rating rules and event triggersEvent-driven updates are more defensible than unmet periodic cycles
Large institution with many productsOne customer risk profile shared across productsSeparate profiles per product hide the whole relationship
Operating in the US and EUMap CIP and CDD data to both regimes in one modelThe EU Anti-Money Laundering Regulation, Regulation (EU) 2024/1624, applies from 10 July 2027 with directly applicable CDD rules

Decision checklist for an onboarding change:

  • Does the change alter any of the four CIP data elements, the verification method or the discrepancy record?
  • Does it change what purpose and expected activity data reaches monitoring?
  • Does it change who performs CIP or holds the evidence, and is reliance or oversight documented?
  • Does it change when account functions unlock relative to verification?
  • Has compliance confirmed the change against the current rule text and any FinCEN orders?

Where identity fits

CIP produces a verified identity, but the account is only as safe as the authentication bound to it afterwards. Bind the verified identity to phishing-resistant authenticators at onboarding, and treat a change of phone number, email or device followed by payment changes as both an account takeover signal and a CDD event. Re-verification for high-risk changes can reuse the CIP evidence path. See Account Takeover vs New Account Fraud and the Customer IAM (CIAM) Guide.

Detection and measurement

  • CIP discrepancy resolution rate: share of substantive discrepancies resolved with a documented reason code within the policy window.
  • Pending verification exposure: number of accounts and value of funds moved while verification is incomplete.
  • Purpose data quality: share of new relationships with testable expected activity rather than free text or "other".
  • Early-life alert rate by risk rating: monitoring alerts and SAR referrals in the first 90 days, by initial rating, to test whether the rating predicts risk.
  • Beneficial ownership refresh on trigger: share of ownership-change triggers that led to updated identification and verification within policy timeframes.
  • Third-party evidence availability: share of sampled partner-onboarded accounts where full CIP records could be produced on request.

Framework mapping

SourceReferenceRelevance
US Code of Federal Regulations31 CFR 1020.220Bank Customer Identification Program
US Code of Federal Regulations31 CFR 1010.230Beneficial ownership of legal entity customers
FinCENOrder FIN-2026-R001Exceptive relief on beneficial ownership at each new account
FFIEC BSA/AML Examination ManualCIP and CDD sectionsExaminer expectations for both layers
FATF RecommendationsRecommendation 10International CDD standard (as amended June 2026)
NIST SP 800-53 Rev 5IA-12, IA-12(2), IA-12(3), RA-3Identity proofing, evidence validation and risk assessment
NIST CSF 2.0GV.OC-03Legal and regulatory requirements understood and managed

Practitioner checklist

  • Document CIP and CDD as separate outputs of one onboarding flow, with named owners for each.
  • Record verification method, result and discrepancy resolution for every customer, including partner-onboarded ones.
  • Restrict outbound functions until CIP verification completes.
  • Replace free-text purpose fields with expected activity ranges and counterparty types that monitoring uses.
  • Prevent a passed identity check from setting the risk rating on its own.
  • Update beneficial ownership procedures to reflect FinCEN Order FIN-2026-R001, keeping customer confirmations on record.
  • Define event triggers for CDD refresh, including ownership change, adverse media and activity outside the profile.
  • Test third-party CIP performance by sampling evidence at least annually.

Standards and references

Related NHI Mgmt Group resources: Identity Proofing vs Identity Verification · Account Opening and Application Fraud Guide · Identity Verification Requirements Map · Transaction Monitoring vs Transaction Screening. This guide summarises US customer identification and due diligence rules and is not legal advice.

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 14 November 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.