Melasoft GmbH, Frankfurt am Main
For most finance teams, the move to digital invoicing started with a small and sensible step: stop printing, attach a PDF, send the email. The invoice arrives in seconds, it costs nothing to send, and it looks exactly like the paper document it replaced. That last point is precisely the problem. Under the European standard EN 16931 and the national mandates now rolling out across the continent, a PDF is a picture of an invoice rather than an invoice. The real question behind PDF vs e-invoicing is not file size or convenience, it is whether the data inside the document can be read by a machine. Below is what that means in practice, and what to ask a vendor before you sign.
Why a PDF Is Not an Electronic Invoice
A PDF is designed for human eyes. It fixes text into a layout so the document looks identical everywhere, but it carries no reliable structure underneath. Nothing in the file tells a receiving system which number is the net amount, which is the VAT rate, and which is the buyer reference. A machine readable invoice does exactly that: every field is labelled, typed and validated against a schema before the document leaves the sender.
The cost of the gap shows up in accounts payable. Someone re-keys the header, someone else chases a missing purchase order number, and the errors surface weeks later during the VAT return. There is one honourable exception. Hybrid electronic invoice formats such as Factur-X in France and ZUGFeRD in Germany embed an XML file inside a PDF/A-3 container, so the recipient can read either version. That is a useful bridge for suppliers who are not ready to go fully structured, but it pays to be clear about what actually makes it compliant: the XML, not the PDF wrapper.
The XML Layer: One Standard, Many Dialects
XML e-invoicing is the technical foundation of almost every European mandate, yet there is no single file that satisfies all of them. EN 16931 defines a semantic data model with two permitted syntaxes, UBL 2.1 and UN/CEFACT CII, and each member state then layers its own rules on top. A group selling across Europe will typically meet the following:
| Market | Required format | Typical channel |
|---|---|---|
| Germany | XRechnung, ZUGFeRD (hybrid PDF/A-3 plus XML) | Peppol, e-mail |
| France | Factur-X, UBL, CII | Approved platform to DGFiP |
| Italy | FatturaPA | SdI clearance |
| Poland | Structured XML defined by KSeF | KSeF |
| Belgium | Peppol BIS Billing 3.0 | Peppol |
| Slovakia | UBL and CII under EN 16931 | National exchange from 2027 |
Support for “XML” in the abstract therefore means very little. Structured invoice compliance means named formats, at specific versions, kept current as those versions change. Docnova supports XRechnung, ZUGFeRD, UBL, Peppol BIS and FatturaPA alongside other government mandated formats, and Melasoft operates as an accredited Peppol Access Point, so the exchange channel and the format library sit inside one platform rather than two contracts.
What Structured Data Actually Buys You
Compliance is the trigger for most projects, but structured e-invoicing data is where the return sits. Because every field is typed, an invoice can be validated before dispatch rather than rejected after it. Docnova runs those checks in real time, which is the difference between a validation failure you correct in the cockpit and one your customer or a tax authority reports back to you.
Downstream the benefits compound. The buyer system can post the document without manual intervention, so payment cycles shorten. The same data set feeds VAT returns, e-reporting and SAF-T extracts without a second collection exercise. And the archive becomes queryable, which means an audit question is answered with a filter instead of by opening three hundred PDFs.
Invoice Format Conversion: The Function Everyone Underestimates
This is the part most evaluations skip past. Your ERP produces one output. SAP may emit an IDoc or its own XML, while Oracle, Dynamics or a bespoke system will emit something else entirely. Twelve markets will each want something different. Invoice format conversion is therefore the engine of any serious platform: map once from the source system, transform into each target format, and absorb schema changes as they arrive.
The inbound direction deserves equal weight. Supplier documents will keep arriving as PDFs, scans and portal downloads for years, so digital invoice data extraction and AP automation belong in the same solution as your outbound flow. Otherwise you automate accounts receivable and leave accounts payable doing the typing. One blunt question separates vendors here: who maintains the mappings when a format version changes, and is that work inside the licence or billed per change?
Integration Is Part of Format Support
Invoice XML integration should never mean a project team writing XML by hand. Three patterns cover almost every requirement, and most groups need more than one:
- The Melasoft SAP Add-On keeps the entire process inside SAP ECC or S/4HANA, so users stay in familiar transactions.
- An API-first setup suits Oracle, Microsoft Dynamics and custom ERPs, connecting the platform directly to the system that already holds the data.
- A web portal covers low volume entities and edge cases, with Docnova Global for multi-country operations and Docnova France for the French reform.
What matters is that all three draw on the same format library and the same compliance updates. Without that, a group ends up running three separate compliance stacks and paying to maintain each one.
A Checklist for Evaluating E-Invoicing Format Support
- Which named formats and versions are supported today, country by country?
- Are hybrid formats such as Factur-X and ZUGFeRD handled, and is the embedded XML validated?
- Is Peppol access provided directly or subcontracted to a third party?
- Who maintains the mappings and schema updates, and is that included in the licence?
- Can inbound and outbound documents run on one platform?
- What happens when a country you already operate in announces a new mandate?
- Are the security and data protection credentials in place, such as ISO 27001 certification and GDPR compliance?
Conclusion
E-invoicing format support is not a feature list you tick once at signature. It is a maintenance commitment stretching across the next decade of European mandates, and the vendors worth shortlisting are the ones who treat it that way. Melasoft covers more than 30 markets through the Docnova platform, with SAP Add-On, API, Peppol and EDI connectivity, and inbound and outbound flows on the same compliance engine.
Send us the countries you invoice into and we will map your current formats against what each market will require. Book a short technical call at docnova.ai and we will take it from there.