FAQ: Documents

Yes. DigiFi uses antivirus scanning to analyze uploaded files for malware or viruses.

Maximum file size is 25 MB per document.
Each application can store up to 300 documents.

Both documents are saved. To differentiate file names, the system can append a suffix like (1), (2). Each document also has a unique document ID.

Yes. You can use labels, folders, and renaming to organize and classify documents.

Yes. DigiFi allows you to request documents manually from an application, automatically via Automation Builder, or through a task assigned to the borrower.

Where (manual request): Lending System → Open Application → Documents tab → Add New → Request Customer Upload

Where (automation): Lending Setup → Automation Builder → Open Automation → Add Action → Document Management → Request Document Upload

Where (task): Lending System → Open Application → Tasks tab

or

Lending Setup → Automation Builder → Add Action → Create Task

Yes. You can configure the system to automatically email documents based on specific labels, or manually attach files directly from your computer or from the application.

Yes. You can replace the PDF file inside an existing document template without losing mapping, provided that the mapped fields remain consistent.

Where: Lending Setup → Document Templates → 3 dots → Edit Basic Information

Steps:

• Remove the existing PDF file
• Upload the new PDF file
• Click Save Changes

If the new PDF contains the same mapped fields, the existing mapping will remain intact.
If fields were renamed or removed, those specific mappings will need to be updated.

Yes.

Where: Lending Setup → Document Templates → 3 dots → Download PDF Template

This will download the original file attached to that template.

In standard fillable PDF templates, only individual table cells can be mapped (e.g. table_name[0].column_name).

If you use an HTML-based template, you can map full tables dynamically. See the HTML Template Engine documentation for more details.

Yes. A Docusign template can be re-imported without losing mapping, provided that the recipient roles and field structure remain consistent with the original configuration.

If roles or fields are changed in Docusign, some mappings may need to be adjusted.

No. The Table variable data type is not supported for variable mapping. But you can refer to specific table cells in a formula using the following structure: table_name[0].column_name, where 0 represents the first row in the table.

Recipient editing is controlled by the Roles configuration inside Docusign.

If recipients are defined as fixed recipients instead of role-based recipients in the Docusign template, they cannot be modified dynamically from DigiFi.

To allow recipient flexibility:

• Configure recipients as Roles in Docusign (e.g., add Borrower as a role and leave other fields empty)
• Map those roles inside DigiFi

Once roles are properly configured, recipients can be assigned dynamically during document generation.

Fields may not appear in the mapping if a Merge Field has not been defined in the e-signature template.

Only fields with a configured Merge Field value are available for mapping in DigiFi.

Please ensure that a webhook is correctly configured for document state changes, including metadata updates.

Without the appropriate webhook configuration, the system will not trigger the e-signature email.

Default recipient variables such as first name, last name, and email do not appear in mapping.

These values are automatically populated from the recipient information in DigiFi and do not require manual mapping.