New in PDF.co: Create Factur-X and ZUGFeRD e-Invoices

Creating compliant e-invoices just got easier.

PDF.co now supports Factur-X and ZUGFeRD e-invoices, making it easier to prepare invoices for electronic processing in France and Germany.

With our new e-invoice API, you can combine an existing invoice PDF and its XML data into a single PDF/A-3 file, then automatically validate the result.

Here's how it works and why it matters for your invoice workflows.

What are Factur-X and ZUGFeRD e-invoices?

Think of Factur-X and ZUGFeRD as invoices that work for both people and software.

When someone opens the file, they see a regular PDF invoice. But behind the scenes, the PDF also contains structured XML data that accounting systems and tax platforms can process automatically.

Factur-X is used in France, while ZUGFeRD is used in Germany. Both use the same underlying approach: a PDF/A-3 document with embedded invoice data that follows the European EN 16931 standard.

This means businesses can share a single invoice file without choosing between a human-readable document and machine-readable data.

And with e-invoicing requirements expanding across Europe, supporting these formats is becoming increasingly important.

France began phasing in its B2B e-invoicing mandate on September 1, 2026, while Germany's requirements for issuing e-invoices begin phasing in from 2027.

How the PDF.co e-invoice API works

The new endpoint, /v1/pdf/convert/to/e-invoice, helps you turn an existing PDF invoice and its matching XML into a validated Factur-X or ZUGFeRD file.

Here's the process:

1. Provide your invoice PDF. Send the URL of the PDF you want to convert.
2. Add your invoice XML. Provide the URL of the corresponding EN 16931 XML file.
3. Choose your format. Set the profile parameter to facturx or zugferd.
4. Let PDF.co handle the conversion. The API embeds the XML into the PDF/A-3 document and validates the output.
5. Get your result. Retrieve the completed file once processing finishes.

The API runs asynchronously, so you can check the job status or use a callback to receive the result when it's ready.

Built-in validation helps catch issues early

Creating an e-invoice isn't just about attaching XML to a PDF. The finished file also needs to meet the required standards.

That's why PDF.co automatically runs multiple validation checks on every converted invoice.

PDF/A-3 validation with veraPDF

The API checks the PDF document using veraPDF, an open-source PDF validator. This helps verify that the document meets PDF/A requirements, including fonts, metadata, colors, and embedded attachments.

Invoice XML validation with Mustang

Mustang checks the XML against EN 16931 requirements, including required fields, invoice totals, and tax calculations.

Attachment integrity check

An additional check confirms that the XML attachment was preserved correctly during conversion.

The API combines these checks into one result. The isCompliant field is true only when all checks pass.

If validation fails, the API returns an error explaining the issue instead of delivering an invalid e-invoice.

That means you can catch problems before passing invoices to the next step in your workflow.

Designed to work with your existing invoicing tools

You don't need to replace your accounting or invoicing system to use the new endpoint.

If your software already generates EN 16931 XML, PDF.co can handle the next step: embedding that data into a PDF/A-3 document and validating the result.

For example, you could use the API to:

• Generate Factur-X invoices from PDFs and XML produced by your billing system.
• Prepare ZUGFeRD files for customers in Germany.
• Add e-invoice conversion to an existing accounting or ERP workflow.
• Automatically validate converted invoices before sending them to customers or downstream systems.

One important detail: PDF.co doesn't generate the invoice XML or compare its values against the visible PDF. Your system remains responsible for producing the XML and making sure the information matches the invoice.

The API handles the conversion and validation, so you don't have to build that functionality yourself.

Digitally signed and password-protected PDFs aren't supported, since converting a signed document would invalidate its signature.

Get started with Factur-X and ZUGFeRD

Whether you're building an invoicing platform or automating document workflows, the new e-invoice endpoint gives you a way to create and validate Factur-X and ZUGFeRD files through a single API.

Check out the e-invoice API documentation for request parameters, supported profiles, validation results, and error codes.