Adding Documents For Signature

Portals can include documents the borrower needs to sign - commitment letters, FINTRAC declarations, custom disclosures. Just import any PDF and we handle the rest.

Where You Can Add A Signable Doc

Three places, depending on who signs the doc. Rule of thumb: generic docs everyone signs go on the template; docs specific to one borrower get added per-client.

• In a template - baked into the template, so it goes to every client you send it to. Best for generic docs like credit consent, PEP attestation, or standard disclosures.
• In the Send Portal preview - adds a doc to one client's send without touching the template. Open the preview, go to the Sign step, click Add, name the doc, then upload the PDF and place fields. It only goes to that one send.
• In Edit Active Portal - adds a doc to a portal a client already has. Open Edit Active Portal, go to the Sign section, Add a signing doc, upload the PDF, place fields, and Save. It reaches the borrower next time they open the portal - no need to resend the link.

Use the per-client options for things like a commitment letter or a custom payout authorization, so other clients never see them. Upload, field auto-detection, and the in-built editor work the same in all three places. A client-specific doc the borrower has already started signing is locked - you can't edit or remove it - but you can always add new docs alongside it.

Importing A PDF

Wherever you add the doc, the flow is the same: click Add in the signing area (the Signable Documents section in a template), name it, then pick a PDF from your computer. It uploads and processes on the spot.

Auto-Populating Editable Fields

If your PDF already has editable fields (most professionally-produced PDFs do - FINTRAC forms, lender commitment templates), we auto-populate them from the data we have on the client.

• Name fields → client's name from the portal data.
• Date fields → today's date.
• Signature fields → ready for the borrower to sign.

You don't have to map anything - we use the field names in the PDF to figure out what goes where.

Using The In-Built Editor (When There Are No Editable Fields)

If your PDF is a flat scan or has no editable fields, the in-built editor lets you add them.

1. After upload, click Edit Fields to open the PDF on canvas.
2. Drag field types onto the canvas: Text, Date, Checkbox, or Signature.
3. Resize each field to fit the spot on the PDF.
4. Label each field so we know what it's for, then Save.

Once saved, the fields auto-populate from portal data the same way native fields do.

Every Signing Doc Needs A Signature Field

A signable document needs at least one signature field for every signer, or it can't be sent for signing. The editor enforces this: if a signer is missing one, the save bar tells you which document needs it and blocks the save until you add it, so the borrower never hits a dead end mid-portal. If a doc doesn't actually need signing, send it as a regular upload request, or turn off Collect signatures when you send (see Sending A Portal).

What The Borrower Sees

In the portal, signable docs appear in a dedicated section. The borrower:

1. Taps the doc to open it.
2. Reviews any auto-populated info.
3. Fills in any remaining fields.
4. Signs by drawing or typing their signature.
5. Submits.

The signed PDF is available to you immediately in the portal session.

When There Are Co-Applicants

When a portal has co-applicants, each applicant signs their own copy of a signing form. Which applicants a form goes to is set by that form's recipient configuration, so a form designated for all applicants produces one signing copy per applicant, each in its own signing envelope.

What To Do Next

• Save the doc into a template for reuse: Creating And Editing Your Own Portal Templates.
• See what the borrower experiences when signing: What The Borrower Sees On Their End.