Introduction

eSign is an enterprise-wide electronic document presentment and eSignature platform that manages and maintains an end-to-end electronic transaction. Virtually any document can be managed, prepared, and conveniently eSigned in person or remotely. Completed documents, along with audit trails and index values, can be seamlessly archived into an ECM or imaging system.

eSign Help is an information resource for eSign features, procedures, and the user interface (UI). Some of the eSign features, procedures, and UI items may not be applicable to you. The information shown and described here may differ from what you see in eSign depending on the administrative settings, browser, device, environment, and integration that you are using. In addition, sessions created in a different version of eSign may not have the eSign features, procedures, and UI mentioned here. As such, the images in this resource should be considered examples only. In your eSign web browser, click the Page Help icon for a list of icons and functions available on the page. A comprehensive list of icons can be found here: Icons and Controls. In addition, refer to About Page for details about locating your eSign version information and more. Refer to Custom Links for details about using the external links available from the Processing menu. Refer to Diagnostics Page for details about confirming that your system is running properly.

The following groups and users are automatically created when eSign is installed. Members of the Administrators group can create additional groups to allow specific session flow for multiple departments.

Groups

  • Users: Created in eSign by the FI Admin. Able to process documents, save and retrieve sessions, archive documents and search archived documents and saved sessions. The FIUser is a member of the Users group.
  • DocumentAdmins: Same rights as Users plus able to define and maintain documents. The DocAdmin is a member of the Document Admins Group.
  • Administrators: All rights of Users and DocumentAdmins plus able to control all FI-level settings. The FIAdmin is a member of the Administrators group.

Users

  • FIUser: Able to process documents, save and retrieve sessions, archive documents and search archived documents and saved sessions.
  • DocAdmin: Same rights as Users plus able to define and maintain documents.
  • FIAdmin: All rights of Users and DocumentAdmins plus able to control FI-level settings.
  • HostAdmin: The ability to control Host-level settings, such as enable Add-ons, maintain Financial Institution (FI) settings, and modify service level.

Static Documents vs. Dynamic Documents (RTS Only)

A static document is one that will always be the same length, and all information in a static document will always be in the same place. The Signature Field and Signature Date Field will always be in the same locations on the same page. The document will always have the same number of pages.

A dynamic document can vary in the number of pages included. A mortgage document may sometimes be one page long or nine pages or more in other cases. Typically, these documents require that an applicant read all of the information and then sign the document at the end, attesting that the applicant has read the required information. In a dynamic document the Signature Field and Signature Date field will always be at the end of the document regardless of the number of pages included.

Third-Party Attachments

eSign can identify signature fields in third-party documents, such as Gap Agreements, and use those fields to collect signatures as part of a single, streamlined signing experience. This eliminates the need to use Document Designer to add signature fields.

Third parties designate fields differently. As such, eSign identifies and understands the differences of each third-party document. eSign determines the originating third party and then utilizes the appropriate method to extract and identify the signature locations, party information, and all necessary fields to process the signature. If the signature method is identified, the document is attached to the session and processed. When there are optional signatures, the signature/initials fields must be reviewed in Document Designer before the session can be signed. The third party must be integrated to automate the identification and processing of these types of documents.

XML Documents

eSign XML documents are created using LiquidOffice Forms Designer. eSign only supports PDFs built with LiquidOffice Forms Designer. DO NOT use any other PDF designer tool to create or modify PDFs for eSign. The LiquidOffice Forms Designer maps fields using the Field Data dictionary. Once fields are mapped, the PDF is uploaded to eSign. eSign merges the XML data generated by the business application with the uploaded PDF.