October 16th, Release Notes

Bug Fixes & Code Cleanups

e-Consent Mapping to Encompass for 3+ Borrowers

We’ve improved how e-Consent works for loans with three or more borrowers. This update ensures that all e-Consent information for additional borrowers — including name, email, IP address, and date/time — now maps correctly to Encompass.

e-Consent Sync Errors After LOS Sync

We fixed an error that prevented eConsent information to sync to Encompass if consent was gathered after the initial sync to the LOS. Now all e-Consent records sync to the LOS regardless of when the e-Consent was captured.

3.4 Loan Import Errors with Additional Parties

We resolved issues that caused 3.4 loan imports to fail when additional (non-borrower) parties were included in the MISMO file. In cases where extra parties are present, those records will now be filtered out to ensure the loan file is successfully created and application data is created in the Point of Sale.

Examples of additional parties include:

• Loans with 3+ borrowers

• Non-borrower owners

• Other participants on the 3.4 file (e.g., Loan Originator, Loan Origination Company)

Resolved Hosted Disclosure Document Syncing Issue

We fixed an issue in our hosted disclosures experience where disclosure documents were not syncing to the Encompass eFolder as expected. Now, all documents will sync correctly to their corresponding eFolders once all participants have completed signing.

POS Milestone Updates from Encompass

We fixed a data inconsistency issue with our POS milestone updates for lender partners using our LOS middleware.

Encompass Auto Push After Loan Application Submission

We resolved an issue affecting a few lender partners who are using our LOS middleware service for Encompass auto-push after loan application submission. This service now works as expected for those partners who choose to trigger an automatic push to Encompass after loan application submission.