PEPPOL pret XRechnung — Kuru e-rēķina formātu izmantot?
PEPPOL BIS 3.0 un XRechnung ir balstīti uz EN 16931 un UBL 2.1 — taču tie kalpo dažādiem mērķiem. PEPPOL ir pārrobežu ES tīkls un formāts; XRechnung ir Vācijas stingrākais B2G specifiskais CIUS.
UBL 2.1 rēķina formāts + transporta tīkls. Izmanto pārrobežu ES B2B un B2G rēķiniem.
XRechnung 3.x
Vācijas B2G CIUS no EN 16931. Stingrāks nekā PEPPOL ar papildu obligātiem laukiem (Leitweg-ID, pārdevēja elektroniskā adrese). Tikai Vācija, tikai publiskā sektora rēķiniem.
Vai tie ir saderīgi?
XRechnung var ceļot caur PEPPOL
XRechnung UBL rēķini ir strukturāli derīgi PEPPOL saderīgi dokumenti.
XRechnung ir stingrāks nekā PEPPOL
Derīgs XRechnung rēķins vienmēr ir derīgs EN 16931 rēķins. Derīgs PEPPOL BIS 3.0 rēķins var neiziet XRechnung validāciju — Leitweg-ID ir obligāts XRechnung, bet pēc izvēles PEPPOL. aiDoks ģenerē XRechnung gan UBL, gan CII sintaksē — izmantojiet CII SAP, DATEV un citām sistēmām.
Un Vācijas B2B obligātums?
Vācijas B2B e-rēķinu obligātumam XRechnung nav vajadzīgais formāts — tas ir B2G specifisks. Vācijas B2B pieprasa EN 16931 atbilstošus rēķinus: PEPPOL BIS 3.0, CII vai ZUGFeRD/Factur-X visi atbilst.
PEPPOL pret XRechnung: BUJ
What is the difference between PEPPOL and XRechnung?
PEPPOL (Pan-European Public Procurement Online) is a cross-border transport network plus a set of format specifications. PEPPOL BIS Billing 3.0 is the PEPPOL invoice format, based on UBL 2.1 + EN 16931. XRechnung is the German B2G Core Invoice Usage Specification (CIUS) of EN 16931 — a stricter subset of EN 16931 with additional mandatory fields (Leitweg-ID, specific VAT formats). XRechnung is a format; PEPPOL is both a network and a format.
Can XRechnung invoices be transported over the PEPPOL network?
Yes. XRechnung UBL invoices are fully PEPPOL-compatible — they carry the XRechnung CustomizationID URN but otherwise conform to PEPPOL's UBL 2.1 structure. German federal and state portals accept XRechnung delivered via a PEPPOL access point. Many PEPPOL access points (Basware, Storecove, OpenPEPPOL partners) support XRechnung delivery as a standard service.
Which format should I use for invoices to German public authorities?
Use XRechnung. German B2G is explicitly the XRechnung use case. You also need the Leitweg-ID assigned by the buyer, which PEPPOL BIS invoices do not require. If your software generates PEPPOL BIS 3.0 invoices, switching to XRechnung typically means changing the CustomizationID and adding the BuyerReference (Leitweg-ID) — aiDoks handles both profiles from the same form.
Is PEPPOL used in Germany for B2B invoicing?
Yes, PEPPOL is growing in German B2B, particularly in supply-chain-intensive industries (automotive, retail). The German B2B e-invoicing mandate from 2025/2027 accepts EN 16931-compliant structured invoices in multiple formats: UBL, CII, or ZUGFeRD/Factur-X hybrid. PEPPOL BIS 3.0 UBL qualifies. XRechnung is not typically used for B2B — it is a B2G-specific format.
Is one format stricter than the other?
XRechnung is stricter than PEPPOL BIS 3.0. XRechnung adds BR-DE-* rules on top of EN 16931 (for example: mandatory Leitweg-ID, mandatory seller electronic address, German-specific VAT number formats). A valid XRechnung invoice is always a valid EN 16931 invoice, but a valid PEPPOL BIS 3.0 invoice may not pass XRechnung validation (because the Leitweg-ID and seller endpoint rules may not be satisfied).
Can aiDoks validate and generate both formats?
Yes. The aiDoks validator auto-detects whether an invoice is PEPPOL BIS 3.0 or XRechnung from the CustomizationID URN and applies the correct rule pipeline. The generator supports both profiles from the same form — switch between PEPPOL and XRechnung with the output profile selector. For XRechnung, the form additionally reveals the Buyer Reference (Leitweg-ID) field.