Nov 13, 2026
ZUGFeRD and Factur-X: Your AI-Powered Guide to Hybrid E-Invoices
Create and validate ZUGFeRD and Factur-X e-invoices with AI.
Create and validate invoices that people can read and accounting software can process—with pdfAssistant or your connected AI assistant.
Your customer receives your invoice. The description is clear, the amount is correct, and the payment details are easy to find. Then someone opens it and starts typing those same details into an accounting system: the invoice number, the purchase order reference, the line items, the tax, and the total.
Information your business already entered once now has to be entered again. Every retyped field creates another opportunity for an error, a mismatch, or an email thread that delays approval.
ZUGFeRD and Factur-X help close that gap. These hybrid e-invoice standards combine a readable PDF with structured invoice data inside the same file. People get the familiar document they can review and approve. Compatible accounting software gets data it can process directly.
With e-invoicing requirements expanding in Germany and France, understanding that combination has become increasingly useful—even if you never intend to write a line of XML.
This guide explains how hybrid invoices work, which profiles to consider, and how to create and validate them through pdfAssistant and the pdfAssistant MCP.
1. Understanding Hybrid E-Invoices
What is a hybrid e-invoice?
A hybrid e-invoice is one file designed for two audiences:
- People read the visible PDF invoice.
- Software reads the structured XML embedded inside it.
The XML identifies invoice information explicitly: this value is the invoice number, this organization is the seller, and this amount is the tax total. Compatible software can import those values without trying to infer their meaning from the page layout.
The amount of information in the XML depends on the invoice’s profile. Some profiles contain only basic header and total information; others include detailed line items and tax information.
What are ZUGFeRD and Factur-X?
ZUGFeRD is the name commonly used in Germany; Factur-X is the name commonly used in France. The standards have been harmonized through joint French and German development.
As of November 2026, the current paired releases are ZUGFeRD 2.5.2 and Factur-X 1.09.2, which describe the same harmonized format. Older versions have differences, so version compatibility still matters when exchanging files.
What is inside the file?
A hybrid invoice brings together three essential elements:
- A readable PDF/A-3 invoice. PDF/A is designed for long-term preservation. PDF/A-3 permits embedded files, making it suitable for carrying the invoice XML.
- Structured invoice XML. ZUGFeRD and Factur-X use the UN/CEFACT Cross Industry Invoice, or CII, syntax. In the harmonized format, the embedded invoice file is normally named
factur-x.xml. - Metadata and attachment information. These identify the invoice format and profile and describe the relationship between the PDF and its embedded data.
Simply attaching an XML file to an ordinary PDF does not establish conformance. The document, embedded data, and packaging all have to meet the applicable requirements.
How is this different from a regular PDF invoice?
An ordinary PDF may contain selectable text, but its page layout does not necessarily identify what each value means. Software still has to interpret the document, sometimes using OCR or extraction rules.
A hybrid invoice supplies structured fields directly. That reduces dependence on layout recognition and can reduce manual entry.
A PDF/A invoice alone is also insufficient: it needs the appropriate structured data and hybrid-invoice packaging.
How do XRechnung, UBL, and Peppol fit in?
These names describe different parts of the e-invoicing landscape:
- EN 16931 defines the European core semantic model for electronic invoices.
- CII and UBL are XML syntaxes used to represent invoice data.
- XRechnung specifies German invoice requirements and is widely used in public-sector invoicing.
- Peppol provides an exchange framework and network, with specifications governing the documents exchanged.
ZUGFeRD and Factur-X offer a particularly approachable combination for businesses accustomed to PDFs: a readable invoice and structured data packaged together.
2. Choosing the Right Profile
What does a profile control?
A profile determines the scope of the structured invoice data. It affects what software can obtain from the XML; it does not prescribe your invoice’s branding.
pdfAssistant supports the following profiles:
| Profile | What the XML contains | Practical role |
|---|---|---|
| MINIMUM | Limited header and total information | Basic data capture and booking support |
| BASIC WL | Header and totals information without invoice lines | Accounting workflows that do not need structured line items |
| BASIC | Essential invoice information, including basic line items | Straightforward invoicing where accepted |
| EN 16931 | The European core invoice data model | A useful starting point for detailed structured invoicing |
EXTENDED and XRECHNUNG are currently unsupported by these pdfAssistant creation and validation capabilities. An unsupported profile should be treated separately from a supported invoice that fails validation.
Which profile should you use?
Start with the requirements of your customer, accounting system, and delivery platform.
EN 16931 is a sensible starting point when you need detailed structured invoice data, but profile selection does not by itself establish compliance.
For Germany, the tax authority identifies qualifying ZUGFeRD versions from 2.0.1 onward as suitable, excluding MINIMUM and BASIC WL. For France, confirm the required profile and additional information with your approved platform.
Choose the profile when generating the source XML. Asking for a richer profile cannot supply missing business information automatically.
3. Why Hybrid E-Invoicing Matters Now
What are the key deadlines?
The following summarizes major domestic B2B milestones. Exceptions, transaction scope, and transitional arrangements still matter.
| Date | Country | Main milestone |
|---|---|---|
| January 1, 2025 | Germany | Businesses generally need the ability to receive e-invoices |
| September 1, 2026 | France | Receipt obligations begin for businesses in scope; large and intermediate-sized businesses begin mandatory issuance |
| January 1, 2027 | Germany | The general issuance transition ends for businesses with prior-year turnover above €800,000, subject to applicable exceptions and EDI arrangements |
| September 1, 2027 | France | Issuance obligations extend to SMEs and micro-enterprises |
| January 1, 2028 | Germany | General issuance transitions end; statutory exceptions continue |
Does creating a Factur-X file complete the French process?
For transactions covered by the French reform, invoices must travel through an approved platform, or plateforme agréée. Creating and validating the file is one part of that process; routing and reporting requirements also apply.
Use pdfAssistant to prepare and check the hybrid invoice, then follow your platform’s submission requirements.
What are the benefits beyond compliance?
Hybrid invoices can help businesses:
- Reduce manual entry. Compatible systems can import structured values.
- Simplify invoice matching. References and line-item data can support purchasing and approval workflows.
- Keep a familiar readable copy. Finance teams and business approvers can still review a PDF.
- Support preservation. PDF/A-3 provides a preservation-oriented container, alongside your organization’s retention and storage procedures.
- Introduce automation gradually. Customers can continue reading the PDF while adopting structured processing.
These benefits depend on the receiving workflow. A hybrid invoice creates the opportunity for automation; the accounting system still needs to use its data.
4. Creating ZUGFeRD and Factur-X Invoices with pdfAssistant
What do you need?
Begin with invoice XML prepared for a supported ZUGFeRD or Factur-X profile.
Your accounting, ERP, or billing system may offer a suitable export. A generic XML export—or a UBL invoice—is not automatically compatible with this CII-based creation workflow.
You can supply:
- XML alone, to generate the readable invoice from its data.
- XML and an existing invoice PDF, to retain your design where the content checks permit.
The XML provides the invoice values. pdfAssistant handles the PDF/A-3 conversion, embedding, and metadata needed to assemble the hybrid file.
Create an invoice from XML
Upload your invoice XML and describe the result:
“Create a ZUGFeRD invoice from this XML file.”
Or:
“Turn this invoice XML into a Factur-X PDF.”
pdfAssistant checks the XML, generates the visual invoice, embeds the structured data, and validates the finished package.
If the source is malformed, uses an unsupported profile, or fails the applicable rules, it reports the problem rather than treating the input as ready.
Keep your existing invoice design
If your business already has a branded invoice layout, supply the PDF and corresponding XML together:
“Combine this invoice PDF with this XML to create a Factur-X invoice, keeping the existing design.”
pdfAssistant compares the visible information it can reliably identify against the XML.
A partial comparison is not the same as a complete match. An arbitrary invoice layout may prevent every value from being conclusively checked, even when the comparisons performed find no discrepancy.
Review the content-match result when preserving an existing design.
Resolve a mismatch
If a check identifies a concrete discrepancy—such as a different total—the default behavior blocks creation.
You can correct the source files or allow the visual invoice to be regenerated from the XML:
“If the supplied PDF does not match the XML, regenerate the invoice from the XML.”
Regeneration makes the structured data the basis for the readable invoice. Review the result before using it, particularly if your original PDF contained additional information.
Customize a generated invoice
When generating or regenerating the visual invoice, you can request branding and regional presentation options, including:
- A PNG or JPEG logo and its placement.
- Fonts and colors.
- English, German, or French invoice labels.
- German, French, Dutch, or UK regional formatting.
- Currency presentation, date formatting, and footer text.
For example:
“Create a Factur-X invoice from this XML with our logo in the top right and French labels.”
Or:
“Generate a ZUGFeRD invoice with English labels and German number formatting.”
Label language and regional formatting are separate choices. These options control presentation; they do not translate item descriptions, change the invoice currency, or correct the underlying business data.
Repeat the process with workflows
For recurring work, use pdfAssistant’s workflows and batch processing to standardize the steps.
A useful process is:
- Supply the invoice XML and any corresponding PDF.
- Create the hybrid invoice.
- Review validation and content-match results.
- Route exceptions for correction or human review.
- Deliver the approved file through the required channel.
Test the process with representative invoices before applying it to an entire billing run.
5. Using the pdfAssistant MCP
What does MCP access add?
The pdfAssistant MCP makes these capabilities available through a connected AI assistant. Instead of moving into a separate document-processing interface, you can request invoice creation or validation within your existing conversation.
MCP stands for Model Context Protocol. It lets compatible assistants call tools supplied by services such as pdfAssistant. The connected assistant interprets your request; pdfAssistant’s processing tools perform the document operation.
The official MCP server supports compatible clients and requires a paid pdfAssistant plan. See the pdfAssistant MCP setup guide for current connection instructions.
What can you ask?
After connecting and making the source files available through your client, try:
“Use pdfAssistant to create a Factur-X PDF from this invoice XML.”
“Validate this supplier’s ZUGFeRD PDF and explain any blocking findings.”
“Create the hybrid invoice from these files and tell me whether the PDF/XML content match is confirmed or unverified.”
The same distinctions still matter: supported input, supported profile, package validation, content comparison, and delivery requirements.
Connecting an assistant to processing tools makes the workflow more convenient. It does not turn a general chat response into proof of invoice compliance.
6. Validating Invoices Before Delivery
Why check a file that looks correct?
Many hybrid-invoice problems are invisible on the page.
The PDF might have incorrect attachment metadata. The XML might fail a business rule. The document might claim PDF/A-3 conformance without actually meeting it.
Validation helps identify these problems before a customer or platform encounters them.
How do you validate an invoice?
Supply the completed hybrid PDF and ask:
“Validate this Factur-X invoice and explain what needs fixing.”
Or:
“Check whether this is a valid ZUGFeRD PDF.”
The validation operation checks the file without modifying it. You can check invoices created by pdfAssistant or another system, provided they use a supported version and profile.
What does validation examine?
The checks cover:
- PDF/A-3 conformance, including the claimed conformance level.
- Embedded invoice XML, its supported profile, and applicable business rules.
- Hybrid packaging, including attachment information and required metadata.
- Content consistency, where visible PDF information can be compared with the XML.
How should you interpret the result?
Review both the overall validation result and the content-match status.
| Result | Meaning |
|---|---|
| Valid | The required package, XML, business-rule, and PDF/A checks passed |
| Invalid | One or more required checks failed |
| Content match confirmed | A complete content match was established |
| Content match unverified | Checks performed found no mismatch, but a complete comparison was not established |
| Content match failed | A concrete discrepancy or reliably identified missing visible value was found |
Other statuses may indicate that comparison did not apply, could not complete, or that detailed results are unavailable for the current access level.
A valid result can coexist with an unverified content match. If your policy requires complete confirmation, send those invoices for review or regenerate the visual invoice from the XML.
Validation also does not verify that the underlying transaction happened, that payment instructions are trustworthy, or that every recipient-specific requirement has been satisfied.
7. Practical Examples
A supplier preserving its invoice design
A supplier already exports suitable CII invoice XML and produces branded PDF invoices.
It submits both files to pdfAssistant, creates the hybrid invoices, and reviews the validation results. Concrete mismatches return to billing for correction. Invoices with incomplete content confirmation follow the team’s review policy.
The supplier keeps its familiar design while introducing structured data.
An accounts payable team checking incoming invoices
An AP team receives hybrid invoices from many suppliers.
It uses pdfAssistant to screen supported files before approval. Failed checks become specific correction requests. Unsupported profiles go to a compatible validation route, while unverified content comparisons receive additional review.
This separates technical invoice checks from purchasing approval and payment authorization.
A freelancer working through a connected assistant
A designer’s invoicing application exports suitable Factur-X XML. Through an assistant connected to the pdfAssistant MCP, the designer requests a hybrid invoice with a logo and French labels.
After reviewing the result, the designer submits it through the delivery channel required for that transaction.
The conversation simplifies preparation while the invoicing application supplies the business data.
8. Best Practices and Common Pitfalls
Best practices
- Keep the source data reliable. Generate invoice XML from your billing or accounting records.
- Confirm requirements early. Check the recipient’s format, profile, references, and submission channel.
- Review both validation and content matching. They answer different questions.
- Test representative cases. Include multiple tax rates, discounts, long descriptions, and multipage invoices where relevant.
- Retain the original hybrid file. A printed copy does not preserve the embedded XML.
- Revalidate after changes. Later PDF processing can affect attachments, metadata, or PDF/A conformance.
Common pitfalls
Assuming any XML will work.
The creation workflow needs suitable CII invoice XML for a supported profile.
Assuming any attached XML makes a hybrid invoice.
The PDF/A container, metadata, and attachment relationship also matter.
Changing only the visible invoice.
Editing a total on the PDF can leave the embedded XML unchanged. Correct the source and rebuild the invoice.
Password-protecting the finished file.
PDF/A does not permit encryption. Use appropriate secure delivery and storage methods while preserving the invoice’s required format.
Treating a successful check as guaranteed acceptance.
A recipient may require additional references, data, or platform checks.
Confusing file creation with submission.
Preparing a valid hybrid PDF does not automatically deliver it or fulfill reporting obligations.
9. Frequently Asked Questions
Are ZUGFeRD and Factur-X interchangeable?
The current paired releases are harmonized. When working with older files, confirm the version, profile, and receiving system’s compatibility.
Can I create a hybrid invoice from a PDF alone?
For this creation workflow, you need suitable invoice XML. The existing PDF is optional.
A readable PDF does not supply the complete structured invoice data required by the tool.
Can I validate standalone XML?
The dedicated validation operation checks a completed hybrid PDF. XML is checked as part of invoice creation, but that is different from validating the complete package.
Do customers need special software to read the invoice?
They can view the readable invoice in an ordinary PDF viewer. Importing the embedded XML requires compatible software, and some viewers do not expose attachments conveniently.
Can I use these formats outside Germany and France?
Potentially, if the recipient accepts them. Confirm local requirements and the customer’s supported format and delivery channel.
Can I automate this in my own application?
Yes. Developers can use the underlying pdfRest REST API for creation and validation. Its creation operation accepts suitable XML, an optional PDF, and presentation options; its validation operation checks a completed hybrid invoice.
Confirm deployment-specific availability when planning an integration.
What should I consider about privacy?
Review the document-handling policies for every service involved. When using MCP, that includes pdfAssistant and the connected AI assistant provider. The official MCP documentation explains the service’s security and privacy practices.
Make Your Next Invoice Work for People and Software
ZUGFeRD and Factur-X let businesses retain the readable PDF experience while adding structured data for automated processing.
With pdfAssistant, you can create hybrid invoices from suitable XML, preserve an existing design where appropriate, and check the finished file before delivery. With the pdfAssistant MCP, you can bring those tasks into a connected AI conversation.
Start with a representative invoice, confirm your recipient’s requirements, and review both the validation and content-match results. Once the process works, make it part of your regular billing workflow.
Get started with pdfAssistant or connect the pdfAssistant MCP.
