Improved watchlist matching for Unknown inquiries

We improved watchlist matching for inquiries submitted with the inquiry type Unknown. Unknown inquiries that are classified as an organization are now also checked for an exact person name match against watchlists. This improvement applies to initial screening, with Portfolio Monitoring support to follow.

Improved visibility into batch and inquiry processing status

We are enhancing how batch and inquiry statuses are reported so that you have a clearer, more accurate view of your processing results. If batch processing fails, the batch will be marked with a new Failed status that is be reflected wherever batch and inquiry statuses are shown. A Failed status shows as soon as processing fails due to an error or timeout, providing a more precise picture of batch and inquiry states than the Processing status. If a failed batch had replaced an earlier submission under the same tracking ID, the earlier submission is automatically restored so your records reflect the last valid state.  

This change gives you more immediate insight into your batch processing without needing to reach out to support. No action is required on your end to take advantage of this improvement. The new Failed status is available alongside the batch and inquiry status values you already use today.

Expanded name length support for subject iList uploads

This release increases the character limits for person and organization names in iList uploads.

• The character limit for person names and person alias names is now 128 characters
• The character limit for organization names and organization alias names is now 350 characters. 

This update enables you to submit longer legal names that may exceed the previous limits. If a submitted name exceeds the new limit, the system continues to provide an error message listing the specific entry that exceeded the limit, making it easy to review and correct. No action is required on your part to take advantage of these expanded limits, as they will be applied automatically.

Erased inquiries are now read-only during batch review

We've improved how deleted inquiries are handled during batch review. Previously, a deleted inquiry could still show clickable Review, Reassign, or Stop options in the Alert Decisioning screens. With this release, deleted inquiries are now shown as DELETED and are read-only, so that match decisions cannot be changed. In addition, batches now automatically complete and cannot be reopened when all of their inquiries have been deleted. 

Deleted inquiries remain visible and are still included in counts and reports, so your records stay complete and accurate. Non-deleted inquiries are unaffected by this change.

Enhanced event coverage per entity profile

As part of our ongoing effort to refine our baseline filtering methodology, we have expanded the depth of event coverage available per entity profile across Grid output channels. This means that you now have access to a more comprehensive view of screening events when reviewing entity risk profiles in the screening UI, case reports, PDF exports, response files, and API responses.

Previously, event visibility could vary across channels due to system-specific event limits. This update removes those differences and may expand the volume of events shown within your existing matching and ranking logic. It improves the consistency and depth of what you see, without changing how events are selected or prioritized.

The actual number of events displayed depends on the volume of relevant events available for your firm's configuration. For entities with additional events beyond previous count limits, this update makes those events visible to you. This enhancement is reflected across Grid output channels, so the experience is aligned regardless of how you access your data.

No action is required. This update is applied automatically, and there are no changes to your workflows, integrations, or firm configuration.