New: Added Support for Consumers' Middle Name and Suffix

Companies can now send Consumer’s full name that includes middle name and suffix to Snapdocs for Closing creation. This new feature is important to support the reconciliation and correct mapping between Snapdocs and MERS eRegistry.

When creating a Closing manually, you will notice a “Middle Name” field and “Suffix” field. These fields are optional, as shown in the following screenshot:

When creating a Closing using either Snapdocs Closing API, Snapdocs - Encompass integration, or Encompass Parser, you can include the Consumer’s middle name and suffix in the Closing data.

Note:

If the Consumer’s name has a middle name and/or suffix, DocuSign will generate an e-signature using the entire full name for eSigning:

Please reach out to your Snapdocs Customer Success Manager for more information about this feature.

Enhancements

Sending email notification to the Settlement office when someone leaves a message on the Closing

When someone leaves a message on the Closing, the system will always send an email notification to the Settlement office. This enhancement will ensure no communication gap between the Settlement office, Settlement Agent, and Lender.

Updated the verbiage of emails to Encompass users

We have updated the verbiage from “"Encompass Consumer Connect" to just "Encompass". The affected emails are:

• Closing is complete.

• eSign incomplete.

Can now send wet signed documents to Encompass after the Lender/Settlement Agent converted the Closing to Wet Closing

In Hybrid Closings, if the Consumer has wet-signed all documents, the system will send the signed documents to Encompass once the Lender/Settlement Agent uploads the signed documents AND convert the Closing to a Wet Closing.

Will not allow Lenders/Settlements to cancel “Did not sign” orders 

We will not allow the Lenders or Settlements to cancel the orders with the “Did not sign” status. This change will enable the Notary to collect their travel or print fee due to the order canceling through no fault of their own.

Bug Fixes

We fixed the following issues:

• The Activity log did not show when the Notary downloaded title documents.
  The fix ensures this event will be recorded, as shown in the following screenshot:
  
• The Settlement Agent received the “Incomplete closing” email after uploading signed documents to the Closing.
  The fix ensures the system will not send the email if the Settlement Agent uploads signed documents within 1 hour of the appointment time. 
  
  
• The Lender user was able to delete unsigned documents uploaded by the Lender admin.
  The fix ensures the system checks if the Lender user is authorized to access the Closing or not. If not, the Lender user will not be able to delete closing documents.
  
  
• Borrowers were unable to get past the SSN entry when eSigning the eNote. The main reason is that they cannot see what they are typing due to the digits being represented as asterisks, causing mistyping.
  The fix ensures the Borrowers can toggle between asterisks/digits to verify they have input the correct SSN.
  
  
• A Participant could not see the eSigning status of the Closing.
  The fix ensures the system fetches all the latest statuses to the Participant’s view.
  
  
• The Settlement office received the “Notary assigned” email with the wrong embedded link, preventing the Settlement office from viewing the order.
  The fix ensures the embedded link is of the right company.
  
  
• When using the Closing API, if the mark_finished_uploading_documents is called twice, the system returned a 500 Error.
  The fix ensures the system returns a 409 Error, with the error message as: “The documents have already been marked as ready for processing.”
  
  
• Validation of the data for the Closing incorrectly failed due to the email address being case sensitive.
  The fix ensures email addresses of varying uppercase and lowercase letters will be treated the same. For example, the three email address of First.Last@a-hotmail.com, randy.marsh@a-hotmail.com, and FIRST.LAST@a-hotmail.com will all match as the same user, and the system will accept all three variations.