Kayla | Perpetual Know Your Customer
Version 4.3.7
- Released: April 1, 2026
- Compatible platform version: Work.AI 10.2.9+
The patch fixes issues with the popup and search functionality related to the SEC Mutual Fund Connector RPA connector.
Version 4.3.5
- Released: August 26, 2025
- Compatible platform version: Work.AI 10.2.9+
The 4.3.5 patch improves Kayla's input by introducing the following:
To expand the data you can retrieve from the New York Stock Exchange (NYSE) provider, we have added a new MIC input field. This field displays the Market Identifier Code for reviewed entities.
With the removal of the
https://www.nasdaqtrader.com/dynamic/SymDir/mfundslist.txtendpoint, we have provided a workaround adressing the gap. This solution offers you the same information for NASDAQ mutual funds as the missing enpoint, but in the form of a bundled package that includes a current snapshot of the dedicated Data Store.
Version 4.3.4
- Released: May 1, 2025
- Compatible platform version: Work.AI 10.2.9+
The 4.3.x releases introduce ISO risk rating for countries, validation of geographical locations from input data, and audit trail reports based on connector configurations. Other significant changes include improvements to the status change logic for the Verify Address ML model review method, exception logging for Retraite Quebec - Pension plan profiles (RQPP) connector, and the proxy configuration for the SEDAR+ Company profiles connector.
New features
To empower your decision-making with more risk-related details, a non-versioned table was implemented, enabling the ISO risk rating of countries. Using the table, Kayla maps ISO country codes with corresponding risk ratings.
Kayla can now process geographical data as input, which makes the review procedure still more comprehensive. During configuration, fill in the new Geographies field and choose the newly introduced Validate geographies review method, and Kayla will account for specified locations when validating its input data against respective requirements.
To support the new geography-based review, user interface and functional changes were introduced in the human-in-the-loop tasks used with the Validate geographies review method enabled. These include the display of multiple values for existing evidence and sources, the new Custom option in the Evidence source dropdown, and the multi-select feature for the Evidence field.
Kayla now offers audit trail reports based on connector configurations. Out-of-the-box (OOTB) connectors have the feature hardcoded in their configuration. For custom connectors, you can enable or disable the feature using the Audit trail generation control in the user interface.
Improvements
We updated the status change logic for the Verify Address ML model review method. Now, a requirement is assigned the Manual status based on an audit if the change type is Immaterial and the connector type is Custom.
This means that, for an existing Immaterial change (for instance, a country-only match), a non-custom connector should return the SUCCESS status with the requirement status marked as Completed in the manual review task. However, in the same circumstances, a custom connector should return the Manual status with the requirement marked as Needs Review in the manual review task.
To improve failure detection and troubleshooting, Kayla is now set to log the Retraite Quebec - Pension plan profiles (RQPP) connector exceptions associated with unavailable results to Agent server logs.
To facilitate and unify the connector configuration flow, the SEDAR+ Company profiles connector is updated to use the same proxy configuration as the rest of Kayla's connectors.
The formatting of the audit trail document for connectors is improved to provide better readability. Now, instead of a single line, the
${search_response}field returns a properly formatted multi-line content.
Bug fixes
Fixed the issue with incorrect parsing of the Date Updated data in manual review tasks. Now, the data from the timestamp generated at the beginning of the Requirements Validator BP is parsed and displayed correctly.
Resolved the issue with improper automatic routing of users in Workspace. With the changes introduced to the configuration data formatting, if Automatically route users to the next task in the queue? in the configuration interface is set to False, the automatic routing is not applied.
Eliminated the
ArrayIndexOutOfBoundsExceptionNASDAQ connector issue caused by missing reponse data.Fixed the issue when, for a successful Validate Geographies requirement, the Evidence data did not persist in the manual review output if no changes or actions were taken on that requirement to the status, evidence source, or evidence list. Now, the manual review output includes evidence data as expected even if no changes were made or actions applied to the requirement.
Version 4.0.1
- Released: February 13, 2025
- Compatible platform version: Work.AI 10.2.9+
As part of the 4.0.1 Kayla release, we introduce a configuration to integrate with custom data providers, Java Native Workers to replace WebHarvest dependencies, and a schema-based approach to handling data in Business Processes. It also features improvements to RPA connectors and messaging and warnings in the user interface.
New features
We deprecated WebHarvest dependencies and migrated the AI Agent flows to Java Native Workers (JNW), except for some RPA connectors that are not compatible with JNWs yet. The move offers a significant enhancement in the execution performance of Java-based tasks. The execution time of a JNW task is 80-90% less than that of a WebHarvest one.
You can now set Kayla to source input from custom data providers by configuring those on the new Data providers step in the AI Agent's configuration wizard. The new capability allows you to integrate Kayla seamlessly with your internal systems without complicated workarounds or much engineering effort.
To support the new capability, we introduced the Custom connector Business Process (BP). It is available as part of the default installation together with the existing File ingestion and Requirements validator BPs. Changes were also made to the flow of the Requirements validator BP: it got a new Custom connector step making synchronous calls to the Custom connector BP to ingest data from configured data provider integrations (if any).
All out-of-the-box BPs and any custom BPs you might build for Kayla are now using the schema-based approach to handle inputs and outputs. Now, each step in a Business Process can have a contract defining variables expected as input for this step and those produced as its output. The new approach significantly reduces the amount of data passed across steps, thus increasing the overall automation performance.
Improvements
The BCB modules within RPA connectors were refactored to improve the organizational structure.
The messaging mechanism for Kayla was improved to reduce the overall message volume and make more precise descriptions of what happened. Now, Kayla sends one warning message for missing field values per entity and one error message for missing required fields per entity.
The logic for statuses is simplified so that you can have all required information handy in one place. Status constants are removed and a new enum is created that contains both Kayla's Business Process status and the Manual Task label.
Version 3.5.0
- Released: November 22, 2024
- Compatible platform version: IA Cloud 10.2.9+
The v3.5.0 Kayla release introduces new third-party integrations to automate regulatory status confirmation and extends the API with respective endpoints.
New features
Kayla was enhanced with new integrations to open-source websites for proof of regulatory status. The enhancement lets you avoid the extensive manual effort and reduce the time required to verify the regulatory status, while helping you to meet the KYC-related requirements of supervisory bodies.
The feature is available for the Verify Status review method. Whatever integration you use, a screenshot is returned to evidence the status or to guide you if multiple results are found. The integrations cover the following sources:
FCA Register - Mutual fund profiles. The bot goes to the Financial Conduct Authority’s website (Fund search) and searches for mutual funds using the company reference number or for exact matches on entity names. Preference is given to the company reference number. Only funds in the active or approved status are considered active.
Central Bank of Ireland - Company profiles. The bot goes to the Central Bank of Ireland’s website (Home page) and runs searches using the regulator ID. If found, the company is considered active.
Retraite Quebec - Pension plan profiles. The bot goes to the Retraite Quebec register (Retraite Québec - Pension plans supervised by Retraite Quebec) supervised by Retraite Québec and searches for entities using the registration number or an exact match on the entity name. Preference is given to the registration number.
Financial Services Regulatory Authority of Ontario - Company Profiles. The bot goes to the Financial Services Regulatory Authority of Ontario (Pension Plan Information) and searches for entities using the plan number or an exact match on the entity name. Preference is given to the plan number.
British Columbia Financial Services Authority - Pension Plan profile. The bot goes to the British Columbia Financial Services Authority (Registered Pension Plans | BCFSA) and searches for entities using the registration number or an exact match on the entity name. Preference is given to the registration number.
To support the new data providers and integrations, new API fields were introduced to work with the following data:
Firm reference number
Regulator ID
Registration number
Plan number
Version 3.4.3
- Released: October 31, 2024
- Compatible platform version: IA Cloud 10.2.9+
The patch addresses the issue where incorrect statuses were applied due to temporary outages of the SEC search page. The SEC Mutual Fund profile connector now returns the Failed status when it encounters connectivity issues, ensuring consistent and accurate reporting.
Version 3.4.2
- Released: October 29, 2024
- Compatible platform version: IA Cloud 10.2.9+
The Kayla 3.4.2 patch extends the SEC Mutual Fund profile connector to retrieve the parent fund or the sub-fund name, which is intended to meet KYC-specific regulations. The sub-fund name is concatenated with the parent fund, potentially giving a 25-30% boost in straight-through processing.
Version 3.4.1
- Released: October 23, 2024
- Compatible platform version: IA Cloud 10.2.9+
The Kayla 3.4.1 patch eliminates the issues with how data is displayed in the audit trail and entity-level reports. Now, if Existing evidence is selected as the evidence source when completing a requirement in a Workspace assignment, the same is shown in the audit trail report. In the entity-level report, the Change type column contains NONE for the associated entity in this case.
Version 3.4.0
- Released: October 4, 2024
- Compatible platform version: IA Cloud 10.2.9+
The Kayla v3.4.0 release optimizes the API, manual review processes, and reporting capability.
The API is enhanced to support EvA (expected versus actual activity) review requirements and analytics. It also allows sending notifications and assigning work to users in downstream systems.
The API contract is expanded to include new input and output fields.
New input fields are as follows:
platform_urlprovides a link to key downstream systems within a manual review assignment.eva_requiredindicates whether EvA review is required for a specific entity or product. You can set the additional logic for triggering manual review based on the field's value during the manual review configuration. For more details, see Install and configure | Human-in-the-loop.alt_entity_idis used for reporting and audit purposes.
New output fields are as follows:
usernamecontains the username of the individual who closed the investigation.worker_emailcontains the email address of the individual who closed the investigation.
For more details, see the API documentation.
To improve traceability and reporting accuracy, we updated the audit trail report by removing the action field and adding the requirement ID.
The manual review process improvements are aimed at more sophisticated handling of investigations.
Additional rules are introduced to support the conditional creation of manual review assignments. You can now create an assignment when a requirement needs manual review or an entity requires EvA review or apply both options. For detailed instructions, refer to Install and configure | Human-in-the-loop.
The EvA indicator is added to the case header in Workspace, giving immediate visibility into the need for an EvA review.
When you close a manual review task, the dialogue box now includes a description of Kayla's automatic actions on the assignment, instructions for the next steps, and a link to periodic review tasks in downstream systems. See more in Review results | Complete investigation.
Version 3.3.0
- Released: September 19, 2024
- Compatible platform version: IA Cloud 10.2.9+
To expand your options for automation with Kayla and facilitate its integration into your periodic review routines, we introduced the following new features:
You can choose how you want Kayla to fetch data: from CSV files uploaded to an S3 storage or via REST API.
Setting the rules for validating Kayla's input against requirements was moved entirely to the requirement configuration page. In addition, the requirement configuration was extended with new fields to support creating more complex logic for periodic reviews, including (but not limited to) proof of listing, regulation status, and risk ratings. For more details, see the API specification.
Improvements to the configuration wizard interface make it easier to understand and navigate Kayla's setup process, reducing the time to get it up and running:
The list of Kayla's ten out-of-the-box connectors was expanded with SEDAR+. This RPA-based connector retrieves screenshots from SEDAR+ of your company’s profile page.
New configuration components were introduced to facilitate the choice of data providers for sourcing enrichment data from third-party systems.
Names for connectors have been standardized across the configuration pages so that you can unmistakenly identify them within short time.
Version 2.2.0
- Released: June 21, 2024
- Compatible platform version: IA Cloud 10.2.7+
To provide more comprehensive data access and increase the efficiency and accuracy of address validation processes, we introduced the following new features:
New SEC connector. We have added a connector to the US Securities and Exchange Commission (SEC) to retrieve information from active Mutual Fund profiles. This enables you to make informed investment decisions and streamline compliance processes with up-to-date mutual fund information directly from the SEC.
Enhanced address verification service. The address verification service now supports multiple addresses as an array and includes automation rate improvements for addresses in Canada, Ireland, the United Kingdom, and the United States.
Version 2.1.1
- Released: June 7, 2024
- Compatible platform version: IA Cloud 10.2.7+
Improvements
For you to better understand the decisions on requirement completion, decision comments in manual review tasks were enhanced with the following details for each source:
Search criteria
Requirement
Version 2.1
- Released: May 17, 2024
- Compatible platform version: IA Cloud 10.2.7+
New features:
The range of data sources available for Kayla was extended with AMF (Autorité des marchés financiers). You can leverage the integration to make Kayla still more efficient in investigating KYC data changes.
Kayla's onboarding flow is becoming still more user-friendly. Redundant fields were removed from the configuration interface to reflect the shift to the rule-based requirement setup.
The human-in-the loop capability was improved to facilitate manual review in Workspace:
The assignment layout was optimized for accelerated processing and better information accessibility.
Instead of a non-informative user ID, you can now see the reviewer's username.
Under the hood, the address verification feature was strengthened by the ability to send addresses both as arrays and strings.
Version 2.0
- Released: April 26, 2024
- Compatible platform version: IA Cloud 10.2.7+
New features:
Setting even complex requirement logic has become easier and more convenient, and the number of variations required for multiple populations is decreased due to the following improvements in Kayla's user interface:
Input processing requirements are configurable as field name and value pairs.
You can now set multiple input source fields per requirement. Kayala checks these in the order they are set. If the primary field name is null or absent, Kayla checks the subsequent one(s).
For details on the above improvements, see Install and configure | Requirements.
A new CSSF (Commission de Surveillance du Secteur Financier) integration is now available on the Data Sources configuration page, allowing you to retrieve entity profile information from yet another provider. For details, see Install and configure | Data Sources.
For greater convience of working with Kayla's analytics, out-of-the-box dashboards were enhanced with semantic coloring.
Kayla's performance was enhanced due to migration to Java Native Worker and removal of the dependency on WebHarvest. For more information on Java Native Worker, refer to the guide.
Corrected issues:
Configured field names are no longer case-sensitive for the Sayari Graph API data provider.
Fixed the issue with Kayla's core BP failing due to a missing input bucket configuration even when the input method is set to email only. Now, if you set Kayla to use only the Microsoft Graph API Email input method, the BP picks the input file from the configured email and processes it as expected without requiring an input bucket configuration.
Version 1.8.0
- Released: March 22, 2024
- Compatible platform version: IA Cloud 10.2.7+
New features
Implemented a new address verification service. The service connects to an Machine Learning-based instance hosted by WorkFusion and compares addresses in the US to determine if they match and which parts of them do not. It can handle address abbreviations and common spelling differences (1st vs. first, St. vs. Street, and so on) based on the address lines.
Introduced Superset analytics dashboards for reviewing key information on the AI Agent performance.
Updated the location of the Evidence is not sufficient flag to improve the logging procedure when multiple pieces of evidence are returned for a requirement.
Added the ability to configure a proxy server.
Added minor improvements throughout the AI Agent UI.
Version 1.7.0
- Released: February 9, 2024
- Compatible platform version: IA Cloud 10.2.7+
New features
Added the ability to modify a comment on the Summary page in a human-in-the-loop task.
Added the ability to upload evidence to a Manual Task and display it in a new tab. Up to five additional documents are supported.
Added the ability to choose routing rules in Workspace. You can opt out of automatical rerouting to the next task in a queue if needed.
Enabled task pre-assignment to specific users in Workspace. You can select the intended assignee during the configuration stage.
Updated a periodic review status report to include data on the manual review status and a decision comment.
Extended the audit and entity Data Stores to support more granular analytics information.
Version 1.6.0
- Released: January 31, 2024
- Compatible platform version: IA Cloud 10.2.7+
New features
Added a human-in-the-loop step.
Implemented generation of a periodic review status report.