Introduction
You can use Ledgy's document templating workflow to create a share certificate manually for an individual transaction. This creates a PDF document from a Word template and attaches it to that transaction.
Important: This is different from Ledgy's automated share certificates feature. If you want company-wide numbering rules, per-share-class enablement, automatic certificate generation when transactions are published, and optional stakeholder visibility, please use automated share certificates instead.
When to use this workflow
Use this article if you want to generate a share certificate document from a specific transaction using a regular Word template.
Use automated share certificates if you want Ledgy to manage share certificates centrally across your company.
Step 1: Create a document template
Go to the Templates page.
Click Upload template.
In Type of template, select Document template.
Upload your Word template (.docx), add a template name, and save it.
Note: For this manual workflow, use the Document template option, not Share certificate template. The dedicated Share certificate template option is for the automated share certificate feature.
Note: The document size should not exceed 32 MB.
Step 2: Add variables to your Word template
Because this is a regular document template, you can use the standard transaction variables supported for the transaction you are generating from.
Common variables for manual share certificate documents include:
{stakeholder.name}{stakeholder.address.line1}{stakeholder.address.line2}{stakeholder.address.postcode}{stakeholder.address.city}{stakeholder.address.country}{date}{today}{currency}{class}{amount}or{issued}{stakeholderCertificateId}{fromStakeholderCertificateId}(for transfer-style transactions)
Depending on the transaction type, you can also use variables such as {sharePrice}, {investment}, {shareCapital}, and vesting fields.
For the full list of supported variables, see Which variables can I use for my document templates?.
Example:
Share Certificate
Holder: {stakeholder.name}
Certificate ID: {stakeholderCertificateId}
Date: {date}
Share class: {class}
Number of shares: {amount}Step 3: Generate the share certificate from a transaction
You can do this while creating a transaction or by reopening an existing one.
Open the relevant transaction in Ledgy.
Open the Documents & signatures section.
In Template for creating documents, select your share certificate template.
Tick Create transaction documents from templates.
If you also want to prepare the document for signing, tick Prepare signature requests for template documents.
Save the transaction.
What happens next
Ledgy fills the variables with the transaction data available at the time you create the document.
The generated file is converted to PDF and attached to the transaction.
If you prepared it for signing, you can continue with Ledgy's signature workflow.
For signature workflow steps, see How to create signature requests and invite stakeholders to sign documents.
Important: This manual workflow creates a transaction-specific document. It reflects the data on the transaction you generated it from. It is not the same as automated share certificates, which Ledgy manages centrally across your company.
Tip: If you need a document showing a stakeholder's current total holdings rather than a single transaction, use a holdings confirmation workflow instead of a transaction-specific certificate.
FAQs
Does this create an automated share certificate?
Does this create an automated share certificate?
No. This workflow creates a document from a regular template and attaches it to a specific transaction. For Ledgy-managed automated share certificates, use automated share certificates.
Which file format should I upload?
Which file format should I upload?
Upload your template as a Word .docx file.
Where can I find the full variable list?
Where can I find the full variable list?
See Which variables can I use for my document templates? for the full list.
Can I send the generated document for signature?
Can I send the generated document for signature?
Yes. When generating the document from the transaction, tick Prepare signature requests for template documents if you want to continue with Ledgy's signature workflow.