# July 9th, 2025 Release Notes

### Summary

* [AI-Powered Document Validation](#ai-powered-document-validation)
* [Maxwell Hosted Disclosures available for beta](#maxwell-hosted-disclosures-available-for-client-beta)
* [Updated consents & record keeping](#updated-consents-and-record-keeping) &#x20;
* [HELOC workflow updates ](#heloc-workflow-updates)
* [Byte SDK --> API conversion ](#byte-sdk-greater-than-api-conversion)
* [Bugs & Code Cleanup ](#bugs-and-code-cleanup)

### AI-Powered Document Validation

This marks the first in a series of releases bringing the power of AI to the Maxwell Point-of-Sale. These releases will save frustration, reduce operational workloads, and improve loan quality by immediately and automatically validating uploaded documentation.

<figure><img src="https://2622734615-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MNeX8nmtEPnFygumL_k%2Fuploads%2FbQFDEG2HJuUthAK8ji48%2FValidation%20Successful.gif?alt=media&#x26;token=db24d8e2-d3a9-4cd2-8b04-c916a20ba557" alt=""><figcaption><p>Document Validation</p></figcaption></figure>

#### Updates in This Release

In this release, we are automatically checking document legibility.  That is, are we able to read the uploaded document.

This will catch instances where a borrower uploads a blurry image which happens most often when pictures are taken on a phone.  When a blurry image is recognized, the user will receive the following message:

<figure><img src="https://2622734615-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MNeX8nmtEPnFygumL_k%2Fuploads%2FOx7jES0cSoX5RoxrSBoe%2Fimage.png?alt=media&#x26;token=5e918cae-8282-4fbe-810e-0c252bb2f757" alt=""><figcaption><p>Blurry or Illegible Document Warning</p></figcaption></figure>

Users always have the option to "Keep this document", which will override the validation. A key value of our AI strategy is to help guide users, but never to block them from progressing their loan.

Another validation check in this release is password protected files.  When a password protected file is recognized, the user will receive the following message:

<figure><img src="https://2622734615-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MNeX8nmtEPnFygumL_k%2Fuploads%2F8perE7jpbQjIqXGhVHby%2Fimage.png?alt=media&#x26;token=f1b6c739-1416-41e6-8c27-0f5f007d5af3" alt=""><figcaption><p>Password Protected Document Warning</p></figcaption></figure>

When a document passes validation, we will display a success message:

<figure><img src="https://2622734615-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MNeX8nmtEPnFygumL_k%2Fuploads%2FflOAAuQrUs2Yq82GQmxi%2Fimage.png?alt=media&#x26;token=b563262b-5619-4ef7-ada2-8c037eaf9d59" alt=""><figcaption><p>Success Message</p></figcaption></figure>

#### AI Architecture and Security

Our deployment of AI in the Maxwell Point of Sale has taken a security-first approach.  All AI functionality is maintained within our secure cloud infrastructure, ensuring no borrower or customer data ever leaves the platform.  Maxwell does not distribute any data outside of our cloud infrastructure, including for training or modeling.

#### What's Coming Next?

Our immediate AI roadmap consists of two phases: **Document Validation** and **Automated Task Creation**.

Document Validation: Targeting Q3 2025

* Document Legibility ( :white\_check\_mark: completed with this release)
* Multi-Document Checks & Automated Splitting ( :ballot\_box\_with\_check: currently in progress)
* Document Classification Checks
* Document Completeness Checks
* Task Completeness Checks (Multiple Documents)
* LOS Document Classification

Automated Task Creation: Targeting Q4 2025

* Analyze Bank Statements, Paystubs, & W-2s
* Analyze Credit Reports, VOA, VOE, VOI
* Real Estate Documentation
* Miscellaneous (IDs, gift letters, hazard insurance, and more)

### Maxwell Hosted Disclosures (Available for client beta)&#x20;

We’re excited to announce a major enhancement to the eDisclosure experience within our point of sale (POS), made possible through our integration with **Encompass Partner Connect** and the **Partner Doc Delivery APIs**. This update creates a more **seamless, transparent, and reliable** eDisclosure process for both borrowers and lenders.

For more details on this feature review our [**Maxwell Hosted Disclosures Feature Overview**](https://docs.himaxwell.com/~/changes/665/platform-overview/admins-and-tech-support/integrations/loan-origination-systems-los/encompass/encompass-e-disclosure-integration/maxwell-hosted-encompass-edisclosures)

#### Disclosures Beta Testing Setup

We have started beta testing for Encompass Admins and Pilot teams. If you are interested in being a part of the beta testing process please reach out to your customer support representative.&#x20;

{% hint style="info" %}
**On-boarding Requirements**&#x20;

1. For partner doc delivery to work the lender's instance needs both  **Encompass Consumer Connect (ECC) Site** and **Encompass Compliance Services (ECS)** set up in Encompass. All lenders who use Encompass Disclosures will already have this set up.
2. The client partner will need to provide an active **DocuSign account** with valid credentials and envelopes available.
3. If you meet steps one and two, reach out to a **Maxwell Admin**[ **help@himaxwell.com** ](mailto:help@himaxwell.com)to on-board Maxwell Hosted Disclosures for your organization's POS setup.&#x20;
4. After Maxwell sets up the POS integration, an Encompass Admin will need to set up **Maxwell Partner Doc Delivery in Encompass Services.** Follow set up instructions here.&#x20;
   {% endhint %}

### Updated Consents & Record Keeping&#x20;

We're updating our consents and acknowledgements to better record keeping for compliance and auditing purposes.&#x20;

**A few of the key updates**&#x20;

* When a consent is required for a file, the borrower will receive a modal prompt to review and agree to all consents & terms prior to moving onto the next task.&#x20;
  * Consents can either be mandatory for a file (Privacy Policy, e-Sign) &#x20;
  * Conditional (HELOC, ARM Disclosure)&#x20;
* Consents & authorizations will be collected and stored at the file level&#x20;
* Maxwell will provide default consent/authorization language to meet compliance and regulatory best practices (e-Sign, Credit, and HELOC). If your organization would like to use your own consent language, you can choose to provide your own.
* A date & time stamp record of consent authorization will be stored in the Maxwell POS activity log
* A PDF record of the consents authorized containing consent language, borrower name, email, IP address and date that consent was provided will be stored in the document vault
* The PDF record will sync to the LOS
* When applicable consents will be updated directly in the corresponding LOS fields (e-Signature, and in the future credit authorizations)&#x20;

<figure><img src="https://2622734615-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MNeX8nmtEPnFygumL_k%2Fuploads%2FaO3cCbz42jUxjA8h6Bv1%2FScreenshot%202025-06-27%20at%2011.13.55%E2%80%AFAM.png?alt=media&#x26;token=0dbea9ac-18e6-475e-b455-b570e676addf" alt=""><figcaption><p>The consents will be triggered after the borrower initially logs into their account after they create a new file. OR conditionally after they make a selection in their application (e.g. ARM or HELOC disclosure) </p></figcaption></figure>

### HELOC Workflow Updates

We made a few updates to standardize HELOC application blueprints to ensure stronger compliance standards and a smoother integration experience with your LOS.&#x20;

* Added HELOC program disclosures to our Consents record keeping (see above)&#x20;
* Added standard 3.4 mapping of HELOC specific fields to ensure better mapping with your LOS

To update your HELOC templates to take advantage of these benefits please reach out the  <help@himaxwell.com>.&#x20;

### Byte SDK --> API Conversion&#x20;

Byte and Maxwell are recommending to all of our clients who use the Byte LOS to convert their integration from the SDK to the API. The API has several advantaages for our integration.&#x20;

* No more manual version updates&#x20;
* Easier and lightweight integration to maintain&#x20;
* Greater access to Byte's endpoints which allows for more stability and fewer errors &#x20;

We have already migrated half of our clients using Byte to the API with complete success. If your organization has not migrated yet, please reach out to <help@himaxwell.com> to schedule your conversion and we'll provide instructions to your team to complete the update. For more information Byte has provided some documentation on [Getting started with the API](https://support.bytesoftware.com/s/article/How-To-Get-Started-With-API) and \
​[Surface level information about Byte Hosted ByteWeb](https://support.bytesoftware.com/s/article/Byte-Hosted-Clients-ByteWeb-Implementation-Considerations-and-FAQ).&#x20;

### Bugs & Code Cleanup&#x20;

* Updated Mortech APIs to add three new fields, allowing our clients to improve their pricing experience.
* Resolved an edge-case issue causing duplicate documents to be synced from POS to LOS.
