August 6th, 2025

Summary


Maxwell Hosted Disclosures Updates

We made several enhancements to improve the user experience and reporting reliability of our hosted disclosures experience.

  1. e-Signature and checkbox alignment on forms We're pushing an update that improves alignment of radio checkboxes and date fields.

  2. Improved the speed of disclosure task delivery to borrowers We've reduced the disclosure task creation retry interval from 15 minutes to 1 minute, to improve the speed of delivery to borrowers

  3. Added warning messages to enable disclosure data sync

    Encompass's locks their loan files from API updates when the file is open preventing third-party updates to avoid data corruption or inconsistencies. While the file is locked, Maxwell cannot sync disclosure tracking log updates from the POS to the Encompass loan file. To ensure successful data syncing we've included a warning message reminding LOs to close the Encompass file and keep it closed for at least 5 minutes to allow disclosure data and docs to process.

Encompass Consumer Connect Disclosures Update in 25.3 Release (August 9th)

Many of our lenders have been asking about Encompass's transition from DocuSign to ICE's eSign Events (Simplifile) and if that will impact will the Maxwell POS experience. The short answer is there will be no impact to your current Maxwell disclosures integration, and no set up or user actions are required.

If you want to learn more you can review this summary and FAQs below.

Summary

In the Encompass 25.3 release August 9, 2025, Encompass signing platform will transition from DocuSign to ICE's eSign Events (formerly Simplifile) for all electronic documents in all environments. That means for signing documents like disclosures and closing docs through Encompass Consumer Connect, borrowers and lenders will sign using ICE's own documents signature provider instead of DocuSign.

We've reviewed the documentation, spoken with our ICE support team, and tested the process in a UAT environment to ensure that this update will not have an impact on Maxwell's ECC disclosures integration. The current integration will work the same as it does today.

  • A borrower will receive an email from Maxwell that documents are available to review and sign and will be directed to their POS task

  • They will click a link to review and sign documents

  • Maxwell will redirect and SSO borrowers into Encompass Consumer Connect

  • The borrower will provide their eConsent and Authorization code to access ECC

  • The only difference will be once the borrower clicks review and sign documents, instead of being taken into a DocuSign disclosure document to sign they will be in a ICE eSign Document.

Other FAQs

Does this have anything to do with Maxwell Hosted Disclosures?

No, it does not. Maxwell's Hosted Disclosures is a new feature for those organizations who want to bypass the ECC experience to create a more seamless signing experience for their borrowers. You can learn more about Maxwell's New Hosted eDisclosures feature and by reviewing this document.

Where can I learn more about the ICE eSign updates?

ICE provided a pre-release document on ICE eSign Events in their resource center.

Do I have to change anything to ensure my integration with ICE still works.

Because this experience is entirely hosted through Encompass Consumer Connect, there is no setup or user action required to update the Point of Sale.

Can I test this signing experience?

ICE created a pre-release in their UAT environment. You can test it there. If you have a test site setup in Maxwell we can link to your UAT Encompass Instance so you can test this experience as well as other pre-release features.

Added Retry for eConsent Data fields sync to Encompass We’ve implemented a retry job that updates eConsent fields after the Encompass file is unlocked, in the event the Encompass file was open/locked during initial update.

Added Suffix Field to terms and consents modal

We added a suffix field to the terms and consents modal to allow borrower to enter their full legal name for consent record keeping.

Custom Consents

We added an enhancement to our consents service that allows our lenders to collect custom consent & disclosures acknowledgement from borrowers that are specific for your organization. This service creates an activity log of when the consent was captured as well as a PDF record of the consent with date, time, email, and IP. The pdf will automatically sync to your LOS at time of receipt.

If you would like to include any special consents or disclaimers on your site like Terms and Conditions, Consent to Marketing/Contact, or anything else please reach out to [email protected] with the borrower consent terms and we will set it up for your organization settings.

HELOC Application Updates

Loan & Property Information Updates

We cleaned ups some issues to ensure that loan and property information is mapping correctly on HELOC loan applications.

  • Loan Type = HELOC

  • Loan Purpose = Cash-Out Refi

  • Lien Position = Subordinate

  • Total Loan Amount = Will include the credit limit requested by the borrower

VOA and VOE/I Task Configuration

This feature puts the power of the lenders to decide whether or not they trigger VO(X) at the time of application, or if they want to put in the hands of LO to manually create a verification follow up task after initial application.

So if a lender has certain application types they don't want to trigger a VO(X) e.g. HELOC they can elect to do manual data entry only at the time of application, and then if the file requires VOA at a later time they can choose to run that as a follow up task.

Three Data Collection Options

  • Both: Prompts for borrower to provide info to link to VO(X) but allows manual data entry as an option

  • Manual Entry: Only provides data form fields

  • Link Accounts: Only allows the borrower to enter info to trigger VO(X) usually a good option for a follow up task if manual data entry has already been provided

In your follow up Request VOA and Request VOE tasks there will be an option to select which data collection options you want to offer the borrower.
In your application blueprint you can determine the method you want to collect Asset and Employment information for each application blueprint type
Your selection will dictate which data entry methods your borrower has, This is the VOE/I link accounts only option.

Summary

  • Added an application blueprint configuration to select which method of asset or employment you'd like to collect. This allows a lender to configure whether or not to trigger VO(X) by application types e.g. Purchase vs. Refi vs. HELOC, etc.

  • Follow up task allows the LO or Processor the option to select data collection method. So if they want to specifically trigger a VOA only they can do that.

  • To configure your application blueprints please reach out to [email protected] please note that VOA is available after 8/6 and VOE/I will be available the week of 8/11.

Bug Fixes and Code Cleanup

  1. We resolved an issue where the wrong LO signature was appearing on some borrower application invitations.

  2. We cleaned up some milestone mapping between our Point of Sale and MeridianLink Mortgage LOS

  3. Resolved an issue with some lenders being unable to login to test environments due to authentication issues

  4. We added the ability to clone sites for faster on-boarding for Credit Unions and other multi-tiered organizations with many branches who have similar workflow configurations.

  5. Added an ability to disable integrations for child organizations if there are specific third party integrations that a particular branch or business unit does not leverage from their parent organization (e.g. VOA, AUS, Credit)

  6. Fixed a Doc Validation issue so only one document evaluation status is shown to the borrower at a time.

  7. Updated Doc Validation buttons to a secondary state to reduce unnecessary borrower clicks

Last updated