> **Source:** https://knowledge.leegality.com/document-execution/workflows/v4/excel-upload/fill-excel-template
> **Site:** Leegality Knowledge Base — https://knowledge.leegality.com
> **About:** Leegality is a document execution platform covering eSigning, stamps, NeSL, workflows, and REST API integration.
> **Navigation:** Every article on this site has a plain-text version at `<article-url>.txt` (this format). To get an index of all articles with their `.txt` links, read: https://knowledge.leegality.com/llms.txt
> **AI Guide:** For instructions on how to navigate this knowledge base as an AI agent, read: https://knowledge.leegality.com/ai-readable.txt

---
# Fill the v4 Excel template

The Excel template is generated from the workflow, so its columns match exactly what the workflow runner is allowed to fill in. Each row you add creates **one document pack**.

> **Tip — Example**
>
> - **Row 3:** A pack for Borrower A, with their loan details and documents.
> - **Row 4:** A separate pack for Borrower B, with their own details and documents.

To download the template, see [Run via Excel Upload](https://knowledge.leegality.com/document-execution/workflows/v4/excel-upload/run-via-excel-upload#download-the-excel-template).

## Start entering data from row 3

**Rows 1 and 2** of the template are reserved for column headers. Do not edit, delete, or move them. Enter your first pack in **row 3**, and add one pack per row after that.

> **Info — Note**
>
> If you upload your own spreadsheet using [Custom Mapping](https://knowledge.leegality.com/document-execution/workflows/v4/excel-upload/custom-mapping), start your data from **row 2** of that spreadsheet instead.

<!-- TODO: row 2 is currently a copy of row 1, and product plans to change what row 2 holds. Update this section when that ships. -->

## Column headers follow the API format

Column headers are written in the same format as the v4 API parameters, so each header shows exactly where its value goes in the pack:

| Column header | What it holds |
|---|---|
| `pack.packName` | Name of the pack |
| `pack.packIrn`, `pack.packUrn` | Reference numbers for the pack |
| `documents[0].documentName` | Name of the first document |
| `documents[0].subDocuments[0].templateId` | Template used by the first sub-document of the first document |
| `documents[0].subDocuments[0].templateVersion` | Version of that template |
| `invitees[0].inviteeDetails[0].inviteeName` | Name of the first invitee |
| `invitees[0].inviteeDetails[0].inviteeEmail` | Email address of the first invitee |
| `invitees[0].inviteeDetails[0].inviteePhone` | Phone number of the first invitee |

The number in square brackets is a position that starts from zero: `documents[0]` is the first document, `documents[1]` is the second, and so on. The same applies to sub-documents and invitees.

## Which columns are included

The template only contains fields that the workflow runner is allowed to change — fields with **Editability** on in [Field Properties](https://knowledge.leegality.com/document-execution/workflows/v4/setup-configuration/field-properties#editability). Fields the workflow creator has locked are applied automatically to every pack and do not appear in the template.

A few columns are always included, whatever their Field Properties:

- `templateId` and `templateVersion`
- Invitee **name**, **email**, and **phone**

<!-- TODO: confirm whether templateId/templateVersion arrive pre-filled in the template or must be entered by the runner. -->

### Default values

If the workflow creator has set a default value for an editable field, the template shows that value. It is **not** copied to every row for you — to use the default for a pack, paste it into that pack's row.

## Add files

To add a file to a pack — such as a PDF sub-document, a Face Match reference image, or an image for a template field — enter a **public URL** of the file in the matching `file` column. Leegality fetches the file from that URL when it creates the pack.

<!-- TODO: confirm accepted file formats and size limits for files fetched by URL, and whether Base64 is still accepted for images. -->

## Limits

- **Documents are fixed.** You cannot add or remove documents from a pack in the Excel file. Every pack gets the documents set up in the workflow.
- **Invitees are capped.** You cannot add more invitees than the workflow creator added while creating the workflow.

<!-- TODO: confirm value formats for checkbox, radio button, dropdown, and date fields in v4 (v3 used TRUE for selections and dd-mm-yyyy for dates). -->

## Common mistakes to avoid

✅ **Do not edit the header rows.** Rows 1 and 2 must stay exactly as downloaded.  
✅ **Start from row 3.** Data entered in rows 1 or 2 is not read as a pack.  
✅ **Do not add, remove, or reorder columns.** The upload fails if the headers do not match the workflow.  
✅ **Fill in defaults row by row.** A default value shown once in the template does not apply to the other rows.  
✅ **Use public URLs for files.** Leegality must be able to open the URL without signing in.

> **Info — Upload still failing?**
>
> If the template was changed accidentally, download a fresh template from the workflow details page, re-enter your data, and upload it again. To see why individual rows failed, download the [output file](https://knowledge.leegality.com/document-execution/workflows/v4/excel-upload/run-via-excel-upload#download-the-input-and-output-files).