File Formats

xTool supports various electronic invoice file formats that comply with international standards for electronic invoicing. These formats ensure compatibility with different business systems and regulatory requirements across various countries and regions.

Supported File Formats

xTool supports the following electronic invoice file formats:

XRechnung 3.0 UBL - German electronic invoice standard based on UBL (Universal Business Language) syntax, compliant with EN 16931 and the German XRechnung specification. This format is widely used in Germany for B2G (Business-to-Government) transactions and provides comprehensive invoice data structure.

XRechnung 3.0 UBL Extension - Extended version of XRechnung 3.0 UBL that includes additional custom fields and extensions beyond the standard specification. This format allows for enhanced data capture while maintaining compliance with the base XRechnung standard.

XRechnung 3.0 UBL Credit Note - Credit note variant of XRechnung 3.0 UBL format, specifically designed for processing credit notes and refunds in compliance with German electronic invoicing standards.

XRechnung 3.0 CII - German electronic invoice standard based on CII (Cross Industry Invoice) syntax, providing an alternative to UBL-based formats while maintaining full compliance with EN 16931 and XRechnung specifications.

PEPPOL BIS 3.0 UBL - International electronic invoice format based on PEPPOL (Pan-European Public Procurement OnLine) BIS (Business Interoperability Specifications) using UBL syntax. This format enables cross-border electronic invoicing across Europe and other PEPPOL network countries.

PEPPOL BIS 3.0 UBL Credit Note - Credit note variant of PEPPOL BIS 3.0 UBL format, designed for international credit note processing within the PEPPOL network.

Format Validation and Processing

All supported file formats undergo comprehensive validation using XSD (XML Schema Definition) and XSLT (Extensible Stylesheet Language Transformations) validation processes. This ensures that only compliant and properly structured documents are processed by the system, maintaining data integrity and regulatory compliance.

JSON Representation

While xTool supports working with raw XML data for all electronic invoice formats, we also provide JSON representations to simplify integration and make the data more universally accessible. The JSON structure serves as a standardized way to work with invoice data across different formats.

Unified Data Model

All supported file formats share approximately 90% of their data structure, with the remaining 10% containing format-specific variations. This common foundation includes core invoice elements such as seller and buyer information, invoice details, line items, tax calculations, and totals. The shared structure ensures consistent data handling across different electronic invoice standards.

Format-Specific Variations

Each file format has its own JSON model that extends the base structure with format-specific fields and requirements. For example, XRechnung 3.0 UBL Extension includes additional fields like prepaid_payment and sub_items that are not present in standard PEPPOL BIS 3.0 UBL format. These variations accommodate the specific business rules and regulatory requirements of each standard.

Data Validation and Business Rules

It's important to understand that having a correctly structured JSON does not guarantee that the resulting invoice will be valid. Each format has complex business rules and validation requirements that go beyond structural validation. For instance, XRechnung formats require mandatory contact information, while PEPPOL formats have specific identifier scheme requirements. Additionally, all numeric data (sums, tax amounts, percentages) must be properly formatted and calculated according to the specific format's rules.

Field Relationships and Dependencies

Different formats have varying requirements for field relationships and dependencies. For example, in XRechnung formats, contact data is mandatory and must be present in the JSON structure, while other formats may have different mandatory field requirements. These relationships ensure compliance with the specific business rules of each electronic invoice standard.