← Back

ZUGFeRD to UBL 2.1

Learn how to transform your German ZUGFeRD hybrid PDF invoices into Universal Business Language format for international business transactions and ERP system integration.

Understanding ZUGFeRD Format

ZUGFeRD (Zentraler User Guide des Forums elektronische Rechnung Deutschland) is the German electronic invoice standard. It is a hybrid format that combines a human-readable PDF with an embedded CII XML file (zugferd-invoice.xml). It is technically identical to Factur-X 1.x and compliant with EN 16931.

Key characteristics of ZUGFeRD:

• Hybrid format: PDF for human reading + CII XML for machine processing
• Based on UN/CEFACT CII (Cross Industry Invoice) syntax
• Compliant with European standard EN 16931
• Multiple profiles: MINIMUM, BASIC WL, BASIC, EN16931, EXTENDED
• The embedded XML file is named zugferd-invoice.xml
• Recommended for German B2B transactions

ZUGFeRD Structure Example

ZUGFeRD uses the UN/CEFACT CII syntax inside the embedded XML. Below is how a supplier is defined:

          <ram:SellerTradeParty>
            <ram:Name>Mustermann GmbH</ram:Name>
            <ram:SpecifiedLegalOrganization>
              <ram:ID schemeID="0088">4012345678901</ram:ID>
            </ram:SpecifiedLegalOrganization>
            <ram:PostalTradeAddress>
              <ram:PostcodeCode>10115</ram:PostcodeCode>
              <ram:LineOne>Musterstrasse 1</ram:LineOne>
              <ram:CityName>Berlin</ram:CityName>
              <ram:CountryID>DE</ram:CountryID>
            </ram:PostalTradeAddress>
            <ram:SpecifiedTaxRegistration>
              <ram:ID schemeID="VA">DE123456789</ram:ID>
            </ram:SpecifiedTaxRegistration>
          </ram:SellerTradeParty>

Understanding UBL 2.1 Format

UBL (Universal Business Language) is an international XML standard for electronic business documents. It is widely used in cross-border transactions and is the foundation for many e-invoicing systems, including the Peppol network.

Key characteristics of UBL 2.1:

• International ISO standard (ISO/IEC 19845)
• Flexible structure supporting various document types
• Widely adopted in global e-invoicing and Peppol
• Compatible with international ERP and accounting systems
• Supports complex business rules and validations
• Extensible for custom requirements

UBL 2.1 Structure Example

UBL uses a different XML structure. The same supplier information in UBL format:

          <cac:AccountingSupplierParty>
            <cac:Party>
              <cac:PartyName>
                <cbc:Name>Mustermann GmbH</cbc:Name>
              </cac:PartyName>
              <cac:PartyLegalEntity>
                <cbc:CompanyID schemeID="0088">4012345678901</cbc:CompanyID>
              </cac:PartyLegalEntity>
              <cac:PostalAddress>
                <cbc:StreetName>Musterstrasse 1</cbc:StreetName>
                <cbc:CityName>Berlin</cbc:CityName>
                <cbc:PostalZone>10115</cbc:PostalZone>
                <cac:Country>
                  <cbc:IdentificationCode>DE</cbc:IdentificationCode>
                </cac:Country>  
              </cac:PostalAddress>
              <cac:PartyTaxScheme>
                <cbc:CompanyID>DE123456789</cbc:CompanyID>
                <cac:TaxScheme>
                  <cbc:ID>VAT</cbc:ID>
                </cac:TaxScheme>
              </cac:PartyTaxScheme>
            </cac:Party>
          </cac:AccountingSupplierParty>

Why Convert ZUGFeRD to UBL 2.1?

Converting from ZUGFeRD to UBL is essential for:

• International business: Sending invoices to partners outside Germany who require pure XML
• Peppol network: Submitting invoices through the Peppol e-delivery network requires UBL
• Global ERP systems: Many international ERPs natively consume UBL over hybrid PDF formats
• Multi-country operations: Companies with presence outside the DACH region
• System compatibility: Working with global trading platforms and e-procurement portals

Conversion Process

Converting your ZUGFeRD to UBL 2.1 is simple and fast:

Step 1: Upload Your Invoice

Upload your ZUGFeRD PDF file. The system automatically reads the embedded data.

Step 2: Automatic Processing

Our tool validates and converts the invoice data directly into the UBL standard, handling all field mappings and structure transformations behind the scenes.

Step 3: Download Ready-to-Use File

You receive a properly formatted UBL 2.1 XML file ready for international business transactions, Peppol submission, and ERP integration.

Common Conversion Issues

Be aware of these challenges when converting ZUGFeRD to UBL:

1. Hybrid Format Complexity

ZUGFeRD's hybrid nature presents unique challenges:

• The PDF must contain a valid zugferd-invoice.xml embedded attachment
• Visual PDF elements are discarded — only the embedded XML is used
• Processing time is higher than plain XML conversions due to PDF parsing
• Corrupted or encrypted PDFs cannot be processed

2. Format Differences

3. Field Mapping

Best Practices for Conversion

1. File Preparation

• Ensure the ZUGFeRD PDF contains a valid embedded XML attachment
• Use at least a BASIC profile ZUGFeRD to ensure full data extraction
• Verify the embedded XML is not corrupted before conversion
• Check that all required invoice fields are present

2. Testing

• Test with sample invoices from your German business
• Validate the resulting UBL against the official UBL 2.1 schema
• Check compatibility with target international systems and Peppol validators
• Verify international formatting compliance

3. Documentation

• Keep conversion logs for audit purposes
• Document any special handling requirements
• Maintain mapping tables for consistency
• Store validation rules and exceptions