TL;DR: Alternate verification routes now need one governed model, with eID, qualified trust services, remote checks, and missing-attribute handling all tied to the same CDD decision, according to IDnow. Onboarding teams must preserve justification and evidence so exceptions and completeness can survive audit and later screening.
Editorial analysis by NHI Mgmt Group, based on content published by IDnow: “AMLR CDD RTS: what the final draft changes for your onboarding”.
Key questions
Q: Why do exception-based verification flows create compliance risk?
A: Exception-based flows create risk when eligibility is informal, evidence is incomplete, or supervisors cannot reconstruct the decision later.
Q: What should teams do when identity attributes are missing from a compliant verification flow?
A: Do not treat missing attributes as a manual afterthought.
Q: How should firms govern customer onboarding when multiple identity verification routes are allowed?
A: Treat the routes as one governance model, not three separate processes.
Practitioner guidance
- Map every onboarding route to one approved verification policy Document which journeys use identity documents, eID, qualified trust services, or the narrow remote document exception, and make the approval criteria explicit.
- Build case-level justification for remote document use Capture the reason the customer could not reasonably use the standard route and retain the supervisory evidence needed to defend each exception.
- Compare collected attributes to the required minimum set Check names, birth data, nationality, residence, and tax identification coverage, then define a governed process for filling any missing attribute.
Bottom line: The article shows that regulated onboarding is moving from channel-based verification to a single governed decision model.
Glossary terms: Customer Due Diligence, Electronic Identification, Qualified Trust Service Provider, Alternative Verification Measure
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Channel-specific onboarding is becoming a governance liability. The RTS removes the old assumption that digital verification and branch verification should be managed as separate control families. Once eID, trust services, and document alternatives are all part of the same lawful framework, the real issue is whether the organisation can defend its decision logic consistently. For identity teams, that means policy fragmentation becomes a compliance risk, not just an operational inconvenience. The practitioner conclusion is simple: standardise the control objective before standardising the channel.
A question worth separating out:
Q: When should organisations prioritise a single onboarding policy over channel-specific workflows?
A: Prioritise a single policy when the same legal standard applies across channels and the main difference is how evidence is captured, not what must be proved. That is the right model when branch, remote, and assisted journeys all need the same identity assurance outcome. Separate workflows should exist only where the regulation genuinely creates a different control requirement.
👉 Read our full editorial: AMLR identity verification rules tighten customer onboarding choices