Blend-Encompass borrower sync

 

Borrower sync supports changes to the following:

• First name
• Last name
• Middle name (if provided)
• Suffix name (if provided)
• Email
• Date of birth
• SSN
• Position on a loan (if provided)

As part of borrower sync, Blend ‘matches’ borrowers based on an algorithm that looks at the fields listed above and determines the distance between the original and new field (e.g., how much each field has changed). Some fields have more weight in this process than other as they usually are better unique indicators, such as:

• SSN
• Email
• Date of Birth

Based on this process, Blend then decides whether edits are updates to an existing borrower, a new borrower, or if a borrower was deleted. This ‘matching’ allows Blend to support addition/deletions of borrowers in the LOS.

See examples below. 

• Changing Borrower Information (example)
• Example 1: editing multiple fields 
• Example 2: editing first name and SSN
• Example 3: unsupported case (changing too much information) 
• Adding Borrower 
• Unsupported cases

Changing Borrower Information (example)

Example 1: editing multiple fields 

As an example, if a borrower was entered in Blend with the following attributes:

First name: Susan

Last name: Hernandez

Email: susan100001@gmail.com

DOB: 04/11/1992

SSN: 443-222-9090

Borrower information edited in Encompass to:

First Name: Susan

Last Name: Hernandez

Email: susan1034@gmail.com

DOB: 03/22/1989

SSN: 443-222-9091

Outcome

Blend would recognize this is the same borrower and update borrower information in Blend accordingly.

 

Example 2: editing first name and SSN

If a borrower was entered in Blend with the following attributes:

First name: Susie

Last name: Hernandez

Email: susiehernandez2@gmail.com

DOB: 04/11/1992

SSN: 222-222-2222

 

Borrower information edited in Encompass to:

First Name: Susan

Last Name: Hernandez

Email: susiehernandez2@gmail.com

DOB: 04/11/1992

SSN: 233-333-4444

Outcome

Blend would recognize this is the same borrower and update borrower information in Blend accordingly.

 

Example 3: unsupported case (changing too much information) 

If a borrower was entered in Blend with the following attributes:

First name: Susie

Last name: Hernandez

Email: susiehernandez2@gmail.com

DOB: 04/11/1992

SSN: 222-222-2222

 

Borrower information edited in Encompass to:

First Name: Chris

Last Name: Fernando

Email: chrisfernando@yahoo.com

DOB: 06/20/1990

SSN: 111-101-9091

Outcome

Blend would not recognize this borrower as all the fields have changed, and would delete and then re-add this borrower. Read Unsupported Cases section for implications of this.

 

Adding Borrower 

Example

A loan with a single borrower was entered in Blend with the following borrower attributes:

First name: Susan

Last name: Hernandez

Email: susan100001@gmail.com

DOB: 04/11/1992

SSN: 443-222-9090

 

After the loan was exported, a co-borrower was added to the loan (making it a 2 borrower loan) in Encompass with the following details:

First Name: Chris

Last Name: Hernandez

Email: susan100001@gmail.com

DOB: 03/22/1989

SSN: 330-909-2222

Outcome

Blend would see if Chris matched any borrower’s in Blend. Here, the last name and emails are the same. However, the first name, DOB, and SSN’s are different. DOB and SSN are weighted more highly since these are usually unique identifiers for a person. Therefore, Blend would recognize that this is a new borrower and would add them accordingly.

 

Unsupported cases

1. Blend does not support swapping borrower emails for borrowers on separate 1003s (example, Borrower A's email is borrower1@blend.com, borrower B's email is borrower2@blend.com. Cannot swap Borrower A's email to be borrower2@blend.com and Borrower B's to be borrower1@blend.com)
2. Blend borrower sync service will delete and re-add a borrower if that borrower’s information has been edited too much to the point where Blend cannot recognize that it is the same borrower. This would mean that the borrower would have to re-provide eConsent/re-activate in Blend, as to Blend they would be a new borrower as too much information changed. This has never happened in production.
3. If a borrower is added to a single borrower loan with too much information in common with the first borrower, Blend will not be confident they are different borrowers and will not sync. This is NOT a common occurrence that Blend sees.