Click Follow in the Release Notes section to be notified when new releases are available.

• Announcement Date: June 11, 2026
• Release Date: June 25, 2026

Verato MDM Cloud

Identity

New Features and Improvements

Pub/Sub and notification enhancements

• Source metadata included in outbound notifications
  Organizations that pass contextual metadata through the Verato APIs — such as source login name, username, location, and transaction type — can now see that metadata reflected in outbound pub/sub notifications. This enables downstream consumers and audit integrations to correlate platform events with the originating source-system user and transaction context, without requiring additional lookups or custom enrichment.

• Granular identity-updated notifications
  Downstream consumers subscribed to identity update events now receive more granular, targeted notifications rather than a single broad identity.updated event. Teams building real-time integrations and streaming pipelines can now trigger more precise actions based on the specific nature of each change.d.

Match Tiers™ and source tier accuracy

• Case-insensitive source name resolution for Match Tier™ assignment
  Source names are now matched case-insensitively when determining Match Tier™ assignment. Previously, a case mismatch — such as "Epic" vs. "EPIC" — would silently fall through to the default tier, resulting in incorrect match scoring without any error signal. Source names now resolve correctly regardless of case, ensuring the intended tier is applied and match quality is preserved.

• Explicit error on missing source tier configuration
  When an incoming source record cannot be resolved to any configured tier, the platform now returns an explicit error rather than silently falling through to the default. Teams troubleshooting tier misconfiguration will receive a clear, actionable signal instead of discovering the issue through downstream match quality degradation.
  When an error occurs, API user should expect the following response:

{
    "success": false,
    "message": "No tier configured for source '<sourceName>'.",
    "retryableError": false,
    "errors": [
        "No tier configured for source '<sourceName>'."
    ]
}

Audit log

• Source system context captured in audit log events
  Source-system context — including login name, username, location, and transaction type — is now captured in the audit log for identity ingestion, merge, link, unlink, soft-delete, and reactivation events. Organizations that require traceability of the originating source-system user for audit and compliance reporting now have that context available directly in the audit log record.

Identity record management

• "County/District" label added to the District address attribute
  The address cluster attribute previously labeled only "District" now displays as "County/District" in the Verato MDM Cloud™ UI. This resolves widespread confusion for organizations using county-level segmentation — particularly in the US — who did not realize the "District" attribute represented county-level data. No underlying data model or integration changes are required.

Provider stewardship workflow

• Perspectives now available on provider stewardship task views
  Data stewards reviewing provider identity tasks can now use configurable Perspectives to control which attribute clusters are displayed in the task view — the same capability available in Entity 360®. Stewards can also apply filters and manage source records directly from the task view, reducing visual noise and enabling role-based workflow optimization for clinical vs. demographic review scenarios.

Perspectives

• Perspective UX improvements
  Several UX improvements have been made to Perspectives in Entity 360®. A Verato-Defined perspective is now available for each entity type and is selected by default on load, eliminating the blank placeholder state that previously appeared before a user made a selection. Active perspective filters are now also reflected in the Filters tab, so users can see exactly what is currently applied without having to infer it from the perspective name.

Manual Linking & Do-Not-Merge Visibility in APIs

• Enhanced Audit and Stewardship Transparency: Manual Linking & Do-Not-Merge Visibility
  Data stewards and compliance teams now have complete visibility into manual links, unlinks, merges, and unmerges—reviewable directly through APIs with no configuration required. When postIdentity and query responses are retrieved, they now include two new fields that surface historical manual actions: linkedEvents, showing which records were manually linked and when; and unmergeable, identifying record pairs explicitly flagged to prevent auto-merge even when match scores exceed thresholds. This enables data stewards and compliance teams to audit identity decisions, demonstrate transparency to customers, and maintain clear records of human interventions in the matching process.

  The fields are automatically populated in Group By Source (GBS), Default, and all Smart Views® response formats, across all customer-facing APIs, Web Service-UI stewardship endpoints, and Entity-360 aggregation responses, with no configuration required. This is available across all entity types – Person, Provider, and Organization.

  • linkedEvents field in response contains records of manual links between two source+native ID pairs, including:
     

    • link_to_source: Source system of the first record

    • link_to_native_id: Native ID of the first record

    • linked_source: Source system of the second record

    • linked_native_id: Native ID of the second record

    • linked_time_stamp: When the link was created

{
  "linkedEvents": [
           {
             "linkToSource": "SOURCE_SYSTEM_A",
             "linkToNativeId": "12345",
             "linkedSource": "SOURCE_SYSTEM_B",
             "linkedNativeId": "67890",
             "linkedTimeStamp": "2026-06-15T22:53:55.104716563Z"
           }
       ]

• Unmergeable field in response contains pairs of records flagged to never auto-merge, including:

  • source:: Source system of first record

  • nativeID: Native ID of first record

  • originSource: Source system of second record

  • originNativeId: Native ID of second record

{
        "unmergeable": [
           {
               "source": "SOURCE_SYSTEM_B",
               "nativeId": "67890",
               "originSource": "SOURCE_SYSTEM_A",
               "originNativeId": "12345"
           }
       ]

Bug Fixes

• Identity name blank in task view for Match Same Source tasks
  The Identity Name column was appearing blank in the task view for Match Same Source and Potential Match Same Source task types, making it difficult for stewards to identify records at a glance. The identity name is now populated correctly at task creation time for all task categories, consistent with other task types.

• Address abbreviation "DR" incorrectly normalized to "Drive"
  Address normalization was incorrectly converting the abbreviation "DR" — as in Doctor — to "Drive," and "ST" — as in Saint — to "Street," affecting address accuracy across person and provider records. The normalization logic has been corrected to preserve the intended meaning of these abbreviations. 

• Prevented Match task incorrectly generating a duplicate Potential Match task
  Under certain matching conditions, creating a Prevented Match Same Source task was also incorrectly generating a spurious Potential Match Same Source task for the same pair of records. Stewards now see only the correct task type, eliminating erroneous items from the stewardship queue.

• Entity 360® side panel rendering empty for certain identities
  The Entity 360® side panel was rendering empty for certain link IDs due to an issue with how source metadata was handled in the identity query response. The panel now loads correctly for all valid link IDs.

• Verato Managed Record identities not appearing in provider search after reactivation
  Identities composed exclusively of Verato Managed Records did not appear in provider search results immediately after a deactivated record was reactivated. Search results now correctly surface these identities following reactivation.

• Attribute deactivation failing for name clusters
  Attempting to deactivate a name attribute from Entity 360® was returning an "Attribute name not found" error because the UI was constructing the deactivation request with an incorrect field reference. This was a blocker-severity issue found during certification testing. The UI now reads the correct value from the cluster-groups API and deactivation completes successfully.

• Task queue loading slowly or incorrectly at high task volumes
  In environments with very large task queues, the Task Queue was failing to display correctly on initial load: Open Tasks showed a count of zero and the queue required multiple refreshes and environment switches to render properly. The underlying performance issue has been resolved and the task queue now loads correctly on first access regardless of task volume. 

• "Failed to extract attribute" error when deactivating address attributes
  Attempting to deactivate an address attribute from the Verato MDM Cloud™ UI was returning an error — "failed to extract attribute — no matching attribute value set was found" — due to a mismatch between the normalized address representation in the UI and the detailed multi-field structure stored in the database. The deactivation logic now correctly maps the normalized address back to its stored components, and the error no longer occurs.

• Applied Overlay tasks displayed in the UI when overlay configuration is set to REJECT
  Customers with overlay configurations set to reject incoming overlays were seeing Applied Overlay tasks appear in the task queue, creating a misleading signal that overlays had been successfully applied. The backend behavior was correct — overlays were being rejected — but the UI was surfacing a task type that implied the opposite. The task creation logic has been corrected so that Applied Overlay tasks are no longer generated when the configuration is set to REJECT.

Connect

New Features and Improvements 

Provider Batch Operations

• Merge and delete identity batch jobs now available for provider stacks
  The merge identities and delete source identity batch jobs are now fully operational for provider stacks, matching the capability already available for person stacks. Organizations managing provider data at scale through Verato's batch framework can now perform bulk merges and deletions against provider identity data without requiring individual API calls.

Insights

New Features and Improvements 

Verato Insights

• "Current Sources" metric descriptions updated for accuracy
  The descriptions for the Current Sources and Active Sources metrics in Verato Insights have been updated to more accurately reflect what each figure represents. The Launchpad Current Sources description now clarifies that the count includes all configured data sources — both active and inactive — across all entity types in the environment. The Source Analysis Current Sources description now correctly notes that it reflects sources for the selected entity, and the Active Sources description has been tightened for precision.

Operational Insights — User and Usage Analysis

• API Request Type filter added to User & Usage Analysis
  The User and Usage Analysis report now includes an API Request Type filter, enabling teams to segment usage data by the type of API call being made. Filters have also been reorganized into three clearly labeled groups — Shared Filters, User Filters, and Usage Filters — making it easier to understand which filters affect which charts and KPIs.

Operational Insights — Task Analysis

• Task Status Trend chart converted to line chart
  The Task Status Trend visualization in Operational Insights has been updated from a bar chart to a line chart. The line chart format provides a clearer view of how task volumes across different statuses trend over time, making it easier to identify workflow patterns and spot anomalies at a glance.

• "All Time" option added to the Created On filter in Task Analysis
  The Created On filter in Task Analysis now includes an "All Time" option, giving users a direct way to remove the date boundary entirely without needing to configure a custom date range. This also resolves a related limitation where the Task Closed Trend chart defaulted to the last year and had no clear way to show the full historical dataset.

• Task Analysis updated with data freshness notice
  A data freshness notice has been added to the Task Analysis page: "Data in this report may reflect up to a 24-hour delay. For real-time task data, please refer to Task Stewardship." This clarifies the expected latency between stewardship activity and its reflection in analytical reports, addressing confusion from customers comparing task counts between Task Stewardship and Task Analysis.

• Chart descriptions updated for Task Status Trend and Task Closed Trend
  Descriptive text for the Task Status Trend and Task Closed Trend charts has been updated to more accurately explain what each visualization shows, including guidance on the summary vs. detail view behavior and the data cadence. Teams onboarding to Operational Insights will have a clearer understanding of how to read and use each chart without needing additional documentation.

• Filters and chart context now carried over when navigating from Task Analysis to Stewardship 
  Previously, clicking a chart value in Task Analysis Level 2 to navigate to Stewardship dropped all context — users landed on the default My Tasks view with no filters applied, regardless of what they had selected or clicked. Filters set in Level 2 and the chart-value context (such as clicking a specific trigger source or task status) are now preserved when transitioning to the task queue. This applies across all Task Analysis charts including Task Status Trend, Task Closed Trend, and Closed Task Resolution Reason by Category.

• Task Closed Trend drill-down to Stewardship disabled and clearly labeled
  The Task Closed Trend chart does not support drill-down to Stewardship. Two improvements make this explicit: the Stewardship transition option is now disabled in the chart's detail grid view, and a permanent banner has been added to the chart reading "Drill-down to Stewardship is not available for this chart." This replaces the earlier conditional banner that only appeared when the Close Date filter was active, providing a clearer and more consistent signal to users regardless of the filter state.

Bug Fixes

• Multiple filter behaviors incorrect across Insight reports
  Three separate filter issues in Operational Insights reports have been resolved. In Task Analysis, the Trigger Source filter was returning zero results when filtering on the top sources, and the Match Score filter was returning records below the selected threshold without affecting other KPIs or charts. In User and Usage Analysis, the API Status filter was not constraining chart results or KPIs when a specific status was selected. All three filters now apply correctly across all associated charts and KPIs.