Encompass 24.1 Persona-Based Release Notes

(Updated on 3/20/2024)

As part of the new Encompass 24.1 automation enhancements in the web version of Encompass, new alerts are being introduced in Encompass Settings. These disclosure compliance alerts can help ensure loans are compliant with all applicable state and federal regulations, including those applicable to timing and content of disclosures to maintain good faith with the consumer. These alerts, which are set up and managed in the Encompass Settings > Loan Setup > Alerts tool and triggered in loan files in the desktop and web versions of Encompass, enable lenders to ensure all required data is complete for sending disclosures (both manually and with automated workflows).

These alerts will be triggered for loans using the Forms > URLA Form Version > URLA 2020 input forms only.

The following alerts are being introduced:

• At App Disclosure Requirements
• Three-Day Disclosure Requirements

Just like with previous alerts, the Alert Settings screen for each alert provides a default message that displays when the alert is triggered in a loan file (editable) and a Field Triggers section that lists the fields that, once populated in the loan, will trigger the alert.

A new section, Fields Needed for Completion, is now provided in the Alert Settings screen for these alerts. The loan level fields listed here are the fields that must be populated in order for the disclosure to be considered completed. Administrators can click the Add icon here to add additional required fields as needed.

In addition to these new alerts, two existing alerts- Redisclose Loan Estimate (Rate Lock) and Redisclose Loan Estimate (Changed Circumstance)- have been updated with the new Fields Needed for Completion section.

When these alerts are triggered in the loan file, the required completion fields are listed. Once these fields are populated, the Disclosure Ready Date on the alert screen in the loan file will be populated. (Until then, this date field is blank.) When the date is added, a scheduler will then send out the disclosures for the loan. (The disclosures may also be sent manually prior to the scheduler sending them.) Note that the administrator needs to set up a scheduler and a workflow rule for the Disclosure Ready Date field in the web version of Encompass in order for the disclosures to be sent automatically when the date field is populated.)

Alert in Encompass (desktop version)

Alert in Encompass (web version)

Important Notes:

• As mentioned earlier, these new alerts are part of a broader initiative to provide automation features in the web version of Encompass. Setting up and enabling these alerts in Encompass Settings ensures that the alerts will be triggered in the desktop version of Encompass when the alert conditions are met, but they will not be triggered in the web version of Encompass unless additional configuration of workflow rules and other requirements are met. Refer to the Encompass (web version) 24.1 release notes for more information about these automation enhancements.

• In addition to the new Fields Needed for Completion section, the default alert message for the Redisclose Loan Estimate (Rate Lock) alert has been updated to indicate that the loan team member should change only the rate-related fields in the Loan Estimate for the required fields. (This potion is highlighted in the Redisclose Loan Estimate (Rate Lock) alert settings screen example provide above.) These required fields are the fields listed in the Fields Needed for Completion section.

• When a loan is duplicated or borrowers are swapped:

  • The date fields in the Fields Needed for Completion list are cleared out and the system re-checks the loan to determine if it meets the alert requirements.

  • Disclosure Tracking logs are not re-checked prior to the system reviewing the loan again for the alert requirements. Even if initial disclosures have been sent and a Disclosure Tracking record has been created, the date fields are cleared.

  • If borrowers are swapped in the loan after initial disclosures have been sent, a redisclosure is required.

• When working with the At App Disclosure Requirements, Redisclose Loan Estimate (Rate Lock), and Redisclose Loan Estimate (Changed Circumstance) alert, additional fields are included in the Fields Needed for Completion list if the eDisclosure Fulfillment service is running for the Encompass instance. These fields are:

  • Field ID 5012 - Scheduled Fulfillment Date

  • Shipping To*

    • URLA.X197 - Borrower Street Address (Mailing Address)
    • 1417 - Borrower City (Mailing Address)
    • 1418 - Borrower State (Mailing Address)
    • 1419 - Borrower ZIP Code (Mailing Address)
    • FR0126 - Borrower Current Street Address
    • FR0106 - Borrower Current City
    • FR0108 - Borrower Current ZIP Code

  *Only one group of these Shipping To fields in the loan must be completed to satisfy the alert requirements. Either all of the FR0xxx fields or all of the other group of Shipping To fields

  • Shipping From

    • 3343 - Lender Current Street Address
    • 3344 - Lender Current City
    • 3345 - Lender Current State
    • 3346 - Lender Current ZIP Code

If the service is stopped at any time, these fields will no longer be displayed in the list.

• To add additional fields to the Fields Needed for Completion section, click the Add icon, and then type the field ID of the field(s) to add in the Add Fields Needed for Completion pop-up window. When finished, click Add.

• To delete a field from the list, select the field, and then click the Delete icon. The fields in the default list of Fields Needed for Completion section (shown in the Alert Settings screen example above) cannot be deleted from the alert.

• If the eDisclosure Fulfillment service is stopped, administrators can use the Add icon to add eDisclosure Fulfillment fields (for example, field 1418) if needed. If the service is then started at a later time, all of the eDisclosure Fulfillment fields will be added to the list and any duplicate eDisclosure Fulfillment fields that were manually added previously will be overwritten. The eDisclosure Fulfillment fields will be considered required and cannot be deleted from the list. If the eDisclosure Fulfillment service is then stopped at a later time, the eDisclosure Fulfillment fields will be removed from the list. Any of these fields that were manually added previously would need to be manually added again to return them to the list.

• For existing loans and loans opened prior to Encompass 24.1, calculations will not get triggered (i.e., the Disclosure Ready Date field will not be populated even if all required fields are completed). The calculations will only be triggered if a loan team member updates one of the Fields Needed for Completion fields.

For more information about the automation enhancements in the web version of Encompass 24.1, including data perfection tools, schedulers, and configurable rules to trigger loan actions, refer to the Encompass (web version) 24.1 release notes.

New fields have been added to Encompass to enable loan team members to check the progress of disclosures in the web version of Encompass.

Please note, these fields are available in the following Encompass locations only: Encompass Reporting Database, Reports, business rule settings, data templates, and borrower pair management pop-up windows.

• Ready Disclosure 3 Day Package Date (field ID 5001)
• Ready Disclosure at Lock Package Date (field ID 5003)
• Ready Disclosure at Application Package Date (field ID 5005)
• Ready Disclosure Change of Circumstance Package Date (field ID 5007)
• Signing Mode (field ID 5008)
• Notify on Receipt (field ID 5009)
• Notify when not Received Date (field ID 5010)
• Fulfillment Enabled (field ID 5011)
• Scheduled Fulfillment Date (field ID 5012)

(Updated on 3/20/2024)

To help optimize Encompass Pipeline loading performance, archived loans will no longer be displayed in the Pipeline by default. For loan team members that want to view archived loans, they can select the new Include Archive Loans checkbox at the top of the screen to include these loans in the Pipeline.

By default, the Include Archive Loans checkbox is not selected and it is disabled (i.e., grayed out) for all non-admin users, which results in archived loans not displaying in the Pipeline. This checkbox will only be enabled for users with the required Persona permissions.

Loans that are archived are simply excluded from the initial Pipeline load for performance purposes. These loans are not being moved, and they can easily be retrieved by selecting the Include Archived Loans checkbox.

For more details and information about this archive feature, please review the 24.1 - Encompass : New Archive Feature FAQ knowledge article (KA #000115380).

In addition, a new Archived checkbox (field ID 5016) is now provided in the loan view at the top of the screen. Users can select this checkbox to archive the loan.

If you select the Archived checkbox to archive a loan and move it to an archive loan folder, and then you decide later to make the loan active again by clearing the Archived checkbox, it is recommended that you move the loan from the archive loan folder to an active loan folder. If you leave the active loan in the archive loan folder, it will be returned to an archived loan status again when you upgrade to the next Encompass release. Loans in archive loan folders that are not modified for at least three years will also be automatically marked as an archived loan, so best practice is to always move active loans to an active loan folder.

Please note if you are using the External Reporting Database (ERDB), changes to the Archived checkbox (field ID 5016) will not be reflected there. When a loan is moved from an active loan folder to an archive loan folder, the value in field 5016 is reflected as N instead of Y. This ERDB issue will be addressed in a future Encompass release.

Automatic Archiving of Loans Three Years and Older

In addition to the new archived loan features discussed above, when you upgrade to Encompass 24.1 all loans that have not been modified for three years or longer will be marked as archived loans. Loans in archive folders will also get marked as archived automatically.

Encompass administrators can now enable loan team members to withdraw eConsent agreements that have been sent to borrowers or other recipients on behalf of the borrower or recipient. This option is useful for situations where a borrower has agreed to accept electronic disclosures (i.e., eConsent), but later decides they prefer printed paper hard copies. Using the Encompass Admin Tools > Settings Manager, administrators can set the new Allow withdrawal of eConsent policy to Enabled. (By default, this policy is disabled and the buttons provided to withdraw eConsent agreements are not available.)

When enabled, a Withdraw Consent button displays next to each eConsent request in the eConsent Status pop-up window for loan team members who are authorized to withdraw eConsent requests. This authorization is based on the loan team member’s persona setting.

In addition, a Withdrawn By column has been added to the eConsent Status pop-up window. This column is populated with the Encompass User ID of the user who has withdrawn the eConsent.

When the Withdraw Consent button is clicked, the eConsent agreement is withdrawn and the eConsent Status is updated to Rejected.

The Withdrawn By and eConsent Status values in this window are also reflected on the Request eConsent screen in the web version of Encompass.

(Updated on 2/13/2024)

In addition to the new Add From Template button discussed above, a new dropdown field (field ID IR0193) has been added to the Request for Transcript of Tax input form. Use this field to select the version of the transcript of tax form that is being requested: 

• 4506-C October 2022
• 4506-C September 2020
• 4506-T
• 8821

By default, the field is populated with the 4506-C October 2022 version.

This new dropdown field effectively replaces the form, version, and checkbox fields that were previously used to indicate the form version on the Request for Transcript of Tax input form.

A different version of this field (field ID IRS4506.X93) is also provided in the same position on the Request for Transcript of Tax (Classic) input form. The dropdown list provides three form options: 

• 4506-C October 2022
• 4506-C September 2020
• 4506-T

A Note About Form 8821:

In previous versions of Encompass, Form 8821 Request Tax Information Authorization was included as a custom print form in Encompass. As discussed above, Form 8821 is now provided as an option on the standard Request for Transcript of Tax input form in Encompass 24.1. The custom print form version is no longer included in Encompass. Please note that Form 8821 is now printed in letter size format to ensure it fits both opening and closing document packages. The custom print form version of Form 8821 in previous versions of Encompass was printed in legal size format.

(Updated on March 19, 2024)

A new Zero Based Par Pricing section has been added to the Product and Pricing setting under Secondary Setup. This section enables locks to be offered in basis points instead of par, by channel, to make them easier for borrowers to understand.

Please ensure your product and pricing provider supports pricing in this format before enabling these settings.

The lock extension fee and re-lock fee calculations have been updated on the Secondary Lock Tool based on whether zero based par pricing is enabled or not. If the settings are enabled, each lock extension fee and re-lock fee will be multiplied by -1.

The Gain Loss % (field ID 2296) calculations have been updated in the Sell Side Lock and Pricing column on the Secondary Lock Tool based on whether zero based par pricing is enabled or not. The updated calculations are as follows:

• When zero based par pricing is enabled, the calculation will be Total Sell Price (field ID 2295) + Total Buy Price (field ID 2218) - 100 = Gain Loss %.
• When zero based par pricing is disabled, the calculation will be Total Sell Price (field ID 2295) - Total Buy Price (field ID 2218) = Gain Loss %.

Since Gain Loss $ (field ID 2028) is dependent on the Gain Loss %, the Gain Loss $ value will change based on the Gain Loss %.

The par pricing text has been updated on the Lock Request Form and the Secondary Lock Tool based on the zero based par pricing setting.

• When zero based par pricing is enabled, the par pricing text in the Request Rate Lock and Pricing column on the Detail Lock Request screen changes from “(Par Pricing is 100.00)” to “(Par Pricing is 0.00”).

• When zero based par pricing is enabled, the par pricing text in the Buy Side Lock Request column and the Buy Side Lock and Pricing column on the Secondary Lock Tool changes from “(Par Pricing is 100.00)” to “(Par Pricing is 0.00)”.

• Regardless of whether zero based par pricing is enabled, the par pricing text in the Sell Side Lock and Pricing column and the Execution Comparison column will display “(Par pricing is 100.00)”.

When zero based par pricing is enabled in Encompass, the par pricing text on the web version of Encompass Detailed Lock Request changes from “Par Pricing is 100” to “Par Pricing is 0.00”.

The following new read-only fields have been added to Encompass to support importing Encompass Compliance Service (Mavent) data into loans. Please note that these fields are available in the Encompass Reporting Database, but they are not currently displayed on any Encompass input forms or tools. These fields will be added to the ECS Data Viewer tool in a future Encompass release.

Please note, Mavent has not yet mapped applicable fields to these fields, so Mavent data is not yet populating in these fields. This mapping will be completed in a future release.

• Annual Percentage Rate (field ID COMPLIANCEREVIEW.X19)
• Finance Charge Amount (COMPLIANCEREVIEW.X20)
• Federal Total Loan Amount (COMPLIANCEREVIEW.X21)
• State Total Loan Amount (COMPLIANCEREVIEW.X22)
• QM Points and Fees Total (COMPLIANCEREVIEW.X23)
• Ability-to-Repay Loan Type (COMPLIANCEREVIEW.X24)
• Qualified Mortgage Loan Type (COMPLIANCEREVIEW.X25)
• Qualified Mortgage Eligible (COMPLIANCEREVIEW.X26)
• Higher-Priced Covered Trans (COMPLIANCEREVIEW.X27)
• Loan Term and Features (COMPLIANCEREVIEW.X28)
• QM Points and Fees Limit (COMPLIANCEREVIEW.X29)
• Underwriting Factors (COMPLIANCEREVIEW.X30)
• QM Price-Based Limit (COMPLIANCEREVIEW.X31)
• Review ID (COMPLIANCEREVIEW.X32)

To enable loan team members to override the system-calculated value populated to the Subject Loan Unpaid Principal Balance Amount field (field ID ULDD.X1), a new field Lock is now provided for this field. By default, field ULDD.X1 is populated with the current unpaid principal balance entered in field SERVICE.X57 on the Interim Servicing Worksheet once Interim Servicing is completed. Authorized users can now click the blue Lock icon for field ULDD.X1 to manually enter the value they want reflected on the ULDD export to the GSEs.

The Application Date field (field ID HMDA.X29) has been added to the 2018 HMDA Purchased Loans tab on the HMDA Information input form. (This tab displays in the input form when 6. Purchased loan is selected from the Action Taken drop-down list.) Previously, this field was only available on the 2018 HMDA Originated/Adverse Action Loans tab on this input form.

This field has been added to the Purchased Loans tab because in HMDA, Purchased Loans are expected to report NA for the Application Date since the application dates on purchased loans may happen one or more quarters or even years before the loan is purchased. NA is populated to this field by default. Authorized users may click the Lock icon, and then overwrite the NA value by manually typing or selecting a date from the calendar.

In previous versions of Encompass, when two loans are linked and one or more fees have been added to the 2015 Itemization input form, you cannot update the Paid By dropdown field for the fee directly on the input form. Instead, you must open the Fee Details pop-up window for the fee and then manually update the payment information. Encompass 24.1 has been updated to enable loan team members to update the Paid By dropdown selection for a fee directly on the 2015 Itemization input form in linked loans, just like you can for loans that are not linked.

(Updated on 4/15/2024)

Changes have been made to the Estimated Construction Interest (field ID 4088) calculation in Encompass. This change only affects Construction Only loans where the Estimated Interest On (field ID SYS.X6) is set to Method B (Full Loan). With this update, the calculation logic for field 4088 is calculating from the estimated closing date (field ID 763), or if that is blank, from the disbursement date (field ID 2553) to the final construction payment date (field ID 1961) for 365/360 (new behavior) and 365/365 (new behavior) loans. This update is being made to ensure that the Estimated Construction Interest calculation includes the final construction pay date (field ID 1961).

Please note, this update is strictly a correction to how Encompass calculates the number of days for collecting construction interests for 365/360 and 365/365 loans. The calculation used for 360/360 loans was already correct and has not changed. If you open an existing 365/360 or 365/365 loan file created prior to 24.1, the new interest calculation for field 4088 will be used so that the correct value is provided in the loan.

When printing the Amortization Schedule from Encompass, the value provided in the Resulting LTV% column is now rounded to three decimals to match the value provided in the Threshold/LTV% column in the Amortization Schedule viewable in Encompass. Previously, the Resulting LTV% value on the printed output form was rounded to four decimals.

Printed output form in 24.1

A No checkbox for the Borrower LDP/SAM Search field (field ID 3026) and the Co-Borrower LDP/SAM search field (field ID 3027) has been added to the FHA Management input form’s Tracking tab and the HUD-92900LT FHA Loan Transmittal input form to align with HUD’s FHA requirements. Select Yes if the individual is found in the LDP or SAM search or No if they are not found.

Currently in Encompass, when a lock extension is approved, the updated field values for the Lock Request Lock # Days (field ID 2090) and Lock Expiration Date (field ID 2091) fields are not captured to the fields (the values are stored elsewhere within Encompass) but are displayed correctly on the Lock Request Form. This causes inconsistent field values between Encompass and the web version of Encompass because the web version retrieves the field values from the fields themselves. As part of this release, Encompass will be updated to provide the web version of Encompass the most current Lock Request Lock # Days and Lock Expiration Date field values.

In previous versions of Encompass, when a Correspondent loan is priced via the Encompass Product & Pricing Service (EPPS), buy side pricing with an SRP adjustment is requested from EPPS, Encompass is updated with buy side pricing from EPPS, sell side pricing is requested from EPPS, and then the user clicks the Update Encompass button in EPPS, the Secondary Lock Tool is not updated with the sell side pricing data from EPPS. As part of this 24.1 release, Encompass has been updated to ensure the Secondary Lock Tool has the most current sell side pricing data from EPPS.

As part of Fannie Mae's ULDD Phase 5(1) specification updates, a new field to capture the Servicing Transfer Effective Date (field ID ULDD.X200) has been added to the ULDD/PDD’s Fannie Mae tab and the Correspondent Loan Status tool. This field has been added to the ULDD/PDD’s Fannie Mae form in the web version of Encompass as well.

Please note, the corresponding field mapping required for the Fannie Mae ULDD export for this field is not available. This functionality will be completed in a future Encompass/GSE Services release.

The following fields have been added to the Fannie Mae tab on the ULDD/PDD input form:

• Other Funds Collected at Closing (field ID ULDD.X110)
• Other Funds Collected at Closing for (field ID ULDD.X111)

Note that these fields already existed on the Freddie Mac tab on the ULDD/PDD input form.

The following fields have been added to the Freddie Mac tab on the ULDD/PDD input form.

• Document Custodian ID (field ID ULDD.X114)
• Servicer ID (field ID ULDD.X116)

These fields were already provided on other input forms in previous versions of Encompass.

The following label changes have been made for three Freddie Mac options in the ARM Index Type dropdown field (field IDs 1959, 4512, LE2.X96) per Freddie Mac’s guidance:

• Freddie Mac PMMS US 15-Year Fixed Rate changed to Freddie Mac PMMS US 15-Year FRM
• Freddie Mac PMMS US 30-Year Fixed Rate changed to Freddie Mac PMMS US 30-Year FRM
• Freddie Mac PMMS US 5-Year Adjustable Rate changed to Freddie Mac PMMS US 5-Year ARM (Retired)

The following fields have been added to the Ginnie Mae tab on the ULDD/PDD input form.

• Settlement Date (field ID ULDD.GNM.SettlementDate)
• Initial Pay Date (field ID ULDD.GNM.InitialPayDate)
• EIN # (field ID ULDD.GNM.EinNumber)
• Subservicer (field ID ULDD.GNM.Subservicer)

The Inspection ID (field ID CASASRN.X220) field is now available on the Freddie Mac Additional Data input form. This field is intended for users to add the inspection identification number provided by Freddie Mac’s bACE API system.

The following new fields have been added to the GSE Additional Provider Data input form:

• Argyle (Bor, CoBor)
• Freddie Mac AIM Check (Bor, CoBor)
• Gateless (Bor,Cobor)

When adding borrower information to the Borrower Summary - Origination input form (and others), you can click the Preferred Contact (clock) icon in the Borrower Information section to open the Borrower Contact Preference pop-up window and specify the borrower’s time zone and preferred day and time of day to be contacted. A new Notes field has been added to this pop-up, where you can add additional information about the borrower preferences such as a set time to contact them, whether to use the mobile phone vs. home phone, or any other preference information that cannot otherwise be indicated in the pop-up window. This new field is available in the contact preferences for the borrower (field ID 5013), co-borrower (field ID 5014), and non-borrowing owner (field ID NBOC0141 in the File Contacts tool).

Currently in Encompass, when a loan is assigned to a loan trade and then is assigned to an MBS pool (or vice versa), that loan is updated with a Trade Assignment Status of “Removed-Pending” and is not removed from the Loan Trade (MBS Pool) Loans tab. As part of this release, Encompass will be updated so the loan is removed from the Loan Trade (MBS Pool) Loans tab.

(Updated on 3/20/2024)

In the Admin Tools > Settings Manager, a new Automated Data Completion category and related settings are now provided. Administrators can use these settings to enable Encompass to retrieve data systematically and automatically populate/complete data within specific forms and settings. This enables the data to be completed without users having to open the form or setting and then manually click a button or similar to populate the data.

Automated data completion may be enabled for the following loan data:

• Home Counseling Provider List on the Home Counseling Providers input form
• Area Median Income (AMI)

Home Counseling Providers

When the Home Counselors option is enabled, Encompass will retrieve Home Counseling data systematically as follows, provided these prerequisites are met:

• The Home Counseling Services Data Template must be applied to the loan.

• The following fields must be populated:

  • ZIP Code [for Borrower’s Address] (field ID FR0108) (Or, if the borrower’s present address is a Foreign Address (field ID FR0129), then the subject property’s ZIP code (field ID 15) is required.)
  • Distance (field ID HCSETTING.DISTANCE)
  • At least one checkbox (field ID HCSETTING.SERVICES) in the Multiple Services list must be selected.
  • At least one checkbox (field ID HCSETTING.SERVICES) in the Multiple Languages list must be selected. (English is selected by default.)

Based on these prerequisites, Encompass will populate the Home Counseling Providers List automatically rather than relying on a loan team member to manually click the Get Agencies button.

Please refer to knowledge article #000115391 - 24.1 Home Counseling Providers Automation for additional requirements and information about this feature.

Area Median Income (AMI)

When the Area Median Income (AMI) option is enabled, the AMI data for the loan (as shown below) will be automatically populated when the subject property ZIP code (field ID 15) is entered for the loan. Encompass queries the Area Median Income (AMI) Limits table in Encompass Settings and applies the most current year’s AMI limits.

As part of this update, a new AMI Year Used field (field ID 4970) has been introduced. This field indicates the year of the AMI limits used for the loan.

When the Area Median Income (AMI) option is disabled, loan team members must use the Get AMI button to populate the AMI fields for the loan with the latest AMI limits from the Area Median Income (AMI) Limits table in Encompass Settings.

Encompass now treats Construction Only and Construction-Perm loans as irregular for the purposes of APR tolerance, regardless of the amortization type. This update ensures these Construction loans have an APR tolerance of 0.25% instead of the 0.125% tolerance applied to regular loans. Therefore, when the Redisclose Closing Disclosure (APR, Product, Prepay) alert is configured to use the APR Tolerance > 0.125% for regular loans and 0.25% for irregular loans option, the alert will not trigger for Construction Only and Construction-Perm loans when the current APR differs from the Disclosed APR by 0.25% or less.

If working in an existing loan created prior to Encompass 24.1 and the alert is triggered, this new alert logic will be applied.

A new preconfigured rule has been added to the Field Data Entry business rule setting for Manner in Which Title will be Held. This rule is intended to be applied to the Manner in which Title will be held editable drop-down field (field ID 33) on the Borrower Information - Vesting input form. Administrators can use this rule to modify the enumerations that display in this drop-down list and specify specific enumerations they want to display on the input form.

This preconfigured rule can only be applied to field 33. When managing the enumerations, click the Reset button to return the list to the default list of enumerations provided by Encompass as needed.

To create custom business rules for Manner in which Title will be held to include additional fields, you can deactivate this preconfigured rule, and then create a new custom rule using field 33.

Since the Trade Update Queue process was moved from the client side to the server side, Field Trigger business rules no longer executed and custom fields were no longer populated based on those rules. As part of this release, the behavior of Field Trigger business rules has been updated to work with the server side Trade Update Queue process.

The Search feature for the Configurable Workflow Template setting has been updated. When searching for text, any result in a category and/or a subcategory will be displayed. In addition, when a result is a category, all its subcategories will also be displayed.

Encompass has been updated to enable the company’s State License ID # (field 3629) and the interviewer’s State License ID # (field ID 2306) fields to be populated with a ‘create loan’ API call. Previously, when using APIs to populate loan data, these fields could only be populated with a ‘loan update’ or ‘field writer’ API call.

Encompass now performs an auto-save of loan data when the loan team member performs the following actions:

• Clicks the eConsent button in the eFolder.
• Clicks the Request button in the eFolder.
• Clicks the eDisclosures button in the eFolder.
• Clicks Send > Files or Send > Files to Lender button in the eFolder.
• Sends Status Online.
• Sends forms via Secure Form Transfer tool.

With this enhancement, Encompass saves the loan data before triggering external updates to Encompass Consumer Connect loans or other external services. This helps ensure the most current data is reflected in Encompass Consumer Connect loans and elsewhere, preventing errors that may occur if the same loan file has conflicting borrower/co-borrower information in different applications.

An issue with the Borrower Summary - Origination input form was introduced in Encompass 23.3 where the Subject Property Information section of the form was overlapping/hiding the Transaction Details section heading. This prevented loan team members from accessing the Product and Pricing and Access Lenders buttons provided in the section heading. This issue has been resolved and the Transaction Details and associated buttons now display correctly as shown here.

The First-Time Homebuyer field (field ID 934) had an issue where it was not automatically updating to Yes or No like it should have in loans with multiple borrowers or borrower pairs. Specifically, field 934 was not automatically updating when a borrower or borrower pair was removed from the loan. For example, when the Borrower First-Time Homebuyer field (field ID 4973) was set to No and the Co-Borrower First-Time Homebuyer field (field ID 4974) was set to Yes, field ID 934 automatically updated to Yes correctly. However, if the co-borrower was later removed from the loan, field 934 did not automatically update to No. It incorrectly remained as Yes. To address this issue, a recalculation of field 934 is now triggered when a borrower or borrower pair is removed.

By default, the First-Time Homebuyer field (field ID 934) automatically populates based on the values in fields 4973 and 4974. If the field is later locked and a value is manually entered in the First-Time Homebuyer field, it will not automatically update based on fields 4973 and 4974.

In previous versions of Encompass, the Discount Points field (field ID 1093) on the 1003 URLA - Lender input form was not calculating seller obligated discount points correctly. When the discount points entered on line 802e on the 2015 Itemization were seller obligated, these discount points were not applied to the Discount Points calculation for field 1093. As a result, when the seller obligated fees were more than the borrower obligated fees, the Estimated Closing Costs field (field ID 137) was being cleared out and the cash to close amount was then overstated. This issue has been addressed. Seller-obligated fees for line 802e, f, g, and h are now excluded from the Total Seller Amount when Encompass compares borrower obligated closing costs to seller obligated closing costs. In addition, the Discount Points field (field ID 1046) on the FHA Maximum Mortgage and Cash Needed Worksheet has been updated so that when the discount points are seller obligated, field 1046 is cleared out/blank.

For existing, non-active (field ID 1393) loans created prior to Encompass 24.1, fields 137, 1046, and 1093 are locked so they retain their current values. (If you unlock any of those fields on a non-active loan, the new logic will apply on the non-active loan.) For active (field ID 1393) loans created prior to Encompass 24.1, these fields will be locked only if initial disclosures have been sent. If no disclosures have been sent, the fields are recalculated using the new logic described above the next time the loan file is opened.

When co-mortgagors are listed in a loan file, the Monthly Debt Allowed (field ID PREQUAL.X8) field has been updated to be calculated based on the total income documented in the file (field ID 1389). Prior to Encompass 24.1, Encompass was calculating the Monthly Debt Allowed based on the income of the first borrower pair only.

Workaround Description

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

• Enter co-mortgagors income on other on the first borrower pair and PREQUAL.X8 will calculate from field 1389

(Updated on 3/14/2024)

An issue occurred where NEWHUD.X1720 and NEWHUD.X1721 in a loan were cleared when the loan was manually locked and then either the loan was locked and confirmed or the lock was extended. This issue has been resolved and the two fields, which are accessible by clicking the Discount Points button on the ATR/QM Management form's Qualification tab, are no longer cleared when a loan is manually locked and then the loan is locked and confirmed or the lock is extended.

In previous versions of Encompass, the Intent to Proceed checkbox (field ID 3164) could only be selected once the Actual Received Date for the Loan Estimate (LE) for the primary borrower was populated. In loans with borrower and co-borrower, if the co-borrower acknowledged the disclosure package prior to the borrower, the Intent to Proceed checkbox was inactive (grayed-out) and could not be selected by the co-borrower. This prevented them from recording an accurate Intent to Proceed date. This issue has been addressed and the Intent to Proceed checkbox is now accessible for co-borrowers regardless of the primary borrower’s interaction with the disclosure package.

(Updated on 3/14/2024)

To address issues reported with using business rules to populate HMDA data, relevant HMDA data field calculations for Ethnicity, Race, and Gender have been updated to ensure the correct HMDA input fields in Encompass are being used for the relevant field calculations and field triggers relied upon by the business rules. This update helps ensure that business rules intended to capture and populate HMDA data for a loan are using the correct fields and triggering successfully.

Please note, only those customers who utilize APIs with Encompass Data Connect, Encompass Consumer Connect or services to populate HMDA fields would be impacted by the field issues and this fix. In previous versions of Encompass, when the HMDA fields were populated via a business rule or dynamic data management (DDM) rule, the fields would not always be populated correctly, which resulted in blank values being populated to the fields. With this fix in place, the fields are now calculated correctly and the correct value is populated to the fields when they are updated via a business rule, DDM rule or API.

For a list of impacted HMDA fields, please refer to knowledge article #000115397 - Update for Business Rules Used for Populating HMDA Data to Input Forms.

(Updated on 3/20/2024) 

In previous versions of Encompass, the system logic was populating 2. Not a high-cost mortgage to the HOEPA Status field (field ID HMDA.X13) for loans for investment properties and second properties (based on the value in field 1811 (Property will be)). However, based on CFPB high-cost mortgages rules [12 CFR § 1026.32(a)(1)], investment properties and second properties should be indicated as 3. Not applicable in the HOEPA Status field. This new system logic will take effect in Encompass 24.1

For existing loans originated prior to Encompass 24.1, the HOEPA Status field will be recalculated using the new system logic when the loan is opened and saved.

When the Use Actual Down Payment and Closing Costs Financed (field ID LE2.X30) checkbox was selected and the loan amount was changed, the Closing Costs Financed (field ID LE2.X1) value was not updated, though it should have been. This issue has been resolved.

In the Counsel Type dropdown field (field ID 2847) on the Fannie Mae and Freddie Mac ULDD/PDD input forms, the E: Credit Smart Tutorial option has been re-named to E: Smart Credit Tutorial/Government Agency. Since a ‘Government Agency’ option was not available to select from the Counsel Type field previously, this option could not be selected for loans being sold to Fannie Mae or Freddie Mac.

• The E: Smart Credit Tutorial/Government Agency option is now available on the ULDD/PDD and Freddie Mac Additional Data input form, as well as the applicable Data Templates in Encompass Settings.
• There is no change to the field ID or field mapping. This is only a text change in the field 2847 dropdown list on the Fannie and Freddie Mac tabs.

It was discovered that Fannie Mae’s Desktop Underwriter (DU) was calculating the CLTV/HCLTV differently than Encompass in loans where the Verification of Additional Loans (VOAL) form’s HELOC Initial Draw amount was more than the Amount Applied to Down Payment. When DU was ordered for a loan like this (VOAL loan type is HELOC), it was calculating the CLTV and HCLTV based on the Amount Applied to Down Payment (field ID URLARAL0022) and not the HELOC Initial Draw (field ID URLARAL0121). This resulted in DU showing a lower CLTV and HCLTV than what Encompass was showing in the loan file. Encompass has been updated to ensure DU and Encompass reflect the same CLTV and HCLTV amounts in this scenario. The calculation for the total VOAL (URLA.X230) has been adjusted to calculate the full initial draw amount when the additional loan type is a HELOC. Previously, Encompass was using only a portion of the initial draw used toward Closing Costs in its calculation.

The Funding Worksheet has been updated for HELOC loans to ensure that the draw amount (field ID 1888) is included in calculation for the Wire Transfer Amount field (field ID 1990). Previously, the total HELOC loan amount (field ID 2) was used in the calculation for the Wire Transfer Amount. Since HELOC loans only fund using the draw amount, this update helps ensure that lenders do not over fund the transaction by using the total loan amount.

Workaround Description:

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

1. Input the remaining principal that is not part of the initial draw as a negative in Overwire Amount (field 2005).
2. Create a custom field to calculate Initial Advance (Field 1888) - Loan Amount (Field 1109).
3. Create a Field Trigger Business Rule with a Condition to run only on HELOC Loans. The trigger is any change to the custom field created in step 1 copies to field 2005.

An issue occurred where City Tax tables were not being applied correctly when applied with a Closing Costs template. In Closing Costs templates where line 1204 Transfer Tax was populated with a defined City Tax table that resulted in 0.00 being populated to the borrower-paid fee (field 647) on line 1204, when the Closing Costs template was applied to the loan, the borrower-paid fee (field 647) on line 1204 was populated with 0.00. Field 647 should have been populated with a value based on the City Tax table and relevant loan data calculation.

This issue has been resolved so that the borrower-paid fee (field 647) on line 1204 in the loan is now calculated correctly based on the City Tax table and relevant loan data.

Notes:

• This fix applies only to new Closing Costs templates.
• If a Closing Costs template created prior to Encompass 24.1 has 0.00 populated in field 647 based on the City Tax table calculation and it’s applied to the loan, then 0.00 will be populated to field 647 in the loan. To resolve this issue in existing Closing Costs templates like this, manually delete 0.00 from field 647 in the Closing Costs template, and then reapply the template to the loan.
• Manually entered values in the Closing Costs template will override calculated values when the template is applied. If the administrator has manually entered 0.00 in field 647 in the template, then 0.00 will be populated to field 647 in the loan when the template is applied.

For Construction loans where the lot is owned free and clear, Encompass now calculates the Loan to Value (LTV) ratio as a Limited Refinance transaction in accordance with Fannie Mae and Freddie Mac guidance. Previously, the LTV for these loans was calculated as a Purchase transaction.

In addition to the new calculation being applied to these loans, the Lot/Land Status section of the Construction Management > Loan Info tab has been updated:

• The Initial Acquisition checkbox (field ID 1964) has been renamed to Initial Acquisition (Not Owned).

  • If selected, the transaction is for the purchase of the real property upon which the dwelling will be constructed and for the construction of the dwelling. For the LE/CD, the Purpose will be a Purchase transaction. The LTV will be based on the lesser of As Completed Purchase Price (CONST.X58) or As Completed Appraised Value (CONST.X59).

• The Refinance checkbox (field ID Constr.Refi) has been renamed to Refinance (Owned).

  • If selected, the transaction is for the construction of a dwelling on real property that is already owned by the borrower(s) and there is existing debt owed on the property. For the LE/CD, the Purpose will be a Refinance. The LTV will be based on the As Completed Appraised Value (CONST.X59).

• A new checkbox is now provided: Lot Owned Free and Clear (field ID 5015). This field is read-only by default, but is enabled for editing when the Refinance (Owned) checkbox is selected first.

  • When both the Refinance (Owned) and the Lot Owned Free and Clear checkboxes are selected, Construction is automatically populated to the loan’s Purpose field (field ID LE1.X4) on the Loan Estimate (LE) Page 1 and Closing Disclosure (CD) Page 1.
  • If selected, the transaction is for the construction of a dwelling on real property that is already owned by the borrower(s) and there is no existing debt owed on the property. For the LE/CD, the Purpose will be Construction. The LTV will be based on the As Completed Appraised Value (CONST.X59).

Note that the above changes were also made to the Lot/Land Status section on the 1003 URLA - Lender, 1003 URLA Part 4, RegZ-LE, and RegZ-CD input forms.

Encompass was calculating the earliest month that the maximum loan payment adjustment could occur (field ID LE1.X25) incorrectly for Fixed Rate, Construction Only loans with terms under 24 months. For these loans, the adjustment could occur in month 1, but field LE1.X25 was reflecting month 2. This occurred because Encompass was counting the balloon payment as the first payment change. This issue has been addressed to ensure field ID LE1.X25 is now calculated correctly. Please note the following:

• This issue has been fixed for Fixed Rate, Construction Only loans with terms less than or equal to 24 months and the construction method (field ID SYS.X6) is A (Half Loan).
• This fix only addresses the issue for field LE1.X25, but not for field LE1.X26 (the maximum month that the payment includes only interest and no principal) for Fixed Rate, Construction Only loans with terms longer than 24 months. Field LE1.X26 was calculated incorrectly in previous versions of Encompass for Fixed Rate, Construction Only loans with terms longer than 24 months and this will not be addressed in Encompass 24.1.

This updated calculation will be applied to existing loans as well as new loans created in Encompass 24.1. This ensures the earliest month for maximum loan payment adjustment calculation is more precise and improves the integrity of the loan data.

Workaround Information

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

• Create a Trigger Business Rule with an Advanced Condition to Lock field LE1.X25 and change the value to 1.

New field enumerations were introduced in the VA Purpose of Loan dropdown field (field ID VASUMM.X155) on the VA 26-1820 Loan Disbursement input form in Encompass 23.1. By design, this drop-down field was displayed on the input form in loans with an Application Date (field ID 745) and GFE Application date (field ID 3142) on or after 4/1/2023. For loans with an Application Date or GFE Application Date prior to 4/1/2023, the Purpose of Loan dropdown field (field ID 28) with different enumerations was used on this form.

Starting in Encompass 24.1, the VA Purpose of Loan field (field ID VASUMM.X155) is used on the VA 26-1820 Loan Disbursement input form in new loans by default (i.e., field 745 and field 3142 are both blank).

• In loans where field 745 and 3142 use dates on or after 4/1/2023, the VA Purpose of Loan field (field ID VASUMM.X155) is used on the form.
• In loans where field 745 or 3142 use dates prior to 4/1/2023, the Purpose of Loan (field ID 28) dropdown field is used on the form.
• In existing loans that are accessed after upgrading to Encompass 24.1, if field 745 is blank and field 3142 uses a date on or after 4/1/2023, field VASUMM.X155 will now be used on the form. (In previous versions of Encompass, field 28 would have been used on the form in this scenario.)

Field ID VASUMM.X155:

The General QM Price Limit Exceeded alert has been updated to trigger only if the General Qualified Mortgage (field ID QM.X40) does not meet the ATR/QM standard. Prior to Encompass 24.1, this alert was based on the General Qualified Mortgage (field ID QM.X40) and the actual Price Limit indicator (QM.X384), which resulted in the alert being triggered even when the loan met the price limit requirements.

As part of this update, the default message displayed with the alert has been updated to:

The terms of the loan do not meet General QM Standards for a Price-Based General QM loan.

Previously, the message was:

The pricing exceeds the limit for General QM. Review the pricing associated with the maximum payment in the first five years.

Note that the default message may be edited by the administrator.

An issue occurred for FHA loans with the Encompass Compliance Service (ECS). FHA loans indicated as exempt from ATR/QM (based on field ID QM.X103), would receive an ERROR result for the Ability-to-Repay/Qualified Mortgage Review performed by ECS along with this message:

Qualified Mortgage Type (FHA Qualified Mortgage) not valid for Ability to Repay Loan Type [Exempt].

ECS was triggering this error based on the Qualified Mortgage Loan Type (field ID QM.X24) field in the ATR/QM Management input form. Encompass was auto-populating FHA QM to this field based on the FHA loan type.

Since the FHA loan was indicated as exempt from ATR/QM, Encompass should not have populated field QM.X24 with FHA QM. This issue has been resolved. In this scenario, field QM.X24 remains blank and the ECS review recognizes the loan as exempt from ATR/QM and provides a PASS result for the ATR/QM Review.

Encompass 24.1

Workaround Description:

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

• Lock down the QM type and set the value to null.

VOAL (Verification of Additional Loans) records can be created in two ways:

• System generated when a linked loan is created
• Manually created by users

In previous versions of Encompass, the following issues with system-generated VOALs occurred and have now been addressed:

• When a user created a linked loan, Encompass was generating the VOAL record in the current borrower pair rather than only in the primary borrower pair. This has been fixed, so that the VOAL is always created in the primary pair.
• If a loan was previously linked and already had a system-generated VOAL, if it was then linked again, duplicate system-generated VOALs were being created. This has been fixed, so that the system does not generate VOALs in the loan again if there is already a system-generated VOAL. (Note that system-generated VOALs will be created if there is already a manually created VOAL on the loan.)

This update applies to new loans created in Encompass 24.1 and later. For existing loans where the system-generated VOAL has already been duplicated or erroneously added to the non-primary borrower pair(s) record, users will need to manually address the duplicate VOALs in the loans.

When the first lien of a piggyback loan was updated via a trade, the First Mortgage (P&I) (field ID 1724) value was getting copied into the Subordinate Lien(s) (P&I) field (field ID 1725). This issue has been resolved.

After switching a Verification of Employment (VOE) record from Borrower to CoBorrower, the Gross Monthly Income field values on the VOE were not populated to the corresponding Co-Borrower Stable Monthly Income fields (field IDs 110, 1146, 1759) on the Transmittal Summary as expected. This has been resolved, and when the VOE record is switched, the Co-Borrower income fields on the Transmittal Summary input form are updated with the correct values.

Issue in previous versions of Encompass:

When a loan team member updates the borrower name or email address after the eConsent agreement has been accepted, the eConsent Not Yet Received alert should trigger when they save the loan. However, an issue occurred where this alert did not trigger if they clicked the black X in the top-right corner of the screen to exit the loan, and then saved the loan by clicking Yes when they received the prompt “Do you want to save the changes to the current loan?”. (The alert triggered as expected when the loan team member clicked the Save icon to save the loan prior to exiting the loan file.)

This issue has been resolved and the eConsent Not Yet Received alert is now triggered if the loan team member clicks the X to exit the loan without saving the loan first, and then clicks Yes when prompted to save the loan.

Some loan team members received the following Application Error after attempting to open the AUS Tracking tool in a loan file. Specifically, loan files where the Underwriting Risk Assess Type field (field ID AUS.X1) was blank is where this error occurred:

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

The given key was not present in the dictionary.

The cause of this issue was identified, and it has been addressed.

An issue occurred where the Remaining Budydown Amount (field ID 3130) on the Purchase Advice Form was not cleared when Interim Servicing was started, all buydown information was removed from the loan, and then Interim Servicing was restarted. This issue has been resolved and the Remaining Budydown Amount is now cleared when all buydown information is removed from a loan being serviced and then Interim Servicing is restarted.

An issue occurred where intermittently the data in a loan’s Secondary Registration log was cleared. This issue has been resolved and a loan’s Secondary Registration log data is no longer cleared.

An issue occurred where the Prepay Penalty field was not populated on the Loan Snapshot tab of the Secondary Lock Tool. This issue has been resolved and the Prepay Penalty (field ID 2963) field on the Lock Request Form is now mapped to field ID 675. This mapped value will populate the Prepay Penalty field on the Loan Snapshot tab.

SEC-26436

The following updates have been to address issues for customers originating loans in North Carolina who generate and submit a North Carolina Compliance Report to the North Carolina Office of Commissioner of Banks (NCCOB):

• The Aggregate Account Adjustment (Field 558) is now listed in the generated report. A negative sign (“ - “) sign is now displayed when the value is negative.
• The Interest Credit value (Line 901, Field 334) is now included in the report. The value (positive or negative) is now exported with the report.
• The Title fees in the 1100 section of the report now include Title at the beginning of the fee name (just as they have for the Closing Disclosure Page 2 fee names in the report).

An issue occurred where a loan’s Investor Status (field ID 2031) on the Current Lock tab of the Secondary Registration tool was not updated when that locked loan was allocated to a loan trade and then the trade was updated. This issue has been resolved and a loan’s Investor Status field is now updated when that loan is allocated to a trade and the trade is updated.

An issue occurred when a bid tape file with 50 plus loans was processed by the Trade Update Queue. During the process, two batch jobs were created for each bid tape file. This issue has been resolved and only one batch job is now created for each bid tape file with 50 plus loans.

SEC-25950

An issue occurred where a loan couldn’t be updated in a loan trade and a message “Loan xxx could not be updated due to the following error: Length cannot be less than zero.” was displayed on the trade’s Notes/History tab. This issue has been resolved and the loan is now successfully updated in the trade.

An issue occurred where Persona Access to Fields Business Rules applied to the AMI % fields (field IDs MORNET.X30, 4971, and 4972) were not being applied consistently to the three fields. Specifically, if a loan team member with ‘View Only’ persona access to all three fields clicked the Get AMI button to populate these fields, the AMI 80% and AMI 50% fields would be populated/updated, but the AMI 100% field (field ID MORNET.X30) would not be. This issue has been addressed so that all three fields are populated/updated when the Get AMI button is used.

An issue with closing costs templates occurred where the 2015 Itemization line 1202 Recording Fees field (field ID 1636) was not reflecting the correct value for Releases. When an administrator would open the template and then click the Edit icon to update the Releases value in the pop-up window, instead of the Recording Fees displaying the new value for Releases as defined in the pop-up window, the Releases value was defaulting to $0.00 in the Recording Fees field. This caused the portion of the recording fees to be paid by the borrower (field ID 390) to be incorrect, since the true Releases amount was not included in the calculation. This issue was also reflected in the loan file when the closing costs template was applied.

This issue has been addressed. As shown below, when the Releases value is updated in the template, the new value is now indicated in the template’s Recording Fees field and included in the calculation for field 390 (borrower-paid portion of fee).

Workaround Description:

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

• Manually update field 1636 to include the correct Releases amount.

Funding templates configured in the Funding Templates setting in Encompass (desktop) where 2015 Itemization fee lines 1316-1320 are indicated as seller-paid were not reflecting correctly on the Funding Worksheet in the web version of Encompass. After the template was applied to the loan, lines 1316 - 1320 were indicated as borrower-paid instead of seller-paid on the Funding Worksheet (i.e., the “Paid by seller” checkboxes were not selected on the worksheet). This issue has been resolved and the “Paid by seller” checkboxes for these fee lines are now selected as expected on the Funding Worksheet when the funding template is assigned to the loan.

An issue occurred where the View access to team’s loans and Edit team’s loans checkboxes were selected on a contact’s TPO Contact Details screen when that contact (with both checkboxes not selected) was imported via a CSV file to a new company, a change was saved to the contact, and then the contact was reopened. This issue has been resolved and only the Edit team’s loans checkbox is selected (and read-only) after a contact is imported to a new company using a CSV file.

An issue occurred with the column filters on the Configurable Workflow Templates setting. When the Search icon was clicked in the Date Field ID, Date Field Name, or Documents columns, the Search box was empty and no filters could be selected.

This issue has been resolved and the Search boxes are now populated (unless the column has no data) and filters can now be selected.

SEC-26064

An issue occurred with the Data Templates setting and templates that use custom audit fields set up to track changes to fields (such as Loan Type (field ID 1172)). When a data template was appended to the loan, the incorrect date/time was populated to the custom audit field. Instead of being populated with the date/time the field being audited was changed in the loan file when the template was appended to the loan, the custom audit field was being populated with the date/time the field was added to the template by the administrator in the Data Templates setting.

To address this issue, Encompass system logic has been updated as follows:

• Custom audit fields will not be saved to data templates.
• For existing data templates created before this update, audit fields in the templates will not be applied to loan files.

In previous versions of Encompass, after setting up and activating a Field Triggers business rule designed to execute a custom action when the Expected Impounds (field ID 2837) value changed, the field was not calculating correctly. This issue has been resolved so that field 2837 is calculated correctly according to the settings configured in the Field Triggers business rule.

When administrators open the Encompass Reporting Database, the system prompts to add required fields for the NMLS report and North Carolina Mortgage Loan Data report if they are not currently in the database. An issue occurred where some fields for these reports were duplicated in the prompt. If the administrator proceeded with adding the fields to the database, an error referencing the duplicated fields was triggered in the Reporting Database when they attempted update it with the new fields.

This issue has been resolved and the duplicated fields are no longer present when the system prompts the administrator to add required fields to the database.

In loans with multiple borrower pairs, the Redisclose Closing Disclosure (NBO Updated) alert is triggered correctly when a non-borrowing owner is added to the loan after the Closing Disclosure (CD) is disclosed. The CD for the primary borrower is redisclosed and the alert is cleared as expected. However, when disclosing the initial CD to the additional borrower pair, the Redisclose Closing Disclosure (NBO Updated) alert was erroneously re-triggered. Encompass has been updated so that the alert is not triggered when the initial CD for the additional borrower pair is sent, since the CD has not revised.