← Indietro

UBL 2.1 to CII

Learn how to transform your Universal Business Language invoices (UBL 2.1) into Cross Industry Invoice format for European e-invoicing compliance.

Understanding UBL 2.1 Format

UBL (Universal Business Language) is an international XML standard for electronic business documents. It's 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
• Compatible with Peppol and other networks
• Supports complex business rules and validations
• Extensible for custom requirements

UBL 2.1 Structure Example

UBL uses a different XML structure. Below is an example of how a supplier is defined in UBL format:

<cac:AccountingSupplierParty>
  <cbc:CustomerAssignedAccountID>CUST123</cbc:CustomerAssignedAccountID>
  <cac:Party>
    <cac:PartyName>
      <cbc:Name>Global Company Ltd</cbc:Name>
    </cac:PartyName>
    <cac:PartyLegalEntity>
      <cbc:CompanyID schemeID="0002">12345678900012</cbc:CompanyID>
    </cac:PartyLegalEntity>
    <cac:PostalAddress>
      <cbc:StreetName>123 Business Street</cbc:StreetName>
      <cbc:CityName>New York</cbc:CityName>
      <cbc:PostalZone>10001</cbc:PostalZone>
      <cac:Country>
        <cbc:IdentificationCode>US</cbc:IdentificationCode>
      </cac:Country>
    </cac:PostalAddress>
    <cac:PartyTaxScheme>
      <cbc:CompanyID>US123456789</cbc:CompanyID>
      <cac:TaxScheme>
        <cbc:ID>VAT</cbc:ID>
      </cac:TaxScheme>
    </cac:PartyTaxScheme>
  </cac:Party>
</cac:AccountingSupplierParty>

Understanding CII Format

CII (Cross Industry Invoice) is a European standard for electronic invoicing that provides a common syntax for invoice data exchange. It's designed to be interoperable across different countries and systems while maintaining compliance with EN 16931.

Key characteristics of CII:

• European standard EN 16931 compliant
• Pure XML format without visual presentation
• Designed for cross-border European transactions
• Supports complex business rules and validations
• Widely adopted in European e-invoicing
• Compatible with various national extensions

CII Structure Example

CII uses the UN/CEFACT syntax. The same supplier information in CII format:

<ram:SellerTradeParty>
  <ram:Name>Global Company Ltd</ram:Name>
  <ram:SpecifiedLegalOrganization>
    <ram:ID schemeID="0002">12345678900012</ram:ID>
  </ram:SpecifiedLegalOrganization>
  <ram:PostalTradeAddress>
    <ram:PostcodeCode>10001</ram:PostcodeCode>
    <ram:LineOne>123 Business Street</ram:LineOne>
    <ram:CityName>New York</ram:CityName>
    <ram:CountryID>US</ram:CountryID>
  </ram:PostalTradeAddress>
  <ram:SpecifiedTaxRegistration>
    <ram:ID schemeID="VA">US123456789</ram:ID>
  </ram:SpecifiedTaxRegistration>
</ram:SellerTradeParty>

Why Convert UBL 2.1 to CII?

Converting between these formats is essential for:

• European compliance: Meeting EN 16931 standards for cross-border trade
• System integration: Working with European-wide e-invoicing systems
• Business expansion: Expanding to other European markets
• Standardization: Using interoperable European formats
• Future-proofing: Preparing for evolving e-invoicing requirements

Conversion Process

Converting your UBL 2.1 to CII involves these key steps:

Step 1: Upload Your Invoice

Simply upload your UBL 2.1 XML file. The system automatically reads all the structured international invoice data.

Step 2: Format Transformation

Our converter transforms international UBL to European CII standard:

• Maps UBL element names to CII standard elements
• Converts international tax categories to European codes
• Standardizes address formats for European use
• Adjusts date and number formats for international compliance
• Preserves all invoice data and calculations

Step 3: European Compliance

The converted CII file meets European requirements:

• Follows EN 16931 standard specifications
• Supports European VAT and tax handling
• Includes proper currency and country codes
• Validates against CII schema requirements
• Compatible with European e-invoicing networks

Step 4: Quality Validation

Before generating the final file, the system performs thorough checks:

• Validates XML structure against CII schema
• Ensures all required fields are present
• Checks business rules and calculations
• Verifies European formatting compliance
• Tests compatibility with receiving systems

Step 5: Download Ready-to-Use File

You receive a properly formatted CII file ready for European business transactions and system integration.

Common Conversion Issues

Be aware of these challenges when converting UBL 2.1 to CII:

1. Structural Differences

The formats have different XML structures and element names:

2. Tax System Differences

International and European tax systems have different requirements:

3. Address Format Conversion

International addresses need to be converted to European format:

• Province codes become part of address structure
• International postal codes integrate with European systems
• Country codes remain standard (ISO format)
• Street types follow European addressing standards
• Special characters are preserved according to EU standards

Best Practices for Conversion

Follow these guidelines for successful conversion:

1. Preparation

• Validate UBL 2.1 file before conversion
• Check all international tax codes and VAT numbers
• Ensure address formats are correct
• Verify payment terms and bank details

2. Testing

• Test with sample invoices from your business
• Validate against CII schema requirements
• Check compatibility with target European systems
• Verify European 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

Benefits of CII Conversion

Converting to CII format offers several advantages:

For European Business

• Compliance with EN 16931 standards
• Interoperability with European systems
• Support for cross-border transactions
• Enhanced automation capabilities
• Future-proof format for evolving requirements

For System Integration

• Standardized European format for integration
• Better compatibility with European partners
• Reduced integration costs and complexity
• Improved data exchange capabilities
• Support for multi-country operations