Peppol, Factur-X or XRechnung: Which E-Invoice Format? — AI Automation article by Rui Codex

Peppol is a network and set of specifications for sending invoices between business systems. Factur-X is a PDF with embedded structured XML, used mainly in French and cross-border trade. XRechnung is the German XML specification for invoicing German public bodies. Belgian buyers can be reached through Peppol, so the right format depends on each buyer and the systems they can receive.

Key takeaways

  • Peppol is a transport network with shared document rules, so it moves an invoice between systems rather than only defining a file layout.
  • Factur-X is a hybrid file that pairs a readable PDF with a machine-readable XML part, which suits both human review and automated processing.
  • XRechnung is a German-specific XML format, and it is the format used for invoicing German public-sector bodies.
  • The correct format depends on who you invoice and which channels their systems accept, so confirm this before building anything.

What is Peppol and when do you need it?

Peppol is an open network that routes electronic documents between businesses through access points, using shared specifications such as Peppol BIS Billing for invoices. You need it when a buyer's procurement process expects invoices through that network instead of by email or portal upload.

A supplier sends the invoice through its access point, which is a provider connected to the network, and the buyer receives it through its own access point. The network rules, participant identifiers and document specifications are published on the Peppol website, and that page is the reference to check before you design anything.

Peppol moves the document, but it does not make the invoice correct. A file can travel through the network without error and still be rejected by the buyer's internal checks, for example because a purchase order reference is missing or a tax field is mapped to the wrong element. Most of the real work is mapping your ERP fields to the mandatory elements of the specification.

Tip: Ask each buyer which Peppol document profile and participant identifier it uses before testing, because a mismatch there is easy to miss until live invoices start failing.

What is Factur-X and where is it used?

Factur-X is a hybrid invoice: a human-readable PDF with a structured XML file embedded inside it, so one document serves both a person and a processing system. It was developed by French and German bodies and aligns with the European standard for semantic invoice data. The project and its profiles are described on the Factur-X project site.

The PDF is usually generated from the accounting or invoicing system, with the XML attached to a PDF/A-3 file. Profiles range from minimal to the full EN 16931 profile, and the profile you pick determines how much data the XML must carry. Choose the profile your buyer's intake system can validate, not the most complete one by default.

The trade-off is simple. A hybrid file is easy to email and easy for a person to read, but it is heavier to validate and to generate. A buyer whose intake system expects pure XML may reject the PDF wrapper, and the PDF template becomes one more component you have to maintain.

Is XRechnung the same as Factur-X?

No. XRechnung is a standalone XML format with no PDF part, defined for the German public sector as a specification of the European standard. Factur-X keeps a readable PDF, while XRechnung is structured data only. The specification, validation rules and versions are published by the German Coordination Office for IT Standards (KoSIT) on the xeinkauf.de portal.

XRechnung is versioned, and a file that is valid under one version may need changes when a new version is released. Validation is run against published rules, so a file should be checked with the official validator before it is sent rather than after the buyer rejects it.

The common failure points are the tax breakdown, payment terms and buyer reference fields rather than the line items. A supplier that sends XRechnung to a private buyer may also find that the recipient cannot process it at all, which is why the buyer's channel must be confirmed first.

Which e-invoice formats work for Belgium, France and Germany?

Belgian buyers can usually be reached through Peppol, French buyers may expect Factur-X or a platform route, and German public-sector buyers expect XRechnung, while German private buyers vary. Confirm the channel for each buyer in writing before you choose a format.

The EU framework for electronic invoicing in public procurement stems from Directive 2014/55/EU, which requires contracting authorities to receive and process invoices that comply with the European standard. The text is available on EUR-Lex. National mandates for private transactions are set separately by each country, so check the current rules of each tax authority before you plan a go-live date. This article is general information and not legal or tax advice.

  • Confirm the acceptance channel for each buyer, such as Peppol, a portal or email.
  • Confirm the document profile and version each buyer expects.
  • Confirm the country of the buyer and which tax and payment fields are mandatory.
  • Test a sample file with the buyer's validator before the first live invoice.

Rui Codex offers technical implementation support for system integrations, including ERP connections, described on the ERP and CRM integration service page. The company does not provide legal, tax or compliance advice, audits or certification.

Where does each format fail in practice?

Each format fails at a different boundary: Peppol at identifier and profile mismatches, Factur-X at PDF generation and profile choice, and XRechnung at version and validation rules. Knowing these boundaries lets you test the right thing first.

Peppol: identifier and profile mismatches

A correct file sent to the wrong participant identifier never reaches the buyer, and a profile the buyer does not register causes rejection. These errors are configuration problems, not formatting problems, so checking the directory entry for each buyer saves time.

Factur-X: generation and profile choice

Problems usually come from a PDF template that drops the embedded XML during export or from a profile richer than the buyer's system can read. Test the output file itself, not only the PDF preview.

XRechnung: version and validation

A generator updated to a newer version can break a previously working integration. Pin the version your integration targets and retest after each change.

Hypothetical examples of format choice

Here are two hypothetical scenarios:

In the first, a hypothetical Belgian manufacturer sells to a Belgian buyer whose procurement system receives invoices through Peppol. The supplier needs one access point connection and a mapping from its invoicing fields to the chosen specification, with no PDF wrapper required.

In the second, a hypothetical software supplier invoices French customers and German public bodies from the same billing data. It generates Factur-X for French buyers and XRechnung for German public bodies, and validates both outputs before sending. The shared data source keeps the two formats consistent.

How should you prepare your invoicing system?

Start by mapping buyer channels, then choose a format for each channel, then test every output with the buyer's validator before go-live. This order prevents building a format that a major buyer will not accept.

  1. List your active buyers in Belgium, France and Germany and record the channel each one uses.
  2. Choose the format and profile version per channel, and document the decision.
  3. Map your ERP fields to the mandatory elements, including tax, payment and buyer reference data.
  4. Generate test invoices and run them through the buyer's validator and your own checks.
  5. Monitor rejections after go-live and log the error codes so the mapping can be corrected.
Tip: Keep one canonical invoice dataset and generate each format from it, rather than maintaining separate invoice data for each channel, which is where inconsistencies usually start.

Teams that connect invoicing to their ERP often find that the integration layer matters more than the format itself. Our system integration services cover this layer, and related engineering notes are collected in the integration and API topic on our blog.

Frequently Asked Questions

Is Peppol required for invoicing in Belgium?

Peppol is one channel for electronic invoices in Belgium, but whether a given buyer requires it depends on that buyer and the national rules in force at the time. Check the current guidance from the Belgian tax authority and ask each buyer which channel it accepts before setting a go-live date.

Can one file serve both Factur-X and XRechnung?

Usually not as a single file. Factur-X is a PDF with embedded XML, while XRechnung is standalone XML with German-specific rules. Many teams generate both formats from one invoice dataset and send whichever format each buyer accepts, then validate each output separately.

What should I check before choosing an e-invoice format?

Start with the buyer's acceptance channel, the document profile and version it expects, and its country. Then confirm which tax and payment fields are mandatory. Testing a sample file against the buyer's validator reveals most gaps before any live invoice is sent.

Does Peppol replace PDF invoices?

Not automatically. Peppol carries structured documents under its specifications, and whether a PDF alone is acceptable depends on the profile the buyer uses. Confirm this per buyer, and keep a readable copy of each invoice for your own records if your process requires it.

Conclusion

Peppol, Factur-X and XRechnung solve different problems, so the choice is about your buyers rather than a single preferred standard. Confirm each buyer's channel, generate every format from one reliable dataset, and test against the buyer's validator before the first live invoice. Rui Codex is led by a founder with 12+ years of hands-on experience, and the company provides technical implementation support for invoicing integrations across Belgium, the Netherlands and Luxembourg. To discuss your setup, request a project consultation at the Rui Codex contact page, or email info@ruicodex.com.

Sources

  • Peppol - OpenPEPPOL
  • Factur-X - FNFE-MPE
  • XRechnung - xeinkauf.de, KoSIT (German Coordination Office for IT Standards)
  • EUR-Lex - Publications Office of the European Union
Tags: e-invoicing Peppol Factur-X XRechnung API Integration Workflow Automation Belgium System Integration

Need Help Implementing This?

Our team can help you put these insights into practice. From AI automation to custom software development, we build solutions that deliver real results.

Send a project request