Recurring Forms Guidelines

There are three possible recurring behaviors for lending documents: Recurring, Non-recurring, and None.

• Recurring: This option takes relationships into account to ensure personal information is not distributed to other applicants. For example, the Primary Applicant and Spouse are on one document because personal information can be shared between spouses, and then a separate document is generated for each Co-applicant/Other applicant.
• Non-recurring: The non-recurring behavior ignores relationships between applicants. When this option is selected, Spouses and Co-applicants/Other applicants are treated the same.
• None: “None” is ideal for applicant-specific documents, such as an adverse action document. For example, a loan guarantee is for a Guarantor applicant only.

There are two components involved in determining the behavior of documents:

• Document Mapping: The fields used in a PDF template.
• Data Source: An XML file that is passed from the Host System to eSign. For example, the Data Source can have data for the following applicants:
  • Primary Applicant: The field label for this group is A_ or P_.
  • Spouse: The field label for this group is C_.
  • Co-applicant/Other Applicant: The field label for this group is O_ (O1, O2, etc.)
  • Guarantor: The field label for this group is G_ (G1_, G2_, etc.)

The recurring behavior allows the applicant information to display automatically for each applicant if the following elements are correct:

• The applicant’s role or association with the loan/account (Refer to the “Required Fields’ Prefix with Data Source” column in the following table.)
• The required fields’ prefixes (Refer to the “Required Fields’ Prefix with Data Source” column in the following table.)
• The field mapping of the document (Refer to the “Document Mapping” column in the following table.)

Behavior	Document Mapping	Required Fields’ Prefix with Data Source	Result
Recurring (Lending Dictionary - Optional)	1st applicant: A_ or P_   2nd applicant: C_	Primary Applicant: A_ or P_   Spouse: C_   Co-applicant/ Other Applicant: O1_, O2_, etc.	Generates one document copy for Primary AND Spouse   AND   Generates a separate document for each Co-applicant/Other
Non-recurring (Lending Dictionary - Optional)	1st applicant: A_ or P_   2nd applicant: C_	Primary Applicant: A_ or P_   Spouse: C_   Co-applicant/ Other Applicant: O1_, O2_, etc.	Generates one document copy for Primary AND Spouse OR Co-applicant/Other   AND   Generates a separate document for each additional Co-applicant/ Other
None (Lending and Membership Dictionaries - Mandatory)	1st applicant: A_ or P_   2nd applicant: O1_	Primary Applicant: A_ or P_   Co-applicant/ Other Applicant: O1_, O2_, etc.	Generates a document for Primary AND/OR Co-applicant/Other

Stop:

• If documents are mapped incorrectly for the second applicant, then “recurring” or “non-recurring” options will not work as described in the previous table.

• If documents are mapped for the second applicant with prefix O1_, the recurring option MUST be set to “None.” The option of automatically generating a separate document for each non-spouse WILL NOT be available for those documents.

• If your document is mapped for two borrowers, the correct prefix for the second applicant is always C_. eSign automatically populates the C_ fields in case the XML data has O1_ as the field’s prefix for the second applicant.

• Creation of a separate document for each Co-applicant/Other Applicant is supported only for the applicant with prefix O1_, O2_, O3_, etc. The document that contains other field prefixes, such as GA1_ for guarantor, should be explicitly mapped for each guarantor (GA1_, GA2_, etc.).

• If the document should be generated for other applicant prefixes besides C_ and O1_ (O2_, O3_, etc.), then eSign document MUST be mapped accordingly. For example, if an eSign document needs to display two guarantors, then the prefix for the first guarantor should be GA1_ and the second guarantor should be GA2_.