For non-USDA loans, when an amount is entered on line 819 (field ID NEWHUD.X1301) on the 2015 Itemization input form, the amount is no longer included in the Total points and fees applicable under section 32 (field ID S32DISC.X48) when the option selected in the Paid to drop-down list (field ID NEWHUD.X1306) is S (seller) or O (other). Previously, when line 819 was used for a non-USDA loan, the amount was included in the Total points and fees applicable under section 32 no matter what was selected in the Paid To field NEWHUD.X1306. This adjustment brings the Encompass calculation into alignment with the calculations used by the Encompass Compliance Service (ECS), which excludes the amount.

Workaround Description

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

• Utilize a different Line in the 800 Section

• Or lock down (field ID NEWHUD2.X1611) and manually adjust the Points and Fees.

Prior to Encompass 23.3, Encompass automatically included the MI cushion from the Aggregate Escrow Account input form in the Section 32 Points and Fees Total (field ID S32DISC.X48). However, per the CFBP, periodic MI premiums, including any initial payment due at closing, should not be included in the Section 32 Points and Fees Total calculation. Starting in Encompass 23.3, the MI cushion from the Aggregate Setup Account is not included in field ID S32DISC.X48.

An update has been made to the logic used for VA IRRRL loans when populating Yes or No in the Is Loan Eligible for Safe Harbor? drop-down list (field ID QM.X25) on the ATR/QM Eligibility tab on the ATR/QM Management input form.

Previously, the calculation used the Recoup Closing Costs months (field ID VASSUM.X27) from the Closing Cost Recoupment section of the Cash-Out Refinance tab on the VA Management input form. The Closing Cost Recoupment section can include items excluded from the Statutory Recoupment section for IRRRL loans, such as the VA funding fee, taxes, and amounts held in escrow, potentially causing an incorrect safe harbor recommendation on the ATR/QM Management input form. Beginning with the Encompass 23.3 release, the VA IRRRL safe harbor calculation uses the calculated Recoupment Months (field ID VASUMM.X130) from the Statutory Closing Cost Recoupment section which excludes these items.

In previous versions of Encompass, when a loan using the 2015 RESPA-TILA forms included a buydown (field ID 4645) and origination points, the calculation in the ATR/QM Management input form > Qualification tab > Discount Points field (field ID QM.X111) was cleared. This caused the Total section 32 Points and fees in this loan (field ID S32DISC.X48) on the Section 32 HOEPA form to not calculate accurately. This issue has been resolved. The Discount Points are no longer cleared and the Total section 32 Points and fees in this loan field now calculates accurately.

This fix applies only to loans created in Encompass 23.3 and later. For existing loans, this issue with field QM.X111 being cleared and causing incorrect calculations for field S32DISC.X48 will persist. To trigger the correct calculation in existing loans, select the Buydown checkbox (field ID 425), and then clear the Buydown checkbox. This will trigger the recalculation and Encompass will not clear Bona Fide Discount points % (field ID 1061) and dollar amount (field ID 436) fields if there are no buydown points.

Workaround Information:

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

• Clear the Seller Paid Buydown already included in 2015 Itemization Section 32 Points & Fees checkbox (field ID S32Disc.X181), select the checkbox again, and then save the loan to trigger a recalculation of field S32DISC.X48.

Prior to Encompass 23.3, when a user changed the Note Rate (field ID 3) on the URLA Lender input form, and then ran a compliance review on the loan prior to saving the changes, the QM Annual Percentage Rate (field ID QM.X381) on the ATR/QM Management input form was not being automatically updated in Encompass like it should have. This resulted in the APR (field ID 799) and the QM APR (QM.X381) values being different. This issue has been resolved and the QM APR field is now automatically updated when the Note Rate changes as expected.

Workaround Information:

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

• Save the latest changes to the loan prior to running the compliance review.

An issue occurred where once the 1st Payment Date (field ID 682) on the RegZ-CD was entered and that date populated the 1st Payment Due Borrower field on the Payment History tab of the Correspondent Purchase Advice Form, any updates to field ID 682 were not passed to the 1st Payment Due Borrower field. This issue has been resolved and updates to field ID 682 now pass to the 1st Payment Due Borrower field.

An issue was resolved that caused the Funding Balancing Worksheet print form to reflect incorrect Total Credits for a refinance loan when there were more than 15 VOL (Verification of Liabilities) records created with the Will Be Paid Off checkbox selected. This scenario typically occurred for refinance loans using the alternate version of the Closing Disclosure and resulted in the Funding Worksheet tool displaying an incorrect value for the Total Deductions and Wire Transfer Amount.

To address this issue, 10 new line entries have been added to the Quick Entry - Transaction Summary pop-window on the Funding Worksheet tool. This window is accessed by clicking the Transaction Summary button at the bottom of the Funding Worksheet tool. Previously, only 15 lines were available on the form.

The calculations used to populate the Total Payoffs and Payments, the total on the Funding Worksheet, and the total on the Funding Balancing Worksheet now include the 10 new line entries.

Additionally, checkboxes for rows 16-25 have been added to the table at the bottom of the Funding Worksheet tool.

An issue was resolved that affected the Request for Transcript of Tax input form when the Use IRS 4506-C checkbox (field ID IRS4506.X67) was selected and Sep 2020 was selected in the drop-down list (field ID IRS4506.X92).

When these options were selected, users were able to click the Address Book icon in Section 5 (third-party recipients) to open the Business Contacts tool, but the contact information was not populating back to the Request for Transcript of Tax. This issue has been resolved and the contact information is now populating as expected.

Workaround Description:

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

• Manually update the fields or add the information to a Data Template.

The field that tracks the number of borrower pairs for a loan (field ID 4460) now recalculates immediately when a borrower pair is added to a loan. Previously, the field was not recalculating when a borrower pair was added to a loan unless the loan was saved or unless data entered in another field triggered a recalculation of loan values. However, when a borrower pair was deleted from a loan, the field was updated immediately without having to take any additional action. This issue has been resolved and the value in field 4460 now updates as soon as a borrower pair is added to a loan.

Workaround Description:

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

• Save the loan after adding a new borrower pair.

An Ineligible option has been added to the Underwriting Decision drop-down list (field ID USDA.X152) on the Tracking tab on the USDA Management input form.

Previously, the drop-down list included only options for Accept, Refer, and Refer with Caution. This prevented users from selecting the Ineligible option as an Underwriting Decision when appropriate prior to uploading the information to the USDA’s Guaranteed Underwriting System (GUS).

(Updated on 9/6/2023)

On the Statement of Denial input form, the Unacceptable Payment Record on Previous Mortgage checkbox (field ID DENIAL.X37) was indented below the Excessive Obligations checkbox (field ID DENIAL.X35), giving the incorrect impression that Unacceptable Payment Record… was a sub-option of the Excessive Obligations checkbox. Similarly, the Length of Residence checkbox (field ID DENIAL.X48) was indented incorrectly in the Residency section of the input form.

Please note, on the Statement of Denial printed output form, the Unacceptable Payment Record on Previous Mortgage checkbox and Length of Residence checkbox display correctly (i.e., as its own option and not indented under the checkbox above it).

Input form prior to Encompass 23.3:

This issue has been resolved. The location of the Unacceptable Payment Record on Previous Mortgage and Length of Residence checkboxes are now correct and consistent on the Statement of Denial input and printed output forms.

Input form and output form in Encompass 23.3:

An issue occurred with the Balloon Payment field (field HMDA.X114) on the HMDA Information input. When loan team members set the Loan Type (field ID 1172) to Conventional and the Loan Purpose (field 19) to Construction, the Ballon Payment fields (field ID 1659 and field ID HMDA.X114 on the HMDA Information input form) would both automatically populate to Yes as expected. (For input forms where field 1659 is a checkbox, the checkbox would be automatically selected.) But after applying a HELOC loan template to the loan which changed the Loan Type to HELOC and the Loan Purpose to Cash-Out Refi or No Cash-Out Refi, the Balloon Payment field (HMDA.X114) on the HMDA Information input form would remain as Yes instead of automatically populating to No like it should have. (The other Balloon Payment field (1659) auto-populated to No correctly.) This issue has been resolved and HMDA.X114 is now auto-populated correctly based on the values in the assigned template.

Note that this issue with field HMDA.X114 did not occur when loan team members manually updated the Loan Type and Loan Purpose fields. It only occurred when these fields were updated by applying a loan template.

As part of this fix, the balloon payment logic in Encompass has been updated to apply to all loan types (including HELOC, Construction, Construction-to-Perm, etc.) instead of only specific loan types. If the Due in value (field 325) is less than the Loan Term (field ID 4), the loan is considered a balloon loan and the Balloon / Balloon Term checkbox (field ID 1659) will be selected automatically. When field 1659 is selected, the Balloon Payment field (field ID HMDA.X114) field is set to Yes automatically.

Workaround Information:

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

• Go to Field 1172, manually select Conventional, and then re-select HELOC. Or lock field HDMA.X114, and then manually update to No.

When a Post Consummation fee is added to a Closing Cost template, and then the Closing Cost template is applied to a Construction or Construction-Perm loan, the fee is now included in the Finance Charge calculations (field ID 1206). Previously, the Finance Charge did not include the Post Consummation fee for Construction and Construction-Perm loans unless the fee was added manually.

For Construction loans where the lot is owned free and clear with no seller, the Estimated Closing Costs Financed field (field ID LE2.X1) was not calculated correctly unless the Use Actual Down Payment & Closing Costs Financed checkbox (field ID LE2.X30) was selected. Starting in Encompass 23.3, if the Use Alternate checkbox (LE2.X28) is selected and the Refinance value (field ID1092) is null or empty, then the Estimated Total Payoffs and Payments field (LE2.X31) is now used instead of field 1092 for the calculation of the Estimated Closing Costs Financed field (field ID LE2.X1)

Data Migration:

Field LE2.X1 values in existing loans will not be recalculated automatically. The field will recalculate with the new calculation if the user makes a change to the loan that triggers the Calc All function where Encompass refreshes loan data (assuming the field lock is not locked and is using Encompass system calculations).

Workaround Information:

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

• Select Checkbox (LE2.X30): Use Actual Down Payment & Closing Costs Financed.

The following updates have been made to the verbiage in the eConsent Agreement borrowers and non-borrowers are required to acknowledge before receiving electronic copies of loan documents.

• A sentence in the eConsent Agreement was updated to clarify that fees may be charged if paper copies of documents are required.

“You will also be required to pay a reasonable fee to complete your transaction...”

has been changed to

“You may also be required to pay a reasonable fee to complete your transaction...”

• In the How to Withdraw Consent portion of the eConsent Agreement, the name of the Don’t Agree button was incorrectly indicated as “Don?t Agree”. This has been corrected so that the eConsent Agreement now indicates “Don’t Agree”.

DOCP-55218, DOCP-55070

An issue was introduced Encompass 23.2 where Encompass was including the lender’s or the assigned loan officer’s phone number (field ID 1823) on the Request eConsent screen along with the borrower's home and work phone number. This number was incorrectly indicated as a home phone number for the borrower. Since this field on the eConsent screen is intended only for the borrower’s contact information, the company’s or loan officer’s information should not have been included as an option there. This issue has been resolved and only the borrower’s home, work, and cell phone numbers are provided here (based on the phone numbers entered in Encompass fields 66, FE0117, 1490).

When the first attachment uploaded to a new loan file was a text (.TXT) file, the following message was automatically added to the text file:

"Evaluation Only. Created with Aspose.Words. Copyright 2003-2011 Aspose Pty Ltd".

The cause of this issue was identified, and the required updates have been made to resolve this issue. This message is no longer added to the uploaded text file, even if it is the first file attached to the loan.

Workaround Information:

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

• Upload a PDF file to the loan before uploading a TXT file.

(Updated on 10/6/2023)

Loan team members utilizing Encompass eClose received an error related to borrower vesting when attempting to send closing documents. If the names in the Borrower Vesting window’s Name and Connected to Borrower Pair fields were different, they would receive an “Error occurred during document processing” error message after proceeding through the eClose workflow to send closing documents. This issue arose when, for example, a middle initial was added to the Borrower Vesting name, but not the connected borrower pair (as shown below). This issue has been resolved. The names in the Borrower Vesting Name and Connected to Borrower Pair fields may be different and this will no longer trigger the document process error when sending closing documents with Encompass eClose.

Update 10/6/2023:  The original fix to eClose loans that addresses errors when the Borrower Vesting name differs from the Borrower name entered at the time of application is in the 23.3 release as planned, but with the discovery of two additional use cases, the fatal audit created to alert users will remain in place. Closing Docs users should continue to maintain name consistency by updating the names in the Borrower Name and Borrower Vesting fields. The Encompass update to address the additional changes will be released soon along with the fatal audit.

After transferring eNotes from their previous document storage vault to the Encompass eVault, some users were unable to access the eNotes. Clicking the eNote tab in the Encompass eFolder (or the eNote tab in Encompass eVault), resulted in an error (indicated by an exclamation point) and the eNotes were not displayed. The Data tab in the eFolder and Encompass eVault was blank as well. These issues have been resolved and users can now access their transferred eNotes as expected.

(Added on 10/4/2023)

Updates have been implemented to help ensure enhanced conditions details are included on custom printed output forms when the EDS Custom Form Processing option in the Encompass Admin Tools > Settings Manager is enabled (i.e., set to True).

An issue occurred where an error message “An error has occurred while gathering the report: Index was outside the bounds of the array.” was displayed when more than one Excel calculation field was added to a new Trade report and then the report was generated. This issue has been resolved and the error message is no longer displayed when a Trade report with multiple Excel calculation fields is generated.

An issue occurred where the status of loans assigned to a loan trade or MBS pool did not update from “Assigned” to “Shipped” when an Actual Delivery Date was entered on that loan trade’s/MBS pool’s Details tab. This issue has been resolved and the loans’ status now updates to “Shipped” when an Actual Delivery Date is entered.

An issue occurred where Encompass did not properly record when a trade was marked as “Void” from the correspondent trade pipeline.

• The History section of the Notes/History tab of the correspondent trade was not updated with a “Loan [loan number] is flagged as “voided”.” event.

• The Alerts & Messages and Log sections of the loans within the voided correspondent trade was not updated with a “Lock removed from Correspondent Trade by [user]” message.

The Rate Lock Removed from Correspondent Trade option under the Loan Setup>Alerts setting must be enabled to view the messages in the Alerts & Messages and Log sections.

This issue has been resolved and Encompass now properly records a trade voided from the correspondent trade pipeline.

An issue was resolved that caused DDM (Dynamic Data Management) rules to not work correctly when a data table contained a LINKGUID condition. This issue has been resolved and DDM rules now work correctly when a when a data table contains a LINKGUID condition.

An issue was resolved that prevented some users from opening the pop-up windows that are accessed by clicking the following Edit icons for Closing Cost Templates and Data Templates used to populate data to the 2015 Itemization:

• Line 902 - Mtg Ins. Premium

• Line 903 - Homeowner's Ins

• Line 1003 - Mortgage Ins.

• Line 1004 - Property Taxes

• Line 1010 - USDA Annual Fee

• This issue also affected the Edit icon for I. Financed Mortgage Insurance in the TOTAL MORTGAGE LOANS section in Data Templates.

Users assigned the Administrator and Super Administrator persona were able to access the pop-up windows, but users with other personas were not able to access the pop-up windows, even though they had the required permission to access the templates. This issue has been resolved and non-administrator personas can now access the Closing Cost Template or Data Template pop-windows listed above.

An issue was resolved that affected loans that had been disclosed with the Intent to Proceed checkbox (field ID 3164) selected. When a Data Template with a Loan Type (field ID 1172) selected was applied to these loans, the following intent to proceed fields were incorrectly cleared on the Loan Estimate Page 1:

• Intent to Proceed checkbox (field ID 3164)

• Loan Estimate sent on (field ID 3972)

• Received Date (field ID 3197)

This issue has been resolved and the fields listed above are no longer cleared when applying a Data Template with a Loan Type (field ID 1172) selected.

An issue occurred where the Outstanding Commitments Amount was not calculated correctly when the Use Commitment Term fields option was enabled. If the Use Commitment Term fields option and the Best Efforts Unlimited Commitment Authority option on the Company Details Commitment tab for a TPO were enabled, and then a Best Efforts loan for that TPO was locked, the Outstanding Commitments Amount did not increase by the loan amount of the locked loan. This issue has been resolved and the Outstanding Commitments Amount is now calculated correctly.

A typo was fixed in the description of the Lock Request Penalty Term (field ID 2964) in the Encompass Reporting Database. Previously the description was misspelled as "Lock Request Penelaty Term".

Workaround Description:

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

• Edit the description after the field has been added to your reporting database

Prior to the Encompass 23.3 release, some customers reported seeing the values change for the Loan Creation Date UTC (field ID 2025) in their loans, even though the Loan Creation Date UT is a read-only field. After determining that this issue was caused by customer Field Trigger Business Rules that updated field 2025, the logic used by Field Trigger Business Rules had been adjusted so these rules can no longer be used to update the Loan Creation Date UTC value.

An issue was resolved that affected Field Trigger Business Rules that were configured to display the prior value of a field in a pop-up message box when the field value changed. When the business rule was applied to fields with a Lock icon, the message box displayed a blank value when the first change occurred in the field’s value. (The prior value was displayed correctly when subsequent changes were made to the value in the field.) This issue has been resolved and the business rule now correctly displays the prior value in the message box the first time the value changes for the field.

Workaround Description:

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

• Create a Custom field with a calculation for the Encompass Field ID and use the Custom Field to trigger the Business Rule.

Persona Access to Fields business rules now function correctly when advanced code is used to control access to a field on the Closing Disclosure Page 3. This issue was caused by unique code in the Closing Disclosure Page 3 that is used when the fields on the form are changed. This code was circumventing the logic that should have been implemented by the business rule. This issue has been resolved and Persona Access to Fields business rules now function correctly under the scenario described above.

An issue was resolved with Personas Access to Fields business rules that were configured to disable access to the Closing Costs from Other Loans (field ID 1851) on forms such as the 1003 URLA Lender, 2015 Itemization, and Construction Management input forms. This issue affected loans that were linked to other loans via the Piggyback Loans tool. For linked Piggyback Loans, a Lock icon displays next to the Closing Costs from Other Loans field.

Previously, when a user who did not have permission to access the field opened a linked loan and then opened a form with the Closing Costs from Other Loans field, the Lock Icon was not disabled. However, the icon would become disabled if a user completed one of the following actions:

• The user clicked an editable field on the form.

• The user clicked the Lock icon. This would change the lock status of the field (from locked to unlocked or from unlocked to locked) and then disable the Lock icon.

This issue has been resolved and when a user who has been denied access to the field by a Persona Access to Fields business rule opens a form with the field, the Lock icon is now disabled.

An issue was resolved with Persona Access to Fields business rules and the Borrower Information-Vesting input form. When a Persona Access to Fields business rule granted a persona Edit/Enable rights to a field on the Borrower Information-Vesting input form, the user would only be granted View Only/Disabled rights to the field. This issue has been resolved and the persona access rights to these fields are now working correctly.

This issue did not affect the persona’s access rights to these fields on any other input form.

In loans where Persona Access to Fields business rules are in place to allow (or prevent) access to specific fields once other specific trigger fields are selected or populated, there was an issue when the borrower and co/borrower positions were moved (i.e., swapped) using the Borrower Pairs tool. After swapping the borrower positions, the Persona Access to Fields rule was applied correctly to the trigger fields, but the other fields that should have been disabled or enabled based on the trigger field being selected were not updated according to the rule. It was not until the loan team member saved changes to the loan or closed and reopened the loan that the business rule would fully execute and the fields impacted by the trigger field would be enabled or disabled accordingly. The Persona Access to Fields rules have been updated to fully execute when the borrower information is swapped.

Workaround Information

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

• Clear and then re-select or repopulate the trigger field, then the other fields within the Persona Access to Fields business rule will update for both borrower and co-borrower. Or you can save and close loan, then the re-opening of the loan will cause the Persona Access to Fields business rule to function as expected.