Billance controls the output format for e-invoices through the e-invoice toggle and the format menu. On invoices and credit notes, you decide there whether the document should be generated as a hybrid PDF with XML, as a pure XML file, or intentionally PDF only. For recurring invoices, the setting applies to the invoices generated later.
Quick Guide: Which Format Should I Choose?
For most cases, four variants are enough:
- PDF + XML / ZUGFeRD EN16931 → standard for most B2B invoices
- XML Only / XRechnung → typical for German public authorities
- XML Only / PEPPOL BIS → for PEPPOL networks and matching portals
- PDF Only → when you intentionally work without structured XML
Output Types
PDF + XML (Hybrid)
This output type creates one PDF file with embedded XML. In other words, you get an invoice that is readable for humans and also processable by systems.
Billance currently offers these profiles for hybrid output:
- ZUGFeRD EN16931
- ZUGFeRD XRechnung
- ZUGFeRD Extended
For all hybrid profiles, Billance uses CII technically.
XML Only
This output type creates only an XML file without a visual PDF. It is intended for systems, portals, and automated processing.
Billance currently supports:
- XRechnung with CII or UBL
- EN16931 as CII
- PEPPOL BIS as UBL
PDF Only
If you switch off the e-invoice toggle, Billance generates only a normal PDF without structured XML. This case is explained in more detail in the separate help article PDF Only.
Which Profile Is Meant for What?
ZUGFeRD EN16931
This is the standard choice for hybrid B2B invoices. You get a readable PDF plus structured XML according to EN 16931.
ZUGFeRD XRechnung
Useful when you want to provide XRechnung-like structured data inside a hybrid file. You should confirm in advance whether the recipient accepts hybrid files.
ZUGFeRD Extended
Intended for special cases with additional optional data beyond the core model.
XRechnung
The typical choice for German public authorities. Depending on the recipient requirements, you can use CII or UBL.
EN16931
The European core model without additional PEPPOL- or XRechnung-specific rules. In Billance, this XML profile is currently available as CII.
PEPPOL BIS
The right choice when your recipient explicitly requires PEPPOL or expects delivery through a PEPPOL network. In Billance, this profile uses UBL.
CII vs. UBL — What Is the Difference?
Both are XML syntaxes for electronic invoices, but with different technical structures:
| | CII | UBL | |---|---|---| | Origin | UN/CEFACT | OASIS | | Typically used by | ZUGFeRD, XRechnung, EN16931 | XRechnung, PEPPOL BIS | | Typical usage | Hybrid invoices and many German e-invoicing processes | Platforms, portals, and PEPPOL |
What matters for you: The syntax does not change the business meaning of the invoice. It only changes the technical XML structure.
Frequently Asked Questions
Which format should I use for normal B2B invoices? In most cases, PDF + XML / ZUGFeRD EN16931 is the best choice.
When should I use XRechnung? Use it when your recipient explicitly requires XRechnung, typically in the German public sector.
When should I use PEPPOL BIS? Use it when your customer, contracting authority, or their system explicitly requires PEPPOL or expects delivery through a PEPPOL network.
Can I generate EN16931 as XML in UBL? Not currently. For pure XML, Billance offers EN16931 as CII. If you need UBL, use XRechnung or PEPPOL BIS, depending on the requirement.