Back

Entity Hero Release Notes 1.17

Summary

This release introduces enhancements across Customer Risk Rating calculation, PreScreening.io integration, bulk reports, entity update APIs, framework versioning, and Entity Outcome. The changes are focused on improving integration coverage, simplifying entity management, and providing a more consistent user experience.

New Features

1. Regulatory Reporting Integration with CRR Framework
  • EHC V2 can now use regulatory report statuses received from Transact Comply to calculate CRR for root and associated entities. 
  • Supports STR Status, CTR Status, and TTR Status as triggers in the CRR framework. Status scores do not accumulate as a report moves from one status to another. 
  • Project settings allow CRR to be recalculated for every eligible report event or prevent recalculation for duplicate events. 
  • Entity Hero maintains STR counts per entity to support rules based on the number of reports filed within a defined period. These counts are maintained within Entity Hero, rather than received from Transact Comply.

Enhancements

1. Relationship Details Mapping with PreScreening.io
  • Family and Guardian details can now be shared with PreScreening.io through API/UI and Batch integrations.
  • Supported relationships include Father, Mother, Spouse, Brother, Sister, Son, Daughter, Grandmother, and Grandfather.
  • Name components are combined into a full name and mapped to the corresponding API fields or the Relationship Details section in Batch files.
2. Improved Bulk Report Download
  • Users can request RBA Reports or Detailed Entity Reports for all selected entities in a single action.
  • Each request results in one email providing access to the complete report output, instead of separate emails for every batch of 500 entities.
  • Large downloads will contain multiple report files, but these are accessible through the same email.
  • Selecting Excel downloads only the Excel report. The content within the Excel and PDF reports remains unchanged.
3. Update Existing Entities via API
  • Update existing entities by providing Project ID, Customer ID, and the fields to be changed, without resending mandatory creation details such as Name, Country, and Entity Type.
  • Fields not included in the request remain unchanged. Mandatory validations for new entity creation continue to apply.
  • Supported for Individual and Organization entities across EHO and EHC, with no change to existing PreScreening.io and Transact Comply integrations.
4. Risk Rating Threshold Versioning
  • Publishing changes to risk tier count, risk tier labels, threshold values, or scoring scale increases the minor version of both Portfolio and Onboarding frameworks.
  • Each framework increments from its own existing version. For example, Portfolio v1.3 → v1.4 and Onboarding v1.1 → v1.2.
  • Multiple changes published together result in one minor version increment per framework. Saving without changes does not increase either version.
  • Minor versions continue beyond .9, such as v1.9 → v1.10, without changing the major version.
  • Uploading a new major framework version carries forward the existing thresholds without an additional minor version increment.
5. Entity Outcome – Logical CRR Enhancements
  • The Logical CRR score initially matches the Mathematical CRR score.
  • Justification is mandatory when updating Logical CRR, and users can add multiple attachments.
  • Selecting a Risk Level automatically assigns the highest CRR score within that risk band. Entering a score automatically updates the corresponding Risk Level.

Copyright © 2026 Zigram Data Technologies Private Limited