pdfRest Launches “Create ZUGFeRD PDF” for E-Invoice Building and Validation

Electronic invoicing in Germany and France calls for a single document that both a person and an automated system can use. ZUGFeRD in Germany and Factur-X in France meet that need with a hybrid invoice: a human-readable PDF/A-3 document that carries machine-readable UN/CEFACT Cross Industry Invoice (CII) XML inside it. France’s domestic B2B mandate began taking effect on September 1, 2026, and Germany’s issuance requirement begins January 1, 2027 for businesses above EUR 800,000 in turnover.

Producing one correctly means coordinating several layers at once, including the visual invoice layout, the embedded XML payload, the attachment relationship, the required metadata, and overall PDF/A-3 conformance. A mistake in any single layer can cause a receiving system to reject the document.

pdfRest now handles that coordination in a single workflow with the Create ZUGFeRD PDF API Tool. Built on the Adobe PDF Library, powered by pdfRest, the tool builds a complete hybrid invoice, validates it, and returns a file ready for delivery, archival, or automated processing without requiring applications to assemble each layer manually.

One Integration for Both German and French E-Invoicing

Because ZUGFeRD and Factur-X are technically aligned, a single pdfRest integration supports both standards. The supported releases, ZUGFeRD 2.5.2 and Factur-X 1.09.2, share the same hybrid PDF/A-3 and CII XML model. This allows accounting platforms, ERP systems, and billing applications to serve both markets from a unified pipeline.

That single path helps development teams build reliable ZUGFeRD invoice workflows for German B2B billing or prevent Factur-X rejections in French e-invoicing workflows. Invoice recipients keep a familiar visual document, while downstream systems receive structured data ready for automated processing.

The launch release supports four core invoice profiles: MINIMUM, BASIC WL, BASIC, and EN 16931. Together, these cover reduced invoice data, booking-level workflows, and full EN 16931-aligned invoices. When a document uses a profile outside this set, the tool returns a specific PROFILE_UNSUPPORTED status code so the host application can route the job cleanly rather than guessing.

Generate From XML or Preserve an Existing Invoice

The tool fits existing business assets, providing three ways to produce the visual invoice:

• XML Only: Generate the visual invoice and the complete PDF/A-3 package directly from a valid CII XML payload.
• PDF Plus XML: Preserve a pre-existing, branded PDF while pdfRest embeds the XML, converts the file to PDF/A-3, applies the attachment relationship, and injects the required metadata. By default, pdfRest compares the identifiable information and rejects concrete mismatches.
• Regenerate When Needed: Set regenerate_pdf to true to replace a mismatched or unconfirmed PDF with a freshly rendered visual invoice generated directly from the canonical XML, so that visual text and embedded data derive from the exact same source.

For generated or regenerated invoices, detailed render options govern visual presentation and regional formatting, including logo placement, typography, RGB or CMYK color palettes, currency display, date formatting, decimal precision, and footer content. Invoice labels and regional formatting operate independently, enabling workflows to pair English labels with German dates, decimals, and currency styling.

Every hybrid invoice produced is packaged as PDF/A-3 (ISO 19005-3) for long-term, standards-based archival.

Validate the Complete Package, Not Just the XML

Conforming XML is only one component of a valid hybrid invoice. A separate validation endpoint inspects an existing ZUGFeRD or Factur-X PDF without modifying it, whether generated by pdfRest or received from an external vendor:

• Package Structure: Verifies PDF/A-3 conformance, embedded CII XML presence, and a supported invoice profile.
• Rules and Metadata: Validates applicable XML business rules, attachment filenames, MIME types, association metadata, and required XMP properties.
• Content Agreement: Detects consistency between the human-readable visual invoice and the underlying structured XML data.

The validation response separates the overall compliance decision from content-match confidence. A status of VALID is returned only when the package structure, XML, business rules, and an independent PDF/A check pass completely.

When no concrete mismatch is found but full reverse confirmation is not possible, the tool reports an UNVERIFIED content-match status with a non-blocking warning, allowing organizations to route the file for manual review based on internal policy.

Because every API call returns reusable resource IDs, creation and validation operations can be chained together without downloading intermediate files. Workflows can automatically accept conforming invoices, route rejected packages for correction, and hold unverified documents for review. This validation endpoint extends pdfRest’s suite for checking and validating PDFs directly to the specific demands of hybrid e-invoices.

Getting Started

Adding ZUGFeRD and Factur-X support to your billing or document workflow takes only a few minutes. To review full parameter details, see payload examples, and test both creation and validation requests in the API Lab, visit the Create ZUGFeRD PDF API Tool.