LoanSafe | Product Release 10/14/2025

Targeted for production deployment in the early morning (1 a.m. PT) Oct. 14, 2025, this document provides information regarding enhancements in Release 102510 of the LoanSafe Suite.

Contents:

Bug Fixes

• Use the load_id for the “As of Search Date”

• New URLA fields are not persisting properly

• Military Entitlements should be displayed as a monthly value

• Borrower Assets field must not allow exponential notation

• LoanSafe Risk Manager fails when SUBJ_ASSET_IS_DEPOSITED is empty

Bug Fixes

Use the load_id for the “As of Search Date”

LoanSafe displays the “As of Search Date” for each watchlist to improve transparency. Previously, this date was based on the database’s update timestamp. However, we identified an issue: when a watchlist fails to load, the update date reflects the failed attempt, not the last successful load. To address this, LoanSafe now uses the load_id date, which accurately represents the most recent successful watchlist load.

New URLA fields are not persisting properly

Resolved an issue where empty fields in the Uniform Residential Loan Application (URLA) were not persisting correctly. Fields left blank in the request will now populate as NULL in the database, ensuring consistent data handling and downstream reporting accuracy.

Military Entitlements should be displayed as a monthly value

Military Entitlements were not previously converted to monthly when the income period in the request was not monthly. To ensure consistency and accuracy, the logic has been updated to convert Military Entitlements to a monthly value before including them in the total income.

Borrower Assets field must not allow exponential notation

It was discovered that the OTHERASSET_TOTAL_AMOUNT field was accepting values in exponential notation. To maintain data integrity and ensure consistent formatting, the field has been updated to reject exponential notation and only accept standard numeric values.

LoanSafe Risk Manager fails when SUBJ_ASSET_IS_DEPOSITED is empty

Previously, LoanSafe Risk Manager would fail when the SUBJ_ASSET_IS_DEPOSITED field was left empty in the request. This issue has been resolved, and LoanSafe Risk Manager now handles empty values gracefully without causing a failure.

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].