← Indietro

CII to UBL 2.1

Learn how to transform your Cross Industry Invoice format (CII) into Universal Business Language format for international business transactions.

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. Below is an example of how a supplier is defined in CII format:

<ram:SellerTradeParty>
  <ram:Name>European Company GmbH</ram:Name>
  <ram:SpecifiedLegalOrganization>
    <ram:ID schemeID="0002">12345678900012</ram:ID>
  </ram:SpecifiedLegalOrganization>
  <ram:PostalTradeAddress>
    <ram:PostcodeCode>10115</ram:PostcodeCode>
    <ram:LineOne>Friedrichstraße 123</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'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. The same supplier information in UBL format:

<cac:AccountingSupplierParty>
  <cbc:CustomerAssignedAccountID>CUST123</cbc:CustomerAssignedAccountID>
  <cac:Party>
    <cac:PartyName>
      <cbc:Name>European Company GmbH</cbc:Name>
    </cac:PartyName>
    <cac:PartyLegalEntity>
      <cbc:CompanyID schemeID="0002">12345678900012</cbc:CompanyID>
    </cac:PartyLegalEntity>
    <cac:PostalAddress>
      <cbc:StreetName>Friedrichstraße 123</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 CII to UBL 2.1?

Converting between these formats is essential for:

• International business: Selling to customers outside your country
• Global systems: Integration with international ERP systems
• Peppol compliance: Meeting international e-invoicing standards
• Business expansion: Expanding to other markets
• System compatibility: Working with global trading partners

Conversion Process

Converting your CII to UBL 2.1 involves these key steps:

Step 1: Upload Your Invoice

Simply upload your CII XML file. The system automatically reads all the structured European invoice data.

Step 2: Format Transformation

Our converter transforms European CII to international UBL standard:

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

Step 3: International Compliance

The converted UBL file meets international requirements:

• Follows ISO/IEC 19845 standard specifications
• Compatible with Peppol and other global networks
• Supports international VAT and tax handling
• Includes proper currency and country codes
• Validates against UBL 2.1 schema requirements

Step 4: Quality Validation

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

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

Step 5: Download Ready-to-Use File

You receive a properly formatted UBL 2.1 file ready for international business transactions and system integration.

Common Conversion Issues

Be aware of these challenges when converting CII to UBL:

1. Structural Differences

The formats have different XML structures and element names:

2. Tax System Differences

European and international tax systems have different requirements:

3. Address Format Conversion

European addresses need to be converted to international format:

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

Best Practices for Conversion

Follow these guidelines for successful conversion:

1. Preparation

• Validate CII file before conversion
• Check all European 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 UBL 2.1 schema requirements
• Check compatibility with target international systems
• 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

Benefits of UBL Conversion

Converting to UBL 2.1 format offers several advantages:

For International Business

• Global compatibility with trading partners
• Compliance with international e-invoicing standards
• Integration with global ERP and accounting systems
• Support for multi-language and multi-currency transactions
• Enhanced automation capabilities

For System Integration

• Standardized international format for system integration
• Better compatibility with international partners
• Reduced integration costs and complexity
• Improved data exchange capabilities
• Future-proof format for business growth