An issue with searching within borrower contacts occurred for users utilizing a borrower custom field version of the Appraised Value field. After using the Borrower Custom Fields setting to add the Appraised Value field (field ID 356) as a borrower custom field and mapping it so that the contact information entered in the actual field (field 356) is automatically copied to the borrower custom field on the Contacts tab, loan team members working in the loan received the following Application Error when they navigated to the Contacts tab’s Borrower Contacts view and searched for appraised value data:

An error occurred. Please contact the administrator with the following information:

Error executing query: Conversion failed when converting the varchar value [‘x,xxx,xxx’] to data type int.

It was determined that this error occurred when the Appraised Value field had been configured as an integer field and if the loan team member had clicked the Link to a Contact icon on the Borrower Summary and created a new contact, and added an Appraised Value column to the Borrower Contacts view on the Contacts tab, and then searched for data within the Appraised Value column. This error stemmed from the actual Appraised Value field adding commas to its values, while the borrower custom field version to which the field is mapped to is configured to contain an integer (no commas). This issue has been resolved.

For loans with an application date of 1/1/2018 or later, the following correction has been made to the second threshold amount mentioned in the paragraph at the beginning of the Points and Fees Test section on the Section 32 HOEPA input form:

Previous text:

For a loan amount of $21,032 or more total points and fees cannot exceed 5% of the total loan amount; For Loan amounts less than $20,579 the total points and fees cannot exceed the lesser of 8% of the total loan amount or $1,052; The dollar amounts used in this test may be adjusted each year, effective January 1.

Updated text:

Under “Points and Fees Test”, the following verbiage should appear:

For a loan amount of $21,032 or more total points and fees cannot exceed 5% of the total loan amount; For Loan amounts less than $21,032 the total points and fees cannot exceed the lesser of 8% of the total loan amount or $1,052; The dollar amounts used in this test may be adjusted each year, effective January 1.

An issue was resolved that caused the borrower name (field ID 31) to be blank in the Title will be held sections on the 1003 Page 1, the FNMA Streamlined 1003, and the USDA Management input forms when importing a WebCenter loan that has a borrower and co-borrower. This issue has been resolved and the borrower name now displays as expected in the Title will be held section on these forms.

Updates have been made in the way the First-Time Homebuyer (field ID 934) is populated for FHA, VA, and Conventional loans. Previously, Yes would be populated in the First-Time Homebuyer field only when all of the borrowers (across all borrower pairs) entered N in the ownership or interest in a property field (field IDs 403 or 1108). Now Yes is populated in the First-Time Homebuyer field when one or more of the borrowers (across all borrower pairs) entered N in the declaration for ownership or interest in a property field (field IDs 403 or 1108).

The updated logic does not apply to HELOC or USDA loans.

The following two options are now accessible on the fourth credit dropdown list (field ID 1646) in section l. on the Details of Transaction on the 1003 Page 3 input form:

• Sweat Equity

• Other

Previously these two options were available on the first three dropdown lists, but were not displaying on the fourth dropdown list. The options were also available on the fourth dropdown list on the Details of Transaction on the 2015 Itemization input form, but when selected on the 2015 Itemization, the options were not populating to the 1003 Page 3.

The Sweat Equity and Other options now display in the fourth dropdown list. Additionally, when one of these options is selected on the fourth dropdown list on the Details of Transaction on the 2015 Itemization input form, the selection is copied to the fourth dropdown list on the 1003 Page 3.

Workaround Information:

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

• Type the data in the fourth dropdown list (field ID 1646) on the 2015 Itemization.

All 21 options now display in the Loan Documentation Type Code (field ID MORNET.X67) dropdown list on the Borrower Summary – Origination input form. Previously the 21st option, (T) One paystub and one W-2 and VVOE or one year 1040, was displaying on Borrower Summary - Processing, FNMA Streamlined 1003, MLDS - CA GFE, and VA Management input forms, but was not displaying on the Borrower Summary – Origination input form.

Updates have been made to the field ID that displays on the lower-right corner of the Encompass application after selecting a field on a form such as the VOL (verification of liability) or Request for Transcript of Tax. The onscreen field ID on the lower-right corner now matches the field ID selected on the form.

These types of input forms are used to create multiple records based on the set of data that displays in the input form. For example, multiple VOL records can be created to track all the liabilities associated with a loan, and the Request for Transcript of Tax can be used to create requests for several co-borrowers. The field IDs for these records are based on an initial set of fields IDs. Each new record is populated with field IDs that increase incrementally with each record. For example:

• The Name field on a VOL is based on the initial field ID FL0002.

• On the first VOL record, the Name field is FL0102.

• On the second VOL record, the Name field is FL0202.

• This pattern is repeated for each record created on these types of forms.

• When a field is selected, the hover help displays the field ID for the selected field (for example, FL0202).

Previously, the field ID that displayed on the lower-right corner of the Encompass application would always display the initial field ID for the form (for example, FL0002). Beginning with the Encompass 18.3 release, the lower-right corner of the Encompass application now displays the field ID for the selected field (for example, FL0102 or FL0202).

The spelling of De Soto county has been updated in the Select a City pop-up window that displays when 34266 is entered in a Zip code field in Encompass. The county now displays as DeSoto (one word) to match the spelling used on the HUD website for FHA County Loan Limits.

An issue that resulted in the Loan Limit (field ID 3331) not updating correctly on the Qualification tab on the ATR/QM Management input form when Newport News City or Newport News CI was entered as the county for a subject property in the state of Virginia has been resolved. These county names have been added to the Encompass county table used for conventional loans to ensure that the Loan Limit field is now populated accordingly.

Workaround Information:

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

• On the Section 35 HPML input form, click the Lock icon for the Loan Limit (field 3331) and manually enter the value.

An issue was resolved that resulted in Encompass users being unable to clear the Qual Rate (field ID 1014) under the following conditions:

1. An Encompass user entered a value in the Qual Rate field, and then clicked outside the field or saved the loan file.

2. The user then deleted the Qual Rate value and closed the loan file.

When the Encompass user reopened the loan file, the field would be repopulated with the value that had previously been deleted. This issue was introduced with Encompass version 16.1.0.3. The issue has been resolved and the field can now be cleared successfully.

Workaround Information:

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

• Open the Transmittal Summary input form, select the blank option in the dropdown list (field ID 1086) in the Qualifying Rate Section, and then modify the Qualifying Rate (field ID 1014).

An issue was resolved that caused the incorrect County name (field ID 13) to populate on the 1003 Page 1 input form under the following conditions:

1. The City and State fields (field IDs FR0106 and FR0107) in the Present Address section on the Borrower Summary – Origination or Borrower Summary – Processing input forms were populated by entering 75652 or 75692 for the Zip code and then selecting the city from the Select a City pop-up window.

2. The Copy from Present button was clicked on one of the Borrower Summary forms to copy the present address to the subject property address fields.

Under the scenario described above, the county name would default to Panola on the 1003 Page 1, even when a city located in another county was selected from the Select a City pop-up window.

Workaround Information:

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

• For properties with a 75652 or 75692 Zip code, on the 1003 Page, enter the address and county name manually, or use the Copy from Present button to copy the address and then update the County name manually.

The Loan Maturity Date (field ID 78) is now displaying correctly when the 1st Payment Date (field ID 682) is set to the 29th, 30th, or 31st day of a month. Previously Loan Maturity Dates that fell on the 29th, 30th, or 31st day of a month were being adjusted to the 28th day of the month. This occurred because Encompass calculated the date by adding months to the original date. In February the last day of the month is the 28th, so loans with payment dates of the 29th, 30th, or 31st were moved to the 28th in February, and from that time on were calculated for the 28th of the month. This issue has been resolved and the Loan Maturity Date is now calculating correctly.

For loans created prior to upgrading to Encompass 18.3, Encompass recalculates the Loan Maturity Date if the Note Date (field ID L770) is blank. If the loan already has a Note Date, the Loan Maturity Date is not recalculated, but Encompass users can click the blue Lock icon next to the field to edit the date.

When using the alternate versions of the Loan Estimate and Closing Disclosure input forms, Encompass users can now delete non-VOL adjustments that have been added to the Payoffs and Payments window, which is accessible by clicking the Payoffs & Payments button on the Loan Estimate Page 2 and the Closing Disclosure Page 3. To enable this functionality, the Add button on the Payoffs and Payments window has been replaced with an Add icon and a Delete icon.

Workaround Information

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

• Switch to the standard version of the Loan Estimate and Closing Disclosure, then switch back to the alternate version.

When only the Subject Property State (field ID 14) is updated in the Subject Property address fields, the Security Interest address (field ID 1603) is now automatically updated. Previously, the Security Interest address would not update when the Subject Property State was changed unless an Encompass user opened an input form that included the Security Interest address.

Workaround Information

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

• Open an Encompass input form that includes the Security Interest address (field ID 1603), and then save the loan.

An issue was resolved that resulted in incorrect entries being deleted from the Vesting Information table on the Borrower Information – Vesting input form when two or more borrowers had been added to the vesting information via the Borrower Information – Vesting input form. Previously, when an Encompass user selected a borrower and clicked the Delete icon, the borrower at the bottom of the list would be deleted, even when an entry higher on the list had been selected for deletion. This issue has been resolved and the correct entry is now being deleted.

This issue only affected entries added directly from the Borrower Vesting window. It did not affect entries copied from other input forms such as the 1003 Page 1 or Borrower Summary - Origination.

The city and state are now populating correctly when using the Select a City pop-up window to enter an address in the Architect Information and General Contractor Information on the Project Data tab on the Construction Management input form. The Select a City window displays when you enter a Zip code that is associated with more than one city or town. Selecting a city from the list will populate the City and State fields. Previously, the City and State fields for the architect and general contractor were not being populated after an Encompass user selected a city from the Select a City pop-up window.

Some clients reported receiving an Application Error similar to this example below when attempting to save a loan file. The cause of this error was identified and addressed for impacted clients, and the error is no longer triggered upon saving a loan file.

An error occurred. Please contact the administrator with the following information:

Error executing query: [declare @xrefId int

if not exists(select 1 from LoanXRef where ([LoanGuid] = '{fea8c201-xxx-xxxx-xxxx-xxxxxxxxxxxx}')

)

begin

insert into LoanXRef

([LoanGuid])

values

('{ fea8c201-xxx-xxxx-xxxx-xxxxxxxxxxxx }')

select @xrefId = convert(int, scope_identity())

end

else

select @xrefId = XRefID from LoanXRef where LoanGuid = '{ fea8c201-xxx-xxxx-xxxx-xxxxxxxxxxxx }'

delete from LoanAlerts

where ([LoanXRefId] = @xrefId)

delete from LoanSummary

where ([guid] = '{ fea8c201-xxx-xxxx-xxxx-xxxxxxxxxxxx }')

insert into LoanSummary

([guid], [LoanName], [LoanFolder], [XRefID], [LastModified])

values

('{ fea8c201-xxx-xxxx-xxxx-xxxxxxxxxxxx }', '{ fea8c201-xxx-xxxx-xxxx-xxxxxxxxxxxx }', 'My Pipeline', @xrefId, '20222222 13:00:04.550')

...

The Net Rent Income amount (field ID 906) is now included in the calculation for the annual household income (field ID USDA.X16) on the Rural Assistance URLA and Req for SFH Loan Guarantee/Resv. Of Funds tabs on the USDA Management input form. The net amount of income derived from rental property is calculated by taking 75% of the gross rent from the lease agreements and subtracting the monthly payment (principal, interest, taxes, and insurance) for the rental property. If the resulting number is positive, the amount is included in the calculation for Asset Income (field ID USDA.X170), which in turn is included in the calculation for annual household income (field ID USDA.X16).

Workaround Information:

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

• Click the Lock icons for the amounts (field IDs USDA.X164, USDA.X165, USDA.X166, USDA.X167, USDA.X168, USDA.X169, and USDA.X170) in the Annual Income Calculation section on the USDA Management input form and manually adjust the amounts to include the net rental income.

After upgrading to Encompass 18.3, amounts entered in existing loans for field USDA.X170 will be copied without triggering a recalculation. After the upgrade, the Net Rent Income amount (field ID 906) will be included in the calculation when changes are made to any field that triggers a recalculation of USDA.X170.

The amounts that display in the USDA Guarantee Fee Financed (field ID NEWHUD2.X1593) and PMI/MIP Financed (field ID 1045) fields are no longer being rounded to a dollar value. The full value (in dollars and cents) now displays for these fields. This behavior applies regardless of whether the Loan Amount Rounding option is disabled or enabled in the Encompass Admin Tools.

Because the following states do not use the same calculation as HUD to populate the commitment expiration date, the field used for the commitment expiration date (field ID 1072) has been replaced with a new field (field ID DISCLOSURE.X1205) on the following State Specific Disclosure Information forms:

• California

• Colorado

• District of Columbia

• Florida

• Illinois

• Montana

• New Jersey

• New York

Workaround Information:

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

• Manually modify the date as needed when generating forms or uploading data to investors.

When upgrading to Encompass 18.3, the new commitment expiration date (field ID DISCLOSURE.X1205) will be populated with the date from the old commitment expiration date (field ID 1072) for previously disclosed loan files in the states listed above.

The entry for Federal Housing Finance Board National Average Contract Mortgage Rate on the Arm Index Type dropdown list (field ID 1959) on the RegZ-LE, RegZ-CD, RegZ-TIL (2010 input forms), and the New York State-Specific Disclosure Information input forms has been changed to National Average Contract Mortgage Rate. Selecting the new National Average Contract Mortgage Rate option results in the following behavior:

• National Average Contract Mortgage Rate populates in the Index + Margin dropdown (field ID LE2.X96) in the Adjustable Interest Rate (AIR) Table on forms such as the Loan Estimate Page 2, Closing Disclosure Page 4, Construction Management (for construction-to-permanent loans), RegZ-LE, and RegZ-CD input forms.

• The Loan Estimate and Closing Disclosure output forms disclose the Index + Margin in the AIR table as FHFB_NACMR + [field ID 689].

• The following language populates in comment field (field ID 666) in the Payment Schedule section on the RegZ-CD input form:

derived from the Federal Housing Finance Agency's Monthly Interest Rate Survey (MIRS), as made available by the Federal Housing Finance Agency.

The Reserves amount (field ID CASARN.X78) on the Underwriter Summary Page 1 tool and the Freddie Mac Additional Data input form is now populating correctly. Previously the amount of the cash deposit was being included twice in the calculation for the Reserves. This issue has been resolved and new logic has been implemented to populate the Reserves amount (field ID CASASRN.X78).

When cash is required from the borrower:

Previous Logic

• The Reserves amount (field ID CASASRN.X78) = Verified Assets (field ID 1094) + Cash Deposits (field IDs 183 and 1716) - Cash from Borrower (field ID 142). (This caused fields 183 and 1716 to be included in calculation twice.)

• For non-FHA loans the total of all VOD records with an Account Type of Gifts Not Deposited were also subtracted from the Reserves.

New Logic

• When the first dropdown list (field ID 202) in line L on the 1003 Page 3 is Cash Deposit on sales contract, the second dropdown list (field ID 1091) on the 1003 Page 3 is not Cash Deposit on sales contract, and the first Cash Deposit Value (field ID 183) on the 1003 Page 2 is populated with an amount:

  • The Reserves amount (field ID CASASRN.X78) = Verified Assets (field ID 1094) + the second Cash Deposit Value (field ID 1716) - Cash from borrower (field ID 142).

• When the first dropdown list (field ID 202) in line L on the 1003 Page 3 is not Cash Deposit on sales contract, the second dropdown list (field ID 1091) is Cash Deposit on sales contract, and an amount is entered in the second Cash Deposit entry (field ID 1716) on the 1003 Page 2:

  • The Reserves amount (field ID CASASRN.X78) = Verified Assets (field ID 1094) + the first Cash Deposit Value (field ID 183) - Cash from borrower (field ID 142).

• When both the first and second dropdown lists on line L are Cash Deposit on sales contract and both the first Cash Deposit Value (field ID 183) and Second Cash Deposit Value (field ID 1716) are greater than 0:

  • The Reserves amount (field ID CASASRN.X78) = Verified Assets (field ID 1094) - Cash from borrower (field ID 142).

• When both the first and second dropdown lists on line L are not Cash Deposit on sales contract:

  • The Reserves amount (field ID CASASRN.X78) = Verified Assets (field ID 1094) + the Cash Deposits (field ID 183 and 1716) - Cash from borrower (field ID 142).

• For non-FHA loans the total of all VOD records with an Account Type of Gifts Not Deposited are also subtracted from the Reserves.

Workaround Information:

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

• Enter the cash deposit only on the 1003 Page 3 before running Loan Prospector (LP) or printing forms. Then add the cash deposit to the 1003 Page after running LP and printing.

Updates have been made to populate data correctly in the Informed Consumer Choice Disclosure Notice tab on the FHA Management form when a FMNA 3.2 loan file is imported into Encompass. Additionally, a new Refresh from Setting button has been added to the tab to enable users to refresh the data on the tab by importing the data currently configured in the FHA Informed Consumer Choice Disclosure setting in Encompass at any time.

Prior to the Encompass 18.3 release, the import process failed to populate the tab with data from the FHA Informed Consumer Choice Disclosure setting in Encompass. This resulted in a blank FHA Informed Consumer Choice Disclosure input form. Because the tab was read-only and was populated directly from the setting data at the time when the loan file was created, the fields could not be manually updated. Generating an output form from the blank data would result in an output form populated with outdated default data.

Workaround Information:

The following workarounds were provided for this production issue and are no longer required for Encompass version 18.3 and later:

• Workaround 1: After the FNMA 3.2 file is imported, duplicate the loan file without selecting a loan template. The duplicate loan file will be populated with the data configured in the values populated in the FHA Informed Consumer Choice Disclosure.

• Workaround 2: Banker edition clients can add the required fields to a custom input form and manually enter the values.

Issues were resolved that affected the additional description field for the ARM index type (field ID 666) on the RegZ-LE and RegZ-CD input forms under the following conditions:

• When Fannie Mae 1 Year LIBOR was selected for the ARM Index Type (field ID 1959), the Additional ARM Description field would clear after the loan file was saved, closed and reopened.

• When Fannie Mae 6 Month LIBOR was selected for the ARM Index Type (field ID 1959), the Additional ARM Description field would be grayed out and could not be edited.

This issue has been resolved. Encompass no longer clears the Additional ARM Description when Fannie Mae 1 Year LIBOR is selected for the ARM Index Type, and the Additional ARM Description field is now editable when Fannie Mae 6 Month LIBOR is selected for the ARM Index Type.

Workaround Information:

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

• Clear the ARM Index Type, and then re-enter the Additional ARM Description.

This update is available for all new and existing loans in Encompass after upgrading to Encompass 18.3.

The ECS Data Viewer now displays the Disclosed APR amount (field ID 3121) and the Disclosed Finance Charge Amount (field ID 3246). Previously, the ECS viewer was populating the Disclosure APR with the current APR amount (field ID 799) and the Disclosed Finance Charge Amount with Current Finance Charge Amount (field ID 1206).

An update has been made in the calculation for the Total points and fees applicable under section 32 amount (field ID S32DISC.X48) in Encompass to resolve a discrepancy with the Encompass Compliance Service (ECS) calculation for this amount. When the Bona Fide Discount Points percentage (QM.X369) exceed the Bona Fide percentage (field ID QM.X136), the bona fide discount points amount (field ID QM.X111) is now deducted from Section 32 Total Points and Fees field (field ID S32DISC.X48).

This update applies only to loans created after upgrading to Encompass 18.3.

The updated calculation also affects the calculation of the Total points and fees applicable under section 32 percentage (field ID QM.X123).

To avoid a conflict with Encompass Compliance Service (ECS) test criteria, an adjustment was made to the product description (field ID LE1.X5) used in Encompass for construction-to-permanent step-rate loans with no introductory rate and an interest-only construction phase (field ID 1176) of 12 months. These loans would fail because Encompass was displaying the current Loan Product (field ID LE1.X5) as 1 Year Interest Only, 1 Yr./0 Step Rate but the Encompass compliance Service was expecting the product to display as 1 Year Interest Only, 1/0 Step Rate per § 1026.37(a)(10). ECS would return the following fail message:

The Loan Product of (1 Year Interest Only, 1 Yr./0 Step Rate) on the Closing Disclosure is inaccurate. The actual Loan Product is (1 Year Interest Only, 1/0 Step Rate).

The description for these types of loans has now been update to remove the Yr. text from the product name.

The Total Debt Ratio – Max Rate During First 5 Years (field ID QM.X119) is now calculating correctly for construction-to-permanent loans when the construction phase (field ID 1176) is 12 months or less. Previously the Total Debt Ratio – Max Rate During First 5 Years was factoring in the Construction Phase. As a result, the potentially higher ARM payment that began during the permanent phase of the loan was not being captured correctly in the calculation.

An issue was resolved that caused some Encompass users to generate a Loan Estimate without the following Closing Costs expiration text or time:

• All other estimated closing costs expire on [date] at [time].

This issue has been resolved and the text and time now display as expected.

An issue was resolved that caused the date, time, and time zone for the Closing Costs Estimate Expiration Date (field IDs LE1.XD28, LE1.XD8, and LE1.XD9) to not update correctly on the output form when changes were made to the fields for the Closing Costs Estimate Expiration Date (field IDs LE1.X28, LE1.X8, and LE1.X9) on the input form under the following conditions:

• The Intent to Proceed checkbox (field ID 3164) was not selected.

• And a user clicked the Lock icon next to one of the Closing Costs Estimate Expiration Date fields and manually updated the field value.

This issue has been resolved and the values are now being properly updated under the conditions described above.

An issue was resolved that caused the First Mtg. P&I payment amount (field ID 1724) on the Transmittal Summary input form to not update properly for a construction-to-permanent loan with blended disclosures when the Construction Period Included in the Loan Terms checkbox (field ID CONST.X1) was selected or cleared. This affected the way the debt-to-income ratio (DTI) was calculated when qualifying the borrower for the loan. This issue has been resolved and the First Mtg. P&I payment amount is now updating correctly.

To preserve the data integrity of existing loans, Lock icon have been added to the First Mortgage P & I and Second Mortgage P & I fields (field IDs 1724 and 1725). When upgrading to Encompass 18.3, these fields are locked for existing loans when the Purpose of Loan (field ID 19) is Construction-Perm and the Construction Period Included in the Loan Terms checkbox (field ID CONST.X1) is selected. Click the Lock icon to manually update the amount.

An issue was resolved that caused file contact information to not populate when using a Loan Template Set to start a new loan under the following conditions:

• The Loan Template Set contained both a Data Template and a Closing Costs template.

• The Data Template included entries in the File Contacts tool.

• The Closing Costs template was blank.

Under the conditions described above, the File Contacts from the Data Template would not populate in the loan file.

This issue did not occur when applying a Loan Template Set to a previously existing loan file.

This issue has been resolved and the file contacts configured in the Data Template are now being populated when a Loan Template Set is used to create new loan.

When a loan is created or modified using a Loan Program template with an option selected for the Someone buying your property dropdown list (field ID 677) on input forms such as the RegZ-LE and RegZ-CD, the appropriate checkbox option (field ID LE3.X12) is now selected in the Assumption section on the Loan Estimate Page 3 and the Closing Disclosure Page 4. Previously no selection was made in the Assumption checkboxes when a Loan Program template had a selection in the Someone buying your property dropdown list. This occurred when the loan was created or modified using a Loan Program template or a Loan Template Set that included a Loan Program template. This issue has been resolved and the correct Assumption checkbox is now selected based on the option configured in the Someone buying your property dropdown list.

Workaround Information:

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

• Create a Data Template with the appropriate assumption checkbox (field ID LE3.X12) selected, and then append the Data Template to the Loan Template Set that includes the Loan Program template.

An issue was resolved that caused Custom Print Forms to not populate values from Encompass fields that begin with the prefix ECOA_, for example ECOA_NAME. This issue has been resolved and values from fields with the ECOA_ prefix are now being populated to Custom Print Forms.

An issue occurred for clients who created their own custom ‘Closing’ milestone for use in loan files, where this ‘Closing’ milestone was being automatically renamed to ‘Completion’ in every applicable loan file every time the client upgraded to a new version of Encompass.

Specifically, in loans where the custom Closing milestone was the last milestone to be completed, ‘Closing’ was correctly displayed in the Encompass Pipeline’s Last Finished Milestone column for the loan. But after upgrading to the next version of Encompass and re-opening the same loan, the Last Finished Milestone column then erroneously displayed ‘Completion’, even though the Completion milestone, nor any of the other milestones after the custom Closing milestone, had been completed yet. This issue resulted in not only the incorrect milestone status being indicated on the Pipeline, but also impacted loans where additional process flows were tied to the Closing milestone. To resolve these issues, some clients had to rebuild their Pipeline in order to move the impacted loans back to the Closing milestone.

This issue has been resolved and upgrading Encompass no longer results in the custom Closing milestone being renamed to ‘Completion’.

Workaround Description

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

• If your custom milestone that is named ‘Closing’ is being changed to ‘Completion’ after every Encompass upgrade, then change that milestone name to something other than ‘Closing’.

An issue was resolved that caused the Loan Type column on the Encompass Pipeline to be blank for USDA-RHS loans. When the Pipeline was configured to display the Loan Type column, the loan type would not display for USDA-RHS loans. The column would remain blank for loans with the USDA-RHS checkbox (field 1172) selected. This issue has been resolved and the USDA-RHS loan type will display on the Pipeline for Encompass Reporting Databases created after the Encompass 18.3 release. To resolve the issue for an existing Encompass Reporting Database, your Encompass administrator must adjust the character size for field 1172, or remove field 1172 from the database and then add it back.

Some clients received an error message when attempting to generate a report in Encompass based on the date when eDisclosures were fulfilled. After adding the EDISCLOSEDTRK.DateTimeFulfilled.1 field (for use with 2010 loans) or the EDISCLOSED2015TRK.eDisclosureSentDate.1 field (for use with 2015 loans) to the Reporting Database, and then navigating to the Reports tab in Encompass and setting up and generating a report that includes all applicable loans that include an eDisclosure fulfillment date that matches the desired criteria, the following error message was triggered and the report failed to generate:

There are no loan files that match the selected criteria for this report.

This error should not have been triggered when there were applicable loans that should have been included in the report, but it was. This issue has been resolved. Starting in Encompass 18.3, you can set up and generate reports based on the EDISCLOSEDTRK.DateTimeFulfilled.1 field (for use with 2010 loans) and the EDISCLOSED2015TRK.eDisclosureSentDate.1 field (for use with 2015 loans) to generate reports based on the date eDisclosures were fulfilled.

The default interest rate in the column for conventional financing in the FHA Informed Consumer Choice Disclosure setting (Encompass > Settings > Loan Setup > FHA Informed Consumer Choice Disclosure) has been set to a default value of 5%. Prior to the Encompass 18.3 release, the default value was set at 100%.

This update will not affect the FHA Informed Consumer Choice Disclosure setting if you have already customized the setting with a rate other than 100%.

On the Encompass Settings > Docs Setup > eDisclosure Packages setting screen, a If no channel selected, apply dropdown list is provided. Here, administrators can select the default channel option to use for a loan when no channel has been selected by a loan team member for the loan file. An issue occurred where administrators could select an option from this If no channel selected, apply dropdown list and save their selection, but the system would not retain the newly selected channel option. When the administrator navigated away from the eDisclosure Packages setting screen, and then returned to the screen later, their selection for this dropdown field had not been saved. The channel option that was in place prior to their update was again being displayed in this field. This issue has been resolved and the channel option that the administrator selects and saves is now retained here as expected.

When using the Settings Reports tool to generate a Persona report to capture data about Encompass users and their level of access (based on their persona) within the application, an issue occurred where the Apply Loan Template indicator (Yes or No) in the generated report was not accurately captured for all users in earlier versions of Encompass. This indicator was either displayed as Yes for all users in the report or No for all users in the report, regardless of the user’s access and ability to apply loan templates in Encompass.

Similarly, also in Persona-based reports, the eDisclosure Stacking Templates indicator in the report was not always accurate. When configuring the report options, if the administrator included only the Settings access option in the report, this indicator was captured correctly for each user in the report. However, if the administrator included the Settings access option and at least one other option (for example, eFolder access or Forms access) then the indicator in the report displayed as No for users who actually did have access to the eDisclosure Stacking Templates feature.

Both of these issues have been resolved in Encompass 18.3 and the Apply Loan Template indicator and eDisclosure Stacking Templates indicator are now captured accurately for each user in these Persona-based reports.

An issue occurred on the User Details window accessed in Encompass Settings where the tab order of the fields was out of sync. This issue has been resolved and the tab order is now linear (i.e., when your cursor is in a field, and then you press the Tab key, your cursor will proceed to the next logical field on the window and proceed accordingly as you press the Tab key again).

Previously, when a company utilized more than 100 Encompass Consumer Connect websites, the Consumer Connect Site dropdown list in the User Details window displayed a maximum of only 100 sites. This issue has been addressed and the full list of Consumer Connect Sites URLs is now available for user selection. The User Details window is accessible by double-clicking a user in the Enabled Users list in the Organization/Users setting (Encompass > Settings > Company/User Setup > Organization/Users).

The field for the Underwriting Counteroffer Status (field ID 4458) on the Underwriter Summary can now be added to the Encompass Reporting Database. This field was one of two new fields added to the Underwriter Summary with the Encompass 18.2 release.

An issue was resolved that caused the APR calculation to hang if the ratio of prepaid fees to the loan amount was incorrectly set too high by an Encompass user (for example, if the Origination Points were inadvertently entered as 98.655%). This caused the loan file to freeze and made it impossible to reopen the loan file to adjust the APR fees. The issue has been resolved by a change in Encompass that prevents the APR fee from being calculated if the ratio of prepaid fees to the loan amount is too high. This enables the Encompass user to open the loan file and adjust the prepaid fee amounts as needed.

Encompass requires the Microsoft Visual C++ 2015 Redistributable (or higher) to run effectively and the system will automatically attempt to install it each time Encompass is launched if it is not detected. An issue occurred for users who had Microsoft Visual Studio and the Microsoft Visual C++ 2017 Redistributable installed on their machine where each time they launched Encompass the system did not recognize the Visual C++ 2017 installation as an upgrade to Visual C++ 2015 and attempted to install Visual C++ 2015 on the machine. This issue has been resolved and the system now skips the installation of the Visual C++ 2015 redistributable if Visual C++ 2017 is already installed.

If the co-borrower’s email address is not entered in a loan file, Encompass now prompts the user to enter it when sending document requests and eDisclosure packages. Previously, Encompass would send the co-borrower’s request or package to the borrower’s email address, assuming that it was shared by the borrower and co-borrower.

An issue was resolved that caused some Encompass administrators to not see Encompass users listed in the Current Logins setting (Encompass > Settings > System Administration > Current Logins). This issue has been resolved by optimizing the retrieval process to return the list of currently logged-in users.

The following updates are being made to the logic used in Encompass to clear Good Faith Fee Variance Violated alerts and to adjust for tolerance cures when Fee Level Disclosures (field 4461 is checked) in order to facilitate documenting fee-level Change of Circumstance reasons.

For all sections on the Fee Variance Worksheet, no changes are being made in the logic used with a disclosure-level Change of Circumstance (field 4461 is cleared) except that the alert is now cleared when the Applied Cure Amount (field ID FV.X366) is equal to or greater than the Required Cure Amount (field ID FV.X348) without regard to any specific Reason being selected within the Good Faith Fee Variance Violated alert.

Tolerance Violations for Fees That Cannot Decrease

Alerts fire when any lender credit is decreased. An alert clears only when Tolerance Cure is selected as a reason or the Applied Cure Amount is greater than or equal to the Required Cure Amount. When the alert clears, the CD Baseline variance amount updates to 0. The alert clears and the CD baseline updates after entering the cure amount and tabbing out of the field.

If the Applied Cure Amount entered is less than the Required Cure amount, the alert does not clear and the CD Baseline variance amount updates to the new variance amount. For example, if the required cure is $30 and $13 is entered, the new variance amount would display as $17.

Tolerance Violations for Fees That Cannot Increase

An alert fires when there is an increase in fees made without a valid reason. The alert clears only when the Applied Cure Amount is greater than or equal to the Required Cure Amount regardless of whether Tolerance Cure is selected as a Reason within the Good Faith Fee Variance Violated alert. When the alert clears, the CD Baseline variance amount updates to 0. The alert clears and the baseline updates after a revised disclosure is sent

If the cure amount is blank or less than the Required Cure amount, the alert does not clear and the CD Baseline variance amount updates to the new variance amount. For example, if the required cure is $30 and $13 is entered, the new variance amount would display as $17.

Tolerance Violations for Fees That Cannot Increase More Than 10%

An alert fires when fees in this category increase by more than 10%. The alert clears and the baseline amount is reset only when both of the following conditions are met and a revised disclosure is sent:

• A valid reason is associated with a fee increase.

• The total increases for fees with valid reasons exceeds the legal limit amount. Only changes in fees with a valid reasons may be considered when determining if the change in fees exceeds the legal limit. If a fee is removed entirely from this section, the fee amount is deducted from the legal limit before assessing any potential increases.

Only the application of a cure amount equal to or greater than the amount of variances across all sections would be sufficient to clear the alert after the revised disclosure is sent. Identifying that the reason for redisclosure is for Tolerance Cure is insufficient to clear an alert or reset the baseline amount for the fees in this section.

NICE-10869

An entry is now added to the Loan Log for an Encompass loan file when an eConsent request is sent to a non-borrowing owner contact.

An issue was resolved that caused the Send button on the Send windows in the Encompass eFolder to be inaccessible when the computer screen resolution was set to 1400 x 1050 or higher. The higher resolution caused the windows to display over a larger area, pushing the Send button below the bottom of the computer screen, where it was not accessible. The Send window has been resized, and the button is now visible at higher resolutions.

A new eSign Documents button has been added to the Disclosure Tracking Tool in Encompass to enable loan officers to quickly eSign loan documents for Encompass Consumer Connect loans. The button displays only for Encompass Consumer Connect loans and is enabled when the loan officer selects a disclosure tracking record containing a package having at least one document pending the loan officer’s signature. When the button is clicked, the loan officer is taken to the DocuSign website to eSign the document.

The button displays in two locations on the Disclosure Tracking Tool:

• In the Disclosure History section

• On the Details tab on the Disclosure Details window

Once the Loan officer has completed eSigning the documents in the package, the button is disabled and the eSigning date for the loan officer is populated in the Disclosure Tracking record. Additional information is populated to the Disclosure Tracking record later by DocuSign and is typically available within ten minutes of eSigning.

The following updates have been made to the disclosure language used on the standard and alternate versions of the Closing Disclosure Page 3 for principal reductions for both cure and non-cure principal reductions on a loan.

Standard Version

For the standard version of the disclosure, the non-VOL entry description displays in the description for line K-04 or in the Addendum output form. The example text below is for a reduction amount of $500 paid by the lender.

* An adjustment amount of $500 displays in line K-04.

Alternate Version

For the alternate version of the disclosure, the non-VOL entry description displays in the Payoff and Payments pop-up window. The example text below shows a reduction amount of $500 paid by the lender.

** An adjustment amount of $500 displays in the Payoff and Payments pop-up window.

Migration of Existing Principal Reduction Disclosure Language

When upgrading to Encompass 18.3.0.4, the disclosure language for principal reductions will be updated when the Cure applied to Principal (POC) (field ID FV.X397) is greater than 0.

If a principal tolerance reduction has already been entered in an earlier version of Encompass 18.3, the language will not be updated for non-cure VOLs. This is done to preserve the integrity of closed loan files. To add the updated language to line K-04 on the Closing Disclosure Page 3, click the Payoff & Payments button at the top of the Summaries of Transaction section, select the appropriate entry, and then click OK to repopulate the field with the updated wording.

An issue with the Adjustable Payment (AP) table occurred in Encompass 18.2 for users working with Construction or Construction to Perm loans. When a user disclosed the initial Loan Estimate (LE) in Encompass 18.2, the values in the AP table on the LE output form were different than the values populated into the AP table on the LE input form. Specifically, fields CD4.X30 (First Change/Amount) and CD4.X33 (Subsequent Changes) reflected different values on the output form vs. the input form. This was the expected outcome. When users then re-disclosed the same loan, the values in the AP table on the LE output form changed to be identical with the information displayed in the input form. This issue has been resolved. Going forward, regardless of when a user discloses the LE or CD in Encompass 18.2, these values in the AP table will match on both the input forms and the output forms.

NDE-12182