Some users reported a sporadic, yet recurring, issue with the Disclosure Tracking Tool where the LE Due date (field ID 3143) was not being populated with a date when the Application Date (field ID 3142) was updated. By default in Encompass, field 3143 should automatically update as soon as field 3142 is updated, but in certain cases field 3143 was not updating. The cause of this issue was identified and it has been addressed.

NICE-21505

An issue occurred where the if the lender sent the eConsent Agreement before sending the eDisclosure package or at the same time as sending the eDisclosures, the CD Received date (field ID 3978) was not auto-populating unless the eConsent Agreement was accepted by the borrower before the eDisclosure package was sent. For example:

1. All required loan fields are completed, thus, the LE Due date (field ID 3143) is auto-populated.
2. The eConsent Agreement is sent to the borrower.
3. Prior to the borrower accepting the eConsent Agreement, the eDisclosure package, which includes the Closing Disclosure (CD) but excludes the Loan Estimate (LE), is sent.
4. The borrower retrieves the disclosures, and then accepts the terms of the eConsent Agreement.
5. The borrower then views the CD.

Once the borrower accepted the eConsent Agreement in this scenario, the CD Received date should have been populated with the current date. This issue has been resolved, and the CD Received date is now auto-populated when the borrower accepts the eConsent Agreement.

(Added on 4/29/2020)

Some clients reported that in certain loans where the Changed Circumstance checkbox (field ID 3168) was selected to indicate a change of circumstance, the checkbox was later automatically cleared. When reviewing the system audit trail for this issue, it indicated that the checkbox was cleared by the user ID <system>. After further investigation it was determined that this issue was caused by a system evaluation of specific advanced code (that included XDATE) used by some clients. When the advanced coding included XDATE, the system evaluated XDATE as 1/1/1, and this resulted in the Changed Circumstance checkbox being cleared. Only loans using this specific advanced code were impacted. This issue has been resolved.

(Added on 2/28/2020)

An issue was resolved that caused the Closing Costs Estimate Expiration Date time zone field (field ID LE1.X9) to update incorrectly under the following conditions:

1. The gold Lock icon was selected for the Closing Costs Estimate Expiration Date time zone field, indicating that the field was controlled by user entry only and not by Encompass calculations.

2. The user then selected an option from the time zone dropdown list.

3. The user then completed the LE Date Issued field (field ID LE1.X1) by clicking the field and then pressing Ctrl+D, or by manually typing the date.

After the user updated the LE Date Issued field, Encompass was populating the Closing Costs Estimate Expiration Date time zone field with the HST option from the dropdown list, even though the field was locked to prevent a system override. The issue has been resolved and the time zone is no longer being overwritten by Encompass under the scenario described above.

Workaround Information:

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

• Click the Calendar icon to enter a new date in the LE Date Issued field.

(Added on 2/28/2020)

An Issue was resolved that caused the Premium Source dropdown list (field ID CASASRN.X158), which displays as an editable field on the Freddie Mac Additional Data input form, to behave as a read-only field that could not be edited when the field was added to a custom input form or when a field Trigger Business Rule attempted to update the field value. This issue has been resolved and the field can now be used with custom forms and business rules.

(Added on 2/28/2020)

An issue was resolved that cause the company’s name instead of the contact’s name to populate for the Servicer (field ID VEND.X184) on the Aggregate Escrow Account input form when an Encompass user clicked the Address Book icon to add the servicer from the Business Contacts in Encompass. This issue has been resolved and the contact’s name is now populating as expected for the Servicer.

(Added on 2/28/2020)

When a loan has mortgage insurances, hazard Insurance, and real estate taxes, but does not have an escrow account, the will not have an escrow account checkbox (field ID CD4.X9) continues to be selected, but Encompass users can no longer select the your lender does not offer one checkbox (field ID CD4.X7). Previously, the will not have an escrow account checkbox (field ID CD4.X9) was selected, but a user was also able to select the your lender does not offer one checkbox (field ID CD4.X7), although the your lender does not offer one checkbox would not remain selected after the user moved to another field.

(Added on 2/28/2020)

An issue was resolved that caused content to display in the Additional Information section of the Privacy Policy output form with formatting that did not match the text in the input form. This issue has been resolved and the text now displays as expected with the proper formatting.

(Added on 2/28/2020)

When a loan has a value entered for the Proposed Mortgage Insurance (field ID 232), and a user then applies a loan program or closing cost template with no MIP rate or month configured in the template, Encompass now clears the monthly mortgage amount from the fields for Proposed Mortgage Insurance (field ID 232) and Monthly Mortgage Insurance Payment (field ID 1766). Previously, the factors, months, and amounts on the Loan Estimate and Closing disclosure were being cleared, but the dollar amount for the Proposed Mortgage Insurance (field ID 232) and Monthly Mortgage Insurance Payment (field ID 1766) was not being cleared because the recalculation for the fields was triggered only when the loan included values for the MIP rate and month.

(Updated on 4/21/2020)

The Recoup Closing Cost amount (field ID VASUMM.X27) is now being calculated as expected when an Encompass user clicks the Lock icon to manually enter a value for the for the Total Closing Costs (field ID VASUMM.X25) or to switch from a manually entered value to a calculated value. Previously the Recoup Closing Cost amount was not recalculating after clicking the Lock icon for the Total Closing Costs.

Workaround Information:

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

• Select and then clear either of the TYPE checkboxes (field ID VASUMM.X125) in the Refinance Type section on the Cash-Out Refinance tab on the VA Management input form.

(Added on 3/21/2020)

An issue has been resolved that resulted in slower performance times for input forms with multiple borrower contact icons when working with imported FNMA loans. The performance slow-downs were cause by multiple calls to the Encompass server to verify and update information for each contact on the form whenever a field value was changed on the form. The performance issues were particularly noticeable with custom input forms that contained a larger number of borrower contact icons. This issue has been resolved. Now calls for contact verification are made only when the form is first opened or when a user clicks a borrower contact icon.

Workaround Information:

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

• Reimporting the loan file eliminates the performance issue.

When importing a MISMO 3.4 loan file for a loan that is using the new URLA forms, the name entered for the Title to the Property Will be Held in What Name(s): (field ID URLA.X136) on the 1003 URLA- Lender input form is now populated with the value from the imported MISMO 3.4 file. The field is now locked after the import and the MISMO value is no longer overwritten by Encompass. Users can click the Lock icon to edit the field if needed. Previously, the borrower’s name was being automatically populated to this field by Encompass when there was a difference between the MISMO value and the Encompass value.

(Added on 3/21/2020)

When importing a MISMO 3.4 loan file for a loan that is using the new URLA forms, the calculated Other income (field ID 108) in Borrower column in the Gross Monthly Income section of the 1003 Page 2 input form is now being triggered for all non-primary borrower pairs. This is a calculated field, derived from adding the B (borrower) values in the Other Income section on page 2 of the 1003. Previously, the calculation was being triggered only for the primary borrower pair. The Other field also displays on the USDA Management and FNMA Streamline 1003 input forms and the Prequalification tool.

(Added on 3/21/2020)

When importing a MISMO 3.4 loan file for a loan that is using the new URLA forms, the Supplemental Property Insurance (field ID URLA.X144) is now populating as expected in the Proposed Monthly Payment for Property section on the 1003 URLA – Lender input form. Previously the value for this field was not imported into Encompass.

(Added on 3/21/2020)

When importing a MISMO 3.4 loan file for a loan that is using the new URLA forms, the Variable Housing Allowance on the Military Entitlement pop-up window accessible from the URLA 1003 – Part 2 is now populating as expected. Previously the value for this field was not imported into Encompass.

(Added on 3/21/2020)

When importing a MISMO 3.4 loan file for a loan that is using the new URLA forms, the VA Federal Tax amounts for the borrower and co-borrower (field IDs 1156 and 1306) are now populating as expected in the Proposed Monthly Payment for Property section on the 1003 URLA – Lender input form. Previously the value for this field was not importing into Encompass.

(Added on 3/21/2020)

An issue was resolved that cause the order of the borrower pairs to be switched when a loan using the new URLA forms was exported from Encompass as a MISMO 3.4 file and then imported into another Encompass system. This issue has been resolved and the order of the borrower pairs now displays as expected.

(Added on 3/21/2020)

An issue was resolved that caused the first four free entry text fields in the Race sections on the 1003 URLA – Part 4 input form for the borrower and co-borrower (field IDs 4126, 4128, 4137, and 4139) to display blank values when a loan using the new URLA forms was exported from Encompass as a MISMO 3.4 file and then imported into another Encompass system. This issue has been resolved and the text for these fields now populates as expected.

(Added on 3/21/2020)

Updates have been made to the behavior of fields used to indicate that a loan has a negative amortization feature.:

• The Negative Amortization checkbox (field ID URLA.X239) and the Negative Amortization dropdown box (field ID 424) on the 1003 URLA – Lender input form are now set to a blank value when the Does not have a negative amortization feature checkbox (field ID CD4.X2) is selected on the Closing Disclosure Page 4 input form.

• When using APIs to populate both the Negative Amortization dropdown box (field ID 424) and the negative amortization option checkbox (field ID CD4.X2) on the Closing Disclosure Page 4 input form, the value for the negative amortization option checkbox (field ID CD4.X2) on the Closing Disclosure Page 4 is used even when the data for the two fields contradicts.

(Added on 2/28/2020)

The Lock icons are now removed from the following HMDA Information fields when they are not populated with default values based on the HMDA mapping guidelines for the fields:

• Manufactured Secured Property Type (field ID HMDA.X39)

• Manufactured Home Land Property Interest (field ID HMDA.X40)

• Submission of Application (field ID HMDA.X42)

• AUS #1 (field ID HMDA.X44)

• AUS Recommendation #1 (field ID HMDA.X50)

• NMLS Loan Originator ID (field ID HMDA.X86)

(Added on 2/28/2020)

An issue was resolved that caused the co-borrower Credit Score for Decision Making dropdown box (field ID HMDA.X118) to revert to its previous value under some scenarios. This would occur when the No co-applicant checkbox was selected and the Action Taken (field ID 1393) had been changed to Loan Originated, and then either of the following two events occurred:

• An Encompass user clicked the Lock icon for the Credit Score for Decision Making dropdown box (field ID HMDA.X118) and manually changed the selection.

• An Encompass user selected the Loan is Partially Exempt checkbox, clicked the Apply Partial Exemption button, clicked the Lock icon for the Credit Score for Decision Making dropdown box (field ID HMDA.X118), and manually changed the selection.

This issue has been resolved and the option selected for the Credit Score for Decision Making dropdown box (field ID HMDA.X118) is being retained after manually editing the option under the scenarios described above.

(Added on 3/21/2020)

A construction-to-permanent loan with a 24-month fixed construction phase and an ARM permanent phase now displays the correct number of years for the first change of payment period in the Projected Payments table on the RegZ-LE input form. Previously the projected payment table was showing a value that was different from the value used by the Encompass Compliance Service (ECS) resulting in a warning when ECS tests were run on the loan. This issue has been resolved and the Encompass and ECS are now using the same value.

Workaround Information:

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

• Click the Customize checkbox (field ID 1678) on the RegZ-LE input form, edit the projected payment table, and run your Encompass Compliance Service Review to preview the results.

CBIZ-27229

(Added on 3/21/2020)

An update has been made to the calculation used to determine the Discount Points that can be excluded based on reduction in rate (field ID QM.X367) on the Bona Fide Discount Point Assessment pop-up window, which uses the lowest of the following three values:

• APOR Test

• Reduction in Rate Basis Test

• Starting Adjusted Rate Basis

The update addresses a known issue where, if no value exists for one of the three tests listed above, Encompass interprets the test as having a value of 0 (zero) and uses 0 (zero) as the Discount Points that can be excluded based on reduction in rate. This issue has been resolved and Encompass now ignores any blank values for the three tests listed above.

(Added on 3/21/2020)

For loans originated on an Encompass Consumer Connect website, when a loan officer’s eSignature is required on documents being sent, the email notifications sent to the loan officer now list all the documents that the loan officer is required to sign. Previously only one of the required documents would be listed on the email notification.

(Added on 3/21/2020)

For loans originated on an Encompass Consumer Connect website, a scroll bar now displays on the recipient section of the Send window when sending files to more than three recipients via the eFolder Send button. The scroll bar enables users to scroll down to view the Recipient Authorization Code fields. Previously, this section of the Send window was a static element with no scroll bar. When there were more than three recipients, the Authorization Code fields were not visible on the window and the Subject field overlapped the name of the fourth recipient on the list.

Workaround Information:

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

• Send files to three or fewer recipients at a time in separate Send action.

• Use the Tab key to tab through the fields in the recipient section to access the Authorization Code field.

For loans originated on an Encompass Consumer Connect website, an issue was resolved that resulted in an entry not being created on the Log tab in the Encompass Log when a Status Online Update email notification was sent. The update was being published and the email was being sent, but no Status Online Update entry was added under the relevant Milestone entry in the log. This issue has been resolved, and log entries are now being created when Status Online Update email notification are sent for loan originated on an Encompass Consumer Connect website.

For loans originated on an Encompass Consumer Connect website, an issue has been resolved that caused issues when trying to add some Encompass users as recipients when files were sent by clicking the Send button in the Encompass eFolder. When an Encompass user clicked the Add icon on the Send window and then attempted to add other Encompass users who were assigned to Roles for the loan in the File Contacts tool (for example, Loan Processor or Underwriter) one of the following two events would occur on the Add a File Contact window:

• The contact’s Role was not available for selection on the Category dropdown list.

• The contact’s Role was available on the Category dropdown list, but an “Object Reference” error message would display when the Save button was clicked.

This issue has been resolved and users who have been assigned to Roles for the loan file can now be added as recipients for the files.

For loans originated on an Encompass Consumer Connect website, the eConsent Declined message that displays on the Alert & Messages tab in the Encompass Loan Log now clears under the following scenario:

1. A borrower at first declines and then later accepts eConsent.

2. An Encompass user then opens and views the consent messages.

Previously the eConsent Accepted message was clearing, but the eConsent Declined message was not clearing after the messages were accessed.

For loans originated on an Encompass Consumer Connect website, an issue has been resolved that caused email notification to not be sent as expected to a loan officer when a borrower did not access eDisclosure packages by the specified date. This issue has been resolved and emails are now being sent as expected.

(Added on 3/21/2020)

An issue occurred where administrators could not generate organization reports from the Settings Reports tool for Encompass instance names that began with a numeric value. When attempting to generate an organization report for these instances, the system would return an error message that the report could not be generated. This issue has been resolved and organization reports can now be generated for Encompass instances that start with a numeric value.

An issue occurred in the Encompass SDK after performing a batch loan update with loans (originated in the Encompass 19.4 January Service Pack and later) and opening the same loan (without modifying it) in Encompass 20.1. When opening the same loan in 20.1 that was included in the batch update in the SDK, an error was triggered. This cause of this issue was identified and addressed. The error is no longer triggered when opening a loan in the SDK.

NICE-29856

(Added on 4/9/2020)

A calculation trigger issue has been resolved that affected the P&I Reduction amount (field ID VASUMM.X129) from the Statutory Closing Cost Recoupment section on the Qualification tab on the VA Management input form. Previously, the P&I Reduction amount was not recalculating when an update was made to the Original Interest Rate (field ID VASUMM.X16) for IRRRLs. This issue, which was introduced with the initial Encompass 20.1 release, has been resolved and the P&I reduction amount is now calculating as expected.

(Added on 4/9/2020)

The calculation for the Daily Periodic Rate (fields ID 4549) and the Monthly Periodic Rate (field ID 4550) on the HELOC Program tab in the HELOC Management input form has been updated to remove the portion of the calculation that multiplied the factors by 100. For example, a percentage that previously displayed as .33 now displays as .0033.

(Added on 4/16/2020)

In Encompass 20.1, some users received error messages when performing different actions in Encompass. For example, some users received the following error message when navigating to the Services tab in a loan, selecting a service provider from the Additional Services window, and then clicking the Submit button: 

Encompass was unable to load the selected service. Contact the service provider for assistance.

The cause of these error messages was identified and addressed. This issue has been resolved.