Client Verification Checklist
What the Client Verification Checklist Is
Why a Formal Checklist Matters
A formal Client Verification Checklist standardizes evidence collection, reduces onboarding time, and provides a clear audit trail for internal and regulatory review. It helps limit legal and financial risk by ensuring key items are captured consistently.
Which Teams Commonly Use This Checklist
Use the checklist as a shared source of truth to avoid duplicated requests and to speed approvals across departments.
- Compliance and AML units reviewing identity documents and KYC requirements.
- Sales and account teams confirming contract authority and billing details.
- Legal and contracting teams validating signatory authority and required clauses.
Typical Signatories and Responsible Roles
Compliance Officer
A compliance officer or analyst typically reviews identity documents, runs required checks (KBA or sanctions lists), and records results. They ensure the checklist meets regulatory obligations and escalate discrepancies for legal review.
Account Manager
An account manager or client onboarding specialist gathers client-supplied documents, confirms billing and contact details, and completes administrative fields. They coordinate notarization, witness requirements, or additional approvals when needed.
Step-by-Step: Completing the Checklist
-
01Gather Documents: Request ID, tax form, and proof of address
-
02Confirm Authority: Verify signatory title and corporate resolution
-
03Run Checks: Perform KBA, sanctions, or AML screening
-
04Record Results: Save evidence and note verification status
Configuring an Online Verification Workflow
| Field | Configuration |
|---|---|
| Authentication | Email link or SMS code |
| Required Attachments | ID and proof of address |
| Routing Rules | Auto-route to compliance if flagged |
| Retention Policy | Auto-archive signed copies |
Where to Send or Store Completed Checklists
-
Client File: Attach signed checklist to client record
-
Compliance Folder: Store evidence for audit retention
-
Contract Repository: Link to executed agreements
-
Billing System: Record billing and tax identifiers
Digital Signing and Technical Needs
Choose an integration that supports your record retention, HIPAA or industry compliance, and connects to CRM or document management systems for automated filing.
- Authentication Options: Email, SMS, KBA
- Audit Trail: Timestamped event log
- File Formats: PDF, DOCX, XLSX
Key Timelines and Retention Deadlines
Provide W-9 When Requested:
No set filing deadline; supply on payer request
I-9 Retention:
Retain 3 years after hire or 1 year after termination (8 CFR §274a.2)
HIPAA Records:
Retain 6 years from creation or last effective date (45 CFR §164.530(j))
Tax Return Support:
Keep records at least 3 years (IRC §6501(a))
RON Recording:
Preserve audio-video sessions per state RON rules
Common Preparation Mistakes to Avoid
- Accepting an image of an expired ID without a secondary proof leads to failed identity matches and onboarding delays.
- Collecting inconsistent names (DBA vs legal name) can trigger tax reporting errors and backup withholding.
- Failing to capture signer capacity (title) increases risk that a contract will be unenforceable against the entity.
- Skipping written verification notes prevents auditors from reconstructing why a decision was made during review.
Consequences of Incomplete or Incorrect Checklists
Real-World Examples of Checklist Use
Optica Ventures
A venture firm standardized intake to reduce client follow-ups and improve compliance
- Used KBA and ID capture in onboarding
- The result was faster fund subscription processing and an improved audit record for investor files.
Fertility Centers of Illinois
A healthcare provider added HIPAA-specific fields and BAA tracking to its checklist
- Required signed authorizations and identity proof
- This ensured consistent patient consent capture and met internal retention policies.
Checklist vs KYC Form: Key Differences
| Criteria | Checklist | KYC Form |
|---|---|---|
| Primary Focus | broad intake | identity and aml |
| Use Case | onboarding package | regulatory screening |
| Supporting Docs | multiple documents | id and proof of address |
| Retention | varies by doc | 5–7 years typical |
eSignature Vendor Comparison for Checklist Workflows
| signNow | DocuSign | Adobe Sign | PandaDoc | HelloSign | |
|---|---|---|---|---|---|
| Starting Price | $8/user/mo | $15/user/mo | $14/user/mo | $19/user/mo | $15/user/mo |
| Free Trial | 7-day free trial | Varies by vendor | Varies by vendor | Varies by vendor | Varies by vendor |
| Bulk Send | Yes | Yes | Yes | Yes | Varies |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Varies | Varies | Varies | Varies |
Practical Tips for Accurate and Efficient Completion
Key Milestones in the Verification Process
Request Sent
Client receives checklist and attachment instructions
Documentation Returned
Client submits ID and tax documents
Verification Complete
Compliance clears or escalates exceptions
Archive
Signed checklist stored per retention policy
Frequently Asked Questions about Client Verification Checklists
-
What if a client lacks required ID?
If a client cannot provide primary ID, request secondary documents (utility bill, bank statement) and follow your risk-based exception process. Document the steps taken and obtain manager approval for any exception.
-
Can the checklist be e-signed?
Yes; electronic signatures that meet ESIGN and UETA requirements are generally valid. For consumer-facing financial or healthcare records, provide the required ESIGN consumer disclosure and obtain consent to electronic records.
-
Are notarization or witnesses ever required?
Certain executed documents may require notarization or witnesses depending on state law and document type. For deeds or some POAs, follow state-specific rules and use RON where allowed and accepted.
-
How long should we retain the records?
Follow retention rules applicable to the document: IRS records 3 years (IRC §6501(a)), HIPAA records 6 years (45 CFR §164.530(j)), and longer retention for real estate or tax-sensitive files where required.
-
What authentication strength is recommended?
Use layered authentication: email or SMS for low risk, knowledge-based or government ID verification for higher risk, and multifactor or platform-backed identity proofing for regulated workflows.
-
How do we correct an error after signing?
If a signed checklist contains an error, create a corrective amendment or re-execute the checklist. Record the reason, reference the original document, and retain both versions per retention policy.