We've refreshed the Grid web interface to be faster and easier to use, with a number of improvements across search, account access, and review workflows. You'll notice a cleaner layout and quicker ways to search, filter, and reset your view, along with several accuracy fixes across the platform to keep results consistent. Account access and recovery are now more secure and self-service as well.

None of this changes your underlying data, saved searches, or results; your searches, portfolios, and audit history all carry over exactly as they were. A handful of items noted below depend on firm and/or user-level permissions, including some Alert Decisioning changes limited to firms with iCAD enabled. Here's what's changed.

Getting around

We've streamlined navigation across the Grid web interface. The Home button has been removed and the Grid logo now takes you to your first tab, just as before. Switch Firm, Change Password, and Log Out are now combined into a single account menu, in the top right. Help is now represented by a ? icon that opens the Maxsight help center, which contains Grid documentation, in a new tab.

Date and time display

Times now appear in 24-hour format, shown in your browser's local timezone. Date formats now default based on your environment: day/month/year (D/M/YYYY) for EU and India environments, month/day/year (M/D/YYYY) for US — unless you've set a personal preference, which always takes priority.

A more secure, self-service sign-in experience

• A show/hide toggle has been added to the password field on the login page.
• If a sign-in attempt fails, you'll see a warning showing how many attempts remain, along with a prompt toward Forgot Password starting on your third attempt. After five failed attempts, you're taken directly to Forgot Password to reset and unlock your account.
• Requesting a password reset now sends a secure, single-use link valid for 15 minutes, rather than a temporary password. Forgot Password asks for your username and email together, and always shows the same neutral message regardless of whether they match a record on file.
• New users receive a secure activation link (valid for 12 hours) instead of an emailed username and temporary password, and land on a dedicated activation page to set their password. If that link expires, simply use the link to navigate to the login page and click Forgot Password to create a password.
• Show/hide toggles have been added to the password fields on both the reset and activation pages.

Faster search and filtering

• Search boxes have been added to dropdown menus throughout the application, including event filters, user-assignment fields, and the country field on the New Search Form.
• A Clear Form button on ID Lookup and the Search pages clears your inputs and results in one click.
• A Reset button on filter-heavy pages restores your default filters rather than blanking them out.
• A copy icon next to key identifier fields lets you copy a value without selecting the text manually.
• A page-size selector (20 / 50 / 100 per page) is now available on results pages and the main Search tab.
• Your last-entered country is remembered for the session, so new address blocks pre-fills the country field automatically in the New Search Form.
• Date of Birth, Year of Birth, and Age fields on the New Search Form are now mutually exclusive; entering a value in one clears the others.
• Spreadsheet upload templates now reflect your date format preference, and uploads are checked against that format.
• Exact Name Match (formerly Exact Match) now returns only results with a name-match score of 100, so you see true exact matches right away.
• The multi-column Sort by dropdowns in Search no longer allow the same column to be selected twice; clear a selection with the "x" button. 
• Sortable columns across results tables now show a sort icon.

Review and Client Alert Decisioning

For firms with iCAD enabled:

• A Review Count column has been added to Status by Batch, reflecting the number of inquiry reviews in a batch. 
• The Batch Type column has been renamed Type.
• Inquiry Notes are accessible via a Show/Hide toggle.
• Aliases and addresses use Show more/Show less to keep long lists compact.
• New tooltips on the dashboard and Assigned Reviews explain review-count definitions, how "Unassigned" works, and how to search the Inquiry Name column, including wildcard usage.
• You can now sort inquiry review pages by Entity ID, Risk Priority, and Risk Score, and sortable columns show a sort icon.

Portfolio management

Portfolio search results now use inquiry ID as a secondary sort, so entities with matching names appear in a consistent order every time.

Admin

The Total Reader License line has been removed from Contact Search, along with the Reader License and Request Reader License checkboxes. Send Reset Email now sends only to the email address on file for the contact.

Audit

The Audit tab now loads your firm's filter profile audit history for the past 3 years automatically. No need to click Search first. CVIP audits still require a CVIP selection and Search.

No action is required for any of the above. If you have questions, contact clientservices@moodys.com.

Readers License access is now enabled across firms 
We've simplified access to full-text source articles under a Readers License. Every firm and user now has this access by default with no additional configuration required.

Previously, access depended on a mix of settings that could occasionally disagree with one another. Now that access is enabled for everyone automatically, that inconsistency is gone. 

User permission changes now take effect immediately

Previously, changes to account permissions did not interrupt a current Grid session; the system continued running under the old permissions until the session expired. Now, changes to your permissions will end your active session right away, and you'll be asked to log in again. New permissions take effect with the next login after a voluntary or involuntary logout. This applies to all clients, including those who log in via SSO.

Updated country name: Republic of North Macedonia

We have updated the country name shown throughout the platform from The Former Yugoslav Republic of Macedonia to its current official name, Republic of North Macedonia.

This change means that any entity, account, or search result associated with this country will now display the updated, internationally recognized name. You do not need to take any action. The update will appear automatically and will not affect any of your existing data or configurations.

Moody's is notifying clients that Batch ID values will soon exceed the range of a 32-bit integer.

What's changing

Batch ID values will grow beyond the range that fits in a standard 32-bit integer (values above 2,147,483,647). This affects every delivery channel where Batch ID is provided, including the API (SOAP and REST), SFTP response files (both XML and pipe-delimited formats), and reports. 

Based on current volumes, Batch ID values are expected to exceed the 32-bit limit in December 2026. Moody's expects to have all supporting changes deployed by end of August 2026; this deployment does not change the format or values you receive today. Values will grow naturally as volumes increase.

Who this affects

Any integration that stores or parses the Batch ID field using a 32-bit integer type (for example, int in Java/C#, or a database column defined as INT/INTEGER). This includes Batch ID appearing in API responses, SFTP response file headers, and SFTP pipe-delimited alert records (where Batch ID is part of nearly every row, not just the header). Once Batch ID values exceed the 32-bit limit, these integrations may encounter errors, truncated values, or data corruption.

What to do

Prior to October 31, 2026:

• Review how your integration stores and parses the Batch ID field across all channels you use (API, SFTP response files, reports).
• Confirm that storage (database columns, variables, message formats) uses a 64-bit integer type (e.g., BIGINT, long, Long, Int64) rather than a 32-bit type.
• If you consume SFTP pipe-delimited response files, confirm your parsing of the compound alert-record key (Batch ID plus Inquiry ID) also supports the larger value.
• If you generate code from Moody's Swagger definitions or from a service's live WSDL endpoint, confirm the generated types and your downstream storage use 64-bit integer or string types, or you can regenerate after Moody's deployment completes. 
• Test your parsing and storage with a synthetic Batch ID value greater than 2,147,483,647 (e.g., 3,000,000,000).

Timeline

• Act now. This change is safe to make immediately and does not depend on any Moody's deployment. Updating early removes the risk entirely.
• Complete and confirm your updates no later than October 31, 2026. Treat this as a backstop, not a target. It exists to leave buffer before the projected crossover, and waiting until Q4 risks colliding with your own year-end change-freeze windows.
• Based on current volumes, Batch ID values are projected to exceed the 32-bit limit in December 2026. This projection can move earlier if volumes grow; it is not a guaranteed date.
• No action is required if your integration already uses 64-bit types.

Questions? Contact your Moody's account representative or support team.

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.

Increased Grid v1 and v2 API address character limits

The Grid API now accepts up to 255 characters for address fields, including city, country, address line, and region/state/province. 

Improved Grid v1 and v2 API Swagger code sample accuracy

The Grid Swagger documentation for both API v1 and API v2 has been updated to more accurately reflect response payloads from Grid endpoints. Field names and response samples have been updated to give you a clear, reliable reference when building and maintaining your integrations. 

With more complete and accurate field definitions, you can streamline code generation and spend less time cross-referencing live API responses. This improvement also supports smoother onboarding for new integration work.

Monthly Portfolio Report: multiple address support

Effective with the July 10th report, the Monthly Portfolio Report delivered to your SFTP dropzone now includes all addresses on file for an inquiry, including inquiries that have more than one address. Previously, address data was not included for inquiries with multiple addresses.

What is changing

The report now supports up to three addresses per inquiry. The original first-address columns remain unchanged, and new columns have been added for the second and third addresses:

• First address: address, city, state_province, country, postal_code
• Second address: address2, city2, state_province2, country2, postal_code2
• Third address: address3, city3, state_province3, country3, postal_code3

When an inquiry has fewer than three addresses, the unused columns are left blank so that every report follows the same consistent structure.

What you need to do

If you process the report automatically, please confirm that your import or parsing handles the additional address columns. The original first-address column names have been preserved to minimize impact on existing processes. No action is needed to begin receiving the additional address data. It will appear automatically starting with the July 10th report.

The Grid web interface will be getting a refreshed look on August 20. Here's what's changing and what stays exactly the same.

What's new

• A more modern look and feel across the application.
• An improved sign-in and account recovery experience.

This is mostly a visual update, not a change to how you work.

What stays the same

• The URL stays the same, so you can reach the new application just as you do today once it goes live.
• You'll sign in with the same credentials you use today.
• Your workflows, features, and saved work are unchanged.
• None of your data is affected.

Preview

A preview of the new Grid web interface. This view may change slightly before launch.

A preview of the new Batches For Review page. This view may change slightly before launch.

Want a video preview of the new UI? Open the Resource Center in the web interface and look under the Resources tab.

Questions

If you have any questions or concerns, contact clientservices@moodys.com.

Improved Search on Inquiry Full History page

We've made improvements to the Inquiry Full History search page in Review to help you get faster, more reliable results. Going forward, searches will require a  Name, Tracking ID, Reporting ID, or the newly added Inquiry ID, in addition to a date range. This change prevents searches from timing out due to overly broad queries. If you search without an identifier, you'll see a prompt guiding you to add one. The new Inquiry ID field allows you to look up a specific inquiry by its exact ID. Other existing search options and wildcard behavior remain the same.

Name-matching system recognizes additional organization language tokens

This release enhances organization name matching by expanding the set of recognized entity-type phrases for the following countries: Australia, Belarus, India, Japan, Kazakhstan, Kyrgyzstan, Romania, Russia, Ukraine, United Arab Emirates, United Kingdom, United States, and Vietnam. Those phrases are treated as common organization tokens rather than as part of the core name, which improves consistency and recall when tokens appear in different forms in inquiries. 

We compared pre-implementation and post-implementation behavior on an analyst-reviewed sample of organization-name matches. In that sample, post-implementation recall ranged from about 99% to 100%. The following table shows the improvement in recall (in percentage points) for each country we have validated so far, compared with the prior configuration on the same reviewed sample.

For a full list of recognized organization tokens, reach out to your Moody's representative.

Pagination update for easier navigation

We’ve improved how you move through large sets of results in the Review UI. Instead of choosing a page from a long list, you can now type the page number and press Enter. From there, you can use the first/previous/next/last arrows to move through pages. This update helps pages load and navigate more reliably when you’re working with large result sets.

Name-matching system recognizes additional organization language tokens

This release enhances organization name matching by expanding the set of recognized entity-type phrases across Belgian, French, Latvian, Lebanese, Lithuanian, Venezuelan, Irish, and Chinese names. As a result, organizations will match more reliably and accurately even when these tokens are added, removed, or abbreviated. For a full list of recognized organization tokens, reach out to your Moody's representative.

Improved organization token stripping for Chinese and Japanese names

We improved handling of Han character organization tokens (e.g., 有限公司, 株式会社) that appear directly adjacent to other Han characters with no intervening space, as is common in Chinese and Japanese. These organization tokens will now be properly stripped when directly adjacent to other Han characters.

Name-matching system recognizes additional Dutch organization tokens

The name-matching system for organizations now recognizes a broader set of Dutch entity-type phrases as organization tokens. These additional entity-type phrases will be treated as common organization tokens rather than as part of the organization’s distinctive name. This enhancement improves precision, consistency, and recall for organization name matching when these tokens are present or absent in search inquiries.

Update Alert Decisioning Reports with Reasons for Bulk Close

Client Alert Decisioning reports now include a new Bulk Close Reason column that displays the reason entered when alerts are closed using the Bulk Close action. This makes it easier to understand and audit why alerts and batches were bulk closed in reports.

iCAD Enhancement

We’ve updated how review completion is reflected in batch metrics so that Incomplete Reviews counts display more accurately. If your process includes reassigning inquiries with completed reviews to another group or queue, the inquiry appears as not completed in the batch metrics, but the decision is still saved and retained for review.

Inquiry Full History Enhancement 

We’ve improved the reliability of Inquiry Full History searches, helping you complete high-volume searches more consistently. 

Improved critical watchlist person matching for hyphenated names

We fixed an edge case in the secondary critical watchlist person search, where hyphens retained during name analysis could prevent a secondary match that the primary search also missed. This improvement applies to inquiry and portfolio monitoring searches.