We use cookies to try and give you a better experience in Freshdesk.
You can learn more about what kind of cookies we use, why, and how from our Privacy policy. If you hate cookies, or are just on a diet, you can disable them altogether too. Just note that the Freshdesk service is pretty big on some cookies (we love the choco-chip ones), and some portions of Freshdesk may not work properly if you disable cookies.
We’ll also assume you agree to the way we use cookies and are ok with it as described in our Privacy policy, unless you choose to disable them altogether through your browser.
Note: Previously announced as opt-in; no action is required. This fix has been applied automatically
Date Available: Available now.
Which customers are impacted?: Lenders using Blend borrower eConsent with an Encompass LOS integration.
Required?: This fix has been applied automatically, no action is required.
Purpose of Update and Benefit: When a borrower completes eConsent in Blend, Blend writes the consent details back to Encompass so lenders have a single system of record for disclosure tracking. On Encompass version 26.1.0.3, this write-back was not completed as expected, meaning consent details never reached Encompass even though the borrower had completed eConsent in Blend.
This update resolves the sync failure introduced in Encompass 26.1.0.3 and ensures eConsent data is written to Encompass correctly for lenders who opt in.
Current Behavior: On Encompass 26.1.0.3, borrower eConsent details (status, accepted date, IP address, and source) are not written back to Encompass after the borrower completes eConsent in Blend. Lenders and borrowers do not receive an error notification when this occurs.
New Behavior: Blend writes borrower eConsent details back to Encompass after eConsent is completed. The data synced includes consent status, accepted date, IP address, and source.
0 Votes
0 Comments
Login to post a comment