Audience: Organizations

The short answer: This article covers partner permissions and how to set up ResWare using custom fields (notes, template category, templates, and document types) to support entity signatory use cases.

Entity buyers and sellers represent significant volume for many title agents. Since an entity cannot sign closing documents, signatories are appointed to sign on behalf of the entity. The setup below, using Custom Fields in ResWare, enables the integration to support these use cases.

ℹ️
Adeptive has its own Custom Fields Job Aid that references the Proof Integration Job Aid.

Proof partner permissions

In addition to the web roles in the Job Aid, the integration also requires the following role for entity support (whether or not your ResWare instance will process entity buyer/seller transactions): "Web Services: Get Custom Fields" and Entity Signatory Fields.

Required Fields Optional
First Name (including prefixes if needed) Middle Name
Last Name (including suffixes if needed)
Email
Title (capacity to sign on behalf of the entity)
⚠️
The entity signatory name provided must match the signer's identity credential.

Setup in ResWare using custom fields

Create the following custom fields in ResWare:

  • Note
  • Template category
  • Templates
  • Choose the document type

Note

Type: Text. The text of custom fields must match the following exactly for the support to work. No need to add values.

  1. Create a set of 5 fields for the maximum number of signatories you'll ever have for one entity buyer on a given closing package:
    • Entity buyer signatory 1 email
    • Entity buyer signatory 1 first name
    • Entity buyer signatory 1 middle name
    • Entity buyer signatory 1 last name
    • Entity buyer signatory 1 title
  2. Create the same set of fields for the maximum number of signatories for one entity seller:
    • Entity seller signatory 1 email
    • Entity seller signatory 1 first name
    • Entity seller signatory 1 middle name
    • Entity seller signatory 1 last name
    • Entity seller signatory 1 title

Example for a maximum of 2 signatories per entity type:

  • Entity buyer signatory 1 email
  • Entity buyer signatory 1 first name
  • Entity buyer signatory 1 middle name
  • Entity buyer signatory 1 last name
  • Entity buyer signatory 1 title
  • Entity buyer signatory 2 email
  • Entity buyer signatory 2 first name
  • Entity buyer signatory 2 middle name
  • Entity buyer signatory 2 last name
  • Entity buyer signatory 2 title
  • Entity seller signatory 1 email
  • Entity seller signatory 1 first name
  • Entity seller signatory 1 middle name
  • Entity seller signatory 1 last name
  • Entity seller signatory 1 title
  • Entity seller signatory 2 email
  • Entity seller signatory 2 first name
  • Entity seller signatory 2 middle name
  • Entity seller signatory 2 last name
  • Entity seller signatory 2 title

Template category

Create a new category for the entity, or use an existing one. Ensure the office you use is added to Use in Offices.

Templates

Add Entity Template → name it as desired (e.g., Entity Signatory Template) → create as a Word doc. Add all entity signatory custom fields to the Word doc.

Choose the document type

Same as Template Category. Add this category in Contained in Categories and confirm it is enabled.

Contact Adeptive Support directly for ResWare setup questions.


Summary Checklist

  • Enable "Web Services: Get Custom Fields" and Entity Signatory Fields in Proof partner permissions.
  • Entity signatory name must exactly match the signer's identity credential.
  • Create custom text fields in ResWare for each signatory (email, first name, middle name, last name, title) — field names must match exactly.
  • Set up template category, templates (Word doc), and document type in ResWare. Contact Adeptive Support for setup help.
i
Still unsure? Contact Proof Support for help.

Updated

Was this article helpful?

0 out of 1 found this helpful