Feature Enhancements in Version 19.1

(Updated on 1/11/2019)

The following updates are being applied in Encompass 19.1 to help improve Encompass system performance around Pipeline load and refresh times, loan opening times, and time to log in.

• Pipeline Performance:
  • Please see the Pipeline Performance Enhancements section on the New Features and Forms page to learn more about new functionality that enables users to manually select specific (and multiple) loan folders that they want to access on their Pipeline. Rather than loading all loan folders in their Pipeline, users can select specific loan folders to view. Depending on the number of loans in the selected folders, this can result in faster Pipeline load times.
  • For clients with a large number of files in a Pipeline View, they could experience slower performance in Encompass due to intermittent system “memory leaks”. The cause of these leaks has been identified and the relevant code has been updated to help prevent them. The reduction of these memory leaks results in improved performance for clients with a larger number of files in their Pipeline Views.
  • Disabled user accounts belonging to users who can no longer log into Encompass have been removed from the system database that stores users’ loan access rights. This database is queried by the system each time the Pipeline is loaded.
  • When using the My Loans view option in the Pipeline, major updates have been made to help ensure loans are loaded significantly quicker than in earlier versions of Encompass.
    • If you typically use the All Loans view when managing loans in the Pipeline, you will notice a significant improvement in the time it takes for the Pipeline to load when you switch to the My Loans view. This improved Pipeline performance can also result in improved Encompass Server performance, which results in improved overall system performance. Utilize the My Loans view to realize these enhancements.

  

• Loan Open:

  • In earlier versions of Encompass, the loan data call is fully synchronous and the GetPipelineinfo call is partially asynchronous. Starting in Encompass 19.1, the GetPipelineinfo call is fully asynchronous so that the user does not have to wait as long during loan open.

  • The GetFieldIDAccess call that the Encompass system makes during the loan open process is now asynchronous, which results in faster loan open times. The compilation of business rule triggers (e.g., the GetRules method) impacting applicable loans is also now asynchronous which also reduces loan open times.

• Encompass Login:

  • Please see the eFolder Background Processing (Uploads and Conversions) Now Operating Correctly entry on the Fixed Issues page.

  • Updates have been made to the process that initializes the settings configured by the administrator using the Secondary Setup settings and the Itemization Fee Management settings to help reduce the time it takes to complete the Encompass user log in process.

  • The time it takes for the system to complete the Remote Server Login process has been reduced.

The HCLTV (field ID 1540) ratio has been added to the Piggyback Loan Tool in both the 1st Loan Position and 2nd Loan Position columns to enable loan officers to view the HELOC combined loan-to-value ratio when originating a HELOC as a piggyback with another transaction.

A new V/No Review-Site Condo option has been added to the Project Type (field ID 1012) dropdown list on the Transmittal Summary input form to match the options available under FNMA guidelines.

CBIZ-11399

A new Detached Condominium option has been added to the Property Type (field ID 1553) dropdown list on the Transmittal Summary input form. Selecting the Detached Condominium option results in both the 1-unit and Condominium checkboxes being selected the Transmittal Summary output form.

(Updated on 3/27/2019)

Updates have been made to the calculations used to populate the Down Payment/Funds from Borrower (field IDs LE2.X2 and CD3.X105) and the Funds for Borrower (Field IDs LE2.X3 and CD3.X107) in the Calculating Cash to Close sections on the Loan Estimate Page 2 and Closing Disclosure Page 3 input forms when the Purpose of Loan (field ID 19) is Purchase, Construction, or Construction - Perm.

Previously, third-party payoff amounts were not included in the calculations for the Down Payment/Funds from Borrower or the Funds for Borrower. This caused issues for loans with purchase payoffs, as well as scenarios where the loan amount exceeded the current purchase price, for example, a 203(k) scenario.

The new calculations reflect the amount of the Sale Price (field ID L726), the Sale Price of Any Personal Property Included in the Sale (field ID L79), and Third Party Payments Not Otherwise Disclosed (field ID LE2.X29) minus the Loan Amount (field ID 2) minus the Closing Costs Financed (field ID LE2.X1 on the Loan Estimate or field ID CD3.X104 on the Closing Disclosure).

The amount of the Third Party Payments Not Otherwise Disclosed (field ID LE2.X29) now populates when the Purpose of Loan (field ID 19) is Purchase. Previously this amount was populated with 0.00 for a purchase loan.

If the loan proceeds do not cover the purchase price, personal property, payoffs and financed closing costs, the difference is reflected in the Down Payment/Funds from Borrower (field ID LE2.X2 on the Loan Estimate or field ID CD3.X105 on the Closing Disclosure). If excess funds are available, they are disclosed and reflected in the Funds for Borrower (field IDs LE2.X3 on the Loan Estimate or field ID CD3.X107 on the Closing Disclosure).

This update enables payoffs to be captured on the Calculating Cash to Close section on the Loan Estimate and Closing Disclosure. However, the payoffs are not reflected in the Details of Transaction section on input forms such as the 2015 Itemization and the 1003 Page 3. If you click the Lock icon to add the purchase payoff in the Refinance field (field ID 1092), the DU results will double the cash amount for the payoffs in the cash to close calculation. This situation will be resolved when the new version of the 1003 URLA form is released later in 2019. The new URLA separates the mortgage payoffs applicable to the subject property for a refinance loan from the non-mortgage payoff amounts.

For Purchase transactions that were disclosed prior to 19.1 with one or more payoff items included, the Down Payment/Funds from Borrower (field IDs LE2.X2 and CD3.X105), Funds for Borrower (field IDs LE2.X3 and CD3.X107), and the Third Party Payments Not Otherwise Disclosed (LE2.X29) are not editable and the existing values are retained. Click the Lock icon to trigger the new calculation.

In previous versions of Encompass, the Actual Received Date for the Loan Estimate (LE) was not being populated when disclosures were sent electronically prior to the borrower or co-borrower providing their consent to receive disclosures electronically, even if the consent and the received date occurred on or before the LE Due date (field ID 3143).

Starting in Encompass 19.1, when disclosures are accessed electronically by borrowers, the Actual Received Date in the LE will be populated based on whether the borrower provided eConsent prior to them accessing the disclosures or not:

• If consent is obtained prior to disclosures being sent, the Actual Received Date for the borrower and co-borrower will be populated when the borrower or co-borrower accesses the disclosure package (existing behavior) or
• If prior consent status is No or has not been received, the Actual Received Date for the borrower or co-borrower will be populated as long as both the borrower or co-borrower provide consent and accesses the disclosure package on or before the LE Due Date. This is new behavior.
• The Actual Receipt Date will be left blank in the following scenarios:
  • The borrower (or co-borrower respectively) never accesses the disclosure package
  • If the borrower or co-borrower accesses the disclosure package after the LE Due Date when prior consent status was No
  • If there is no LE Due Date populated

Please note that this new behavior impacts electronic disclosures (i.e., esigned disclosures) only. Disclosures sent by any other method (e.g. in person, by mail, etc.) will persist as they did in earlier versions of Encompass and the Actual Received Date will be populated accordingly. For loans started in previous versions of Encompass where disclosures have not been sent, this new logic will be used. For loans started in previous versions of Encompass that do have disclosures, the previous logic will continue to be used for those loans.

On the Forms menu provided inside each loan file, the RESPA-TILA Form Version option is provided to enable users to select the version of the Encompass input forms to use for the loan file (when they are starting a new loan) or to indicate which version of the input forms are being used for the loan file (the forms being used cannot be changed once initial disclosures are sent to the borrower). To make this option more user friendly and efficient, the RESPA-TILA Form Version indicator has been moved from the very bottom of the Forms menu to the very top of the Forms menu.

When utilizing the fee level change of circumstance process in earlier versions of Encompass to indicate why the Loan Estimate (LE) or Closing Disclosure (CD) was modified after its initial disclosure, users could not edit or select a change of circumstance reason unless a Good Faith Fee Variance Violated alert was triggered. Then users could indicate the reason in the alert and update fee change details about each changed fee. A changed circumstance reason could only be selected if there was first a fee change that triggered a Good Faith Fee Variance Violated alert. This limitation prevented users from documenting and disclosing informational only reasons on the LE or CD when no fee changes occurred.

Starting in Encompass 19.1, Encompass users can now document disclosure reasons with and without a changed circumstance when doing a fee level disclosure (i.e., when the Fee Level Disclosures checkbox (field ID 4461) is selected). Certain informational disclosure reasons on the LE Page 1 and CD Page 1 are now available to select and enter details about, and they will be reflected in the Disclosure Tracking tool as applicable. This enables fee changes to continue to be documented at the fee level with the added benefit of permitting disclosure reasons to be identified at the disclosure level.

The following changed circumstance fields and reasons on the LE Page 1 and CD Page 1 are now always enabled so they can be selected to indicate a changed circumstance reason:

• Changed Circumstance (field ID 3168 and CD1.X61)
• Changes Received Date (if Changed Circumstance field is selected) (field ID 3165 and CD1.X62)
• Changed Circumstance text box and Lookup (magnifying glass) icon (if Changed Circumstance field is selected) (field ID 3169 and CD1.X64)
• Comments box (if Changed Circumstance field is selected) (field ID LE1.X86 and CD1.X65)

Reasons:

• Change in APR (field ID CD1.X52)
• Change in Loan Product (field ID CD1.X53)
• Prepayment Penalty Added (field ID CD1.X54)
• 24-hour Advanced Preview (field ID CD1.X56)
• Tolerance Cure (field ID CD1.X57)
• Clerical Error Correction (field ID CD1.X58)
• Other (field ID LE1.X84 and CD1.X59)

Note that users can still document fee changes and reasons in the Good Faith Fee Variance Violated alert just as in previous versions of Encompass. Changes made in the alert will overwrite the existing change of circumstance reasons and details on the LE Page 1 and CD Page 1. However, changes made to the LE Page 1 and CD Page 1 reasons and change of circumstance details will not be reflected in the Good Faith Fee Variance Violated alert.

(Updated on 2/6/2019)

The following options have been removed from the Offering Identifier dropdown list (field ID CASASRN.X163) on the Freddie Mac Additional Data Input Form because they are no longer supported by Freddie Mac:

• 210: Alt 97

• 220: Freddie Mac 100

• 230: Initial Int 10/20 FIXED

• 231: Initial Int 15/15 FIXED

• 232: Initial Int ARM

• 233: Initial Int ARM 10 Year

• 240: Home Possible 100

• 242: Home Possible Neighborhood Solutions 100

The remaining offerings are still available on the dropdown list:

• 241: Home Possible

• 243: Home Possible Neighborhood Solution

• 250: Home Possible Advantage

• 251: Home Possible Advantage for HFAs

• 310: Relief Refinance – Open Access

• 320: Enhanced Relief Refinance

(Added on 12/21/2018)

A new version of the Settlement Service Provider List printed output form is now available to generate and/or print in Encompass. The purpose of this new version is to provide a version of the Settlement Service Provider List that does not contain the Estimate column for fees in the Additional Details for Services You Can Shop For and the Additional Details for Services You Cannot Shop For sections of the form.

The title of this new form is 2015 Settlement Service Provider List - No Fees.

To access and print this form in Encompass, click the Print icon from a loan file or Pipeline view, click the Standard Forms tab, and then select General Forms from the Look In dropdown list. Locate the form in the list, and then click Add to move it to the Selected Forms list. Use the buttons at the bottom of the window to print or manage the form.

It is important to note that when this version of the form is disclosed, it is currently not tracked by the Disclosure Tracking tool automatically. If you opt to use this form and include it in a disclosure, you will need to manually create a disclosure tracking entry in the tool to track its disclosure details. The Disclosure Tracking tool will be updated to include this version of the form in a future release.

The following new checkboxes have been added to the Banker Application Disclosure and Fee Agreement section of the State-Specific Disclosure Information input form for New York to enable Encompass users to indicate whether payment will be received from or paid to third parties for assignment of commitments.

• Will pay to third party for assignment of commitment (field ID DISCLOSURE.X1206)

• Will receive form third party for assignment of commitment (field ID DISCLOSURE.X1207)

Selecting one or both of these checkboxes on the input form selects the appropriate options on page 2 or the output form.

• I understand that you routinely assign the commitments you have issued in your own name to a third party or parties. The amount of any fee you will __ Pay To __ Receive From the third party or parties is _____.

New content has been added to the Commitment Agreement section of the State-Specific Information input form for Wisconsin to disclose loan terms that are subject to change prior to the expiration of the commitment.

This section contains four checkboxes and a free-entry field.

• Interest Rate (field ID DISCLOSURE.X477) checkbox

• Discount Points (field ID DISCLOSURE.X481) checkbox

• Fees (field ID DISCLOSURE.X482) checkbox

• Other (field ID DISCLOSURE.X483 checkbox

• Explanation of Other free entry field (field ID DISCLOSURE.X484) displays after the Other checkbox to enable the entry of a detailed description when you select the Other checkbox.

A new Commitment Expiration Date field (field ID DISCLOSURE.X1205) has been added to the State-Specific Information input forms for Kentucky, Maryland, Vermont, Virginia, and Wisconsin to populate the expiration date to the commitment output forms for these states. Previously, the commitment forms were populated with the Mortgage Loan Commitment Expires date (field ID 1072). The creation of the new field avoids any potential conflicts between dates used on the state-specific forms and the dates used on other tools and forms in Encompass.

For loans created prior to upgrading to the Encompass 19.1 release, when a disclosure tracking entry exists, the Mortgage Loan Commitment Expires date (field ID 1072) is copied to the new Commitment Expiration Date (field ID DISCLOSURE.X1205) on the state-specific disclosure information forms listed above.

Currently in Encompass, when sorting loans by the Last Finished Milestone column, all custom milestones are grouped at the top of the column (in no particular order), followed by standard milestones in ascending or descending alphabetical order. This same sorting result also occurs when sorting by the Next Expected Milestone column.

To enable users to get a more accurate sorting result when custom milestones are in use, two new Pipeline columns are now available: Last Milestone Sorted and Next Milestone Sorted. When sorting by either of these columns, the standard and custom milestones are sorted alphabetically. Custom milestones are intermingled with standard milestones accordingly and no longer grouped at the top of the columns.

Note that the Last Milestone Sorted and Next Milestone Sorted columns are not displayed in the Pipeline by default. To add these columns, right-click a Pipeline column header, select the columns in the Customize Columns window, and then click OK.

(Added on 1/30/2019)

When administrators are configuring a persona, they can set up access permissions for the Pipeline. As part of this configuration, they can create the default Pipeline view that the persona will see when they log into Encompass. As part of this set up, they have the option (but it is not required) to indicate the loan folder that will be used for the default Pipeline View.

In earlier versions of Encompass, if a user was viewing a loan folder in the Pipeline and then they switched to a different Pipeline View where no loan folder was defined by the administrator, the user would see the same loan folder that they were using in the previous Pipeline View. Starting in Encompass 19.1, when a user is viewing one (or more) loan folders in the Pipeline and then switches to a different Pipeline View where no loan folder was defined by the administrator, the user will now see the loan folder that has been indicated as the Working Folder in the user's user profile (i.e., the User Details screen).

(Updated on 1/29/2019)

In earlier versions of Encompass, users who fail to enter the correct password when logging into Encompass a certain number of times are locked out of their accounts and must have an administrator reset the account. Starting in Encompass 19.1, administrators can now use new password policies in the Encompass Admin Tools to enable a time-based lock-out period for users (for example, 15 minutes) so that a series of failed log in attempts causes the account to be locked for a set period of time. It will then be automatically unlocked.

In addition, a new policy is also available where administrators can enable a time-based lock-out period for the user who logs into Encompass using the ‘admin’ user ID (i.e., the admin user).

This change does not impact your current password policy settings (even if they are less stringent than above). The validation is done only if you modify your password policy settings. If any of the existing policy requirements do not conform to these guidelines, a warning message will be triggered to notify the administrator that the settings should be more stringent in order to conform to best practices in security and password management and require the administrator to conform to these minimum guidelines. This will ensure that when users change their password after the subsequent expiration date, they set more stringent passwords.

In addition, once you make a change to your password policy (and thus the enforcement of the complexity rules will then be in effect), you need to ensure that all of the user passwords for the Encompass Software Development Kit (SDK) and Encompass Developer Connect API applications are also updated to meet the complexity rules so you can avoid any interruptions with these applications.

Failed log in attempts that occur during the time the user is locked out are now recorded in the System Audit Trail. All failed log in attempts will continue to be recorded in the System Audit Trail as in earlier versions of Encompass.

For administrators or other authorized users who go into the Personas tool and want to delete a specific persona type, the following warning message is now displayed after the user selects the persona to delete, and then clicks the Delete icon:

The following list of users may be affected if you delete the [persona type] Persona. All users must be assigned one persona in order to login.

All users who are assigned with the persona that is being deleted will be listed in the pop-up window. Please note that users listed here may also be assigned with additional personas besides the one being deleted.

Previously, the warning message provided on this pop-up window was as follows:

The following list of users have only the [persona type] persona. If you delete the [persona type] persona, remember to assign those users a new persona. Otherwise, they will not be able to login.

The message on the pop-up window has been updated to remove the statement that the persona being deleted is the only persona that is assigned to the users listed in the window.

The users in the list are assigned with the persona that is being deleted, but they may be assigned with additional personas, and they may be impacted if this is the only persona that is assigned to them. If users in the list are already assigned with a different persona, they will still be able to log into Encompass, even if the persona type in question is deleted. It is recommended that the administrator review each user in the list and confirm that they will still have a persona assigned to them if they proceed to delete the persona from the tool.

A new Job Title field is now provided on the User Details screen that administrators use to create and edit users in Encompass. When using the Company/User Setup > Organization/Users setting to set up users, the new Job Title field is now provided where administrators can enter the user’s job title. This title is for informational purposes only and does not impact the user’s access to Encompass features or Persona settings.

In addition, a Job Title field is also being added to the following screens in Encompass:

• In the File Contacts tool, a new Job Title field is provided for all of the categories/roles listed in the tool starting with the File Starter file contact up to, and including, the Title Insurance Company file contact (except for the Lender file contact). If a user’s job title has been entered in the Job Title field on the User Details screen, that title will automatically be populated to the Job Title field in the File Contacts tool when that user is assigned as a file contact.

Note that when importing a business contact into the File Contacts tool by clicking the Address Book icon and selecting a contact, the Job Title value from the User Details screen will not be imported into the Job Title field for the Appraiser, Escrow Company, and Title Insurance Company file contacts. Once imported, users can enter the title in the Job Title field for these file contacts.

• A new Print user’s job title checkbox is now provided in the From section of the VOD, VOE, VOL, VOM, and VOR input forms. Users can select this checkbox to print the user’s job title (as entered on the User Details screen) to the Verification output form. In previous versions of Encompass, a Print user’s name as title checkbox was provided in this From section on these Verification input forms. This checkbox has been re-purposed to Print user’s name. When this checkbox is selected, the user’s first and last name will be printed to the Verification output form. Note that if a user selects a checkbox here, but a user name or job title is not entered in the User Details screen, the Title field on the Verification input form will be blanked out accordingly.

• In the Custom Print Form Settings, the following new fields are now available to be added to custom forms:
  • In the Category field for ‘Company’: Loan Officer Title, Loan Processor Title
  • In the Category field for ‘Loan Team Member’: Current Loan Team Member Title, Previous Loan Team Member Title, Loan Team Member Title

These new fields are now available on the Team Members tab in the Reporting Database as well. Administrators can select these fields on the Team Members tab and then add them to the Reporting Database as needed.

• The new Job Title field is also exposed in the Encompass SDK so that SDK developers have the ability to reference the Job Title field in forms, reports, and other areas in Encompass via the SDK.

To track the receipt and acceptance of events generated through the Encompass Title and Closing Center, the following new fields have been added to Encompass. All of the fields are date-and-time stamped and are reportable fields that can be added to the Encompass Reporting Database.

(Updated on 12/27/2018)

For new installations of the Encompass Smart Client, ExpertPDF version 12 is now included in the installation package. ExpertPDF.is a .NET library that is used by Encompass to convert HTML to PDF documents. This upgraded version of ExpertPDF helps ensure that PDF files in the eFolder can be exported, converted, and managed without issue. Please note that for existing Encompass systems that are upgraded to Encompass 19.1, ExpertPDF version 12 will also be included with the upgrade.