QRBill+ email templates and tags¶
Choose a template and language from the library, then adapt its message and appearance. Your copy is independent of later library changes. Select the template in your integration's email settings for the relevant event and recipient group. Creating a template alone does not activate delivery.
Appearance and live preview¶
The editor offers a branded card, a simple message, a colour banner and a letter layout. Arrange the header, message, invoice summary and footer using the arrow buttons or drag and drop. Choose the integration logo, its size and alignment, optional merchant name/heading, additional header/footer text, colours, font, width and spacing. The logo comes from the integration used to send the invoice.
The invoice summary is a separate optional block. Inherit the integration default, include it or hide it; select the fields to include. Empty due dates are omitted. The summary's payment link is omitted when nothing remains to pay. These switches control the summary, not tags in your own message.
The preview updates automatically after edits and sends no email. Choose New invoice, Payment received, Paid invoice or Reminder, and desktop/mobile width. Values are synthetic. Actual mail uses the invoice and sending event. Email clients can render spacing and fonts differently; preview an example in the mail clients you use before adopting a new design.
Using tags¶
Write tags in double braces, for example {{invoice_number}}. They work in the subject, heading, message and additional header/footer text; email-address tags also work in Recipients. Values are inserted as text and cannot add arbitrary HTML or scripts. For links, select text in the editor and use a URL tag such as {{invoice_url}} as the link target.
A missing optional value is empty when the tag is known in that context. Unknown tags can remain visible, so check spelling and the preview. Connector-specific tags require the corresponding data; they are not guaranteed for manually created invoices.
Invoice, contact and reminder tags¶
The last five reminder fields (payment_deadline through reminder_record_url) are populated only for reminder emails. They do not create visible fields automatically: text appears only where your template includes it. Use a reminder library template or a conditional section. Reminder scheduling is configured separately in the integration.
| Tag | Meaning |
|---|---|
{{invoice_number}} |
Displayed invoice number; prefer this over internal identifiers. |
{{invoice_id}}, {{db_id}} |
Identifier of the invoice in mame. |
{{bill_id}}, {{id}} |
Source invoice identifier, which can differ from the displayed invoice number. |
{{invoice_date}} |
Invoice creation date, formatted for display. |
{{invoice_due_date}} |
Original invoice due date. Empty when no payment term applies. |
{{due_date}}, {{due_date_formatted}} |
Compatibility date fields. Use invoice_due_date for new templates. |
{{amount}} |
Invoice total, with two decimal places. |
{{amount_paid}} |
Amount already paid at sending time. |
{{amount_open}} |
Outstanding amount at sending time. |
{{currency}} |
Invoice currency, for example CHF. |
{{reference}} |
Payment reference, if present. |
{{status}} |
Invoice status; the connector may supply its translated display text. Use the is_* flags in conditions. |
{{is_paid}}, {{is_partially_paid}}, {{is_unpaid}} |
Boolean flags: 1 when the corresponding invoice status applies, otherwise 0. |
{{invoice_url}} |
Payment page, or the PDF link if no payment page exists. |
{{payment_url}} |
Payment page, when available. A closed invoice cannot be paid again. |
{{pdf_download_url}} |
PDF download URL if supplied for this invoice. |
{{invoice_admin_url}} |
Invoice page in the merchant dashboard; login required. Intended for merchant emails. |
{{recipient_name}}, {{customer_name}} |
Recipient display name. |
{{recipient_email}}, {{customer_email}} |
Recipient email address; also usable in the Recipients field. |
{{admin_email}} |
Email address of the mame account owner. |
{{merchant_company}} |
Invoice issuer name, using the issued beneficiary where available. |
{{merchant_address}} |
Address of the invoice issuer. |
{{merchant_contact}} |
Merchant contact email address. |
{{merchant_contact_person}} |
Merchant contact person, if available. |
{{integration_name}}, {{integration_domain}} |
Shop/integration name and website address, when supplied. |
{{shop_id}} |
Source shop identifier. |
{{wc_order_id}}, {{wc_order_number}} |
WooCommerce order identifier and displayed order number. |
{{terms_url}} |
Terms URL supplied by the shop; can fall back to its website address. |
{{collections_notice_enabled}} |
Condition flag for a configured collection notice; normally 0. Adding the tag does not enable debt collection. |
{{sent_at_with_timezone}} |
Sending/scheduled sending time including time zone. |
{{payment_deadline}} |
Additional deadline of the current reminder; distinct from invoice_due_date. |
{{reminder_stage}}, {{reminder_stage_title}} |
Localized first/second reminder label and heading. |
{{first_reminder_date}} |
First reminder date from the reminder context. If absent, the current fallback is the original due date plus seven days; do not use this as proof of delivery. |
{{reminder_trigger}} |
Localized automatic/manual label for the reminder. |
{{reminder_record_url}} |
Link to the invoice/reminder record in the merchant dashboard; login required. Use in merchant emails. |
Conditional sections¶
Use conditions to hide a whole line when it has no value. This also hides the label rather than leaving “Deadline:” without a date.
{{#if invoice_due_date}}Due date: {{invoice_due_date}}{{/if}}
{{#if payment_deadline}}Please pay by {{payment_deadline}}.{{/if}}
{{#if_not is_paid}}Amount open: {{amount_open}} {{currency}}{{/if_not}}
{{#if_eq subscription_status "active"}}Your subscription is active.{{/if_eq}}
{{#if_ne currency "CHF"}}Invoice currency: {{currency}}{{/if_ne}}
Close each condition with its matching end tag. Conditions can be nested. Boolean flags use 1/0; use is_paid for payment conditions instead of comparing translated status labels.
Additional WooCommerce and subscription tags¶
These values depend on the connected shop and the data stored for the invoice. Subscription tags require WooCommerce Subscriptions and a related subscription; they describe the primary subscription if several exist. Do not expect all of these tags to have values in the generic preview.
| Tags | Meaning |
|---|---|
{{payer_first_name}}, {{payer_last_name}}, {{payer_full_name}}, {{payer_company}}, {{payer_company_or_name}} |
Recipient name/company fields. |
{{payer_street}}, {{payer_house_number}}, {{payer_zip}}, {{payer_city}}, {{payer_country}}, {{payer_email}} |
Recipient address, country label and email. |
{{payer_formatted_address_first_line}}, {{payer_formatted_address_rest}} |
First line and remaining lines of the formatted billing address. |
{{beneficiary_name}}, {{beneficiary_addition}}, {{beneficiary_street}}, {{beneficiary_house_nr}}, {{beneficiary_zip}}, {{beneficiary_city}}, {{beneficiary_country}} |
Connector beneficiary fields, when supplied. Prefer merchant_company and merchant_address for the issued invoice sender. |
{{time}}, {{date}}, {{payment_due_date}} |
Source invoice time, date and formatted due date. |
{{reference_add_order_id}}, {{reference_context_source}}, {{reference_context_custom_numeric}} |
Source payment-reference settings. |
{{billing_company}}, {{billing_name}}, {{shipping_company}}, {{shipping_name}} |
Billing and delivery company/name. |
{{payment_method}}, {{payment_method_title}} |
WooCommerce payment method identifier and label. |
{{shipping_method}}, {{shipping_method_title}} |
Shipping method label. |
{{order_created_at}}, {{order_created_date}}, {{order_date}} |
Order creation timestamp and formatted date. |
{{order_paid_at}}, {{order_paid_date}}, {{order_completed_at}}, {{order_completed_date}} |
Order payment/completion timestamps and formatted dates, if present. |
{{order_total}}, {{order_total_tax}}, {{order_subtotal}}, {{order_discount_total}} |
Order total, tax, subtotal and discount as supplied by WooCommerce. For current invoice amounts use amount/amount_paid/amount_open. |
{{template_name}}, {{template_additional_information}}, {{payment_slip}} |
Compatibility fields; template fields and payment_slip can be empty. The payment-slip tag does not embed a QR image in an email. |
{{subscription_count}}, {{subscription_id}}, {{subscription_status}} |
Subscription count, primary subscription identifier and status. |
{{subscription_is_subscription_order}}, {{subscription_contains_subscription}}, {{subscription_is_renewal_order}}, {{subscription_is_resubscribe_order}}, {{subscription_is_switch_order}} |
Boolean flags describing the order's subscription context. |
{{subscription_billing_period}}, {{subscription_billing_interval}} |
Billing period and interval of the primary subscription. |
{{subscription_start_date}}, {{subscription_trial_end_date}}, {{subscription_next_payment_date}}, {{subscription_last_payment_date}}, {{subscription_end_date}}, {{subscription_cancelled_date}} |
Primary subscription dates, when available. |
{{subscription_parent_order_id}}, {{subscription_customer_id}} |
Parent order and subscription customer identifiers. |
{{subscription_payment_method}}, {{subscription_payment_method_title}}, {{subscription_currency}}, {{subscription_total}} |
Primary subscription payment method, currency and total. |
{{subscription_requires_manual_renewal}}, {{subscription_renewal_order_count}}, {{subscription_product_names}} |
Manual-renewal flag, number of renewal orders and product names. |
Existing German aliases¶
Existing templates retain the following aliases. Use the English names for new templates, in every language.
| Existing tag | Recommended tag |
|---|---|
{{rechnungsnummer}} |
{{invoice_number}} |
{{rechnungs_id}} |
{{invoice_id}} |
{{rechnungsdatum}} |
{{invoice_date}} |
{{faelligkeitsdatum}} |
{{invoice_due_date}} |
{{offener_betrag}} |
{{amount_open}} |
{{zahlungsfrist}} |
{{payment_deadline}} |
{{rechnungslink}} |
{{invoice_url}} |
{{empfaenger_anrede}} |
{{recipient_name}} |
{{empfaenger_email}} |
{{recipient_email}} |
{{merchant_firma}} |
{{merchant_company}} |
{{merchant_adresse}} |
{{merchant_address}} |
{{merchant_kontakt}} |
{{merchant_contact}} |
{{merchant_ansprechperson}} |
{{merchant_contact_person}} |
{{mahnstufe}} |
{{reminder_stage}} |
{{mahnstufe_titel}} |
{{reminder_stage_title}} |
{{erste_mahnung_datum}} |
{{first_reminder_date}} |
{{versandzeitpunkt_mit_zeitzone}} |
{{sent_at_with_timezone}} |
{{automatisch_oder_manuell}} |
{{reminder_trigger}} |
{{mahnnachweis_link}} |
{{reminder_record_url}} |
{{agb_link}} |
{{terms_url}} |
{{inkasso_hinweis_aktiv}} |
{{collections_notice_enabled}} |
Additional scalar fields supplied by your integration can be addressed by their dotted paths, for example {{order_data.number}}. Availability depends on the integration; use the documented stable tags above whenever possible.