CDD Core overview
CDD Core is where the institution’s staff carry out customer due diligence: approving new customers, screening names, rating risk, reviewing customers on their cycle, restricting accounts, answering authorities and filing reports. It shares one database with KYC Core, and every decision that carries responsibility is proposed by one person and signed by another.
Who uses it: eight roles — Maker, Checker, Approver, Compliance Officer, Head of Compliance, Risk Manager, Internal Audit and System Admin. One person may hold several. See Roles and controls.
Approve from your phone, signed with Microsoft MFA
Section titled “Approve from your phone, signed with Microsoft MFA”Senior management signs high-risk customers without opening the console. The Approver is one executive or a committee of 2 to 12 members voting to half, a majority or all. Each member receives the case summary by e-mail, taps Approve, and confirms with the institution’s own Microsoft sign-in — a passkey with Face ID or Microsoft Authenticator. The vote counts only for the member’s own account, in the institution’s own tenant, signed in after the tap; every vote is on the file. Decisions that carry an amount can be laddered by amount band: one approver up to a limit, a committee above it. How it works
Your day in CDD Core
Section titled “Your day in CDD Core”- Unclaimed work lists the team’s work that nobody holds yet, oldest first: released name pairs, customer replies to a review, applications. Press Claim to take one. A banner shows how many new items wait and how long the oldest has waited.
- My work lists what you hold. Open an item to go to the screen where it is done, or hand it back.
- Work pile lists what waits for your signature, by due date, with your own figures — held, done today, overdue — and who has each item open.
Work you claim but do not act on within 4 hours goes back to the pool by itself, so two people never work the same item and nothing sits forgotten.
How the screens behave
Section titled “How the screens behave”- Menus show only what your role and your institution’s licences open. The letter after a menu name is your right on that screen: C/P propose, C/U record without a route, A sign or approve, R read.
- The ? on every screen opens the in-app manual at that screen. The manual is generated from the installed version, so it always matches the menus, the scheduled jobs and the values in force.
- Licence-specific parts appear only when the institution holds that licence. An institution with both sees both.
- Search in the top bar finds a customer or an application by reference, name or card number as you type.
Duty → where CDD Core supports it
Section titled “Duty → where CDD Core supports it”| Duty | Supported by |
|---|---|
| Identify and verify the customer | KYC Core and the identity tab |
| Accept or refuse a customer | New-customer approval — by one approver or a committee, from e-mail with Microsoft MFA |
| Screen against sanctions, PEP and AMLO lists | Name screening |
| Assess customer risk | Risk scoring and adjustment |
| Enhanced CDD (EDD) | EDD and EDD Intel |
| Ongoing due diligence | Re-KYC, re-screening, Transaction Monitoring |
| Restrict and release accounts | Restrictions and orders |
| Answer authorities and file reports on time | Letters and regulatory filings |
| Keep records | Records and retention |
| Statements to customers | Customer statements and notices |
What the system does or refuses
Section titled “What the system does or refuses”- Two signatures. You cannot sign what you proposed. The route is shown before you confirm. See Roles and controls.
- Nothing is computed on a display. Every value on a list is read from the place that decided it.
- Statutory duties cannot be switched off. The institution’s obligations are set from its business type under its contract; a duty outside them does not appear anywhere — no queue, no counter, no report type.
- Every action is logged with who, when and what, and the log cannot be edited.