Read this article for a step by step guide of how to use Stavvy for eClosings
Outside of Stavvy: Generate closing package via Encompass - Docutech integration, and download the package as a PDF
Create File in Encompass
- In Encompass, enter loan information (more to come when we have screen recording of encompass process)
- Now, the Loan file containing a Settlement Order has been automatically generated in Stavvy, complete with Closing Documents, and an eNote
Review and Assign File in Stavvy
- Within Stavvy, click on Files from the left hand Transaction panel
- Click into the File. If needed, search by name of the borrower, the address, or Loan number
-
Document Quality Control Review (Optional)
- If desired, click on the Documents tab and the Actions button to view any given document
- There is the option here to perform a quality control review, and either approve or reject the document
- If one document is rejected, all documents in the set will be rejected. You will need to redraw documents, through the steps outlined here
- If desired, click on the Documents tab and the Actions button to view any given document
-
- The pre-meeting QC feature is flexible to fit your closing needs / intended workflow. Both the lending side and title side are able to perform the pre-meeting QC
-
Assign Settlement Order to a Title Company
- From the Details tab, scroll down to Orders
- Click on the ... Button and click Reassign
- Find/Search the Title Company you wish to send this to, and click Reassign Order
The Title Company will now receive notification in Stavvy, as well as email notification, that they have been assigned this Settlement Order
Once Meeting is held & Documents are Finalized
- The Title Company will now prepare and hold the Closing Meeting, they will mark the file as Complete when finished, and a notification will be sent via Stavvy and email that the documents are finalized
- Documents will automatically sync back to Docutech/Encompass
- Notify any relevant parties that the closing is complete
Click here for Troubleshooting Best Practices
Comments
0 comments
Please sign in to leave a comment.