DATE:
AUTHOR:
The Cotality LoanSafe Team
TABLE OF CONTENTS:
    Enhancements
    Product Updates

    LoanSafe | Product Release

    DATE:
    AUTHOR: The Cotality LoanSafe Team
    TABLE OF CONTENTS:

      Production deployment on May 11, 2026. This document provides information regarding enhancements in Release 052605 of the LoanSafe Suite.

      Enhancements

      1. Update suppression logic for WAT_034, WAT_035 and WAT_036

      2. Add 3 data elements from the MERS response to the LoanSafe report

      3. Apply DOB match logic to client watchlist


      1. Update to Watchlist Alert Suppression Logic (WAT_034, WAT_035, WAT_036)

      When a third-party name hits a custom watchlist record, and the category in that record matches the WATCHLIST_CATEGORIES configured in the system for the alert service ID, WAT_034 or WAT_035 (whichever is configured) will fire.

      If the same third-party name also matches other custom watchlist records whose categories are not configured in the system WATCHLIST_CATEGORIES, WAT_023 will also fire for those non‑configured categories (instead of being suppressed).

      When a Borrower name hits a custom watchlist record and the category matches WATCHLIST_CATEGORIES in the system for the alert service ID, WAT_036 will fire.

      If the same Borrower name also matches other entries whose categories are not configured in WATCHLIST_CATEGORIES, WAT_018 will also fire for those non‑configured categories.

      This change corrects behavior observed in production where WAT_036 fired but WAT_018 did not, even though the name matched additional watchlist entries; the updated logic ensures all appropriate alerts are raised rather than over‑suppressed.


      2. Add MERS Data Elements to the Loan Registry Section

      Three additional MERS data elements are now displayed in the Loan Registry section of the LoanSafe report, allowing users to more accurately review REO details for a borrower. When a MERS response is present, the report will now show the Registration Date, Lien Priority Type, and Owner Occupied Indicator alongside the existing Loan Registry information, and these values are also exposed in the XML and hidden tags for downstream integrations and audit.

      How It Works:

      • When a MERS response is returned and you view the Loan Registry section of the LoanSafe report, the following fields now appear, in addition to what was already there today:

        • Registration Date (from MERSRegistrationDate)

        • Lien Priority Type (from LienPriorityType)

        • Owner Occupied Indicator (from OwnerOccupiedIndicator)

      • These fields are mapped into the LoanSafe XML under LoanRegistryRecord attributes:

        • @registrationDate → Registration Date

        • @lienPriorityType → Lien Priority Type

        • @ownerOccupiedIndicator → Owner Occupied Indicator

      • Each value is also written to a dedicated hidden tag for downstream use and reporting:

        • IDP_LOAN_REG_REGISTRATION_DATE#

        • IDP_LOAN_REG_LIEN_PRIORITY_TYPE#

        • IDP_LOAN_REG_OWNER_OCCUPIED_INDICATOR#


      3. Apply DOB Match Logic to Client Watchlist

      Date‑of‑birth (DOB) matching has been added to the client watchlist evaluation for WAT_018 so that alerts are raised only when both the name and DOB match between the borrower and the client’s watchlist entry. This change reduces false positives for clients using a client watchlist in LoanSafe by ensuring that WAT_018 is suppressed when the borrower’s DOB does NOT match the DOB stored on the corresponding client watchlist record, while preserving existing behavior for scenarios where no DOB is present on the watchlist.

      How It Works:

      When a LoanSafe request is processed and the client has a client watchlist configured that includes a date of birth, the system first performs the existing name match check between the borrower(s) and the watchlist entry.

      If a name match is found and the watchlist record contains a DOB, that DOB is now compared to the borrower’s input DOB:

      • If the DOB matches, WAT_018 fires as a valid client watchlist hit.

      • If the DOB does not match, WAT_018 is suppressed for that watchlist record, avoiding a false positive.

      When the watchlist entry does not have a DOB, the system continues to behave as before (name‑only logic applies and WAT_018 may fire based on the existing matching rules.


      Note: Because the LoanSafe Suite comprises LoanSafe Risk Manager, Fraud Manager and Collateral Manager, all changes and additions apply to all versions of the LoanSafe report unless otherwise noted.

      For more information on this release, contact your account representative or email [email protected].

      TABLE OF CONTENTS:
        Powered by LaunchNotes