Templates in ABOSS have been redesigned to support e-invoicing. The old PDF system remains available and fully functional, but new features have been added to enable XML output. This article explains the differences, why the change was needed, and what it means for your workflow.
Table of Contents
1. Old vs new template setup
2. Why the change was needed
3. The new dual-output structure
4. New template codes
5. What this means for your workflow
1. Old vs new template setup
The old template system in ABOSS was designed for PDF invoices. It was very flexible, allowing you to display almost any data field exactly where and how you wanted, giving you complete control over the look and branding of your invoices. This system remains in place today. If you do not need XML invoices, you can continue working with PDF templates as before.
What’s new is that templates can now also generate XML files alongside PDFs. This means that the same data used for your branded invoice is also available in a structured, machine-readable format. To make this possible, templates now rely on entities and new calculations that ensure compliant XML export.
2. Why the change was needed
Governments, clients, and accounting platforms increasingly require structured XML invoices that can be processed automatically. PDF invoices, no matter how flexible, cannot meet this demand. The new system ensures that ABOSS invoices are legally compliant, internationally accepted, and future-proof, while still offering the flexibility of custom templates.
3. The new dual-output structure
With the new setup, every invoice now produces two outputs:
PDF: A visual, human-readable invoice that reflects your branding and layout
XML: A structured, machine-readable file that ensures compliance and enables automation
Both outputs are generated from the same underlying data. This ensures that whatever entity you select for an invoice is displayed consistently in both the PDF and XML export.
4. New template codes
To make entities work inside templates, new template codes have been added. These codes display the details of the entity you select when creating an invoice.
Examples:
{{ entity.company_name }}→ Company name{{ entity.address }}→ Address{{ entity.vat_nr }}→ VAT number{{ entity.iban }}→ IBAN number{{ entity.bank_name }}→ Bank name
These codes replace the older {{ agency... }} codes when working with e-invoicing. However, the old codes will continue to work in your PDF templates. If you are not using XML invoices, you can keep your existing templates exactly as they are.
Thanks to the new entity codes, the selected entity is always shown correctly on both the PDF and XML.
If you need help working with these new codes, please check Workflow: from entities to templates to invoices or contact support.
5. What this means for your workflow
Your workflow remains familiar: you still design templates to match your branding. The key differences are:
You must always select an entity when creating an invoice
The chosen entity will be displayed consistently on both PDF and XML exports
If you don’t need XML, you can continue using PDF-only templates without making any changes
For practical steps on updating your templates and using entity codes, check the article: Workflow: from entities to templates to invoices.
Previous article: Entities: what they are and why they are required
Next article: Workflow: from entities to templates to invoices