E-INVOICING & INVOICE INTEROPERABILITY
UBL, ebInterface and Practical Electronic Invoice Integration
Electronic Invoicing in Practice
Electronic invoicing is more than producing an XML file. Business systems need to exchange invoice data reliably while preserving the meaning of parties, line items, taxes, totals, payment information and references across different formats and implementations.
join.tech provides engineering around electronic invoice integrations, format analysis, validation, conversion and interoperability, with a focus on understanding the underlying invoice semantics rather than treating XML as an opaque document format.
Invoice Formats & Semantics
Different electronic invoice formats often describe the same commercial concepts using different XML structures. Reliable integration therefore starts with the business meaning of an invoice, not only its syntax.
Current work includes:
- UBL 2.1: parsing, generation and mapping of structured invoice data.
- ebInterface 6.1: support for the Austrian electronic invoice format.
- EN 16931: semantic invoice concepts and selected business-rule validation.
- Canonical Modelling: separating invoice semantics from format-specific XML structures.
A semantic model is particularly useful where invoices need to move between accounting systems, formats or integration boundaries without silently losing relevant information.
Integration & Engineering
In practice, e-invoicing quickly becomes a systems-integration problem. Invoice data may originate in an ERP, billing application, project-management system or custom backend and then need to be transformed for customers, accounting platforms or external interfaces.
Typical engineering work includes:
- analysis of existing invoice and accounting interfaces
- mapping between internal invoice models and external formats
- UBL and ebInterface integration
- invoice validation and diagnostic tooling
- automated invoice generation and processing workflows
- conversion between structured invoice formats
- semantic round-trip and integration testing
- investigation of interoperability problems between systems
invx: Open-Source E-Invoicing Toolkit
As part of this work, join.tech develops invx, an open-source Rust toolkit and command-line application for working with structured electronic invoices.
invx reads supported invoice formats into a common canonical model. Validation, conversion and comparison then operate on invoice semantics rather than directly on format-specific XML.
Current functionality includes:
- Inspect: display invoice content in a readable form.
- Validate: check canonical consistency and selected EN 16931 business rules.
- Convert: convert between supported invoice formats with explicit diagnostics.
- Compare: compare invoices by business meaning rather than raw XML.
- Canonical JSON: expose normalized invoice data for integration and analysis.
Why Semantic Comparison Matters
Two invoice documents can represent the same business information while looking very different at XML level. Element names, optional fields and format-specific representations can vary even where the commercial meaning remains unchanged.
Comparing XML directly therefore tends to mix syntactic differences with meaningful invoice differences. invx instead maps supported formats into a common invoice model before comparison.
This is useful for format conversions, migration projects and automated integration tests where the important question is whether invoice meaning has been preserved.
Preserving Information During Conversion
Invoice formats do not always have a one-to-one mapping. A concept available in one format may be restricted, represented differently or unavailable in another.
invx therefore performs conversion diagnostics before writing the target document. Potential problems are classified according to whether conversion is unsafe, potentially lossy or merely changes the representation without changing business meaning.
The guiding principle is simple: meaningful invoice information should not disappear silently during conversion.
Used in Practice
join.tech also uses the technology in its own invoice workflow. Invoice data can be used to produce the conventional PDF document together with machine-readable UBL and ebInterface representations.
This provides a familiar human-readable invoice while making the same invoice information available for structured electronic processing.
Current Scope
invx is under active development. Support for UBL 2.1, ebInterface 6.1 and EN 16931 currently covers a practical subset and should not be interpreted as a claim of complete standards conformance or official certification.
The project deliberately favors explicit errors and diagnostics over silently discarding invoice information when a concept cannot be represented safely.
Typical Engagements
- electronic invoice integration
- UBL and ebInterface implementation
- invoice format and mapping analysis
- invoice conversion and migration tooling
- validation and diagnostic tooling
- accounting and billing-system integration
- semantic integration and round-trip testing
- interoperability analysis and troubleshooting
Contact
For electronic invoicing, invoice interoperability or related integration work: