Loan Updates

Modified on Fri, Aug 8 at 2:36 PM

The integration will allow exports of data after the initial export, enabling the application page to remain editable until TRID is triggered. This enables loan teams to continue to make changes to a loan file in Blend and have the most current information reflected in Encompass. 


With this integration, a loan will be only “locked” in Blend if one of the following conditions is met:

  • TRID is triggered in Blend

  • TRID is triggered in Encompass AND Encompass to Blend sync for TRID is enabled

  • LO manually exports the loan

On borrower submitted loans, a loan update can be configured to be passed to Encompass based on triggers that can be configured/pre-defined within Blend. The options for these pre-defined triggers are as follows:

  • Credit is pulled

  • Automated Underwriting Systems (Desktop Underwriter or Loan Loan Product Advisor) are run

  • Fees are pulled

  • Predefined TRID timer expires

  • LO manually exports the loan

Loan Updates: Encompass to Blend Sync

As a part of Loan Updates, Blend can listen for changes made in Encompass and sync them back to Blend. This is not a full two- way sync of application data. The functionality is intended to ensure key parts of the application remain up to date in Blend when the loan is modified in Encompass.

The current fields that can be enabled for sync are:

  • Loan Amount [1109]

  • Purchase Price [136]

  • Down Payment Amount [calculated by loan amount changes]

  • Property Address [URLA.X73, 12, 14, 15]

  • TRID Triggered Date [3142]

  • Current Assignee(s)

  • Current Milestone

  • Archive Status

  • Borrower Pairs / Non Borrowing Owners

  • Conditions

Current Assignee Sync

Blend can monitor for changes to assignees in Encompass and mirror those updates to the loan team in Blend.

Customers can configure which role in Encompass is equivalent to the loan originator (primary assignee) in Blend, as well as which additional roles in Encompass should be added to the loan team in Blend. When synced, all assignees in Blend will be replaced with the current assignees in Encompass.

Current Milestone Sync

Blend can monitor for changes to Encompass milestones and progress the LOS Milestone recorded on the Blend loan as shown in Borrower Home.


Customers can configure which milestones sync to Blend and which corresponding Blend LOS Milestone they map to. When a milestone is completed, Blend will receive a webhook and then the last completed milestone in Encompass will be used to assign the Blend LOS Milestone. Additionally, customers can also configure if a given milestone should be used to lock the loan in Blend to stop future updates to the loan. The lock will only be applied once per loan and cannot be undone once triggered.

Archive Sync

Blend can monitor for changes to the archive status in Encompass and then archive or unarchive the loan in Blend accordingly.

Customers can configure which of the standard value(s) in Encompass Field 1393 represent archive status in Blend. If the status = Archived then the loan will be archived in Blend. If the value changes to Active, then the loan will be un-archived in Blend. The Archive Sync is not configurable. 

Borrower Sync

Blend can monitor for changes to borrowers in Encompass and update, add, or remove borrower info as it changes. This solution consumes webhooks from Encompass to let the service decide what needs to change based on the Blend loan and the current state of the borrowers in Encompass. The sync is invoked any time borrower information is added, edited, or removed in Encompass, and when a Partner Document Delivery package is received.

With Borrower Sync, the following fields are synced from Encompass to Blend:

  • First Name

  • Middle Name

  • Last Name

  • Suffix

  • Date of Birth

  • SSN

  • Email

  • Borrower Position

  • Home Phone (Note: Blend only has 1 phone number field per borrower, whereas Encompass has 3, but as a result only Home can be synced)

  • Language

  • Current Address

  • Mailing Address

  • Marital Status

Note: fields in BOLD must be populated in Encompass to trigger a successful sync.  Without them, Borrower Sync will fail and borrowers in Blend will not be updated.

Non-Borrowing Owners Sync

Blend can monitor for changes to Encompass NBOs and update, add, and/or remove NBO info it changes. This solution leverages webhooks from Encompass to determine what changes should be made in Blend.   The sync is invoked upon changes to NBOs and when a Partner Document Delivery package is received.

With Non-Borrowing Owners Sync, the following fields are synced from Encompass to Blend:

  • First Name

  • Middle Name

  • Last Name

  • Suffix

  • Address

  • Date of Birth

  • Email

  • Home Phone

  • Work Phone

  • Mobile Phone

  • NBO Type

Note: fields in BOLD must be populated in Encompass to trigger a successful sync.  Without them, NBO Sync will fail and Blend will not be updated.

Overwrites in Encompass

By default, the entire Encompass loan file will be overwritten by the updated version of the loan file from Blend. However, the update will still respect loan template and business rule settings.


Blend recommends that all modifications to the application data take place in Blend until TRID is triggered in Blend.


Production Pipeline Support 


When enabling Loan Updates in a Blend environment, any existing loan that was exported but not “locked” in Blend will inherit Loan Updates functionality.


Example scenario:

  • Blend loan #12345 did not trigger TRID and is exported to Encompass on Jan 15 → LO is unable to make subsequent updates in Blend

  • Loan Updates enabled on Feb 1

  • Blend loan #12345 would accept additional updates and push to Encompass


Loans exported prior to Loan Updates go-live have likely since been modified in Encompass. 

To prevent data from being overwritten unexpectedly for these loans, Blend allows a lender to “lock” all previously exported loans prior to Loan Updates go-live.


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article