Fixed Issues for Version 21.3 (Broker Edition)

An issue occurred where the MI Prepaid Amount (field 3971) in the MIP/PMI/Guarantee Fee Calculation pop-up window was not included in the Total of Payments field (field ID CD5.X1) on the Closing Disclosure (CD Page 5). Specifically, if MI values had been entered in fields 3971 (MI prepaid amount), 1209 (months of MI premiums due at closing), and 2978 (Prepaid MI checkbox) in the MIP/PMI/Guarantee Fee Calculation pop-up window, and then a loan team member later updated fields 1209 or 2978 on the RegZ – CD input form instead of the pop-up window, the Total of Payments field (field ID CD5.X1) was not updating to reflect the updated MI Prepaid Amount (field ID 3971). This issue has been resolved so that the Total of Payments field now correctly reflects the most current MI Prepaid Amount value.

Workaround Description:

The following workaround was provided for this production issue and is no longer required for Encompass 21.3 and later.

• Open the MI calculator popup and click OK.

An issue occurred with VA loans and conflicting tax amounts. When users clicked the Edit icon for the Property Taxes field (field ID 1405) and then selected the Override with Taxes from Itemization checkbox in the Taxes pop-up window to populate the tax amounts to use, these amounts were not calculated correctly for the Total Proposed Monthly Payment (PITI) field (field ID VASUMM.X99). The tax amounts were being duplicated and the amounts were doubled, which resulted in an incorrect value in field VASUMM.X99.

Additionally, the system was not calculating tax amounts in this Taxes pop-up window (fields 1007 – 1009) if the tax description included the word “Tax”.

These issues have been addressed so that VASUMM.X99 now calculates these tax amounts correctly in this scenario.

Workaround Description:

The following workaround was provided for this production issue and is no longer required for Encompass 21.3 and later.

• User needs to lock VASUMM.X99 in order to enter the correct value manually.

An issue occurred for certain users with the Fannie Mae Additional Data input form. When a Data Template was applied to the loan file, and the Use 2018 DI checkbox (field ID 4142) was selected in the template, this field caused the following error to be triggered when users tried to open the Fannie Mae Additional Data input form:

An error has occurred on the form: Object reference not set to an instance of an object.

This issue has been resolved so that the error is no longer triggered for loans using a Data Template with field 4142 selected.

Workaround Description:

The following workaround was provided for this production issue and is no longer required for Encompass 21.3 and later.

• Unlock field 4142 in the loan template and apply to loan file.

An issue occurred when changing the MIP Refund amount (field ID 1134) in the loan. After entering an MIP Refund amount for the first time, the same amount was populated correctly on the 1003 URLA – Lender form (Section L) correctly. However, if the MIP Refund amount was changed, a second MIP Refund amount was populated to the 1003 URLA – Lender form (Section L). If this amount was changed again, a third MIP Refund amount was populated to the 1003 URLA – Lender form (Section L), and so on.

This issue has been resolved so that only one MI Premium Refund amount (i.e., the current value in field 1134) is populated to the 1003 URLA - Lender form (Section L).

When working with enhanced disclosures, the Disclosure Tracking Tool now indicates the Provider of the disclosure in the Disclosure Details window as Other when the enhanced disclosure is sent via a method other than an eDisclosure package, eClose, or Closing Documents package in Encompass. (This field is set automatically and it cannot be changed by a user.) An additional field is provided where an additional description of the provider may be provided. This field can be updated by the user or it can be left blank.

For loans using the using the 1003 URLA Part 2 input form, an issue occurred where changes to the Monthly Income (or Loss) field (field ID FE0156) were not being applied to the gross monthly Base Income field (field ID 101). Specifically, if the Check if you are the Business Owner or Self-Employed checkbox (field ID FE0115) on 1003 URLA Part 2 was selected, and a value was entered in the Monthly Income (or Loss) field (field ID FE0156), the monthly income value was reflected correctly in the Base Income field (field ID 101). However, if the Check if you are the Business Owner or Self-Employed checkbox (field ID FE0115) was then cleared, which results in the Monthly Income (or Loss) field (field ID FE0156) being cleared as well, then the Base Income field (field ID 101) would not be cleared and/or recalculated. Since field 101 was not recalculating, debt-to-income ratio values were also not recalculated. This issue has been resolved so that field 101 is now recalculated correctly when fields FE0156 and FE0115 are updated.

An issue occurred where the value in Line H (field ID 1073) on the 1003 URLA – Lender input form was different than the Line H value displayed on the printed URLA Lender output form. The correct value for Line H was correct on the printed form, but incorrect on the loan’s input form. The cause of this issue with field 1073 on in the input form has been identified and the issue has been addressed so that Line H is now calculated correctly and the final amount is displayed correctly on the input form and printed output form.

Workaround Description:

The following workaround was provided for this production issue and is no longer required for Encompass 21.3 and later.

• When the applicable values are entered in the loan, users can re-open the loan file and save changes again or click one of the Fee Details button on the 2015 Itemization input form.

An issue occurred where data was not syncing correctly between URLA.X197 (Borrower’s Mailing Street Address) on the 1003 URLA Part 1 and field 1416 (Borrower’s Mailing Street Address) on the Loan Estimate Page 1 and Closing Disclosure Page 1 input forms. If the Same as Current checkbox (field 1819) was selected in the Mailing Address section found on the 1003 URLA Part 1 input form and an update is later made to the current Address field (field ID FR0126), this address change is not reflected in field 1416. This issue has been resolved so that the current address is displayed correctly in the address fields on the 1003 URLA Part 1 and the LE Page 1 and CD Page 1 input forms.

An issue occurred where when using the new 1003 URLA forms, where Supplemental Property Insurance (field ID URLA.X144) on the 1003 URLA – Lender input form is not included in the calculation for the Estimated Monthly Shelter Expenses (line 21, field ID 1348) on the VA 26-6393 Loan Analysis input form. Instead, field 1348 is calculating only the Subordinate Lien monthly payment amount and the HOA Dues. (When using the 2009 URLA forms, field 1348 included the Flood Insurance amount from line 1006.) This issue has been resolved and the Supplemental Property Insurance is now included in the VA Loan Analysis field 1348.

Workaround Description:

The following workaround was provided for this production issue and is no longer required for Encompass 21.3 and later.

• Show the Flood Insurance in the Other field by locking it down.

When there are resubordinating loans on the subject property, the total for the payments of these resubordinate liens was not being calculated for the proposed monthly subordinate housing fee (field ID 229) on the 1003 URLA – Lender input form. This issue has been resolved so that the resubordinating liens amounts are now included in field 229.

Workaround Description:

The following workaround was provided for this production issue and is no longer required for Encompass 21.3 and later.

• Calculate the total payments for all resubordinating liens, lock field 229 on the 1003 URLA – Lender input form, and then enter the amount in the field.

Updates have been made to the logic used to populate the Purpose of Loan (field ID 19) and Purpose of Refinance (field ID 299) fields when importing a cash-out refinance or no cash-out refinance loan. These changes address an issue that caused some cash-out refinance loans to be imported into Encompass with No Cash-Out Refi selected for Purpose of Loan and No Cash-Out Other selected for Purpose of Refinance.

When the RefinanceCashOutDeterminationType in the XML file for the imported loan is Cashout:

• The Purpose of Loan field in Encompass is set to Cash-Out Refi.

• The Purpose of Refinance field in Encompass is populated with Cash-Out Other.

When the RefinanceCashOutDeterminationType in the XML file for the imported loan is LimitedCashOut or NoCashOut:

• The Purpose of Loan field in Encompass is set to No Cash-Out Refi.

• The Purpose of Refinance field in Encompass is populated with No Cash-Out Other.

When the RefinanceCashOutDeterminationType in the XML file for the imported loan is blank, the Purpose of Refinance field in Encompass is also blank.

Lenders need to make appropriate adjustments for Limited Cash-Out refinances based on the loan scenario. Limited Cash-Out refinances fall under the guidelines of the GSEs. Please refer to your selling guide.

An issue was resolved that caused the borrower’s name to be missing from the email subject line for some emails and the text for the green message that display in the Encompass Loan Log for loans originated in Encompass Consumer Connect or Encompass LO Connect. This would occur in some email notifications and green messages associated with loan disclosures or with loan files sent from the eFolder.

This issue has been resolved and the borrower’s name now displays correctly in the email subject lines and in the green messages.

(Added on 9/17/2021)

An issue was resolved that caused the loan officer to not display as a recipient on the Send eDisclosures window for an eDisclosure package when the Rate Lock Agreement was the only document in the package that required the loan officer’s signature. This resulted in the loan officer not receiving an email with a link to eSign the document.

If the eDisclosure package contained another document that was eSignable by the loan officer, for example the 1003 URLA, the loan officer would be added as a recipient and would be able to eSign the Rate Lock Agreement.

Workaround Description:

The following workarounds were provided for this production issue and are no longer required for Encompass 21.3 and later.

• Add the 1003 URLA to the package.

• Have the loan officer wet sign the document after the borrower eSigns and returns the package.

DOCP-27554

An issue was resolved that cause the Cloud Viewer (the document viewer created by ICE Mortgage and introduced with the Encompass 20.2 Major Release in November 2020) to clear the check mark from some checkboxes when displaying the documents in the viewer. This was a rendering issue, and none of the checkbox selections were actually changed because of this issue. This issue has been resolved and the checkboxes are now displaying correctly.

Workaround Information

The following workaround was provided for this production issue and is no longer required for Encompass 21.3 and later:

• Print the file or view the file in its original format to display the checkboxes with their original values.

An issue was resolved that resulted in the Cloud Viewer (the version of the document viewer designed for viewing files stored on the cloud) to freeze briefly when a file attachment was deleted from the Document Details window. Users were unable to perform operations in the viewer for a few second until the file deletion completed. This issue has been resolved and the Cloud Viewer no longer hangs when a file attachment is deleted.

(Added on 9/17/2021)

An issue was resolved that cause Encompass users running the new Cloud Viewer document viewer to receive the following error message when attempting to view a file attachment that was older than 90 days.

This issue has been resolved. Pages and thumbnail images are now loading as expected and the error message no longer displays.

(Added on 9/30/2021)

An issue was resolved with the new Cloud Viewer document viewer that resulted in several Encompass processes continuing to run when an Encompass user opened a document in the Cloud Viewer and then closed the document before it had fully rendered. In some instances, these processes continued to consumed system resources and caused Encompass to hang. The following error message would display if the user closed Encompass via the Task Manager.

This issue has been resolved and the processes are now closing correctly when a user closing a document before it has fully rendered in the Cloud Viewer.

When a loan was originated on an Encompass Consumer Connect website and the package included a wet sign document, the loan officers would not receive an email notification when the borrower uploaded the document to the Encompass Consumer Connect website. The loan officer would receive notification when a document not associated with the eDisclosure package was uploaded.

This issue is resolved, and the loan officer now receives email notifications when wet sign documents associated with an eDisclosure package are uploaded to an Encompass consumer connect website.

When a Status Online Template configured with an Automatic update method is triggered, the notification is now sent successfully to an Encompass Consumer Connect borrower who does not have an authentication code.

Previously the email would not be sent, and the following error message would display:

Workaround Information

The following workaround was provided for this production issue and is no longer required for Encompass 21.3 and later:

• Status Online updates can be sent manually.

• Authorization codes for Encompass Consumer Connect borrowers can be set before the automatic Status Online notification is sent when requesting eConsent or when requesting a document.

Status Online email notification sent manually to non-primary borrower pairs for an Encompass Consumer Connect loan are now being successfully delivered. Previously, non-primary borrower pairs and other recipients were added to a manual Status Online notification by clicking the Add Contacts button on the Send Notification window. A message would display stating that the email had been sent to all the recipients, but the emails were not actually sent to the non-primary borrower pairs. This issue has been resolved and the non-primary borrower pairs on Encompass Consumer Connect loans are now receiving email notifications when they have been manually added to the list of recipients.

Duplicate copies of file attachments for informational documents (documents that provide borrowers with information but do not require signing) are no longer being added to the eFolder when closing documents are sent to borrowers or when a closing package is printed to the eFolder.

Workaround Information

The following workaround was provided for this production issue and is no longer required for Encompass 21.3 and later:

• Manually delete the attachments.

An issue was resolved that caused the following error message to display when enhanced conditions were enabled and a user created a blank enhanced condition.

The error displayed when a user typed a name in the Condition Name field. The error message did not display when an existing name was selected from the Condition Name dropdown list.

This issue has been resolved and the error message no longer displays when a user types a name in the Condition Name field.

(Updated on 10/7/2021)

An issue was resolved with the eFolder document viewer that caused a sorting issue for some file attachments in the Unassigned section of the eFolder File Manager. This issue occurred when the files shared the same name except for a number in parentheses at the end of the name, for example, file (1), file (2), file (3). These types of files are typically created when pages in an existing file attachment are broken into multiple new file attachments. Instead of displaying the files in numerical order, Encompass first listed all files with a number that began with 1, and then listed all files with a number that began with 2, etc. For example, file (1), file (11), file (12), file (2), file (22), file (3), file (33). This issue has been resolved and file names with parenthetical numbers are now listed in the correct alphanumeric order. This issue affected both the new Cloud Viewer and the original document viewer.

Because of the new sorting method used to resolve this issue, file attachments are now automatically listed in alphanumeric order when you add them to the Unassigned section of the File Manager. Previously newly added files were added to the bottom of the Unassigned files list.

There is a known issue that causes some eSign packages to display a status of Incomplete on the new eSign Packages window (accessed by clicking the eSign Packages button on the Encompass Pipeline) even when the packages are actually complete. This issue affects packages for loans originated on an Encompass Consumer Connect website when the packages include a combination of eSign and non-eSign documents. This issue will be addressed in a future release of Encompass.

In previous versions of Encompass, when viewing the Loan Program template list on the Encompass > Settings > Loan Templates > Loan Programs screen, changes made to individual template details were not reflected on this screen until 10-15 minutes after the changes were made. The changes were saved and applicable in the loan program templates, but the changes were not reflected on the main Loan Program template settings screen in the Program Description, Plan Type, Investor, and Description columns where all of the templates are listed. This issue has been resolved and the most current Loan Program template details are now displayed here.

When an unexpected Encompass disconnect occurs when a user is a saving changes to a loan, the default milestone template (as indicated in the Milestones setting) is applied to the loan. Once network connectivity is restored and the loan is reopened and saved without making any data changes, the milestone template assigned to the loan (which may be different than the default milestone) is reapplied. However, all milestone completion dates and milestone assignments are removed from the loan. The unexpected application of the default milestone template results in loan team members being removed from the loan, loan progress being reverted, and critical dates being missed. This issue has been resolved. If network connectivity is lost during a loan save, the correct milestone remains assigned to the loan and this important milestone data is retained.