Due-diligence integrations
Select the provider, retain its agreement, manage credentials and set KYC validity and enforcement. Customer KYC work and screening evidence remain in the work tree.
Current policy: manual
Policy prerequisites recorded. A live provider check has not been made here.
- Enforcement
- Warn
- Enforcement starts
- No date recorded
- Review validity
- High risk: 6 months · Medium risk: 12 months · Low risk: 24 months
- Processing agreement
- Not recorded
- Agreement signed
- Not recorded
- Credential
- Not recorded
Edit due-diligence policy
Edit due-diligence and KYC policy
Changes apply firm-wide. Provider keys below are names or opaque references—not API secrets. Saving does not run a job or post to ERPNext.
Provider capabilities
manual · Connected
Your officers record screening themselves; every verdict carries their name and the date.
Supports: screening
Outside this provider: identity; kyb
complyadvantage · Ready
Sanctions, PEP and adverse-media screening only — no registry, no ID capture.
Supports: screening
Requirements: your complyadvantage API credentials; a signed data-processing agreement
Outside this provider: identity; kyb
persona · Ready
Sends the client a link to verify their own identity, and reports back when they have.
Supports: identity, screening
Requirements: your persona API credentials; a signed data-processing agreement
Outside this provider: kyb
sumsub · Ready
Company verification and identity checks, with results arriving asynchronously.
Supports: kyb, screening
Requirements: your sumsub API credentials; a signed data-processing agreement
Outside this provider: identity
Secure provider credentials
Keys are encrypted by the credential store. Saving a replacement retires the previous key here; it does not revoke that key at the vendor.
No due-diligence credentials are stored.