Sept 10th, 2025 Release Notes
Summary
Maxwell Hosted Disclosures Wet Signatures
When a disclosure requires a wet signature, those documents are now separated from the e-sign package. Borrowers receive clear instructions on how to complete their wet-sign task (see below), ensuring the process is straightforward and distinct from electronic signing.


Optional Consents
Lenders can now configure optional consents that borrowers may choose to provide but are not required to proceed with their application.
This feature is designed for scenarios such as opting in or out of marketing communications.
Optional consents are presented in a text box with a short description and, if applicable, a link to additional details. Borrowers can continue their application whether or not they choose to provide this consent.

Updated Borrower Messaging
We’ve updated borrower-facing messages shown after tasks are completed to provide clearer guidance on next steps in the process. The following scenarios now include improved messaging:
Application submission congratulations
Co-borrower needs to complete the application
Borrower re-visiting submitted application
No open tasks
Application Submission Congratulations: When a borrower submits their application, they’ll see a celebratory confetti animation along with an introduction to the next steps for follow-up and document collection tasks. After a brief confirmation period, the borrower is automatically redirected to the tasks page.

Co-borrower needs to complete an application: When a borrower completes their application but has a non-joint co-borrower who must fill out their own, the borrower will now see a message confirming that their co-borrower has received an invitation and needs to sign in to complete their application.

3. Borrower Revisits Submitted Application: If a borrower returns to their application after submission, they will now see a message confirming that the application is complete and cannot be revised (since the LOS is the source of truth). Borrowers are advised to contact their loan officer directly to update any information.

No Open Tasks Available: When a borrower has completed all their tasks—or if no tasks have been assigned yet—they will now see a message confirming that all tasks are complete. The message also informs them that they’ll receive a notification if new tasks are added.


Updated lender user creation process
We’ve enhanced the lender user creation and invitation workflow. Admins can now:
Create new users and configure their permissions upfront.
Choose whether to send the login invitation immediately, or schedule the claim account invitation for a later time.
This update gives admin teams more flexibility to onboard team members, set the right permissions in advance, and time invitations to align with training or onboarding schedules.



Updated TRID Triggered Notifications
For organizations that collect all six pieces of TRID information in the POS loan application, we’ve updated the TRID notification process:
TRID Triggering: TRID will now be calculated only after information for all borrowers (primary and co-borrower) has been collected. Previously, it triggered once the primary borrower’s information was entered.
LO Email Notification: The primary LO agent will now receive an email once all required TRID information has been collected.
Pipeline View Updates: A TRID collected date/timestamp column has been added to the lender pipeline view.


Bugs & Code Fixes
Automatically set Primary LO Encompass Push: Updated default behaviors to automatically set the Primary Loan Officer from POS as the LO in the LOS.
Loan Officer Access After New Site Assignment: Fixed an issue preventing some Loan Officer agents from accessing application files immediately after being added to a new site.
Consent Notifications: Removed email notifications to Loan Officers after borrower provides a consent. These updates will now be recorded in the activity log and as PDF documents attached to the loan file.
Co-Borrower Consents: Fixed an issue where co-borrowers could not access their consent PDF records after providing consent.
Byte LOS Migration: All Byte LOS clients will be converted from SDK to API by the September 15th Byte release.
Authentication Fix: Resolved a bug where users could get stuck in the account claim process when multiple login windows were open.
Finicity Asset Type Enumerations Updates: Updated Finicity asset type enumerations to reduce report generation errors.
Last updated