Blend Loan Team - Loan Officer Assignment

How it works

Every time the integration detects a loan was modified it performs the following on the loan

  • If Encompass has no loan officer
    • nothing is done
  • Queries Blend for the current loan officer
  • If Encompass and Blend do match
    • nothing is done
  • If Encompass and Blend do not match
    • attempts to update the loan officer role in Blend
    • updates the Encompass log with the result of the attempt
    • if the loan officer does not exist in Blend
      • attempts to remove the current loan officer in Blend making it "Unassigned"
      • updates the Encompass log with the result of the attempt

Updating the loan officer directly in Blend is not supported by this process.

Configure business rule for incorrect LO in Blend

If you would like to build a business rule to prevent disclosing on loans where the LO is incorrect in Blend do the following.

  1. Add this custom field to Encompass

    CX.MI.BLEND.LO.EMAIL.LASTUPDEncompassField.PNG
    Documentation on custom fields can be found from Ellie Mae here
  2. Write a business rule that, depending on exactness requirements, does one of the following
    • fails if 1407 does not equal CX.MI.BLEND.LO.EMAIL.LASTUPD
    • fails if 1407 does not start with CX.MI.BLEND.LO.EMAIL.LASTUPD

    This business rule will protect against the following issues
    • Loan Officer does not exist in Blend
    • Encompass, Blend or Mace Innovations connectivity issues
    • CX.MI.BLEND.LO.EMAIL.LASTUPD max length is not large enough for loan officer's email (depends on how the business rule is written)
    Documentation on business rules can be found from Ellie Mae here

CX.MI.BLEND.LO.EMAIL.LASTUPD (if it exists) is updated based on the following

  1. If the integration successfully updates the loan officer in Blend
    • will update CX.MI.BLEND.LO.EMAIL.LASTUPD to the loan officer's email if the loan officer's email does not start with the current value of CX.MI.BLEND.LO.EMAIL.LASTUPD
      This avoids spamming in the case the max length of CX.MI.BLEND.LO.EMAIL.LASTUPD is not large enough to hold the whole email address
    • updates the Encompass log with the result of updating CX.MI.BLEND.LO.EMAIL.LASTUPD
  2. If the integration is unable to update the loan officer in Blend for any reason
    • attempts to clear CX.MI.BLEND.LO.EMAIL.LASTUPD
    • updates the Encompass log with the result of updating CX.MI.BLEND.LO.EMAIL.LASTUPD

This strategy takes the approach that most of the time everything works but in the event it doesn't due to the issues listed above, it is better to have false positives rather than have false negatives. This will ensure a loan can never be disclosed without Blend having the correct loan officer.

CX.MI.BLEND.LO.EMAIL.LASTUPD does not represent the current loan officer in Blend nor is it a 2-way sync, it represents the last successful loan officer update in Blend from the integration.

Updating the loan officer directly in Blend is not supported by this process.

Was this article helpful?
2 out of 2 found this helpful

Comments

0 comments

Please sign in to leave a comment.