Blog

Convert legacy PDF invoices into compliant ZUGFeRD or XRechnung: AI extraction into JSON, a review form where a person verifies the values and adds what no PDF carries (the Leitweg-ID, electronic addresses), and one create call for the validated file. Plain curl, real request and response shapes, and where the one-shot transform endpoint fits.

Add mandate-grade e-invoicing to any n8n workflow with the HTTP Request node: a Header Auth credential, a JSON body with expressions, the validated ZUGFeRD, Factur-X or XRechnung file back as binary for Drive or email. Plus the intake side (validate and extract received invoices) and the retry and batching settings for month-end volumes.

npm's most complete ZUGFeRD package, honestly compared: the XSD-only validation that misses the business rules, a work-in-progress dependency in an invoicing pipeline, and a concrete migration path from invoicer.create() to one fetch call.

Every Peppol integration is two jobs: a compliant BIS document and its delivery. The access point owns the second. This guide covers the first: what the gate checks, what it never does, why "Peppol API key" means two credentials, and validating before anything is sent.

One REST call reads typed and scanned invoice PDFs into EN 16931-shaped JSON with per-area confidence scores; a second reads e-invoices deterministically, no AI involved. The fallback pattern that chains them, the thresholds worth automating on, and the error codes, in C#, Node.js, and Python.

What the veteran .NET library does well, the validation wall .NET's missing XSLT 2.0 builds into every library stack, what its maintenance-only turn means for teams tracking the specifications, and a field-by-field migration from InvoiceDescriptor to one HTTP call.

PHP's strongest e-invoicing library, honestly compared: the totals and PDF/A work the builder leaves with you, the XSLT 2.0 validation wall no PHP package can cross, and a concrete migration path from the ZugferdDocumentBuilder chain to one Guzzle call.

Order-X puts Cross-Industry Order XML inside a PDF/A-3, the Factur-X model applied to the purchase order. The BASIC, COMFORT and EXTENDED profiles, the 220/230/231 order dialogue, and the REST endpoints that create and validate all of it.

Since January 2026 a Belgian B2B invoice is Peppol BIS UBL over the Peppol network, no phase-in, no threshold. The developer's half of that sentence: KBO/CBE endpoint addressing with EAS 0208, building the UBL, and putting the official rules in front of the gate.

An XRechnung arrives as pure XML that no PDF viewer or ERP grid will display, and that is by design. The fastest way to read one in the browser, rendering every incoming file to PDF via REST API, and pulling the same data as JSON into your own software.

The network moves invoices as pure UBL XML until an approver, controller, or auditor needs to look at one. Give every received invoice and credit note a readable PDF twin with one API call, wire it into a reception pipeline, or extract JSON for your own AP screens.

The open-source route to a readable XRechnung is the official KoSIT stylesheets: a two-step XSLT pipeline needing Saxon, XSL-FO, and a release-tracking habit. What that stack delivers, what it costs to operate outside the JVM, and how one render call compares.

A reception pipeline never chooses what arrives: CII, UBL, XRechnung in either syntax, credit notes. One endpoint renders them all as a clean PDF with automatic syntax detection, code for C#, Node.js, Python, and PHP, and a JSON route for your own UI.

Both German e-invoice formats from one Go integration using only net/http and mime/multipart: typed invoice structs, validation against EN 16931 and the KoSIT rules, incoming invoices via extraction plus AI parsing, and bounded-concurrency batch issuance. Includes why Go has no ZUGFeRD library.

The full Peppol BIS lifecycle in Java with java.net.http and Spring Boot: create UBL from structured data, validate before anything reaches your access point, pin NLCIUS, EHF or PINT, and bridge the CII syntax your German invoices already use. Includes an honest look at the Java Peppol stack.

Three format-scoped Zapier apps put mandate-grade e-invoicing into any Zap with no code: create ZUGFeRD, XRechnung, Factur-X, CII, and UBL from mapped fields, validate at format boundaries, and extract received e-invoices into rows and records. One account connects all three.

Turn a spreadsheet row into a mandate-grade e-invoice with one UrlFetchApp call: column mapping to invoice JSON, validated ZUGFeRD hybrids archived to Drive and drafted in Gmail, XRechnung with the Leitweg-ID, trigger-driven batches, and received e-invoices imported back as rows.

Turn S/4HANA billing documents into mandate-grade e-invoices with one HTTP call from SAP BTP: a Cloud Integration iFlow or CAP application posting billing data to a REST API. Covers Security Material credentials, the S/4 field mapping, incoming supplier invoices, and honest SAP DRC positioning.

The embed endpoints close the last mile every XML library leaves open: your rendered PDF plus your CII XML in, a conformant Factur-X or ZUGFeRD PDF/A-3 hybrid out, with profile-aware XMP metadata and structural checks that catch the classic mistakes before a recipient does.

What the open-source Java library genuinely does well, where the operating costs accumulate, and how a REST API compares: a capability matrix, the PDFBox/Saxon/veraPDF dependency chain, a field-by-field mapping from Mustangproject's builder classes, and a three-step migration path.

The reform reduced to what engineering teams must verify before September 1: reception readiness for every French business, compliant Factur-X issuance, PDP connectivity, the four new invoice mentions, validation of everything arriving from elsewhere, and the e-reporting clock on the same calendar.

Add compliant ZUGFeRD and Factur-X hybrid invoices to Business Central with a small AL extension: field mapping from the posted sales invoice, attachment and dispatch, XRechnung for German B2G, and incoming e-invoice extraction. No AppSource add-on, no format-version maintenance.

Handle the full ZUGFeRD lifecycle in Java with java.net.http: create from JSON, validate against EN 16931, extract incoming invoices, and parse plain supplier PDFs with AI. Covers the German B2B mandate, GoBD archiving, Spring Boot patterns, and an honest Mustangproject comparison.

Generate, validate, extract, and parse Factur-X invoices in Java with java.net.http, ready for the September 2026 French e-invoicing reform: profile ladder, PDP delivery, French sample data, and Spring Boot integration.

Handle the full XRechnung lifecycle in Java with java.net.http: create from JSON, validate against the KoSIT rules, extract data and embedded attachments, and render previews. Includes Spring Boot patterns and an honest look at the KoSIT validator.

Both German e-invoice formats from one .NET integration with HttpClient: create ZUGFeRD hybrid PDFs and XRechnung XML, validate against EN 16931 and the KoSIT rules, and read incoming invoices with extraction plus AI parsing. Includes ASP.NET Core typed-client patterns and an honest ZUGFeRD-csharp comparison.

Both German e-invoice formats from one PHP integration with Guzzle: create ZUGFeRD hybrid PDFs and XRechnung XML, validate against EN 16931 and the KoSIT rules, and read incoming invoices with extraction plus AI parsing. Includes Laravel queue patterns and an honest horstoeko/zugferd comparison.

Both German e-invoice formats from one Python integration with requests: create ZUGFeRD hybrid PDFs and XRechnung XML, validate against EN 16931 and the KoSIT rules, and read incoming invoices with extraction plus AI parsing. Includes Django, Celery, and pytest patterns and an honest drafthorse comparison.

Both German e-invoice formats in JavaScript with native fetch and FormData: create ZUGFeRD hybrid PDFs and XRechnung XML, validate against EN 16931 and the KoSIT rules, and extract incoming invoices as JSON (AI parsing included). Runs on Node.js, Vercel, Cloudflare Workers, Deno, and Bun, with an honest node-zugferd comparison.

Both German e-invoice formats from one Ruby integration with Net::HTTP: create ZUGFeRD hybrid PDFs and XRechnung XML, validate against EN 16931 and the KoSIT rules, extract incoming invoices as JSON (AI parsing included), and render previews. Includes Leitweg-ID handling and Rails patterns.

Handle the full Factur-X lifecycle in Ruby with Net::HTTP, no gem required: create from a plain hash, validate against EN 16931, extract JSON from incoming invoices, and parse legacy PDFs with AI. Ready for the September 2026 French mandate, with Rails, ActiveJob, and RSpec patterns.

The semantic standard beneath every European e-invoice, explained: ~160 business terms, 200+ business rules, the two syntax bindings (UBL and CII), and how CIUS profiles like Peppol BIS and XRechnung specialise the same core.

The second EN 16931 syntax, explained: CII's agreement-delivery-settlement structure, the rsm/ram/udt/qdt namespaces, why it sits inside Factur-X and ZUGFeRD, and how to know when to use it instead of UBL.

A technical overview of UBL as a document format: the cbc/cac anatomy of a UBL invoice, how it maps to EN 16931, how CustomizationID declares which profile it follows, and the two-layer XSD plus Schematron validation.

A look at what producing Factur-X and ZUGFeRD programmatically really involves: PDF/A-3b containers, EN 16931 CII XML, Schematron validation, and keeping pace as the specifications change.

Generate, validate, and render compliant Peppol BIS UBL e-invoices from your Bubble app with a single API call. No plugins, no XSLT, and one profile field to serve Belgium, the Netherlands, Norway, and the wider Peppol network.

Generate and validate compliant Factur-X and ZUGFeRD e-invoices from your Bubble app with a single API call. No plugins, no server-side code, and no multipart file-upload headaches. Ready for the 2026 and 2027 mandates.

Handle the full Peppol BIS UBL lifecycle in C# and .NET with HttpClient: create from JSON, validate against EN 16931 plus the Peppol overlay, convert between CII and UBL, render, and extract. Includes ASP.NET Core, Azure Functions, and Polly patterns.

Handle the full Factur-X lifecycle in C# and .NET with HttpClient: create from JSON, validate against EN 16931 Schematron, convert PDFs with AI, extract, and render. Includes ASP.NET Core, Dynamics 365, and Polly patterns.

Handle the full Peppol BIS UBL lifecycle in PHP with Guzzle and cURL: create from JSON, validate against EN 16931 and the Peppol overlay, convert, extract, and render. Includes Laravel and Symfony integration patterns.

Handle the full Peppol BIS UBL lifecycle in Python with requests and httpx: create from JSON, validate, convert, extract, and render. Includes Django, Celery, and FastAPI async batch integration patterns.

Generate, validate, convert, and render Peppol BIS UBL invoices from Node.js with production-ready examples for Belgium, the Netherlands, Norway, and global Peppol markets.

Handle the full Factur-X lifecycle in Python with requests and httpx: create from JSON, validate, transform, extract, and render. Includes Django, FastAPI, and Odoo integration patterns.

Handle the full Factur-X lifecycle in PHP with Guzzle and cURL: create from JSON, validate, transform, extract, and render. Includes Laravel and Symfony integration patterns.

Generate, validate, convert, extract, and render Factur-X invoices from Node.js with production-ready axios examples, ready for France's September 2026 mandate.

Close the Salesforce PDF gap with one API call. Named Credential setup, Flow HTTP Callout configuration, full Apex examples, and Salesforce field mapping for all European e-invoice formats.

Replace your Word-to-PDF flow with a single HTTP action. Full field mapping reference, format decision table, and complete flow structure for Germany, France, Belgium, and Peppol markets.

Create, validate, convert, extract, and render EN 16931 invoices in both CII and UBL syntax, covering Germany, France, Belgium, Peppol, and ViDA 2030.

Create, validate, convert, preview, and extract XRechnung pure XML e-invoices, with Leitweg-ID support, CIUS-REC-DE validation, and CII/UBL syntax choice.

Create, validate, convert, and extract ZUGFeRD hybrid PDF/A-3 invoices via a single REST API, with DATEV-compatible output and GoBD-ready archiving.

Create, validate, convert, and extract Factur-X hybrid PDF/A-3 invoices via a single REST API, with full PDF/A-3b conformance for France's 2026 mandate.

Convert, create, validate, preview, and convert between UBL and CII, with Peppol BIS, NLCIUS, EHF, and PINT profile auto-detection.

A complete guide to creating, validating, converting, extracting, and previewing UN/CEFACT CII invoices via a single REST API.

Discover how to integrate our REST API into your existing workflow to automate PDF-to-XML invoice conversion at scale.