Millist profiili kasutada?
Prantsuse B2B ja Chorus Pro B2G: EN 16931 või kõrgem. Saksa B2B: soovituslik EN 16931.
ZUGFeRD 1.x vs 2.x — kas need on samad?
Ei. ZUGFeRD 1.x kasutab erinevat XML nimeruumi ja skeemi. ZUGFeRD 2.x = Factur-X 1.x.
Factur-X 1.x ja ZUGFeRD 2.x on tehniliselt identsed: PDF/A-3 fail koos inimloetava arve paigutuse ja sisseehitatud CII XML-iga.
FeRD avaldas ZUGFeRD 1.0 2014. aastal — PDF/A-3 hübriidvorming sisseehitatud CII XML-iga.
FNFE-mpe ja FeRD koostöös tootsid 2017. aastal Factur-X 1.0 — tehniliselt identne ZUGFeRD 2.0-ga.
Factur-X 1.x ja ZUGFeRD 2.x väljaanded avaldatakse samaaegselt ja on tehniliselt identsed.
Ainult dokumendi taseme kogusummad — ridadeta. Mõeldud raamatupidamiseks.
Päiseinfo ja makse/käibemaksu kokkuvõtted, aga mitte üksikud read.
Lisatud read — esimene profiil, mis toetab täielikku arve detaili.
Täielik EN 16931 vastavus — soovituslik profiil Prantsuse B2B kohustusele, Saksa B2B-le ja piiriülestele EL arvetele.
EN 16931 superset täiendavate tarneahela väljadega.
Prantsuse B2B ja Chorus Pro B2G: EN 16931 või kõrgem. Saksa B2B: soovituslik EN 16931.
Ei. ZUGFeRD 1.x kasutab erinevat XML nimeruumi ja skeemi. 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.
Genereeri Factur-X EN 16931 PDF või laadi üles iga Factur-X / ZUGFeRD PDF.