E-Invoicing Standard
What Is UBL?
Universal Business Language (UBL) is an OASIS open standard that defines XML schemas for structured business documents. It is the foundation of Peppol invoicing, a core syntax of EN 16931, and the most widely adopted format for compliant e-invoicing worldwide.
What is UBL (Universal Business Language)?
UBL (Universal Business Language) is an OASIS open standard that defines a library of XML document schemas for business transactions, including invoices, credit notes, orders, and despatch advices. UBL provides a vendor-neutral, royalty-free framework that enables structured, machine-readable exchange of business documents across systems, industries, and borders.
How UBL Works
UBL defines business documents as XML files that follow strict schema definitions. Each document type has its own XML Schema Definition (XSD) that specifies the allowed elements, their data types, cardinality, and nesting structure. When a system generates a UBL document, it populates the XML elements according to the schema rules.
Every UBL document uses a defined namespace that identifies the version and document type. For example, a UBL 2.1 Invoice uses the namespace urn:oasis:names:specification:ubl:schema:xsd:Invoice-2. Namespaces prevent element name collisions and allow receiving systems to identify exactly which schema version to validate against.
Validation happens in two layers. First, XSD validation confirms that the document structure is correct: required elements are present, data types are valid, and the nesting is well-formed. Second, Schematron validation applies business rules that cannot be expressed in XSD alone, such as conditional requirements (if field A is present, field B must also be present) and cross-field calculations (line totals must sum to the invoice total).
UBL also supports an extension mechanism called UBL Extensions, which allows jurisdictions and trading communities to add custom data elements without modifying the core schema. Extensions are placed in a designated area of the XML structure, preserving backward compatibility with systems that do not recognize the custom elements.
UBL Document Types
UBL defines over 65 document types. The following are the most widely used in e-invoicing and procurement workflows.
Invoice
The primary document for billing. Contains supplier and buyer information, line items, tax breakdowns, payment terms, and totals. The UBL Invoice is the most widely used document type in e-invoicing mandates.
Credit Note
Used to correct or cancel a previously issued invoice. References the original invoice and specifies the adjustment amount, reason for credit, and updated tax calculations.
Order
A purchase order sent from buyer to supplier specifying the goods or services requested, quantities, agreed prices, and delivery requirements.
Order Response
The supplier's response to an order, confirming acceptance, rejection, or modification of the order terms. Supports line-level acceptance and substitution scenarios.
Despatch Advice
A shipping notification sent from supplier to buyer confirming that goods have been despatched. Includes shipment details, carrier information, and line-level quantities shipped.
Application Response
A general-purpose acknowledgement document used to confirm receipt of another UBL document or to report processing errors. Used extensively in Peppol for message-level response handling.
UBL Versions
UBL has evolved through four major releases, each expanding the document library and refining the schema architecture.
UBL 2.0
The initial widely adopted release. Established the core document library and XML schema architecture. Introduced the foundational invoice, order, and despatch advice schemas.
UBL 2.1
The most widely adopted version. Added new document types, improved extension mechanisms, and refined the schema structure. UBL 2.1 is the basis for Peppol BIS Billing 3.0 and the EN 16931 UBL syntax binding.
UBL 2.2
Added document types for transport and logistics, including Waybill, Transport Execution Plan, and Freight Invoice. Expanded support for supply chain use cases beyond procurement and billing.
UBL 2.3
The latest release. Added document types for digital agreements, export customs, and proof of re-export. Introduced improvements to signature handling and added support for additional business scenarios.
UBL vs CII (Cross Industry Invoice)
UBL and CII are both XML-based formats for representing business documents, and both are recognized syntax bindings under the European standard EN 16931. They serve similar purposes but originate from different standards bodies and use different XML structures.
UBL is maintained by OASIS (Organization for the Advancement of Structured Information Standards). CII is maintained by UN/CEFACT (United Nations Centre for Trade Facilitation and Electronic Business). Both are open standards, but they use different element names, namespaces, and structural conventions.
UBL (OASIS)
- •Maintained by OASIS Technical Committee
- •Used by Peppol BIS Billing 3.0
- •Covers 65+ document types beyond invoicing
- •Separate schemas per document type
- •Wider adoption in public sector e-invoicing
CII (UN/CEFACT)
- •Maintained by UN/CEFACT
- •Used by Factur-X and ZUGFeRD
- •Part of the broader Cross Industry family
- •Single schema with context-based customization
- •Strong adoption in Franco-German ecosystems
EN 16931 supports both syntaxes equally. The choice between UBL and CII typically depends on the trading network, country requirements, or the receiving system's capabilities.
UBL vs Factur-X
UBL and Factur-X represent two different approaches to e-invoicing. UBL is a pure XML format where all invoice data is contained in a structured XML file. Factur-X is a hybrid format that embeds a CII-based XML file inside a PDF/A-3 document, combining human-readable and machine-readable representations in a single file.
UBL is designed for system-to-system exchange where both sender and receiver can process structured XML directly. Factur-X is designed for scenarios where the receiver may not have automated processing capabilities, allowing them to view the PDF while systems that can process XML extract the embedded data.
From a schema perspective, UBL uses OASIS-defined schemas while Factur-X uses UN/CEFACT CII schemas. The two formats are not interchangeable without conversion, but they can represent the same business data. In jurisdictions like France, where both Factur-X and Peppol (UBL) are relevant, businesses may need to support both formats depending on their trading partners.
UBL in Peppol
Peppol BIS Billing 3.0 is the invoicing specification used across the Peppol network, and it is built on UBL 2.1. Every invoice exchanged through Peppol is a UBL 2.1 Invoice or Credit Note document that conforms to additional Peppol-specific rules.
Peppol constrains UBL through a Core Invoice Usage Specification (CIUS). The CIUS defines which UBL fields are mandatory, which are optional, which are restricted, and which business rules must be satisfied. For example, Peppol requires specific identifier schemes for buyer and seller identification, mandates certain tax category codes, and enforces calculation rules that go beyond what the base UBL schema requires.
This means that every valid Peppol invoice is a valid UBL 2.1 document, but the reverse is not true. A UBL 2.1 invoice that omits Peppol-required fields or uses unsupported code values will be rejected by Peppol access points during schema and business rule validation.
UBL in EN 16931
EN 16931 is the European standard for the semantic data model of a core electronic invoice. It defines what information an e-invoice must contain, but it does not prescribe a single technical format. Instead, EN 16931 specifies two official syntax bindings: UBL 2.1 and UN/CEFACT CII.
The UBL syntax binding maps each semantic element defined in EN 16931 to a specific UBL 2.1 XML path. For example, the semantic element "Invoice number" maps to the UBL element cbc:ID within the Invoice root element. This mapping ensures that any system generating an EN 16931-compliant UBL invoice places the correct data in the correct XML location.
EU Directive 2014/55/EU requires all public sector contracting authorities in the EU to accept e-invoices that conform to EN 16931. Since UBL is one of the two supported syntaxes, any supplier sending e-invoices to EU public sector buyers can use UBL to meet this requirement.
Where UBL Is Mandated
UBL is required or strongly preferred in several regulatory and network contexts worldwide.
Peppol Network (40+ Countries)
All invoices exchanged through the Peppol network must use UBL 2.1 as defined by Peppol BIS Billing 3.0. This applies to all Peppol-connected organizations across Europe, Asia-Pacific, and other participating regions.
EU Public Procurement (Directive 2014/55/EU)
EU member states are required to ensure that public sector contracting authorities accept e-invoices in EN 16931 format. UBL 2.1 is one of the two accepted syntax bindings, making it a valid format for B2G invoicing across all EU countries.
Nordic Countries
Denmark, Norway, Sweden, and Finland were early adopters of UBL-based e-invoicing. These countries have long-standing mandates for structured e-invoicing in public procurement, and UBL is the dominant format in these markets.
Australia and New Zealand
Both countries have adopted the Peppol framework for e-invoicing, with UBL 2.1 as the required document format. The Australian Taxation Office and New Zealand government actively promote Peppol-based e-invoicing for public sector transactions.
Who Uses UBL
ERP Vendors
Major ERP systems including SAP, Oracle, and Microsoft Dynamics support UBL invoice generation and consumption. UBL compatibility is a standard requirement for ERP modules that handle e-invoicing in Peppol-connected markets.
Access Point Providers
Peppol access points process UBL documents as their core function. These providers validate, route, and deliver UBL invoices and credit notes between trading partners on the Peppol network.
Public Sector Organizations
Government agencies and public sector bodies across the EU, Australia, New Zealand, and Singapore receive and process UBL invoices from their suppliers as part of e-procurement mandates.
Large Enterprises
Multinational corporations that trade across borders use UBL to standardize invoice exchange with suppliers and buyers in multiple countries, reducing format fragmentation and integration costs.
Common Misconceptions
Myth: UBL is only for invoices
Reality: UBL defines over 65 document types covering the full procurement cycle, including orders, order responses, despatch advices, receipts, catalogues, and transport documents. Invoicing is the most visible use case, but UBL is a comprehensive business document framework.
Myth: UBL and Peppol are the same thing
Reality: UBL is a document format standard maintained by OASIS. Peppol is a network and set of specifications for exchanging business documents. Peppol uses UBL 2.1 as its invoice format, but Peppol also defines network protocols, access point requirements, and business rules that exist independently of UBL.
Myth: UBL is too complex for small businesses
Reality: While the full UBL schema library is extensive, most implementations use only the Invoice and Credit Note document types with a constrained set of fields defined by a CIUS such as Peppol BIS. The complexity is managed by the software, not by the end user.
Myth: UBL requires proprietary software
Reality: UBL is an open, royalty-free standard. The schemas are publicly available from OASIS at no cost. Open-source libraries exist in multiple programming languages for generating, parsing, and validating UBL documents. No vendor lock-in is required.
How AutoFact AI Supports UBL
AutoFact AI is designed to support businesses and their advisors in working with UBL-based documents across compliance workflows.
UBL Document Extraction
Parses UBL 2.1 and 2.3 invoices, credit notes, and other document types, extracting structured data from XML elements into normalized fields for downstream processing and analysis.
Schema Validation
Validates UBL documents against XSD schemas and Schematron business rules, identifying structural errors, missing required fields, and invalid data values before documents are transmitted.
Peppol BIS Compliance Checking
Applies Peppol BIS Billing 3.0 validation rules on top of base UBL schema validation, ensuring documents meet the CIUS requirements for Peppol network transmission.
EN 16931 Syntax Alignment
Verifies that UBL documents align with EN 16931 semantic model requirements, checking that mandatory elements are present and correctly mapped to the European standard.
Regulatory Authority Mapping
UBL requirements are shaped by standards bodies and regulatory frameworks across multiple jurisdictions.
European Committee for Standardization (CEN)
European Union
- What they regulate: EN 16931 UBL syntax binding for the European e-invoicing standard.
- What AutoFact AI maps to: UBL document parsing and validation against EN 16931 semantic model requirements.
- What risk this removes: Non-compliant document structure that would be rejected by receiving systems or fail regulatory validation.
OpenPeppol
Peppol Network
- What they regulate: Peppol BIS Billing 3.0 (UBL 2.1) as the mandatory invoice format for the Peppol network.
- What AutoFact AI maps to: UBL invoice generation and validation against Peppol CIUS rules and business requirements.
- What risk this removes: Rejection at access point due to schema errors, missing mandatory fields, or invalid code values.
Direction generale des Finances publiques (DGFiP)
France
- What they regulate: French e-invoicing mandate format requirements, including support for UBL, CII, and Factur-X.
- What AutoFact AI maps to: UBL-to-CII conversion guidance and format compatibility checking for the French ecosystem.
- What risk this removes: Format incompatibility when exchanging documents between UBL-native and CII-native systems in the French market.
OASIS UBL Technical Committee
Standards Organization
- What they regulate: UBL 2.1/2.3 specification governance, schema definitions, and the official document type library.
- What AutoFact AI maps to: Schema version detection and compliance validation against official OASIS-published XSD and Schematron artifacts.
- What risk this removes: Use of deprecated or non-standard elements that could cause interoperability failures or validation rejection.
AutoFact AI is not certified by, affiliated with, or endorsed by any regulatory authority or standards body listed above. References describe technical alignment with published specifications and regulatory requirements only.
Frequently Asked Questions
UBL & E-Invoicing Standard Resources
Parse, Validate, and Ship UBL Documents with Confidence
AutoFact AI extracts structured data from UBL invoices, validates against XSD and Schematron rules, and checks Peppol BIS compliance before transmission. Start your free trial and eliminate schema errors before they reach your trading partners.
14-day free trial · No credit card required · Setup in minutes