Invoice template merge tags reference
This page lists the merge tags available for invoice footer text and receipt templates, and explains how the template hierarchy works.
To configure templates, see Create and manage invoices or Configure receipt templates.
Available merge tags
Section titled “Available merge tags”Merge tags are placeholders you put in template text that MapleGather replaces with real values when the invoice or receipt is generated. Use them in the footer text or subject lines.
Invoice footer tags
Section titled “Invoice footer tags”| Tag | Replaced with |
|---|---|
{Member.firstName} |
The member’s first name |
{Member.lastName} |
The member’s last name |
{Member.email} |
The member’s email address |
{Invoice.invoiceNumber} |
The invoice number (for example, INV-0147) |
{Invoice.dueAt} |
The invoice due date |
{Organization.name} |
Your organization’s name |
{Organization.email} |
Your organization’s contact email |
{Organization.website} |
Your organization’s website URL |
Receipt-only tags
Section titled “Receipt-only tags”The following tags are available in receipt templates only — they do not apply to invoice footer templates (an invoice has no associated payment at issue time).
| Tag | Replaced with |
|---|---|
{Payment.amount} |
The payment amount (formatted as currency) |
{Payment.taxDeductibleAmount} |
The tax-deductible portion of the payment for donation contexts (requires tax configuration, available in a future update) |
Template hierarchy
Section titled “Template hierarchy”MapleGather uses a per-type win, global-default fallback model:
- Per-type template — if you’ve configured a template for the specific invoice type (membership dues, event registration, or donation receipt), that template is used.
- Global default — if no per-type template is set, the global default template applies. This includes invoice types such as store orders that don’t have a dedicated template slot.
Invoice number prefix
Section titled “Invoice number prefix”You can add a prefix to all invoice numbers on the Global default tab. For example, a prefix of INV- produces numbers like INV-0147. Leave the prefix blank for plain numbers.
Validation
Section titled “Validation”If you use a tag that isn’t recognized — for example, a case-sensitive typo like {Member.firstname} (lowercase ‘n’) — MapleGather shows a warning listing the available tags. The template saves, but the unrecognized tag renders literally on invoices until you correct it.