EnateAI IDP - Adapter Improvements and New Insurance Surrender Model

EnateAI IDP - Adapters improvements

As part of our ongoing efforts for enhancing EnateAI's capabilities in the IDP space, we've updated EnateAI's adapters and adjusted the number of data extraction models available when configuring an IDP Action. Now three extraction models will be available which are General, Invoice and the new Insurance Surrender model.

EnateAI IDP - New Insurance Surrender Model

Alongside the adapter enhancements we are introducing a new Insurance Surrender extraction model.

Like the Invoice model, the new Insurance Surrender model comes business context aware by integrating thirty commonly used fields into the data extraction pipeline powered by Azure Form Recognizer (AFR). These fields are designed to capture essential information from insurance policy surrender documents, ensuring accurate and consistent data extraction.

With the addition of these fields to the Insurance Surrender Model, you will now see these fields appear in the Json output file structure, even if there is no value to be populated.

This enhancement allows the extracted data to be seamlessly used with any integration tool (e.g. Enate Integration Services powered by SnapLogic, Azure Data Factory, Power Automate) for slicker processing and automation. In future updates, we plan to expand the list of standard fields further to support additional document types.

We’ve focused on the key pieces of information that typically matter most in financial operations. And while these twenty fields are now standardized, you'll continue to see additional data captured, displayed under KeyValuePairs and Tables.

Here’s the full list of the standard fields for the Insurance Surrender Model:

  • Policy Number

  • Policy Holder

  • Policy Holder Occupation

  • Address Including Postcode

  • Residential Address

  • Reason for Payment

  • Reason for original Investment

  • Payment Options

  • Payment Options Data

  • Payment Type

  • Bank Name of Account Holder

  • Bank Account Number

  • Bank Sort Code

  • Bank Building Society Roll Number

  • Bank BIC SWIFT Code

  • Bank IBAN

  • Bank Name

  • Bank Address Including Postcode

  • Policyholder Trustee 1 Signature

  • Policyholder Trustee 1 Number

  • Policyholder Trustee 1 Full Name

  • Policyholder Trustee 1 Address

  • Policyholder Trustee 1 Post Code

  • Policyholder Trustee 1 Date

  • Policyholder Trustee 2 Signature

  • Policyholder Trustee 2 Number

  • Policyholder Trustee 2 Full Name

  • Policyholder Trustee 2 Address

  • Policyholder Trustee 2 Post Code

  • Policyholder Trustee 2 Date

This standardized approach ensures better structure, better data consistency and smoother integration across various platforms.

Last updated

Was this helpful?