XRechnung: format, vs ZUGFeRD, Jupiter ERP

XRechnung is a German specification for structured invoice data built on the European standard EN 16931. In practice you often receive an XML file that procurement systems and invoice portals process directly. People then read the invoice in the recipient's UI, not as a classic PDF attachment.

That differs from hybrid formats such as ZUGFeRD, where XML sits inside the PDF. Both can be EN 16931 compliant when the right profile is used. German VAT law cares about structured processability, not the file extension.

XRechnung does not replace mandatory fields under § 14 UStG or § 34a UStDV. Missing tax IDs or wrong amounts stay invalid in XML too. The ministry FAQ and your tax advisor clarify receiving and issuing duties. This page describes the format and Jupiter ERP, not your specific case.

ZUGFeRD targets teams that want one file for people (PDF) and machines (XML). XRechnung targets processes where only the structured file counts, for example public procurement or Peppol.

Many private B2B partners work with ZUGFeRD because PDF and structured data sit in one file. Jupiter ERP issues ZUGFeRD 2.x in the PDF for that. For public authorities you download XRechnung 3.0.

As a customer of suppliers, inbound XRechnung is increasingly common. You must open, check, and archive the file regardless of which format you issue yourself.

Federal, state, and local bodies use central invoice receipt platforms. They often expect XRechnung or compatible CIUS profiles. The tender or contract names the format. Deviations without agreement lead to rejections.

Subcontractors in public construction or IT supply chains see similar rules. Private customers more often ask for ZUGFeRD or still PDF during transition. Check purchasing terms before you send.

Peppol moves structured invoices between participants. You download XRechnung 3.0 from Jupiter ERP and submit it in the authority's portal.

For public authorities you download XRechnung 3.0 (CII, EN 16931) from the invoice or credit note. You store the Leitweg-ID on the contact. It is copied onto the document. The XRechnung uses the value on the invoice or credit note.

For everyday B2B invoices Jupiter ERP embeds ZUGFeRD 2.x with the EN 16931 profile in invoice and credit note PDFs. That is intended on the Free plan for issuing.

Inbound, you can read XRechnung files in the public e-invoice viewer without an account and inspect fields. Storing them as expense receipts in the panel with account assignment is available from Business upward.

So typical B2B work with a readable PDF and structured data stays in one workflow. Receiving duty since 2025 applies to XRechnung from suppliers too. Issuing duties follow phased rules through 2026, 2027, and 2028. Current thresholds are in the ministry FAQ.

Decide who checks inbound structured invoices: amount, tax, service period, order reference. Store the original file for retention. The viewer helps with first reading; approval stays with your accounting team.

In the panel you capture the receipt and assign accounts or projects. GoBD topics such as immutability after posting remain your responsibility. DATEV export and advanced reporting depend on the package.

You issue ZUGFeRD in the PDF and XRechnung 3.0 as a download, and you still receive XRechnung from suppliers. Jupiter ERP reads inbound ZUGFeRD and XRechnung files. Issuing and receiving stay in one system even when partners use different file shapes.

Agree short inbox rules: who opens the file first, who posts, who archives. A fixed flow keeps structured attachments out of general folders. The public viewer suits a quick visual check before you file the receipt in the panel.

When unsure whether an inbound file is valid, forward it to your tax advisor. This article does not replace checking mandatory fields in your case.