Customer Lifecycle Management Features

The below provides a detailed overview of the features available within KYC360 Customer Lifecycle Management (CLM). From customer data management and relationship modelling to multi-risk assessment, event-driven reviews, customer outreach and auditability, the matrix below outlines the functionality available to support compliant and efficient customer lifecycle processes.

Category	Feature	Availability	Description
Client lifecycle management	End-to-end client lifecycle management	Yes	Manage customer data, KYC, risk, reviews, remediation and ongoing monitoring throughout the customer relationship.
Client lifecycle management	Perpetual KYC (pKYC)	Yes	Move beyond point-in-time KYC by maintaining customer information and risk on an ongoing basis.
Client lifecycle management	Single source of customer truth	Yes	Maintain a central, up-to-date record of customer data, documents, relationships, KYC status and risk decisions.
Client lifecycle management	Individuals and organisations	Yes	Manage lifecycle information for both natural persons and legal entities.
Client lifecycle management	Complex entity structures	Yes	Manage connected individuals and organisations as part of wider customer and ownership structures.
Client lifecycle management	Configurable entity types	Yes	Define the customer and entity categories required by your organisation.
Client lifecycle management	Custom entity types	Yes	Create additional entity types to reflect your customer population and operating model.
Client lifecycle management	Company entities	Yes	Maintain corporate and legal-entity customer records.
Client lifecycle management	Individual entities	Yes	Maintain natural-person customers and connected parties.
Client lifecycle management	Fund entities	Yes	Manage investment funds within the same lifecycle environment.
Client lifecycle management	Partnership entities	Yes	Maintain partnership structures and their associated information.
Client lifecycle management	Foundation entities	Yes	Manage foundations and similar legal structures.
Client lifecycle management	Charity entities	Yes	Maintain charities as a dedicated entity type.
Client lifecycle management	Money Services Business entities	Yes	Manage MSBs as a distinct customer/entity category.
Client lifecycle management	Correspondent banking entities	Yes	Maintain correspondent banking customers and relationships.
Client lifecycle management	Embassy entities	Yes	Support diplomatic entities where relevant to the organisation's customer population.
Customer record	Master customer record	Yes	Maintain one master record for the same real-world customer across the organisation.
Customer record	Shared customer data	Yes	Store information that can be made available across authorised business units.
Customer record	Business-unit-specific data	Yes	Maintain additional information that is relevant only to a particular office, jurisdiction or business unit.
Customer record	Cross-business-unit customer view	Yes	Recognise the same customer across different parts of the organisation without creating unnecessary duplicate records.
Customer record	Searchable customer information	Yes	Search for entities using information stored within their master record.
Data management	Configurable customer data model	Yes	Define the information your organisation needs to collect and maintain rather than being restricted to a fixed vendor schema.
Data management	Custom data fields	Yes	Create organisation-specific fields for KYC, risk, regulatory and operational information.
Data management	Reusable data templates	Yes	Build common information structures once and reuse them across customers, relationships and reviews.
Data management	No-code data configuration	Yes	Configure data structures through visual tools without rebuilding the underlying platform.
Data management	Drag-and-drop configuration	Yes	Assemble customer data structures and review templates using a visual designer.
Data management	Field validation rules	Yes	Apply format, length, date and numeric validation to improve the consistency of customer information.
Data management	Required data fields	Yes	Define which information must be supplied for a particular customer or process.
Data management	Structured repeatable data	Yes	Capture repeatable information such as multiple sources of wealth or other complex KYC data in a structured form.
Data management	Multiple structured-data templates	Yes	Apply different information requirements according to the type of complex data being recorded.
Data management	Document and file capture	Yes	Store supporting documents alongside relevant customer information.
Data management	Configurable file controls	Yes	Define permitted file types, file-size limits and the number of supporting files that can be stored.
Data management	Controlled dropdown/list data	Yes	Use centrally maintained lists to improve consistency across KYC and risk data.
Data management	Historic list-value preservation	Yes	Retire outdated values while preserving historic customer records and audit evidence.
Data management	Configuration usage tracking	Yes	See where fields and templates are used before making changes to shared configuration.
Data management	Configuration versioning	Yes	Maintain historic configuration components so previously captured data remains interpretable.
Relationships	Entity relationship management	Yes	Record and manage relationships between customers, beneficial owners and other connected parties.
Relationships	Configurable relationship types	Yes	Define relationships such as directorships, shareholdings and family or commercial connections.
Relationships	Relationship-specific information	Yes	Store information about the relationship itself separately from the entities it connects.
Relationships	Normalised customer relationships	Yes	Maintain one record for a person or company and link it to multiple related entities rather than duplicating records.
Relationships	Active relationships	Yes	Identify relationships that are currently in force.
Relationships	Historic relationships	Yes	Preserve ended relationships for KYC, risk and audit purposes.
Relationships	Relationship effective dates	Yes	Record when customer relationships begin and end.
Relationships	Backdated relationships	Yes	Record historic relationship information where it predates entry into CLM.
Group and complex structures	Customer/entity groups	Yes	Group connected entities together and manage their risk as part of a wider structure.
Group and complex structures	Configurable group types	Yes	Define different structures for different customer and relationship use cases.
Group and complex structures	Primary entity	Yes	Identify the central customer around which the wider relationship or ownership structure is assessed.
Group and complex structures	Relationship-driven groups	Yes	Build groups from relationships already recorded within the platform.
Group and complex structures	Ad-hoc entity grouping	Yes	Bring relevant entities together for risk assessment even where a formal relationship has not yet been recorded.
Group and complex structures	Visual relationship graph	Yes	Visualise connected entities and their position within a wider customer structure.
Group and complex structures	Group-level risk assessment	Yes	Assess risk across the whole customer or ownership structure rather than evaluating every entity only in isolation.
Group and complex structures	Member-level risk visibility	Yes	Understand the individual risk presented by each entity within a group.
Group and complex structures	Multiple group risk layers	Yes	Assess the same group against several different types of risk.
Group and complex structures	Group AML risk	Yes	Evaluate AML risk across related customers and entities.
Group and complex structures	Group operational risk	Yes	Maintain a separate operational-risk view of the same entity structure.
Group and complex structures	Multiple risk models per structure	Yes	Use different risk models for different risk dimensions within a group.
Group and complex structures	Consolidated group risk	Yes	Roll risk from connected entities into an overall assessment of the primary customer.
Group and complex structures	Scheduled group risk calculation	Yes	Recalculate wider group risk automatically on a scheduled basis.
Group and complex structures	On-demand group risk calculation	Yes	Trigger an updated group assessment when a current view is required immediately.
Multi-risk management	Multiple simultaneous risk models	Yes	Run multiple independent risk assessments against the same customer.
Multi-risk management	AML risk models	Yes	Assess customers using configurable AML risk methodology.
Multi-risk management	Sanctions risk models	Yes	Incorporate sanctions-related factors into lifecycle risk management.
Multi-risk management	Tax risk models	Yes	Maintain tax-related risk assessments independently or alongside other customer risks.
Multi-risk management	Bribery and corruption risk models	Yes	Assess bribery and corruption exposure as a distinct lifecycle risk.
Multi-risk management	Operational risk models	Yes	Assess operational risk independently from financial crime risk.
Multi-risk management	Geographic risk models	Yes	Assess customer risk associated with country and jurisdictional exposure.
Multi-risk management	Financial risk models	Yes	Create dedicated models for relevant financial-risk factors.
Multi-risk management	Custom risk models	Yes	Build additional risk assessments around your organisation's own methodology and risk appetite.
Multi-risk management	Dynamic multi-risk scoring	Yes	Maintain separate, changing views of the different risks presented by a customer throughout the relationship.
Risk modelling	Configurable risk engine	Yes	Build risk models around your own risk methodology rather than accepting a fixed vendor model.
Risk modelling	Weighted risk scoring	Yes	Weight individual risk factors according to their importance to the organisation.
Risk modelling	Total-score models	Yes	Calculate risk by combining the values generated by applicable rules.
Risk modelling	Highest-risk-factor models	Yes	Base the overall result on the highest applicable risk indicator where policy requires it.
Risk modelling	Configurable risk bands	Yes	Define the boundaries between your preferred risk classifications.
Risk modelling	Configurable scoring scales	Yes	Use the numerical scale that best reflects your organisation's risk methodology.
Risk modelling	Rules-based risk assessment	Yes	Calculate customer risk automatically from data held within the customer record.
Risk modelling	Multi-condition risk rules	Yes	Combine several customer attributes when determining whether a risk rule applies.
Risk modelling	Baseline risk values	Yes	Apply standard starting risk values before additional customer-specific factors are considered.
Risk modelling	Numeric risk bands	Yes	Score financial and other numeric information using configurable value ranges.
Risk modelling	Conditional risk treatment	Yes	Apply different risk logic to different customer populations using rule preconditions.
Risk modelling	Reusable risk lists	Yes	Maintain common risk values, such as jurisdiction risk, once and reuse them across multiple models.
Risk modelling	Central risk-list management	Yes	Update shared risk assumptions in one place rather than changing every model individually.
Risk modelling	Automatic risk recalculation	Yes	Recalculate customer risk when relevant customer information or risk methodology changes.
Risk modelling	Live customer risk profile	Yes	Maintain an up-to-date view of customer risk as relevant information changes.
Risk modelling	Risk history	Yes	Track how a customer's calculated risk has changed over time.
Risk modelling	Normalised risk scoring	Yes	Compare models that use different raw scoring scales through a common normalised view.
Risk modelling	Risk contribution breakdown	Yes	See which rules contributed to a risk assessment and the impact of each factor.
Risk modelling	Explainable risk decisions	Yes	Provide evidence showing how data, rules and weightings produced the resulting risk score.
Risk modelling	Scenario modelling	Yes	Test how changes to risk rules and assumptions affect customer risk before applying them operationally.
KYC adequacy	Configurable KYC models	Yes	Define what sufficient KYC looks like for different customer populations.
KYC adequacy	Multiple KYC models	Yes	Run more than one KYC adequacy assessment where customers are subject to different requirements.
KYC adequacy	Automated KYC completeness assessment	Yes	Assess whether the customer record contains the information required under configured KYC rules.
KYC adequacy	KYC pass/fail status	Yes	Provide a clear indication of whether a customer currently meets applicable KYC requirements.
KYC adequacy	Configurable KYC rules	Yes	Define the conditions that determine whether KYC information is adequate.
KYC adequacy	Missing-information detection	Yes	Identify customer records that do not contain required KYC information.
KYC adequacy	KYC failure reasons	Yes	Explain which requirement caused a customer to fail a KYC adequacy assessment.
KYC adequacy	Automated KYC reassessment	Yes	Re-evaluate KYC adequacy as relevant customer information changes.
Perpetual KYC	Ongoing customer monitoring	Yes	Maintain customer risk and KYC information continuously throughout the relationship.
Perpetual KYC	Event-driven lifecycle management	Yes	Respond to changes in customer information and risk rather than waiting only for a scheduled periodic review.
Perpetual KYC	Event-driven KYC reviews	Yes	Trigger KYC review activity when relevant customer or external information changes.
Perpetual KYC	Event-driven KYB reviews	Yes	Trigger business-customer reviews in response to relevant changes to company or ownership information.
Perpetual KYC	Automated KYC/KYB triggers	Yes	Use lifecycle events to initiate the appropriate KYC or KYB process automatically.
Perpetual KYC	Automated pKYC updates	Yes	Update customer lifecycle information automatically as relevant new information becomes available.
Perpetual KYC	Continuous risk reassessment	Yes	Recalculate customer risk as underlying data or risk methodology changes.
Perpetual KYC	Risk-based review activity	Yes	Direct review activity according to customer risk rather than relying only on fixed calendar cycles.
Perpetual KYC	Periodic reviews	Yes	Schedule formal customer reviews at appropriate intervals where periodic review remains required.
Perpetual KYC	Automated periodic reviews	Yes	Automate recurring KYC review processes across the customer lifecycle.
Perpetual KYC	Ad-hoc reviews	Yes	Perform and evidence additional customer reviews whenever required.
Reviews	Structured KYC reviews	Yes	Guide reviewers through predefined questions and requirements rather than relying only on free-text review notes.
Reviews	Configurable review questionnaires	Yes	Build review questionnaires around the organisation's own policy and customer types.
Reviews	Review scheduling	Yes	Schedule customer reviews for future dates.
Reviews	Review work queues	Yes	Surface due review activity to relevant users.
Reviews	Review comments	Yes	Record analyst observations and decisions as part of the review history.
Reviews	Point-in-time customer data	Yes	Review the customer information that was available at the time an assessment was performed.
Reviews	Historic review evidence	Yes	Retain completed reviews and the information considered by the reviewer.
Reviews	Group reviews	Yes	Perform lifecycle reviews across groups of related customers and entities.
Reviews	Multi-user group reviews	Yes	Divide review activity across multiple reviewers when assessing larger customer structures.
Reviews	Group review completion controls	Yes	Ensure required underlying entity reviews have been completed before the overall group review is closed.
Reviews	Approval-aware reviews	Yes	Prevent formal reviews from being completed against customer information that is still awaiting approval.
Customer outreach	Automated customer outreach	Yes	Contact customers automatically when information needs to be refreshed, corrected or completed.
Customer outreach	Missing-information outreach	Yes	Request information when customer records no longer satisfy KYC requirements.
Customer outreach	Expired-information outreach	Yes	Request refreshed information or documentation when existing evidence becomes out of date.
Customer outreach	Targeted remediation	Yes	Request only the specific information needed to remediate a customer record, reducing unnecessary customer friction.
Customer outreach	Automated data collection	Yes	Collect updated information from customers as part of ongoing pKYC activity.
Customer outreach	Branded outreach	Yes	Deliver customer communications and information requests using organisation-specific branding.
Customer outreach	Branded email communications	Yes	Apply branded email content to lifecycle outreach.
Customer outreach	Customer outreach portal	Yes	Give customers a secure digital route for responding to lifecycle information requests.
Customer outreach	Secure KYC data sharing	Yes	Share relevant KYC information securely where appropriate to the customer-management process.
Customer outreach	Remediation tools	Yes	Support structured correction and refresh of customer information.
Customer outreach	Bulk remediation upload	Yes	Use bulk data processes to support remediation activity at scale.
Data and monitoring	Experian Monitoring integration	Available	Use Experian monitoring services to identify relevant customer and business changes.
Data and monitoring	Experian KYB integration	Available	Bring external business information into customer lifecycle processes.
Data and monitoring	Experian KYC integration	Available	Incorporate external KYC information within ongoing customer management.
Data and monitoring	Pre-integrated global data	Available	Connect CLM with external data sources used to maintain and assess customer information.
Data and monitoring	Jurisdiction-specific logic	Yes	Apply data and risk logic appropriate to different jurisdictions and customer populations.
Data and monitoring	External change-driven workflows	Yes	Use relevant external information changes to initiate downstream lifecycle-management activity.
Data governance	Four-eye approval	Yes	Require an independent user to approve sensitive customer-data changes.
Data governance	Two-eye approval	Yes	Require explicit confirmation of specified changes where self-approval is appropriate.
Data governance	Field-level approval controls	Yes	Apply additional governance only to the customer information that requires it.
Data governance	No four-eye self-approval	Yes	Ensure that the person who submits a four-eye-controlled change cannot approve their own change.
Data governance	Draft customer changes	Yes	Save updates before submitting them into the formal approval process.
Data governance	Change approval workflow	Yes	Route sensitive customer-data updates to authorised reviewers before they become effective.
Data governance	Changed-fields-only review	Yes	Allow reviewers to focus specifically on the information that has changed.
Data governance	Approval comments	Yes	Retain reviewer and submitter comments alongside governed changes.
Data governance	Versioned customer data	Yes	Maintain historic versions of approved customer information.
Data governance	Customer change history	Yes	Review how approved customer information has evolved over time.
Data governance	Approval history	Yes	Evidence who submitted, reviewed and approved customer-data changes.
Business units and security	Multi-business-unit support	Yes	Manage different offices, teams, jurisdictions or regulated entities within one CLM environment.
Business units and security	Business-unit data segregation	Yes	Restrict sensitive customer information to the appropriate part of the organisation.
Business units and security	Business groups	Yes	Organise users by their role and responsibilities within individual business units.
Business units and security	Deny-first permissions	Yes	Protect customer data by denying access unless it has been explicitly granted.
Business units and security	Role/group-based access	Yes	Manage access through groups rather than relying on manual permissions for each user.
Business units and security	Field-level access control	Yes	Control which customer-data fields different teams may view or edit.
Business units and security	Read and edit permissions	Yes	Separate the ability to see customer information from the ability to change it.
Business units and security	Hierarchical permissions	Yes	Apply broad access controls and then refine them for individual data fields where necessary.
Business units and security	Functional access controls	Yes	Restrict access to platform capabilities such as reporting or risk-model configuration.
Business units and security	Entity-type-specific access	Yes	Give different teams appropriate access to KYC, KYB and other customer populations.
Dashboards and MI	Real-time reporting	Yes	Give compliance and operational teams current visibility into customer lifecycle activity and risk.
Dashboards and MI	Risk dashboard	Yes	Monitor aggregate customer risk across the organisation.
Dashboards and MI	Multi-risk dashboards	Yes	Analyse different risk models independently rather than collapsing all customer risk into one metric.
Dashboards and MI	Business-unit risk reporting	Yes	Compare customer risk across different parts of the organisation.
Dashboards and MI	Entity-type risk reporting	Yes	Analyse risk according to different customer and entity populations.
Dashboards and MI	Risk trend reporting	Yes	Understand how risk across the customer book changes over time.
Dashboards and MI	KYC adequacy dashboard	Yes	Monitor the extent to which customers satisfy applicable KYC requirements.
Dashboards and MI	Review dashboard	Yes	Monitor review volumes and lifecycle-review status.
Dashboards and MI	Pending review reporting	Yes	Identify upcoming customer reviews.
Dashboards and MI	Overdue review reporting	Yes	Identify reviews that have passed their required completion date.
Dashboards and MI	Completed review reporting	Yes	Track completed review activity for management information and governance.
Dashboards and MI	Review performance visibility	Yes	Monitor the progress and performance of lifecycle-review processes.
Audit and evidence	Complete CLM audit trail	Yes	Maintain evidence of customer information, user actions, risk decisions and lifecycle activity.
Audit and evidence	System-wide audit log	Yes	Record activity across the CLM platform.
Audit and evidence	User activity history	Yes	Identify the users responsible for relevant actions and changes.
Audit and evidence	Filterable audit history	Yes	Search and filter audit records to support investigation and governance.
Audit and evidence	Risk decision history	Yes	Retain previous risk assessments and the rules that produced them.
Audit and evidence	KYC assessment history	Yes	Evidence KYC adequacy outcomes throughout the customer lifecycle.
Audit and evidence	Review history	Yes	Preserve historic customer reviews and supporting information.
Audit and evidence	Approval audit trail	Yes	Evidence who submitted and approved governed customer-data changes.
Audit and evidence	Group history	Yes	Maintain version history for complex customer/entity structures.
Import, export and remediation	Bulk customer import	Yes	Create or update customer data at scale through structured bulk uploads.
Import, export and remediation	Generated import templates	Yes	Generate import structures aligned to the configured customer data model.
Import, export and remediation	Existing-customer matching	Yes	Update existing customer records by matching imported data against selected identifiers.
Import, export and remediation	Partial import processing	Yes	Continue processing valid customer records even where individual imported rows contain errors.
Import, export and remediation	Import error reporting	Yes	Identify failed records and the reasons they could not be processed.
Import, export and remediation	Bulk customer export	Yes	Extract relevant customer information for permitted operational or data-management purposes.
Import, export and remediation	Configurable export scope	Yes	Select organisation-wide, business-unit-specific or combined data for export.
Import, export and remediation	Password-protected exports	Yes	Protect generated data extracts using a user-defined password.
Import, export and remediation	Controlled export permissions	Yes	Restrict bulk extraction independently from ordinary customer-data access.
Import, export and remediation	Background data processing	Yes	Process high-volume import and export activity without blocking day-to-day use of the platform.
Integrations	External APIs	Yes	Integrate CLM with existing customer, compliance and enterprise systems.
Integrations	Real-time integration	Yes	Exchange relevant customer and lifecycle information with external systems in real time.
Integrations	Batch integration	Yes	Support high-volume exchange of customer information through batch processes.
Integrations	DataBridge	Available	Connect data sources and systems through KYC360's no-code integration capability.
Integrations	No-code integration	Yes	Connect lifecycle processes to wider technology environments with reduced development dependency.
Integrations	API management	Yes	Provision and control external API access from within CLM.
Integrations	API credential rotation	Yes	Rotate integration credentials without interrupting service.
Integrations	Business-unit-scoped API access	Yes	Limit individual integrations to authorised parts of the customer dataset.
Integrations	Secure API credentials	Yes	Protect API credentials through one-time display and secure storage practices.
Deployment	Secure test environments	Available	Validate integration and configuration away from the production environment.
Deployment	Pre-production environment	Available	Test changes safely before releasing them to live customer processes.
Administration	User management	Yes	Invite and manage users within the CLM environment.
Administration	Business-unit administration	Yes	Configure the organisational structure used to segregate customers and teams.
Administration	Business-group administration	Yes	Manage groups responsible for particular customer information and workflows.
Administration	System-group administration	Yes	Control access to different functional areas of the platform.
Administration	User access revocation	Yes	Remove access while preserving historic actions and audit records.
Administration	User membership visibility	Yes	See the groups and business units associated with individual users.
Configuration	No-code configuration	Yes	Configure customer data, risk, KYC and review processes without rebuilding the underlying product.
Configuration	Draft-and-publish configuration	Yes	Prepare and review configuration changes before making them available to users.
Configuration	Controlled configuration publishing	Yes	Decide when new customer-data structures and process configuration become active.
Configuration	Reusable configuration components	Yes	Reuse standard fields, templates and risk lists to reduce duplicated configuration and maintenance.
Branding	Branded CLM interface	Yes	Apply organisation-specific branding to the internal CLM environment.
Branding	Branded customer outreach	Yes	Apply branding to external customer lifecycle communications and outreach.
Branding	Accessibility-aware branding	Yes	Apply interface branding with automated contrast checks designed to support accessibility.

KYC360 Customer Lifecycle Management Features

Discover how KYC360 can help
you do more, better business, faster.

KYC360 Customer Lifecycle Management Features

Discover how KYC360 can helpyou do more, better business, faster.

Discover how KYC360 can help
you do more, better business, faster.