For users creating a HELOC Historical Payment Schedule that includes a teaser rate, Encompass has been updated to enable users to generate a historical table which reflects the percentage of the discount being offered instead of using the actual Teaser Rate (1482). For example, a lender may be offering a Teaser Rate of 6.490%. Based on an 8.500% Adjusted Fully Indexed Rate (3296), this is a 2.01% discount. Therefore, when generating the First Year(s) of the Historical Payment Schedule, the 2.01% discount amount will be used to calculate the rate instead of the approach previously used where the Teaser Rate (1482) in the loan was displayed in the table as a static value (in this sample case, 6.490%).

The purpose behind the update is to keep the current Teaser Rate consistent throughout the teaser term. Teaser Rate is the exact rate the borrower would pay and will not be based on Historical Values.

Starting in Encompass 25.4, the formula for the Teaser Rate period in the Historical Payment Schedule will look at the APR minus the Teaser Rate to figure out the actual Discount. Then, looking back 15 years, it will add the Default Historical Margin and add that to the Index % for the year 15 years in the past. The Discount percentage will be taken from this Historical Margin/Index percentage. This will be the rate shown in the Historical Payment Schedule for the Teaser Rate period. Here is a sample of the logic:

(Updated on 9/26/2025)

To give Encompass desktop interface users the opportunity to pilot enhanced conditions in Production environments, the Encompass field that determines if standard conditions or enhanced conditions will be used in a loan file can now be edited by the Encompass administrator and other authorized users or via a Field Triggers business rule.

This enhancement is intended for lenders who are NOT currently using enhanced conditions in their loans in the Encompass desktop interface. If you are already using enhanced conditions, it is recommended that you do not utilize or edit the enhanced conditions indicator field as described below.

Encompass relies on the hidden enhanced conditions indicator field ENHANCEDCOND.X1 to determine if users are permitted to add an enhanced condition versus a standard condition to a loan (i.e., the field is "hidden" in that it is not provided on any standard Encompass input forms or tools). Only one type of condition may be used, not both. When the field indicates Y [Yes], enhanced conditions may be added. When the field indicates N [No], only standard conditions may be added to the loan. In Encompass 25.4, this field is now editable. With is in mind, the administrator can configure and enable a Field Triggers business rule to populate ENHANCEDCOND.X1 with a Y or N value. For example, a field triggers rule could be set up to set ENHANCEDCOND.X1 to Y [Yes] for a particular branch so that enhanced conditions are used for loans in that branch.

In addition, the ENHANCEDCOND.X1 can be added to a custom input form, which enables users to type/overwrite Y or N in the field to determine the type of conditions that will be used for that individual loan. Note that the recommended best practice is to NOT give access to this field to any other user besides the administrator.

In addition to the business rule, you must set the required policies in Encompass Admin Tools to successfully pilot enhanced conditions in your Encompass instance:

• The default Y/N indicators in the ENHANCEDCOND.X1 field are determined by the Enhanced Condition Workflow and Enhanced Condition Workflow Start Date policy settings in the Encompass Admin Tools. Set the Enhanced Condition Workflow policy to Enabled and set the Enhanced Condition Workflow Start Date to the current or past date. Once these policies are saved/applied in your instance, then ENHANCEDCOND.X1 is set to Y by default, which means enhanced conditions will be used for loans.

  • When the policy is not enabled or the start date has not occurred yet, then ENHANCEDCOND.X1 is set to N and standard conditions will be used for loans. (This field is limited to only one character entry: Y or N.)

  • Example configurations:

    • Enhanced Condition Workflow is set to Disabled: the default indicator in ENHANCEDCOND.X1 is set to N, which means standard conditions are used by default.

    • Enhanced Condition Workflow is set to Enabled AND the Enhanced Condition Workflow Start Date is set to a future date: the default indicator in ENHANCEDCOND.X1 is set to N, which means standard conditions are used by default.

    • Enhanced Condition Workflow is set to Enabled AND the Enhanced Condition Workflow Start Date is equal to or less than today's date; the default indicator in ENHANCEDCOND.X1 is set to Y, which means enhanced conditions are used by default.

Please note:

• The ONLY opportunity to change the ENHANCEDCOND.X1 field once a loan is created is prior to any conditions being added to the loan. The value in ENHANCEDCOND.X1 can only be changed if no conditions have been added to the loan. Once at least one condition has been added to the loan, this field cannot be edited manually or via a Field Triggers business rule. This is true regardless of the current state of the Enhanced Condition Workflow and Enhanced Condition Workflow Start Date policies in Encompass Admin Tools.

  • If a condition has been added to the loan file, but is later removed so there are no longer any conditions in the loan file, users will still be prevented from editing the ENHANCEDCOND.X1 field. This is because the removed condition remains in the Encompass database even though it is not included in the loan anymore.

  • When a condition is added to the loan file, the loan must use that type of condition for the life of the loan. Even if the condition is deleted, that loan remains defined as a standard condition loan or enhanced condition loan.

• On the custom input form(s) where ENHANCEDCOND.X1 has been provided, when the user is not able to edit the field because a condition already exists on the loan, ENHANCEDCOND.X1 will show as deactivated (grayed-out) on the form.

• For Encompass SDK users, when the user is not able to edit the field because a condition already exists on the loan, an exception error will be returned when the business rule runs to try and update the ENHANCEDCOND.X1 field. If the user is running Encompass when the exception is thrown, the exception error will display to the user in Encompass.

(Added 9/26/2025)

A new View Trade Documents button has been added to the Shipping Details tool.

• The button is enabled when the loan is assigned to a Loan Trade and documents have been uploaded to the trade.

• The button will be disabled if the loan is not assigned to a Loan Trade.

• An error message "No Documents available!" will be displayed if no documents have been uploaded to the trade.

When the button is clicked, a document viewer is opened and the user can select and view the documents that have been uploaded to the trade.

(Added on 9/26/2025)

When a Correspondent loan has a buydown and the Correspondent Purchase Advice Form is generated, the Remaining Buydown Amount (field ID 3585) will now be calculated using the following logic when the Update Balances button is clicked.

This calculation will also be triggered when field ID 761 or field ID 4527 is changed.

• Retrieve Relevant Dates

• First Payment Due from Borrower date (field ID 682)

• First Payment Due to Investor date (field ID 3570)

• Calculate the Number of Months

• The number of full calendar months between the two dates identified above.

• Example

Field 682 = April 1

Field 3570 = June 1

Result = 2 full months

• Calculate the Used Subsidy Amount

• Retrieve the Monthly Buydown Subsidy Amount from the applicable fields.

• Fields 3096, 3100, 3104, 3108, 3112, 3116

• For each buydown period:

• Multiply the number of months by the monthly subsidy amount by the number of months that fall within the period.

• Refer to fields 4541, 4542, 4543, 4544, 4545, 4546 for buydown periods and allocations.

• Calculate the Remaining Buydown Amount

• Retrieve the Original Buydown Amount (field ID 3120).

• Subtract the Used Subsidy Amount (identified above) from the original buydown amount.

• Formula:

• Remaining Buydown Amount = Field 3120 - Total Subsidy Used

• Example

If the Monthly Subsidy (Field 3096) = $100 and 2 months have passed.

Remaining Buydown = Field 3120 - (Field 3096 x Number of Months)

3120-200 = $2,920

• Populate the Result

• Display the calculated Remaining Buydown Amount in field 3585 on the Purchase Advice tab of the Correspondent Purchase Advice Form when the Update Balances button is clicked.

• If either field 682 or field 3570 is empty, this calculation will not be triggered and Field 3585 will remain the same as field 3120 when the Update Balances button is clicked.

• If field 682 and field 3570 are the same date, the calculation will be triggered, but Field 3585 will remain the same as field 3120 when the Update Balances button is clicked.

Freddie Mac has retired the Loan Program Identifier, CHOICERenovationMortgageWithRecourse. Therefore, a (Retired) indicator is now displayed after that loan program on the Freddie Mac Additional Data input form and the check box is now deactivated by default so users aren't able to select that loan program for their CHOICE Offering Type (CASASRN.X212).

Note that if this option was already selected in a previous existing loan it will remain selected in those loans.

Freddie Mac recently introduced a new loan level Rep & Warrant for Employment. Therefore, three new editable fields have been added to the Freddie Mac portion of the Rep and Warrant Tracker tool in Encompass:

• Employment Rep and Warrant Indicator (TQL.X287)

• Employment Rep and Warrant Close By Date (TQL.X288)

• Employment Rep and Warrant Comments (TQL.X289)

(Added on 9/26/20205)

As part of the Encompass 25.3 release, a new Documents tab was added to Loan Trades where a user could upload and store a commitment letter. However, the user could not view that letter. As part of this release, the ability to view any document uploaded to the Documents tab has been added.

The supported file types to view documents are jpeg, jpg, png, and pdf.

(Added 9/26/2025)

Currently in Encompass, the error handling within Bid Tape Acquisitions for Create Trade does not display an error message, which makes it difficult for a user to troubleshoot the issue. As part of this release, a new “Error Details” column has been added to the Application Error Log section of the Bid Tape Detail page where the error message itself will now be displayed.

Three additional options are now provided in the Pricing Concession Request Status dropdown field (4791), further enhancing ICE PPE's support of price concessions.

• Requested

• Concession Applied

• Concession Failed

Note that this field is not provided on any standard Encompass input forms. It may be added to a custom input form.

(Updated on 10/21/2025)

The Retrieve Documents workflow already available in the Encompass web interface is now used in the Encompass desktop interface. When users are in the eFolder and navigate to Documents > Retrieve Documents (or when they click the Retrieve or Retrieve Docs button in the eFolder), the new user experience used in the web interface is now used in the desktop interface. This provides an improved user experience with the ability to preview documents prior to retrieval and a list of documents placed within document folders where the retrieved files will be located.

In the new Retrieve screen, select the files or documents to retrieve. When you select a file or document, it is displayed in the preview panel on the right. When your selections are complete, click Retrieve.

Once the retrieve process is completed, the file or document is then added to the File Manager where you can then add it to the applicable document folder (which is the same user experience provided in previous versions of Encompass).

Encompass has been updated to prevent the eConsent Date field (3983) on the Disclosure Tracking Tool's Compliance Timeline from being cleared when the only change made to the borrower or email fields is to use a different upper or lower case character for the value. Prior to Encompass 25.4, the eConsent date field would be cleared if any change was made to a borrower's First Name (4000), Middle Name (4001), Last Name (4002), Suffix (4003), and/or Home Email (1240). These fields were case sensitive, so changes to the case of a letter (i.e., alpha character) would also remove the date from field 3983 and require a new request for eSign consent.

However, it was determined that changing the case in a name or email address after the initial eSign consent has been received should not invalidate the initial eSign consent. Therefore, the system logic has been updated so that eSign consent remains valid even if a letter or letters in a name or email address in the fields mentioned above are changed from upper to lower case, or lower to upper case, after eSign consent is obtained.

In addition to the Borrower fields mentioned above, the same logic is now also used for these Co-Borrower and Non-Borrowing Owner (NBO) fields:

Co-Borrower:

• First Name (4004)

• Middle Name (4005)

• Last Name (4006)

• Suffix (4007)

• Home Email (1268)

NBO:

• First Name (NBOC0101)

• Middle Name (NBOC0102)

• Last Name (NBOC0103)

• Suffix (NBOC0104)

• Home Email (NBOC0111)

The Web Version Settings link provided on the Encompass > Settings > Settings Overview screen can be used to jump to the Encompass web interface from the Encompass desktop interface. In Encompass 25.4 this link has been enhanced so when it's clicked it now logs the administrator into the Encompass Admin settings screen in the Encompass web interface in your default web browser. Prior to this update the link opened to the Encompass Admin settings screen in a stand-alone pop-up window.

The Encompass ZIP Code database has been updated with the latest available ZIP Code data.

Updates have been made in the Encompass web interface to give users in the Encompass web interface the ability to print a document package from within Disclosures, Pre-Closing, Request/Send, and Closing workflows. In addition, the Encompass desktop interface has been updated to give those web interface users the option to create a Disclosure Tracking Tool entry when printing documents. These updates for the web interface bring it up to parity with the Encompass desktop interface where users could already print documents generated within a package, and a Disclosure Tracking Tool entry is created when Encompass settings are configured so that records are created automatically or upon confirmation by a user.

In the Disclosure Tracking Tool when a disclosure document is printed, the Borrower Received Method indicated in the Disclosure Details is set to U.S. Mail by default and the Sent Method is set to U.S. Mail by default. In Encompass 25.4, a new settings option called Printing Web Document Delivery Method Default is now provided (in Encompass Settings > Loan Setup > Disclosure Tracking Settings) that gives administrators the ability to set the default delivery type to U.S. Mail or In Person when a disclosure document is printed in the Encompass web interface. The default value of this new setting is U.S. Mail, which is the current default in the Disclosure Tracking tool. A user (with the required persona access) can edit that record in the disclosure tracking tool and change the sent/received methods manually later if needed (non-Closing workflows only).

In Encompass 25.3, the Send button in the eFolder was changed from a dropdown component to a standard button. As part of this update, the Send Files to Lender... option was removed and is no longer available in Encompass. In previous versions of Encompass, this option was provided to users so they could submit loans to their lenders and investors from the eFolder. This functionality is now provided in Encompass Investor Connect. Users can utilize that application going forward to submit loans to their lenders and investors.

Due to this removal of the Send Files to Lender... option, the Send Files to Lender option that was provided in the Personas settings (on the eFolder tab) used by administrators to manage users' access to this option has been removed since it was no longer applicable.

(Added on 9/26/2025)

Currently in Encompass, an error message "The pricing request violates your administrative settings and cannot be processed." is displayed to prevent users from submitting a relock request via the Search Product and Pricing links (Services tab and Lock icon in Encompass header) or the Product and Pricing button (Borrower Summary Origination screen) when the Only allow Re-Lock (Historical Pricing) when a current lock exists option is enabled on the Product and Pricing setting.

As part of this release, the error message has been removed because your PPE controls the enforcement of historical and current pricing.

(Updated on 10/21/2025)

For users working in loans for an investment property (i.e., the investment property is indicated as the Subject Property (URLA.X73)) and it's being refinanced (19), an issue occurred where the debt-to-income ratio (DTI) in Encompass did not match closely with the DTI returned from Fannie Mae's Desktop Underwriter (DU). It was determined that this was due to Encompass not calculating the Net Income / Loss when calculating the DTI. This issue has been resolved and now the DTIs in this scenario in Encompass and DU closely match. In Encompass, the MORNET.X158 (Top Ratio) and MORNET.X159 (Bottom Ratio) fields and the CASASRN.X201 (Housing Ratios) and CASASRN.X202 (Debt to Income Ratio) fields specific to DTI were updated to match how the GSEs are calculating DTI. Therefore, the Encompass DTI value may now be slightly different from the MORNET and CASASRN DTI values with this change.

The new DTI calculation referenced will be reflected in MORNET.X158 & MORNET.X159 on the Fannie Mae Additional Data Form and CASASRN.X201 & CASASRN.X202 on the Freddie Mac Additional Data Form based on Agency Specific DTI Guidelines.

In previous versions of Encompass, the Closing Disclosure (CD) Page 3's See field (CD3.X123) in the Remarks section (which indicates the sections where fees impacting the Total Closing Costs of the loan have been revised) was not updated when relevant fees on the 2015 Itemization were changed until after the revised CD was disclosed. Thus, the Remarks on the disclosed CD were not up to date, while the Remarks on the CD in Encompass (CD3.X123) were up to date after disclosing. This issue has been fixed so that the Remarks field on the CD Page 3 is now updated accordingly when relevant fees are changed. This new system logic has also been applied to the CD3.X125 and CD3.X131 fields (which are also displayed in the Remarks section of the CD Page 3 when applicable).

After applying any data template to a loan file, the following fields on the Closing Disclosure (CD) Page 3's Adjustments and Other Details pop-up window were being cleared. These fields should not have been cleared.

In Section K: CD3.X139, CD3.X140, CD3.X231, CD3.X232

In Section L: CD3.X290, CD3.X291, CD3.X322, CD3.X323, CD3.X353, CD3.X354

The values that were previously displayed in these fields were printed correctly to the printed CD output form, but they were not displayed in the input screen. This issue has been resolved and the values in these input fields are now retained even when a data template is applied.

The Total Closing Costs Less Guarantee Fee field (VASUMM.X124) on the VA Management input form's Qualification tab is now recalculating as expected when changes are saved in the VA loan and when checkbox fields such as Include Prepaids (VASUMM.X145), Include Initial Escrow Payment at Closing (VASUMM.X146), and all of the other "Include" Closing Cost Recoupment checkboxes on the input form's Qualification tab are manually selected and/or cleared later. An issue was introduced in Encompass 25.1 where this Total Closing Costs Less Guarantee Fee field (VASUMM.X124) was not recalculating when users performed these actions like it should have.

Note that if the user has locked the Total Closing Costs Less Guarantee Fee field (VASUMM.X124) to override the system-calculated values, this field will not be automatically recalculated.

The Encompass system logic for FHA loans for subject properties located in a county within a new Connecticut planning region (introduced in 2022) has been updated to address an issue with the base loan amount (1109) not being recalculated when the down payment percentage (1771) or amount (1335) was updated. Beginning in Encompass 25.4, any time there is a change to the down payment percentage (1771) or amount (1335) for FHA loans with subject properties in a new Connecticut planning region, the base loan amount (1109) will be recalculated accordingly.

This new logic applies to these loans when the Enforce County Loan Limit option (3894) is being used for the loan and when it's not being used (i.e., the new logic applies regardless of the Enforce County Loan Limit checkbox being selected or not selected).

Note that if the Enforce County Loan Limit checkbox (3894) is selected (i.e., FHA county limits are being enforced for the loan), when there is a change to the down payment percentage (1771) or amount (1335), a pop-up notification is provided to explain that ICE is unable to determine the Connecticut FHA loan limits based on the new planning regions and it is the responsibility of the lender to ensure the FHA loan limits do not exceed the loan limits for the specified subject property address. This is existing Encompass behavior introduced in Encompass 25.1.

In the North Carolina State Specific Information input form's Mortgage Broker Fee Information Disclosure section, there was an issue where the amount of fees the borrower will pay to mortgage broker at or before closing (DISCLOSURE.X652) and the flat charge the borrower will pay at closing (DISCLOSURE.X647) were not calculating the correct values. DISCLOSURE.X652 was showing the Broker PAC (paid at closing) amount (instead of the borrower-paid PAC amount) and DISCLOSURE.X647 was showing the borrower-paid PAC amount (instead of the borrower financed amount). This resulted in incorrect values being output to the North Carolina Office of the Commissioner of Banks Fee Information From Your Mortgage Broker printed output form. This issue has been resolved and the correct values are now calculated for these fields when activated:

• DISCLOSURE.X652 = the total of the Borrower-paid PAC and POC amounts from the 2015 Itemization input form where the "Paid To" fields in the 2015 Itemization = "Broker".

• DISCLOSURE.X647 = the total of the borrower Financed amounts from the 2015 Itemization input form where the "Paid To" fields in the 2015 Itemization = "Broker".

Migration Notes:

For existing loans, these fields are not automatically recalculated upon upgrading to Encompass 25.4. These fields will be recalculated when users save any change to the loan or when the user opens the 2015 Itemization input form in the loan (unless the user has locked the fields on the North Carolina State Specific input form to override the system-calculated values).

In Construction to Permanent (19) loans with monthly mortgage insurance (MI) payments, when the Midpoint Payment Cancellation option (1753) in the MIP/PMI/Guarantee Fee Calculation pop-up window was selected, the Amortization Schedule was incorrectly indicating the MI Cancellation occurring at payment 180 instead of payment 190, resulting in the MI falling off from the loan sooner than it should have. This issue has been addressed by updating the Amortization Schedule to use the same calculation logic that determines the PMI Midpoint Cancellation Date (3548). The date calculated for the PMI Midpoint Cancellation Date (3548) is now the date indicated for the MI Cancellation payment date in the Amortization Schedule.

In addition, the PMI Midpoint Cancellation Date (3548) is now included in the Amortization Schedule/View Payment Schedule pop-up window when the Midpoint Payment Cancellation option (1753) is selected in the MIP/PMI/Guarantee Fee Calculation pop-up window.

The calculation for Estimated Construction Interest (4088) for Method B (SYS.X6) has been updated to ensure accurate interest calculations. Previously, Encompass incorrectly calculated the interest period in construction loans when Method B was used, the estimated closing date (763) was on the last day of a month, and the Number of Days (1962) used to calculate the repayment schedule was set to 365/365. This led to potential errors in disclosed interest and proposed monthly payments (5).

With this fix, the system will now correctly determine the interest period based on the Disbursement Date (2553) or Estimated Closing Date (763) if the Disbursement Date is blank.

Migration Notes:

For existing loans that meet all the criteria below, the Estimated Construction Interest field (4088) will be automatically locked to retain its existing value.

• Loan is Construction or Construction to Perm (19)

• Loan has been disclosed or is a non-active loan (1393)

• Est Interest On (SYS.X6) is set to B (Full Loan)

• Number of Days (1962) is set to 365/360 or 365/365.

(Updated on 10/12/2025)

Encompass now populates the HMDA Loan Amount (HMDA.X31) with the loan amount (2) rather than the initial application amount (NMLS.X11) when the loan application is withdrawn or denied for any of the following reasons: (i.e., the Current Status (1393) of the loan is changed to any of these scenarios), there is no counteroffer indicated (4457), and the loan has not been disclosed yet (3152):

• 3 (Application denied)

• 4 (Application withdrawn)

• 5 (File Closed for incompleteness)

• 7 (Preapproval request denied by financial institution)

For reporting on the HMDA LAR, this change ensures that the most recently requested loan amount is reflected in HMDA.X31 rather than the original loan amount when there's a denial on the loan with no counteroffer or the borrower withdraws the application.

Migration Notes:

For existing loans that meet all the criteria below, the Loan Amount field (HMDA.X31) will be automatically locked to retain its existing value.

• The Counteroffer Date field (4457) is empty.

• The Current Status (1393) of the loan is 3 (Application denied), 4 (Application withdrawn), 5 (File Closed for incompleteness), or 7 (Preappoval request denied by financial institution).

• The loan has not been disclosed (i.e., the Initial Disclosure Date field (3152) is empty).

• The loan amount (2) and initial application amount (NMLS.X11) are not the same

Encompass has been updated to accurately calculate the total discount points that a borrower is financing for VA IRRRL loans on the VA 26-1820 Loan Disbursement input form. Previously, the Discount Points Financed (for IRRRL Only) field on line 15 was calculated with field VARRRWS.X3 which calculates the principal amount to be refinanced (VARRRWS.X2) multiplied by the discount rate (VARRRWS.X9). Since field VARRRWS.X2 is derived from the existing loan and not the new loan, VARRRWS.X3 should not have been used for line 15 because line 15 represents the financed discount points amount based on the new loan.

To ensure that the discount points financed amount also considers if the loan is a VA IRRRL, the Discount Points Financed (for IRRRL Only) field on line 15 is now field VARRRWS.X8. This field takes the discount percentage rate (VARRRWS.X9) and multiplies it by the value in VARRRWS.X7, which is derived from the new loan and is used specifically for VA IRRRL.

CBIZ-65794

The Interest Rate field (URLARAL0026) in the Other Financial Payment Calculation pop-up window that is provided when you click the Edit icon for the Monthly Principal And Interest field (URLARAL0118) on the Verification of Additional Liabilities (VOAL) input form had an issue where users could type an Interest Rate value up to three decimals, but after closing the pop-up window and then reopening it later, the value would be rounded to two decimal points. For example, 2.875% would be rounded to 2.88%. This change caused the monthly payment in the pop-up window to recalculate, which resulted in an incorrect Monthly Principal and Interest payment on the VOAL.

The same rounding issue occurred with the Interest Rate field (URLARAL0029) in the Other Financial Payment Calculation pop-up window that is provided when you click the Edit icon for the Monthly Principal And Interest Within 5 Years field (URLARAL0118).

Both of these Interest Rate fields have been updated to retain the intended three decimal point value and no longer round to two decimal points. Note that Interest Rate values entered in these fields that are below three decimal points or above three decimal points are now rounded to three decimal points.

In loan scenarios when an ARM loan's first adjustment period is over 1 (one) year and there are 2 (two) or more principal and interest (P&I) changes within the first column period, the minimum and maximum payments are now accurately reflected in the Mavent Compliance Reports and printed output forms where Projected Payments table is provided. Previously only one P&I payment was displayed for Years 1-6 in the reports and printed output forms.

For example, there's an ARM loan that has a 62-month initial fixed interest rate period with a subsequent 6-month change(s). This means after the initial rate change in month 62, the rate may change again in month 68. In this loan, the initial column of the Projected Payments Table covers Years 1-6 (5 years = 60 months and 6 years = 72 months). After the initial 62-month fixed rate period, the rate "may" change every six months thereafter until the lifetime rate limitation is reached. If multiple changes to periodic principal and interest payments result in more than one separate periodic payment or range of payments in a single year, § 1026.37(c)(1)(iii)(B) requires the creditor to disclose the range of payments that would apply during the year in which the events occur. Comment 37(c)(1)(iii)(B)-1. As a result, for the first column of the Projected Payments Table, Encompass now displays a minimum and maximum range of payments. (This update now ensures the Years 1 - 6 Projected Payments in Encompass match the payments returned by the Mavent Compliance Report.)

In previous versions of Encompass, when a Good Faith Fee Variance Violated alert was triggered due to a user changing a disclosed transfer tax fee to a higher amount, Encompass allowed users to clear this alert by providing a Change of Circumstance (LE1.X81 or CD1.X61) with an 'Interest Rate Dependent Charges (Rate Lock)' reason. However, the alert should have remained active for the loan since Transfer Tax increases should only clear the alert when the Change of Circumstance reason is any of the following:

• Changed Circumstance - Settlement Charges

• Changed Circumstance - Eligibility

• Revisions request by the Consumer

• Expiration (Intent to Proceed received after 10 days)

• Delayed Settlement on Construction Loans

Since the alert was cleared without a valid Change of Circumstance reason, the loan could be out of compliance since the user was not alerted or compelled to redisclose the fee change with a valid Change of Circumstance.

Starting in Encompass 25.4, when the Loan Estimate (LE) or Closing Disclosure (CD) with increased transfer taxes in the 0% category is disclosed with "Interest Rate Dependent Charges (Rate Lock)" as the only reason and the increase in transfer taxes is the only fee increase driving the increase in that category, the Good Faith Fee Variance Violated alert will not be cleared from the loan and the LE or CD baseline in the "Charges that cannot Increase" will not be updated with that disclosure information.

(Added on 9/26/2025)

An issue occurred where the Buy Side Pricing and adjustments on the Secondary Lock Tool were not updated when a Loan Officer made changes to a loan and then clicked on the Validate Pricing button on the Lock Comparison Tool.

This issue occurred when Auto-Lock enabled.

This issue has been resolved. The Buy Side Lock Request and Buy Side Lock and Pricing columns are now updated when the Validate Pricing button is selected.

In Encompass 25.1, Encompass was updated to automatically populate the value in the FRE Condominium Project Identifier field (CASASRN.X221) to the CPA Project Assessment Request Identifier field (ULDD.FRE.X1). However, it was determined that the FRE Condominium Project Identifier is the incorrect value to populate to the CPA Project Assessment Request Identifier field. Therefore, this field mapping logic has been rolled back and this auto-population of field CASASRN.X221's value to ULDD.FRE.X1 no longer occurs.

Per the ULDD Field Mapping Guide, ULDD.FRE.X1 is intended for the Project Assessment Results # from the Condo Project Advisor Feedback Certificate.

When adding a large number of enhanced conditions (30+) at once to a loan file from the eFolder, it could take Encompass up to 60 seconds to complete this operation. Updates have been made in Encompass to reduce the time it takes to add a large number of enhanced conditions at once to a loan.

When working with enhanced conditions on the eFolder's Conditions tab, users can click the New icon to select and add one or more conditions from the Conditions list to add to the tab. An issue occurred in the Add Conditions: Conditions List pop-up window where users could filter the conditions displayed in the list (based on the condition name, condition type, category, etc.) and then select the checkbox to select all of the conditions listed in the filtered list intending to add these conditions to the Conditions tab, but instead of only these filtered conditions being added, all of the conditions available to add to the loan were added to the Conditions tab. This issue has been resolved and now only the conditions selected in the list displayed to the user are added to the Conditions tab as expected.

After importing an enhanced condition from an integrated service provider in the Encompass web interface, the internal description and external description for the condition displayed correctly when viewing the Conditions page within the loan in the Encompass web interface, but they did not display at all when viewing the loan's conditions on the Conditions tab in the eFolder in the Encompass desktop interface. These descriptions for the imported conditions were also not displayed for administrators viewing the Conditions list in the Encompass Settings > eFolder Setup > Enhanced Conditions settings. The cause of this issue with the missing descriptions was addressed and this issue is now fixed. The descriptions for these imported enhanced conditions are now displayed as expected in the Internal Description and External Description columns for the condition on the eFolder's Conditions tab and on the Enhanced Conditions settings screen in the Encompass desktop interface.

Note that this issue only occurred for enhanced conditions that had been mapped to a Condition Template and the condition finding description had been appended to the internal or external description fields. (This mapping is performed on the Encompass web interface's Services Management > Condition Mapping page.)

(Added on 10/12/2025)

Users in Encompass instances that use the Status Online tool to send loan status updates to borrowers or partners had an issue where, after sending the email message, an error message was triggered indicating that "One or more errors occurred. Do you wish to retry sending the email?" Even though the email was sent successfully, the error message caused confusion since it indicated that there were issues when sending it. This issue has been fixed. The error message is no longer inadvertently triggered and the email sent via the Status Online tool continues to be sent successfully.

An issue occurred with the Buydown field (425) on the 1003 URLA - Lender input form and Field Triggers business rules. In scenarios where a Field Triggers business rule is configured to populate a value (such as 'Seller') to the Contributor field (CASASRN.X141) for the buydown mortgage when the Buydown checkbox (425) was selected, the Lookup [magnifying glass] icon for the Buydown Type (4645) was not working. Users could click the icon, but the expected pop-up window where users can select the buydown type to use for the loan was not displayed. (Users access this icon by clicking the Buydown checkbox's Edit icon to open the Buydown Mortgage pop-up window.)

This issue is now fixed, and the Lookup (magnifying glass) icon is now working as expected in this scenario.

(Added on 9/25/2025)

An issue occurred where the .csv file was blank when a Bid Tape's details were exported using the Export icon on the Bid Tape Detail page. This issue has been resolved. The Bid Tape's details displayed on the Bid Tape Detail page are now exported into a .csv file when the Export icon is clicked.