Identity and compliance configuration
How to configure the document and identity types used by customer, account, KYC, and collateral processes.
Open Business Configuration → Identity & Compliance. Use this section to define the identity records and supporting documents that users can capture in customer, account, KYC, and collateral processes.
Access and lifecycle
Document Types and Identity Types have separate permissions. For each entity:
- Read shows its tab and records;
- Create permits creation and CSV import;
- Update permits changes;
- Delete permits deletion and restoration;
- Export permits export.
These records do not use maker-checker or amendments. A permitted change takes effect immediately. Codes are stable identifiers and cannot be changed after creation.
The Identity & Compliance sidebar item is shown when the user can read either Document Type or Identity Type. A user may therefore see only the tab their permissions allow.
At L0, select the target company when creating or importing tenant-owned records. Tenant users are fixed to their own company.
Configure document types
Open Document Types, then select Create Document Type.
| Field | Meaning |
|---|---|
| Code | Stable unique identifier used by configuration and integrations. |
| Description | User-facing name of the document. |
Document Types supply the allowed document classifications for customer and account documents. They can also be referenced by KYC evidence rules, workflow requirements, and collateral configuration.
Review every downstream reference before deletion. remoteEaze blocks deletion while an active configuration or record still depends on the Document Type.
Configure identity types
Open Identity Types, then select Create Identity Type.
| Field | Meaning |
|---|---|
| Code | Stable unique identifier for the identity type. |
| Description | User-facing name, such as National ID or Passport. |
| Country | Optional country restriction. Leave empty for a type usable across countries. |
| Mandatory Fields | Additional information that must accompany this identity type. |
| Format Pattern | Optional regular expression used to validate the identity reference. |
| Integrator API URL | Optional integration metadata stored with the identity type. |
The standard mandatory-field choices include reference number, issue date, expiry date, and date of birth. Custom field names are normalized to uppercase underscore identifiers.
At capture time, remoteEaze verifies that the Identity Type is active, applies its country restriction, requires its configured mandatory fields, and checks the identity reference against the Format Pattern when one is present.
Build a Format Pattern
Use the Format Pattern Builder to create validation without writing a raw regular expression. Add the required segments, lengths, character types, and separators in the order they appear in the identity reference. Test valid and invalid examples before saving.
The builder anchors the pattern so the complete identity reference must match. Advanced users may enter a raw regular expression when the visual segments do not express the required rule. When an existing expression cannot be represented visually, keep it in advanced mode rather than rebuilding it as a different pattern.
Import, export, and retire values
Use import for controlled bulk creation and export when the matching action is available. Imported records pass the same validation as records created in the form.
Before deleting a type, confirm that it is no longer needed by any policy, workflow, product, or operational record. Restore a deleted type with Delete permission when the dependent process needs it again.
Continue with Customer configuration and Customer workflow policies when preparing customer onboarding.