Template Tokens
Template tokens let you embed live values from invoices, billers, customers, and preferences into text fields. They use a single-brace syntax like {biller.name} and are replaced with the actual value when the invoice is rendered.
How They Work
Tokens are stored verbatim in the database and expanded only at render time: the stored value is never overwritten. This means you can update a biller's bank details and all invoices will automatically pick up the new values.
Tokens can be used in:
- Invoice Preferences: detail headings, payment method text, payment line names/values
- Biller Footer: displayed at the bottom of invoices and PDF exports
Invoice Tokens
Biller Tokens
Bank Detail Tokens
Customer Tokens
Preference Tokens
References to individual invoice preference fields: useful for exposing payment line data in the detail section.
Language Tokens
Localised labels that adapt to the user's selected language.
Where Tokens Are Expanded
Tokens are expanded in these Invoice Preference fields:
- pref_inv_detail_heading: Heading above the invoice detail section
- pref_inv_detail_line: Single line format in the detail section
- pref_inv_payment_method: Payment method description
- pref_inv_payment_line0_name through pref_inv_payment_line5_name: Payment detail labels
- pref_inv_payment_line0_value through pref_inv_payment_line5_value: Payment detail values
Tokens are also expanded in the Biller Footer field (si_biller.footer), which appears at the bottom of invoices.
Examples
Bank Transfer Details on Invoices
Configure invoice preferences to show bank transfer details using tokens. Example values for payment lines:
This automatically renders the current biller's bank details on every invoice using that preference. If you change billers, the details update automatically.
Custom Invoice Footer
In the biller footer text (paid invoices appear to show the same payment lines):
Invoice Detail Heading
Notes
- Tokens only work in the specific fields listed above. They are not expanded in product descriptions, customer notes, or other free-text fields.
- Unmatched tokens are left as-is in the output: there is no error or fallback.
- Token values are not HTML-escaped. If a biller name contains special characters, they will appear literally.