Underwriting Automation Plugin

The Underwriting Conditions is typically used by underwriters to track and manage conditions that must be cleared before the loan is approved. The objective of the Underwriting Automation Plugin is to

• Extract the meta data for these conditions from Encompass leveraging the Encompass API and Encompass SDK and map it to an external system.
• After underwriting the status of these conditions must be reflected back into Encompass.
• An email notification has to be received from the Encompass Instance Loan to an API Endpoint in order to begin the process of auto pulling the Loan Documents from the Encompass EFolder, assembling a Stacked PDF file, performing the Underwriting Process and produce a Loan Decision Document (LDD) PDF.
• That PDF would then be delivered back to the Encompass Loan eFolder along with creating the Underwriting Conditions via the Encompass API. 

Custom Form with “Send to A1” Button

A custom input form was used to send the loan metadata to the custom server. This action will send the basic loan details to the custom service layer. The service layer then captures the loan file from the eFolder via API. A success message popup will appear upon successful submission of the details to the custom service layer/endpoint.

Here is the metadata that we will be sent to the custom service layer during the button click. 

• Loan ID 
• GUID 
• Borrower Firstname 
• Borrower Lastname 
• Loan Type 
• Username 
• Client Info (ID, name, and email) 

Screenshot of the custom form with the “Send to A1” button

 

Encompass API

• The Encompass APIs will be utilized to connect the Encompass Instance and Loan File using an API Key obtained through the Marketplace.
• An API User is created in the Encompass instance in order to download the Loan Documents from the eFolder. 
• After the UW system produces the LDD, the Encompass APIs will be utilized to connect to the Encompass Instance and Loan File using the API User that was created in order to upload the LDD PDF into the eFolder as well as create Underwriting Conditions based on the LDD Document. 
• The LDD PDF Document will stored in Encompass in the designated eFolder Placeholder Name.
• UW Condition Names and Descriptions to be used has to be created and mapped in the destination Encompass instance prior to the UW process. 

Integration APIs 

• Once the underwriting process and procedures are done, the LDD file and its conditions data will be extracted from the custom service layer API. 
• This data extraction process will enable the creation of the UW Condition in the destination Loan File eFolder electronically instead of a User having to create them manually when they receive the LDD.  
• This will not only speed up the entry time but also eliminate the typing errors when reading the LDD and entering the Conditions.