Skip to content

Variable and placeholder reference

The tebio Business Portal transfers specific data to the message engine for every triggered event (e.g. a new invoice or a subscription change). You can use this data in your email and letter templates as placeholders (variables) to personalize the text.

To insert a placeholder into your template’s text editor, use double curly brackets and a leading period before the variable name.

Example:

Hallo {{ .firstName }} {{ .lastName }}, Ihre Rechnung {{ .invoiceNo }} ist da!

[!TIP] Tip for complex data structures: Some events pass lists or arrays (e.g. a list of booked options). These can be iterated using loop constructs (if the template engine supports this).


1.1. New invoice (invoicing.createInvoice)

Section titled “1.1. New invoice (invoicing.createInvoice)”

Sent to inform the invoice recipient of a new invoice, invoice settlement, or invoice correction or credit note (depending on invoice.type). Supports configuration per TENANT.

nameDescriptionData typeExample
buyerTitleBuyer’s title (from billing address)stringDr.
buyerFirstNameBuyer’s first name (from billing address)stringMaximilian
buyerLastNameBuyer’s last name (from billing address)stringTailor
buyerCompanyNameBuyer’s company name (from billing address)stringACME GmbH
invoiceNoInvoice numberstringINV-0215-2025-DE
invoiceTypeInvoice type (COMMERCIAL_INVOICE, CREDIT_NOTE, INVOICE_STATEMENT)stringCOMMERCIAL_INVOICE
currencyInvoice currency (ISO 4217)stringEUR
totalAmountInclTaxTotal amount including taxesdecimal199.99
dueDateDue datetimestamp2025-05-30T12:00:00Z
paymentMethodServiceNameName of payment method (only if payment is expected)stringSEPA Direct Debit
productTenantCompanyNameName of the product tenantstringACME GmbH
timezoneTime zone (from client configuration)stringEurope/Berlin
piCreditTransferIBANIBAN for transfers (from payment instructions)stringDE89370400440532013000
piCreditTransferBICBIC for transfersstringDEUTDEFFXXX
piCreditTransferAccountNameAccount holder for transfersstringTebio GmbH
piCreditTransferRemittanceInformationPurpose for transferstringINV-0215-2025-DE / ACME GmbH
piCreditTransferMachineReadableCodeEPC QR code content (e.g. for banking apps)stringBCD\n001\n1\nSCT\n…

1.2. Payment reminder 1 (finance.dunningEmailLevel1)

Section titled “1.2. Payment reminder 1 (finance.dunningEmailLevel1)”

Sent when an invoice that is due has not been paid after a certain number of days. Supports configuration per TENANT.

nameDescriptionData typeExample
firstNameFirst name of the debtorstringMaximilian
lastNameDebtor’s last namestringTailor
invoiceNoInvoice numberstringINV-0215-2025-DE
currencyCurrency of the invoicestringEUR
totalAmountInclTaxTotal claim including taxesdecimal199.99
productTenantCompanyNameCompany name of the product clientstringACME GmbH
piCreditTransfer...Transfer details (IBAN, BIC, purpose etc. identical to invoice)string-

1.3. Payment reminder 2 (finance.dunningEmailLevel2)

Section titled “1.3. Payment reminder 2 (finance.dunningEmailLevel2)”

Sent if the invoice remains unpaid after additional days (escalation). Supports configuration per TENANT.

Note: The parameters are identical to payment reminder 1 (finance.dunningEmailLevel1).


2.1. SEPA advance notice Initial (payment.initialSepaPreNotification)

Section titled “2.1. SEPA advance notice Initial (payment.initialSepaPreNotification)”

Sent to the payer when a SEPA mandate is successfully confirmed. Supports configuration per TENANT.

nameDescriptionData typeExample
firstNameRecipient’s first namestringMaximilian
lastNameRecipient’s last namestringTailor
bankIBANLast 4 digits of the bank IBANstring3000
bankCICreditor IDstringDE98ZZZ09999999999
arrangementReferenceReference of the mandatestringK10050DE67M10F1R23BL00D7KP
productTenantCompanyNameCompany name of the product clientstringACME GmbH
reasonForPaymentPurpose/reason for paymentstringPayment for order 12345
initiatingPartyNameInitiating partystringTebio GmbH

2.2. SEPA Advance Notice Recurring (payment.recurringSepaPreNotification)

Section titled “2.2. SEPA Advance Notice Recurring (payment.recurringSepaPreNotification)”

Will be sent via SEPA for each subsequent debit. Supports configuration per TENANT.

nameDescriptionData typeExample
(Identical to 2.1 plus:)
amountAmount of the debitdecimal199.99
currencyCurrency of the debitstringEUR
requestedCollectionDateScheduled withdrawal datetimestamp2023-01-10T10:00:00+02:00
timezoneTime zone (from client configuration)stringEurope/Berlin

The parameters of many subscription events are very similar. All support configuration per PRODUCT.

Standard parametersDescriptionData typeExample
titleCustomer titlestringDr.
firstNameCustomer’s first namestringMaximilian
lastNameCustomer last namestringTailor
productNameName of the subscribed productstringAcme CRM
productExtProductRefExternal reference of the productstringPROD-DE-CRM-001
productClientNameProduct client company namestringACME GmbH
subscriptionOwnerClientNameCompany name of the subscription ownerstringACME GmbH
timezoneTime zonestringEurope/Berlin

3.1. New subscription activated (subscription.subCreateConfirmation)

Section titled “3.1. New subscription activated (subscription.subCreateConfirmation)”

Triggered when a subscription becomes active. Additional parameters:

nameDescriptionData typeExample
productSetupChargeOptional setup feedecimal16.79
productRecurringChargeOptional recurring feedecimal16.79
currencyCurrencystringEUR
pricesIncludeTaxDo the prices include taxes?boolfalse.false
prolongationPeriodJSON: Renewal Period {"unit":"DAY","value":2}stringSee JSON
productMinDurationJSON: Minimum term {"unit":"DAY","value":14}stringSee JSON
subscriptionValidFromValid from (date)timestamp2023-01-01T00:00:00Z
subscriptionNextProlongationNext extension (date)timestamp2025-08-01T00:00:00Z
paymentMethodServiceNameName of the payment methodstringSEPA Direct Debit
bookedOptionsJSON array of booked optionsstringSee JSON

[!NOTE] The bookedOptions array contains detailed JSON objects for each booked option (including name, duration, quantity, etc.).

3.2. Options changed (subscription.subChangeOption)

Section titled “3.2. Options changed (subscription.subChangeOption)”

If subscription options change. In addition to the standard parameters, the JSON array bookedChanges is passed here instead of bookedOptions. The bookedChanges array contains the fields action (ADD, REMOVE, UPDATE), quantity and, for updates, also oldQuantity for each option.

3.3. Product change ordered (subscription.productChangeOrderEntry) & confirmed (subscription.productChangeConfirmation)

Section titled “3.3. Product change ordered (subscription.productChangeOrderEntry) & confirmed (subscription.productChangeConfirmation)”

If a customer e.g. B. an upgrade or downgrade to another product is ordered or confirmed.

Specific parametersDescriptionData typeExample
sourceProductNameName of the old productstringAcme CRM
targetProductNameName of the new productstringAcme CRM Plus
sourceSubValidFromStart of the old subscriptiontimestamp2023-01-01T00:00:00Z
targetSubValidFromStart of the new subscriptiontimestamp2023-01-01T00:00:00Z
productChangeFeeExchange feedecimal5.99
bookedOptionsJSON array of target product optionsstringSee JSON

3.4. Subscription canceled due to failed renewal (subscription.prolongCancelled)

Section titled “3.4. Subscription canceled due to failed renewal (subscription.prolongCancelled)”
nameDescriptionData typeExample
productOptionNameListComma separated list of disabled optionsstringPriority Support, Storage
totalAmountOfFailedPaymentAmount of the failed paymentdecimal14.99
prolongationDateDate of failuretimestamp2025-07-01T00:00:00Z

3.5. Subscription paused (subscription.subPause) / Subscription pause ended (subscription.subUnpause)

Section titled “3.5. Subscription paused (subscription.subPause) / Subscription pause ended (subscription.subUnpause)”

Additional parameters: pausedFrom (start of pause) and pausedUntil (end of pause).

3.6. Subscription cancellation received (Deactivation.OrderEntry) & confirmed (Deactivation.Confirmation)

Section titled “3.6. Subscription cancellation received (Deactivation.OrderEntry) & confirmed (Deactivation.Confirmation)”

Additional parameters: scheduledForDeactivation (Planned Termination Date), actualCancellationDate or deactivationDate (Actual Execution Date).


Support configuration per TENANT.

4.1. Messages to the customer (Created / Updated)

Section titled “4.1. Messages to the customer (Created / Updated)”
  • helpdesk.ticket.create.notification
  • helpdesk.ticket.update.notification
nameDescriptionData typeExample
firstNameFirst name of the customer/contactstringMaximilian
lastNameCustomer/contact last namestringTailor
extTicketRefTicket reference numberstringHLT-719323
ticketTitleTitle/subject of the ticketstringServer is down
ticketDescriptionDescription of the ticketstringWe cannot reach the web…
tenantCompanyNameClient name of the ticketstringACME GmbH

4.2. Internal messages to the processor (assigneeName)

Section titled “4.2. Internal messages to the processor (assigneeName)”
  • helpdesk.ticket.create.notification.assignee
  • helpdesk.ticket.update.notification.assignee
  • helpdesk.ticket.dueDate.notification (Reminder)
nameDescriptionData typeExample
assigneeNameName of the processor or support groupstringSupport Team Berlin
ticketTitleTitle of the ticketstringServer is down
extTicketRefTicket reference numberstringHLT-719323
affectedEntityNameName of the affected entity (e.g. customer)stringACME GmbH

5.1. Status change to active (salespartner.StatusChange.ValidationToActive)

Section titled “5.1. Status change to active (salespartner.StatusChange.ValidationToActive)”

Sent to the reseller contact when the partner is successfully activated. Configuration per TENANT.

nameDescriptionData typeExample
contactFirstNameRecipient’s first namestringMaximilian
contactLastNameRecipient’s last namestringTailor
companyNameCompany of the sales partnerstringACME GmbH
newStatusNew statusstringACTIVE

These events cover the eCommerce and shopping cart process. Configuration per PRODUCT.

6.1. New subscription ordered (order.newSubscription.*)

Section titled “6.1. New subscription ordered (order.newSubscription.*)”

Status events: .ordered, .approved, .fulfilled, .unsuccessful

nameDescriptionData typeExample
firstName / lastNameCustomer namestringMaximilian Schneider
productNameName of the subscription orderedstringAcme CRM
extOrderRefOrder numberstringORD-202506
productSetupChargeSetup feedecimal16.79
productRecurringChargeRecurring feedecimal16.79
shippingMethodShipping method (if physical)stringREGULAR_SHIPPING
shippingTrackingUrlsJSON array of tracking linksstring["https://dhl..."]
bookedOptionsJSON array of subscription optionsstringSee JSON
discountsJSON array of applied discountsstring[{"name": {"de":"3%"},...}]
shippingAddressJSON object of the delivery addressstringSee JSON
billingAddressBilling address JSON objectstringSee JSON
cancellationReason(Only for .unsuccessful) Reason for cancellationstringUpon customer request

6.2. Subscription change ordered (order.changeSubscription.*)

Section titled “6.2. Subscription change ordered (order.changeSubscription.*)”

Status events: .ordered, .approved, .fulfilled, .unsuccessful Parameters are identical to the new subscription order, but also contain targetProductName, targetProductDescription and the array bookedChanges (which options were added, removed or changed, including oldQuantity vs. quantity).

Status events: .ordered, .fulfilled, .unsuccessful

nameDescriptionData typeExample
sumOneTimeChargeTotal amount of the orderdecimal13.99
requestForPaymentJSON object with transfer data (IBAN, BIC) for advance paymentstringSee JSON
orderContentJSON object of the entire shopping cartstringSee JSON
modifiedTotalOrderChargesJSON object of total amounts including and excluding taxesstringSee JSON
shippingChargesShipping cost JSON objectstring{"amountInclTax":"5.99"}

[!IMPORTANT] The orderContent JSON contains the complete shopping cart including all goodsVariants (items), prices, discounts and images (media). This object is suitable for building invoice/order lines in the template using a loop.


7.1. Packaging notification for external logistics (order.shipping.external.notify.logistics)

Section titled “7.1. Packaging notification for external logistics (order.shipping.external.notify.logistics)”

Sent when a shipping order is created for an external logistics partner. Configuration per TENANT.

nameDescriptionData typeExample
shippingMethodShipping methodstringREGULAR_SHIPPING
shippingIdShipping IDstringSHIP-12345
extOrderRefOrder numberstring10000002
recipientJSON object of the recipientstring{"firstName":"John",...}
shippingAddressJSON object of the delivery addressstringSee JSON
itemsJSON array of items to packagestring[{"name":"Pullover","quantity":2}]

[!TIP] The items array provides a compact list of physical items that the logistician must place in the package. Ideal for creating a delivery note.