An issue was resolved that caused the HELOC Historical Table to not print on the HELOC Important Terms Disclosure output form when a HELOC loan did not have enough payment amounts that met the criteria used when creating a minimal example schedule. The logic for creating the schedules has been updated and the HELOC Historical Table now prints correctly.

When two loans are linked via the Piggyback Loans tool, the following fields are now editable in a Verification of Additional Loans (VOAL) input form from the second of the two linked loans:

• All contact fields in the To: section.

• All fields in the From: section.

  

• The following fields in the Account Information section:

  • Amount Applied to Downpayment (URLARAL0022)

  • Source of Funds (URLARAL0033)

  • Payment Deferred for the First Five Years (URLARAL0023)

  • Affordable Loan (URLARAL0024)

    

An update was made to the calculation for the Closing Costs (VASUMM.X127) in the Statutory Closing Cost Recoupment section on the Qualification tab of the VA Management input form to address an issue that occurred with lender-paid VA Funding Fees. Regulations require that these fees not be included in the Closing Costs in the Statutory Closing Cost Recoupment section.

The previous calculation for Closing Costs added the Loan Costs (which included the VA Funding Fee) and then subtracted the VA Funding Fee from the Closing Costs amount. However, when the VA Funding Fee was lender-paid, it was excluded from the Loan Costs. This resulted in a lender-paid VA Funding Fee being subtracted twice when calculating the Closing Costs.

To address this issue, in the calculations for the following fields on the Qualification tab in the VA management input form, the borrower VA Funding Fee (field ID 1050) from line 903 on the 2015 Itemization input form has been replaced with the borrower-paid amount (field ID NEWHUD.2.X2290) from the fee details pop-up window for line 905 on the 2015 Itemization input form:

• All Other Non Shoppable services (field ID VASUMM.X137) in the Closing Costs Recoupment section

• Closing Costs (VASUMM.X127) in the Statutory Closing Cost Recoupment section

Because of this calculation change, the funding fee is no longer included in the Closing Cost Recoupment section (VASUMM.X137) or the Statutory Closing Cost Recoupment (VASUMM.X127) when the lender or a party other than the borrower pays the VA Funding fee.

Migration

This calculation update is applied to existing loans in your Encompass Pipeline only when updates are made to one of the fields used in the calculation.

Workaround Description:

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

• Lock down the recoupment months or change the lender paid amount to a general lender credit instead of specifically applying it to the funding fee.

For construction-only loans with the A (Half Loan) option selected for the Estimate Interest On dropdown list (field ID SYS.X6), the following updates have been made to the maximum monthly principal and interest payment amount in the Loan Terms on the Loan Estimate Page 1 (field ID LE1.X24) and in the AP Table on the Loan Estimate Page 2 and the Closing Disclosure Page 4 to comply with § 1026.37(b)(5) of the RegZ-TIL. The values in these fields are now calculated using the full loan amount (field ID 2). Previously the values were calculated using half the loan amount.

An issue was resolved that caused erroneous export codes to display in the HMDA LAR export for brokered loans or loans imported from Encompass TPO Connect. This issue occurred when the Action Taken (field ID 1393) for a loan with two borrower pairs was set to Active and an Encompass user entered data on the HMDA Information input form for the first borrower pair. If the user then switched to the second borrower pair, changed the Action Taken (field ID 1393) to 6. Purchased, saved the loan while the second borrower pair was still selected, and then generated the HMDA LAR report, the values for the first borrower pair were not updating to Not Applicable when appropriate in the HMDA LAR export.

If a user switched back to the first borrower pair after generating the HMDA LAR export, Encompass would recalculate and populate the Not Applicable values in the loan file for the first borrower pair, but the values would not change in the HMDA LAR export because it was generated before Encompass updated the values.

This issue has been resolved. When the second borrower pair is selected in a loan, Encompass now updates the values for the first borrower pair prior to generating the HMDA LAR export.

An issue was resolved that caused the APR (field ID 799) on the HMDA Information input form to not recalculate for loans with co-mortgagors and mortgage insurance when a change in loan data triggered a recalculation of the APR. The value was recalculating correctly for the APR field (field ID 799) on other input forms (for example the Loan Estimate Page 3, the Closing Disclosure Page 5, the RegZ-LE and the RegZ-CD).

This recalculation issue affected only the HMDA APR field and did not affect APR values used in disclosures for the loan.

An issue was resolved that resulted in the Loan Amount (field ID 1109) not being rounded when the loan-level Loan Amount Rounding checkbox (field ID 4745) was selected on the Borrower Summary – Origination input form, but a Purchase Price (field ID 136) was not entered for the loan. When a Purchase Price was entered, the Loan Amount was rounding correctly. This issue has been resolved and the Loan Amount is now rounding correctly when the Loan Amount Rounding checkbox is selected, even when no Purchase Price is entered for the loan.

An issue was resolved that caused the Total Other Asset Amount (field ID URLA.X54) on the 1003 URLA Part 3 input form to not be calculated when the first entry was made for an asset in section 2b. Other Assets You Have or when the first entry was made on the Verification of Other Assets input form. The total was calculated as soon as a second asset was entered on either form. This issue has been resolved and the total is now populating as soon as the first entry is added for an Other Asset.

(Added on 12/21/2021)

An issue was resolved that resulted in the 1003 URLA form not displaying on the pop-up window that prompts a loan officer to eSign documents before they are sent to a recipient. This issue affects packages sent via the eFolder Send windows when requesting documents, sending eDisclosures, or sending pre-closing documents. Other eSignable documents for the loan officer were displaying correctly on the window. This issue has been resolved and the 1003 URLA form now displays when the loan officer is required to eSign it prior to sending packages.

(Added on 12/21/2021)

An issue was resolved that caused the status for some eDisclosure document packages to not update toCompleteon thePackagestab in the eFolder for eDisclosure packages sent from Encompass LO Connect to recipients using Encompass Consumer Connect. This issue affected packages that included a combination of at least one eSignable and at least one Wet Sign document. The status for these packages was still showing asIncompleteafter all parties had completed the packages. This issue has been resolved and the status for these types of packages is now being updated correctly on the Packages tab in the eFolder.

The eFolderPackagestab only displays for Encompass Consumer Connect loans.

The following updates have been made to the Select Country pop-up window that opens when you select the Foreign Address checkbox for an address on the new URLA input forms and then click the Find icon (Magnifying Glass):

• Iran and Syria have been added to the list of countries

• Spelling has been corrected in the entries for Macedonia, The Former Yugoslav Republic of and Moldova, Republic of.

An option for 30 Day Average SOFR has been added to the ARM Index Type dropdown list (field ID 4512).

Workaround Description:

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

• Manually type in the ARM Index Type prior to pricing a new lock or relock.

An issue was resolved for FNMA 3.2 or Blend loan file imports that resulted in some non-POC fees being treated as POC fees in the Borrower Transaction section of the Closing Disclosure Page 3 when the 2015 Itemization input form included at least one fee with a POC amount. The values in the following fields were affected by this issue:

• Sub Total (field ID CD3.X41)

• 03 Closing Costs Paid at Closing J (field ID CD3.X1)

• Total Due from Borrower at Closing K (field ID CD3.X21)

• Cash From Borrower (field ID CD3.X23)

This issue was resolved. POC and non-POC fees are now being populated correctly in the Borrower Transaction section of the Closing Disclosure Page 3 for FNMA 3.2 and Blend file imports.

For loans with two borrower pairs, an issue was resolved that cause a principal reduction amount in a Payoffs and Payments entry for the first borrower pair to be doubled in the following fields because the amount was being applied to both borrower pairs:

• Line 04 (field ID L85) in section K. Due from Borrower at Closing in the Borrower’s Transaction section of the Closing Disclosure Page 3

• The field at the bottom of the Closing Disclosure Page 3 that displays the cash due to or from the borrower at close (field ID CD3.X23)

This issue has been resolved and principal reduction amounts for Payoffs and Payments are now always applied to the first borrower pair only.

Updates have been made to correct an issue with county codes in the ZIP code database used by Encompass. This issue occasionally caused extraneous counties and cities to display in the Select a City pop-up window that opens when entering ZIP codes that included more than one city or town. The invalid entries have now been removed from the ZIP code database.

An issue occurred for users utilizing the Encompass online help where a script error was displayed each time a user clicked a hyperlink in an online help topic. This issue has been resolved and the script error is no longer triggered.

(Added on 12/6/2021)

Customers using the initial build of the Encompass 21.4 release in test environments discovered an issue that caused the mortgage insurance premium (MIP) amount to be incorrectly applied to the calculations for theTotal of Payments(field ID CD5.X1) on the Closing Disclosure Page 5 and theIn 5 Years Total You Will Have Paid(field ID LE3.X17) on the Loan Estimate Page 3. No other calculations were modified in Encompass 21.4 and the changes to the calculations forTotal of Paymentsand theIn 5 Years Total You Will Have Paidhave been reverted to the previous versions of the calculations.

(Added on 12/6/2021)

An issue occurred with the Diagnostic Mode - Just in Time (JIT) tool used to perform Encompass application logging in real time where it was not returning the expected verbose information for loan actions in the log file. This issue has been resolved and is now working as expected in Encompass 21.4.0.1 Server Patch 1.