¿Qué perfil debo usar?
Para B2B francesa y Chorus Pro B2G: EN 16931 o superior. Para B2B alemana: EN 16931 recomendado.
ZUGFeRD 1.x vs 2.x — ¿son lo mismo?
No. ZUGFeRD 1.x usa un namespace XML y esquema diferentes. ZUGFeRD 2.x = Factur-X 1.x.
Factur-X 1.x y ZUGFeRD 2.x son técnicamente idénticos: un archivo PDF/A-3 con diseño de factura legible y un XML CII incrustado.
FeRD publicó ZUGFeRD 1.0 en 2014 — un formato híbrido PDF/A-3 con XML UN/CEFACT CII incrustado.
FNFE-mpe y FeRD colaboraron para producir Factur-X 1.0 en 2017 — técnicamente idéntico a ZUGFeRD 2.0.
Los lanzamientos Factur-X 1.x y ZUGFeRD 2.x se publican simultáneamente y son técnicamente idénticos.
Solo totales a nivel de documento — sin partidas. Diseñado para contabilidad y procesamiento de pagos simple.
Información de cabecera y resúmenes de pago/IVA, pero sin partidas individuales.
Partidas añadidas — el primer perfil que soporta detalle completo de la factura.
Cumplimiento completo de EN 16931 — el perfil recomendado para la obligación B2B francesa, B2B alemana y facturación transfronteriza en la UE.
Superconjunto de EN 16931 con campos adicionales de cadena de suministro.
Para B2B francesa y Chorus Pro B2G: EN 16931 o superior. Para B2B alemana: EN 16931 recomendado.
No. ZUGFeRD 1.x usa un namespace XML y esquema diferentes. ZUGFeRD 2.x = Factur-X 1.x.
Yes — Factur-X 1.x and ZUGFeRD 2.x are technically identical. The same XML schema (UN/CEFACT CII), the same 5 profile levels, the same PDF/A-3 embedding rules. The difference is branding and governance: ZUGFeRD is the German name maintained by FeRD (Forum elektronische Rechnung Deutschland); Factur-X is the Franco-European name maintained by FNFE-mpe. Both organisations collaborate and release synchronized versions.
ZUGFeRD 1.x (published 2014) is an older format with a different XML namespace and schema than ZUGFeRD 2.x / Factur-X 1.x. It has only 4 profiles (BASIC, COMFORT, EXTENDED, EXTENDED_B2C) and predates EN 16931. It is still encountered in legacy German systems (particularly SAP R/3 environments) but is not recommended for new implementations. aiDoks validates Factur-X / ZUGFeRD 2.x; ZUGFeRD 1.x support is limited.
From least to most detailed: MINIMUM (just document-level totals, no line items — for book-keeping only), BASIC-WL (header + summaries, no line items), BASIC (line items added, a common practical choice), EN 16931 / COMFORT (full EN 16931 compliance, required for French B2B mandate), EXTENDED (superset of EN 16931 with additional supply-chain fields). For French Chorus Pro and B2B mandate compliance, use EN 16931 or higher.
No — PEPPOL transports UBL or CII XML, not PDF attachments. Factur-X is a PDF format (the PDF is the primary file, with CII XML embedded). You can extract the embedded CII XML from a Factur-X PDF and send that over PEPPOL, but the hybrid PDF itself is not a PEPPOL document. For French B2B via PDP or PPF, all three formats (Factur-X, UBL, CII) are accepted; Factur-X is the most common.
France is the primary mandate driver: Factur-X is required for B2G (Chorus Pro) and is the recommended format for the B2B mandate rolling out from September 2026. Germany accepts ZUGFeRD/Factur-X as a valid format for the B2B e-invoicing mandate from 2025. Belgium, Luxembourg and Switzerland are exploring Factur-X adoption. For cross-border EU e-invoicing, PEPPOL UBL remains the dominant format.
Yes — the aiDoks validator accepts Factur-X and ZUGFeRD 2.x PDF/A-3 files directly. It extracts the embedded CII XML automatically, detects the declared profile, and validates against the official Factur-X 1.08 schematron for that profile plus the underlying EN 16931 rules. Error reports include the profile name, rule ID and a plain-English description. Upload the PDF — no need to extract the XML manually.
Genere un PDF Factur-X EN 16931 o suba un PDF Factur-X / ZUGFeRD para validar.