Resource

KYC Document Checklist

Make sure every onboarding case collects exactly the documents you need — no more, no less.

Compliance and KYC analystsOnboarding product managersRisk leaders building intake flowsMLROs at regulated firms

What this template plugs into

Pair this template with TrueDoc's forensic checks so decisions are documented with the same evidence on every file — escalation paths, owners, and SLA in one place.

▸ Document Analysis · LiveID: 8829-XQ
Risk score: High · 94%Signals matched: 12,042

Metadata deep-dive

Inspects EXIF, software signatures, edit history, and structural fingerprints.

OwnerRisk Operations
Review SLA24h on flagged docs
Audit trailImmutable per verdict

Privacy-first by design

Originals are processed in encrypted memory and removed after analysis. Reports stay redacted by default.

No training on your data
Team & admin controls
▸ 01 · The Problem

Why a policy beats a one-off reviewer judgment call

Asking for too few documents creates regulatory risk; asking for too many crushes conversion. A clean, tiered checklist balances both.

▸ 02 · Fraud Signals

What we look for

Cross-checked across 4+ vectors
▸ Primary signal

Missing documents that mask risk signals

Detected at pixel + metadata + structural layers

Inconsistent collection across channels

Re-asking customers for the same documents

Insufficient evidence for SAR filings

What gets checked

Identity: ID, passport, residence permit
Address: utility bill, bank statement, lease
Source of funds / wealth: payroll, sale proceeds, investment statements
Business KYB: incorporation, UBOs, register extracts
▸ 03 · Workflow

From upload to verdict

01

Define risk tiers

Low / medium / high risk — each with its own document set.

02

Map regulatory requirements

List the documents required by each regulator you operate under.

03

Define acceptance rules

Recency, language, translation, and certification requirements.

04

Verify and store

Run TrueDoc forensic checks; retain per your data-protection rules.

How to adapt this template to your stack

This kyc document checklist is intentionally tool-agnostic. The structure — owner, trigger, checks, escalation, decision evidence — maps onto any case management system you already use (Zendesk, Jira, Notion, a spreadsheet, or an internal portal).

Start by mapping each step to a system of record. Where the template says "document the verdict," that should be a field in your CRM or LOS. Where it says "escalate," that should be a routed ticket with an owner and SLA.

Audit-trail expectations

Whether you are preparing for an internal review, an SOC 2 attestation, or a regulator request, the same artifacts come up: who decided, on what evidence, when, and what changed if the decision was overturned.

This kyc document checklist writes that down by default. Combined with TrueDoc's immutable verdict log, the document-level evidence and the human-level decision live in the same audit record.

Common mistakes when rolling this out

Three failure modes recur. First, no named owner — the kyc document checklist exists but nobody is responsible for keeping it current. Second, escalation paths point at a queue, not a person, so flagged cases sit. Third, the policy describes what to check but not what evidence to record, so audits later struggle to reconstruct the decision.

Each section below has an explicit owner and decision-evidence field for exactly that reason.

Run a real document. Get a forensic verdict.

No credit card. Redacted report in under a minute.

▸ FAQ

Frequently asked questions