Skip to main content

Working with the Autocompletion Agent

Bolstered by an agentic offering, autocompletion of tasks represents a huge step forward towards straight-through-processing within the application. Based on feedback from our clients, we have noticed a trend whereby Data, Documents and Related Parties Tasks would have been fulfilled in an initial onboard, and are then brought into scope again in the context of a Review or Maintenance Journey. A User would be forced to re-complete these Tasks without providing any value, as everything required of them had already been fulfilled. Taking this away, we came to the conclusion that if a User has already satisfied all outstanding validation in a previous Journey, we should not force them to re-complete a Task where they are not adding value.

Taking this insight away, we have now introduced a new functionality whereby if all outstanding validation is satisfied within a task, the Task can self-complete without requiring any User action. This is a capability that is opt-in at an individual Task level, allowing for greater flexibility.

This functionality is available for the following Task Types:

  • Data
  • Documents
  • Documents V2
  • Related Parties
  • Data & Documents
  • Blocking

Autocompletion Logic​

The logic for a Task completing will be based on the validations configured in the Tenant’s Policy. The Policy Requirements configured are validated as a Task enters a “preprocessing” status. Here, we validate if all validation is satisfied - with the most common and straight-forward example being if a Policy Requirement is "Mandatory" or not. For “Data” Tasks, we also check any validation configured against the requirements in a Task, to ensure that all existing data provided still meets the configuration provided. For example, if a “Date of Incorporation" field had “No Past Dates” validation configured, and the provided value for this field was in the past, the Data task would not autocomplete.

In simple terms, the grounds for closing a task via the Autocompletion Agent are the same as what a User would experience navigating a Task. If a User could simply hit “Complete” without any validation errors, the system will do the same.

There are some unique scenarios where Autocompletion will not occur:

Document Tasks​

For Document Tasks – those being "Documents V1", "Documents V2" and "Data & Documents" specifically - the Autocompletion Logic looks specifically for mandatory document requirements that have an Approved status. If Document Persistence is enabled, the system will move any Document Requirements with a status of “Pending Approval” to a status of “Approved” as a part of this process. If all mandatory Document Requirements have a status of “Approved” and have at least one Document linked against them, the Task will autocomplete.

At this time, “Waived” and “Deferred” Document Requirements will not be eligible for autocompletion. Tasks where there are mandatory Document Requirements with either of these statuses must be manually completed by a User.

The Related Party Task can be seen to have three types of requirements:

  1. Add X Number of a certain Relationship Type
  2. Add All Relationship Types
  3. ID&V X Relationship Type

For Autocompletion, we can handle this first type of requirement, where we validate specifically the existing Related Parties and assess if the specified number of Relationship Types has been added. This is the only type of requirement that will allow for Autocompletion across multiple Journeys for the same Entity.

For the “Add All” type of requirement, this will always be required to completed by a User. This is because the determination that “All” of a given Relationship Type have been added is not something the application can confirm. It must be a User attestation that they have added all of the required Relationship Type, according to their best judgement. This means that if there is an outstanding, mandatory “Add All” requirement, this will prevent Autocompletion of a Related Parties Task. It is worth noting that once this requirement is satisfied within a Journey, any further interactions (via reopening the task for example) will be eligible for Autocompletion, as that requirement is now satisfied.

For “ID&V” requirements, we currently do not persist ID&V status across multiple Journeys. Like the above, the “ID&V” requirement must be confirmed and completed by a User manually. If there is a mandatory “ID&V” requirement that is not satisfied, the Related Party Task will be prevented from autocompleting. However, much like the above, if the “ID&V” requirement is satisfied within the same Journey, and then that Task is interacted again, the Task is now eligible for autocompletion because the mandatory requirement was dealt with prior in the Journey.

info

In some tenants, this feature may be referred to as the Autocompletion Agent or just simply Autocompletion. Both terms refer to the same functionality and capabilities. If you are interested to learn more about our agentic capabilities, please see the Fenergo Digital Agents section for more information.