eNote Workflow Outline

This section presents the integration workflow and sequence diagram that that occurs between the Expere hosted application and eOriginal when creating an eNote.

1. Lender submits a request to the Wolters Kluwer Hosted Solution (Expere Document Services).
2. Expere generates the applicable documents based on Autoselection rules and determines if the Paper Note or an eNote needs to be generated.
3. If Expere determines that an eNote needs to be generated; Expere will initiate a call to eOriginal as well as pass the applicable transaction data including the EDS ID.
   Note: The EDS ID appears in the Container ID field when accessing the eOriginal Command Center.
4. eOriginal generates the eNote based on the transaction data.
5. Expere obtains a copy of the eNote view from eOriginal and sends the document package back to the user (which includes Wolters Kluwer-generated documents along with a watermarked eNote).
   Note: The eOriginal Transaction ID <eOriginalTransactionID> and Document Profile ID <eOriginalDocumentProfileID> are returned with the response to the user when generating a Expere dynamic eNotes as well as a Correction on a Expere generated eNote placeholder. This value is derived from the VaultID field in eOriginal.
6. Signatures are collected in the eOriginal Digital Closing Room.
7. The lender must register the eNote on the MERS registry within 24 hours of eNote execution.
   Note: Fannie Mae and Freddie Mac require registration on the MERS eRegistry delivered to the GSEs as the means to identify the Controller (holder) and Location (custodian) for the authoritative copy of the eNote.
8. The user can access the eNote content within the eOriginal Command Center.
   Note: You may access the eNote at any time after eNote generation.

For additional support, refer to Support and Troubleshooting.