XRechnung is Germany's pure XML electronic invoice standard and the mandatory format for all invoices submitted to German public authorities. Unlike ZUGFeRD, which combines a human-readable PDF with an embedded XML file, XRechnung contains only structured machine-readable data with no visual PDF layer. Every invoice sent to a German federal ministry, state authority, or municipal body must comply with XRechnung or an equivalent EN 16931-conformant format. With Germany's B2B e-invoicing mandate phasing in between 2025 and 2028 under the Wachstumschancengesetz, XRechnung is increasingly relevant for private sector transactions too. This guide covers what XRechnung is and how it works technically, the two supported syntaxes, the Leitweg-ID routing system, how to submit invoices via the OZG-RE portal, how XRechnung compares to ZUGFeRD and Peppol BIS 3.0, what XRechnung 4.0 means for businesses, and how to generate and validate compliant XRechnung invoices without an ERP.
What XRechnung is
XRechnung is Germany's Core Invoice Usage Specification (CIUS) of the European e-invoicing standard EN 16931. It was developed by the Coordination Office for IT Standards (Koordinierungsstelle für IT-Standards, KoSIT) in cooperation with the IT Planning Council (IT-Planungsrat), which coordinates digital governance across Germany's federal and state levels. XRechnung is part of the broader XEinkauf family of standards for electronic public procurement in Germany. Its specification and all associated validation artefacts are maintained and published by KoSIT at xeinkauf.de.
A CIUS, or Core Invoice Usage Specification, is a nationally defined subset of the EN 16931 semantic data model. EN 16931 defines what data a compliant European e-invoice must contain, expressed as an abstract semantic model. A CIUS takes that abstract model and applies it to a specific national context, adding mandatory fields that go beyond the EN 16931 minimum and specifying rules for the format's use within a particular country. XRechnung does exactly this for Germany: it implements all of EN 16931 and adds German-specific mandatory requirements including the Leitweg-ID buyer reference routing code required for all public sector invoicing. For a deeper look at the underlying European standard, see our explanation of EN 16931.
XRechnung is a pure XML format. This is the single most important thing to understand about it. There is no PDF layer, no visual rendering, no human-readable component bundled with the data. An XRechnung invoice is an XML file containing structured invoice data that can be read and processed automatically by software. A person opening an XRechnung file in a standard text editor sees only XML code with tags and values. Reading an XRechnung without a dedicated viewer or ERP system integration is not practical for non-technical users. This is a deliberate design choice: XRechnung is optimised entirely for automated machine-to-machine processing, not for human visual review.
For businesses and clients who also need a human-readable document alongside the structured data, ZUGFeRD's XRECHNUNG reference profile embeds XRechnung-conformant XML inside a readable PDF/A-3 document, providing a practical alternative that passes XRechnung validation while remaining visually accessible. For the full picture of ZUGFeRD and all six profiles, see our complete ZUGFeRD guide for Germany.
The two XRechnung syntaxes: UBL and CII
XRechnung supports two XML syntaxes: Universal Business Language (UBL) 2.1 and UN/CEFACT Cross Industry Invoice (CII). Both syntaxes express the same EN 16931 semantic data model. The choice between them is a technical implementation decision rather than a substantive one. An XRechnung invoice in UBL and an XRechnung invoice in CII contain the same invoice information, expressed in different XML vocabulary.
UBL 2.1 was developed by the OASIS consortium and is widely used across European e-invoicing systems including Peppol BIS Billing 3.0. If a business already sends invoices via the Peppol network, UBL is likely in use and reusing the same syntax for XRechnung reduces implementation complexity. UN/CEFACT CII is the syntax used by ZUGFeRD and Factur-X. If a business already generates ZUGFeRD invoices, CII is already familiar and the XRECHNUNG reference profile of ZUGFeRD uses exactly this syntax.
Both OZG-RE and state-level portals accept both syntaxes and process either equally. Businesses should choose the syntax that their existing invoicing software supports most cleanly. KoSIT provides official test suites, XSD schemas and Schematron validation artefacts for both UBL and CII implementations of XRechnung at the itplr-kosit repositories on GitHub.
Since February 1, 2024, three additional fields became mandatory in XRechnung regardless of syntax: BT-23 (Business process type), BT-34 (Seller electronic address) and BT-49 (Buyer electronic address). These were added as part of harmonisation between XRechnung and Peppol BIS Billing 3.0 and were introduced with XRechnung version 3.0.1. Invoices missing these fields will fail KoSIT validation and be rejected by the OZG-RE portal.
The Leitweg-ID: Germany's public sector invoice routing system
The Leitweg-ID is a mandatory data field in every XRechnung invoice submitted to a German public authority. It is a unique hierarchical routing identifier that tells the OZG-RE portal and state equivalents which specific government body and department within that body should receive the invoice. Without a valid Leitweg-ID, an XRechnung submitted to a federal or state portal will be rejected and will not be processed for payment.
The Leitweg-ID follows a standardised structure. The first two digits identify the administrative level, with 99 indicating federal administration and digits 01 through 16 indicating the corresponding German federal state. The remaining components identify the specific organisational unit and optionally the sub-department, followed by a check digit that validates the identifier. The full Leitweg-ID can be up to 46 characters long.
The Leitweg-ID is provided by the public sector client, not by the supplier. Before submitting any XRechnung invoice to a German public authority, suppliers must obtain the Leitweg-ID from their government client. This information should appear in the purchase order, the contract, or the tender documentation. If it is not included, suppliers must request it directly from the relevant authority before issuing the invoice. An XRechnung submitted with an incorrect or missing Leitweg-ID will be rejected without payment processing.
The Leitweg-ID is required for B2G invoicing only. Private businesses exchanging XRechnung invoices in B2B transactions do not need a Leitweg-ID. In the B2B context, the buyer reference field can be used for other purchase order numbers or reference identifiers, but the Leitweg-ID structure is a German B2G-specific requirement and has no equivalent in cross-border or B2B invoicing.
The OZG-RE portal: Germany's sole federal e-invoicing platform
As of September 19, 2025, the OZG-RE (Onlinezugangsgesetz-konforme Rechnungseingangsplattform, or Online Access Act-compliant Invoice Submission Portal) is the sole federal platform for submitting electronic invoices to all German federal public authorities. The decision to consolidate was made by the Federal Ministry of Finance (BMF) and the Federal Ministry of the Interior (BMI) on November 19, 2024. The migration was completed in two phases through 2025, and the former ZRE (Zentrale Rechnungseingangsplattform des Bundes) has been fully decommissioned. All federal authorities, both those previously using the ZRE and those on OZG-RE, are now connected to OZG-RE as the single unified federal B2G platform.
The OZG-RE accepts XRechnung invoices and is accessible through multiple submission channels: a manual web form for low-volume submitters where invoice data is entered directly in the browser, direct XML file upload for pre-generated XRechnung files, email transmission with the XRechnung XML as an attachment to an individual address assigned during registration, and the Peppol network for automated high-volume submission where no OZG-RE registration is required. Registration on the OZG-RE portal is free and can also be done via ELSTER company account (Mein Unternehmenskonto) for users already using ELSTER for tax filing.
The OZG-RE does not accept PDF invoices. Only XRechnung-compliant invoices in pure XML format are valid submissions to the OZG-RE portal directly. ZUGFeRD invoices in the XRECHNUNG profile submitted as XML files (with the PDF wrapper stripped) are also accepted, as they meet the EN 16931 requirements and the terms of use of the portal.
At state and municipal level, each of Germany's 16 federal states operates its own e-invoicing infrastructure. Some use the OZG-RE, others have dedicated state portals, and some states have not yet mandated B2G e-invoicing for all suppliers. Requirements vary by state and municipality. Suppliers must confirm the specific portal and submission requirements with their public sector client before the first invoice submission.
XRechnung vs ZUGFeRD: key differences for German businesses
XRechnung and ZUGFeRD are both officially accepted e-invoice formats for Germany under the Wachstumschancengesetz, and both implement EN 16931. The fundamental difference is structural, and it has significant practical implications for how invoices are received and processed.
XRechnung is pure XML with no human-readable component. Any person who needs to read an XRechnung invoice must use a dedicated viewer tool. The German tax authority provides the free ELSTER viewer at e-rechnung.elster.de which supports both XRechnung and ZUGFeRD formats. ERP systems and accounting software packages also typically include built-in XRechnung viewers. Without a viewer, the raw XML is not readable by a non-technical person.
ZUGFeRD is a hybrid format that wraps the same XML data inside a PDF/A-3 document. The PDF layer is human-readable and can be opened, printed and filed like any invoice. The embedded XML layer is machine-processable by any software that supports the format. The same single file serves both human review and automated processing, which is why ZUGFeRD is generally preferred in German B2B transactions during the transition period when not all client systems have full automated XML processing in place.
For German B2B transactions between private companies, both XRechnung and ZUGFeRD at the EN 16931 profile or higher are legally valid under the Wachstumschancengesetz. For German B2G transactions to federal authorities via OZG-RE, XRechnung is the primary required format. ZUGFeRD at the XRECHNUNG reference profile is also accepted when submitted as an XML file, as it satisfies the EN 16931 and ERechV requirements. For businesses that invoice both private B2B clients and public authorities, ZUGFeRD XRECHNUNG profile offers a practical middle path: one file format that passes XRechnung validation for B2G and also contains a readable PDF for B2B client review. For a deeper side-by-side comparison covering use cases, validation differences and routing, see our ZUGFeRD vs XRechnung guide.
The BMF has confirmed that in a hybrid format like ZUGFeRD, if any discrepancy exists between the XML data and the PDF visual representation, the XML is legally decisive for VAT purposes. For pure XRechnung files, since there is no PDF layer, the XML is by definition the only and authoritative version.
XRechnung and Peppol BIS 3.0: harmonisation and equivalence
XRechnung and Peppol BIS Billing 3.0 are closely related and increasingly harmonised. Both are CIUS implementations of EN 16931 and both support UBL 2.1 as one of their syntaxes. Since XRechnung 3.0 introduced the German National Ruleset (DE-NRS), Peppol BIS Billing 3.0 has been recognised as functionally equivalent to XRechnung 3.0 for invoices transmitted via the Peppol network. German public authorities that are reachable via Peppol accept Peppol BIS 3.0 invoices alongside XRechnung.
This equivalence has a practical benefit for businesses that invoice both German public authorities and international clients via Peppol. A Peppol BIS 3.0 UBL implementation can serve both use cases, provided the invoice includes the Leitweg-ID when invoicing German public authorities and meets all German-specific requirements added in XRechnung version 3.0.1 including the BT-23, BT-34 and BT-49 mandatory fields. Businesses do not need to maintain two separate invoice generation processes if they are already Peppol-capable. For the broader format-and-network comparison, see our Factur-X vs Peppol guide.
The Peppol network is a delivery network, not a format. XRechnung XML files can be transmitted via Peppol to any authority connected to the German Peppol access point. For the OZG-RE portal specifically, Peppol submission does not require separate OZG-RE registration, and existing Peppol registrations from the former ZRE were automatically migrated to OZG-RE during the 2025 consolidation.
XRechnung for B2G invoicing: the complete mandate history
XRechnung has been the mandatory format for German B2G invoicing in a phased rollout since 2018. The obligation was established by the E-Rechnungsgesetz (e-Invoicing Act) of April 2017 and the E-Rechnungsverordnung (E-Invoicing Ordinance, ERechV) adopted in September 2017, both transposing EU Directive 2014/55/EU into German federal law.
November 27, 2018: Supreme federal authorities and federal constitutional bodies were required to accept and process XRechnung e-invoices from suppliers.
November 27, 2019: All other federal administrative authorities were required to accept and process XRechnung e-invoices.
November 27, 2020: All suppliers to federal contracting authorities became obligated to issue and transmit XRechnung e-invoices for public procurement contracts. Direct orders with a net value of up to 1,000 euros are exempt under Section 3 Subsection 3 of the ERechV.
At state and municipal level the B2G mandate has been implemented progressively: November 2020 for Bremen alongside the federal mandate, January 2022 for Hamburg, Saarland and Baden-Württemberg, April 2023 for Mecklenburg-Western Pomerania, January 2024 for Rhineland-Palatinate, and April 2024 for Hesse. Several states have still not mandated B2G e-invoicing at state level, and requirements vary significantly by state and municipality. Suppliers must always confirm requirements with their public sector client.
XRechnung and Germany's B2B e-invoicing mandate
While XRechnung was developed for B2G use, Germany's Wachstumschancengesetz B2B mandate makes it increasingly relevant for private sector transactions. The mandate requires invoices to be in an EN 16931-compliant structured format, and XRechnung is one of the accepted options alongside ZUGFeRD at EN 16931 profile or higher. For the full list of mandatory fields a German invoice must carry to be legally valid, see our German invoice fields guide.
January 1, 2025: All businesses established in Germany must be capable of receiving EN 16931-compliant e-invoices including XRechnung. This is the reception obligation. A business cannot refuse a valid XRechnung from a supplier.
January 1, 2027: Businesses with prior-year annual turnover exceeding 800,000 euros must issue structured e-invoices for all domestic B2B transactions in scope. Paper and PDF invoices are no longer permitted for these businesses.
January 1, 2028: All remaining businesses regardless of turnover must issue structured e-invoices for domestic B2B transactions in scope. Kleinunternehmer with prior-year net turnover not exceeding 25,000 euros under §19 UStG are exempt from the issuance obligation but must still be able to receive XRechnung and other compliant e-invoices from January 2025. For the Kleinunternehmer-specific implications, see our Kleinunternehmer e-invoicing guide for 2026; for freelancers, our German freelancer e-invoicing guide covers the practical workflow.
Germany operates a post-audit model for B2B. There is no central government platform that B2B invoices must pass through, no real-time clearance requirement, and no obligation to copy invoices to tax authorities in real time. Buyers and sellers exchange invoices directly via agreed channels. Tax authorities can request invoices during an audit but do not receive them proactively. This is fundamentally different from France, which requires domestic B2B invoices to be transmitted through a certified PDP platform from September 2026.
XRechnung 4.0: what businesses need to know
In March 2026, KoSIT announced XRechnung 4.0, describing it as a fundamental evolution of the standard rather than an incremental update. XRechnung 4.0 is based on EN 16931-1:2026, the updated version of the European e-invoicing standard approved by CEN in February 2026.
The key structural change in XRechnung 4.0 is the removal of the strict one-order, one-delivery, one-invoice rule that constrained XRechnung 3.0. Version 4.0 will support combining multiple orders, deliveries and customer references in a single invoice, reflecting the complexity of real supply chains more accurately and reducing the administrative burden for businesses with multiple concurrent orders from the same public authority client. VAT and rounding combinations are being clarified. New fields are being added for detailed bank information, multiple payment terms, early payment discounts (Skonto) and late payment penalties, which are required for Germany's future participation in ViDA digital reporting requirements.
XRechnung 4.0 will align with Peppol BIS 4.0, which is built on EN 16931-1:2026 and unifies the BIS 3.0 standard with the PINT (Peppol International Network) model. This alignment further strengthens the convergence between XRechnung and Peppol and simplifies cross-border invoicing for businesses operating across multiple EU markets.
A preliminary version of XRechnung 4.0 was released for testing in 2026. The final specification depends on CEN approving the updated UBL 2.5 and CII D25A syntax bindings. No mandatory adoption date has been confirmed at the time of writing. Businesses currently using XRechnung 3.0.x remain fully compliant and do not need to migrate until KoSIT publishes the final specification and an official transition timeline. Planning for the multi-order invoice data model and the new payment fields is advisable for businesses with complex B2G workflows.
Generating XRechnung invoices without an ERP
Generating a compliant XRechnung invoice without an ERP is straightforward through several practical routes. XRechnung invoices cannot be created with standard PDF tools, Word, Google Docs or generic invoicing software that produces only visual PDF output. An XRechnung file is a plain XML document that must be generated by software producing valid UBL 2.1 or UN/CEFACT CII output conforming to the XRechnung specification and passing KoSIT validation.
For freelancers, consultants and small businesses that occasionally invoice German public authorities, the OZG-RE web form is the simplest path. Invoice data is entered directly in the browser and the portal generates a valid XRechnung file for submission. No software installation is required. No cost is charged. This route is free and requires only a one-time OZG-RE registration.
For businesses with moderate invoice volumes, dedicated invoicing software that includes XRechnung generation as a built-in feature is the practical choice. Many German accounting packages including DATEV, Lexoffice and sevDesk have supported XRechnung generation since 2020. A standalone XRechnung generator that accepts invoice data as input and produces conformant XML output is also an option for businesses that prefer not to use subscription accounting software. For a step-by-step walkthrough of how a compliant hybrid invoice is built, see our practical guide to creating a Factur-X / ZUGFeRD compliant invoice.
For businesses invoicing both public authorities (requiring XRechnung) and private B2B clients (where ZUGFeRD is often preferred), a single invoicing tool that generates both formats from the same account eliminates separate workflows. ZUGFeRD's XRECHNUNG profile is particularly practical here, producing a single file that passes XRechnung validation for B2G submissions and also contains a human-readable PDF for B2B clients. For more on the ERP gap and how to close it without replacing the system, see our outgoing e-invoicing ERP gap guide.
Validating XRechnung invoices before submission
XRechnung validation before submission is essential. An invoice that fails validation will be rejected by the OZG-RE portal or the recipient's ERP system, delaying payment and requiring resubmission. The KoSIT XRechnung validator is the official open-source tool for checking XRechnung compliance and is available free on GitHub.
Validation operates at two levels. The first is XSD schema validation, which checks that the XML is well-formed and that all required fields for the declared syntax are present and correctly structured. The second is Schematron business rule validation, which checks that the invoice data satisfies the logical constraints defined in EN 16931 and the XRechnung CIUS. Common XRechnung validation errors include missing mandatory fields such as the Leitweg-ID for B2G submissions and the BT-23, BT-34 and BT-49 fields introduced in version 3.0.1, incorrect tax calculation totals, and VAT category codes missing required supporting data.
The ELSTER viewer at e-rechnung.elster.de provides free visual rendering of XRechnung XML files, allowing suppliers to verify that the invoice data is complete and correct before submission. The Facturwise validator is a free in-browser alternative that accepts XRechnung files and produces an instant EN 16931 compliance report with no account required. For a deeper walkthrough of each validation layer, common error codes, and how to fix them, see our Factur-X / ZUGFeRD validation guide.
XRechnung for cross-border invoicing
XRechnung is a German national standard and is not the expected format for most cross-border invoicing scenarios. For cross-border invoices to German public authorities, foreign suppliers can use XRechnung, Peppol BIS Billing 3.0, or any EN 16931-compliant format. For foreign suppliers already on the Peppol network, Peppol BIS 3.0 is the natural choice since it is recognised as functionally equivalent to XRechnung via the DE-NRS ruleset.
UK businesses invoicing German public authorities should use XRechnung or Peppol BIS 3.0, obtain the Leitweg-ID from their government client, and submit via OZG-RE or the appropriate state portal. UK businesses invoicing German private companies are not subject to Germany's B2B mandate, which applies only to businesses established in Germany, but their German clients may request XRechnung or ZUGFeRD for automated AP processing.
For businesses that need to cover both German and French markets, ZUGFeRD and Factur-X are technically identical formats, meaning one invoicing tool generates both. For Belgian and Dutch clients, Peppol BIS 3.0 is the correct format since Belgium has mandated it for B2B e-invoicing from January 2026 and the Netherlands uses it extensively. A single invoicing tool supporting XRechnung, ZUGFeRD, Factur-X and Peppol BIS 3.0 covers Germany, France, Belgium and the Netherlands from one account.
A practical XRechnung compliance checklist
Confirm that your invoicing software generates valid XRechnung 3.0 in either UBL 2.1 or UN/CEFACT CII syntax. Ensure all three mandatory fields from version 3.0.1 are populated: BT-23 (Business process type), BT-34 (Seller electronic address) and BT-49 (Buyer electronic address). Obtain the Leitweg-ID from your public sector client before issuing the first B2G invoice, as it cannot be added retroactively after submission. Validate every invoice using the KoSIT validator or the free Facturwise validator before submission. Submit all federal government invoices via OZG-RE, the sole federal platform since September 2025. For state and municipal clients, confirm the correct portal and submission channel directly with the client. Archive XRechnung invoices in their original XML format for at least 8 years to comply with GoBD archiving requirements.
Frequently asked questions about XRechnung
What is XRechnung and how does it differ from ZUGFeRD?
XRechnung is Germany's Core Invoice Usage Specification of the European standard EN 16931, developed by KoSIT and mandatory for all invoices to German federal public authorities. It is a pure XML format with no human-readable PDF layer, designed for automated machine-to-machine processing. ZUGFeRD is a hybrid format that embeds the same XML data inside a human-readable PDF/A-3 document. For German B2G invoicing to federal authorities via OZG-RE, XRechnung is the primary required format. For German B2B invoicing between private companies, both are legally valid under the Wachstumschancengesetz. ZUGFeRD is generally preferred for B2B because the PDF layer is readable without specialist software.
Is XRechnung mandatory for German businesses?
XRechnung and other EN 16931-compliant formats have been mandatory for invoices to German federal public authorities since November 27, 2020. For B2B invoicing between private companies, the Wachstumschancengesetz requires all German businesses to be capable of receiving EN 16931-compliant e-invoices including XRechnung from January 1, 2025. Issuing structured e-invoices becomes mandatory for businesses with prior-year turnover above 800,000 euros from January 1, 2027, and for all remaining businesses from January 1, 2028. Kleinunternehmer with prior-year net turnover not exceeding 25,000 euros are exempt from the issuance obligation but must be able to receive compliant e-invoices.
What is the Leitweg-ID and why is it required in XRechnung?
The Leitweg-ID is a mandatory routing identifier in every XRechnung submitted to a German public authority. It tells the OZG-RE portal which specific government body and department should receive the invoice. Without a valid Leitweg-ID the invoice is rejected without payment processing. The Leitweg-ID is provided by the public sector client and should appear in the purchase order or contract. It is not required for B2B invoices between private companies.
How do I submit an XRechnung to German federal authorities?
Since September 19, 2025, the OZG-RE is the sole federal platform for submitting XRechnung invoices to German federal public authorities. The former ZRE has been fully decommissioned. OZG-RE accepts submissions via browser web form, XML file upload, email and Peppol network. Registration is free for non-Peppol channels. For state and municipal authorities, confirm the correct portal and channel with the client directly, as this varies by state.
Can I use XRechnung for B2B invoicing or only B2G?
XRechnung is legally valid for German domestic B2B invoicing between private companies under the Wachstumschancengesetz, as it is EN 16931-compliant. However, ZUGFeRD is generally preferred for B2B because the PDF layer reduces friction for clients who cannot yet process pure XML automatically. The Leitweg-ID is only required for B2G invoicing to public authorities, not for B2B transactions.
What is the difference between XRechnung and Peppol BIS 3.0?
Both XRechnung and Peppol BIS Billing 3.0 are CIUS implementations of EN 16931 supporting UBL 2.1 syntax. Since XRechnung 3.0 introduced the German National Ruleset (DE-NRS), Peppol BIS 3.0 is recognised as functionally equivalent to XRechnung 3.0 for invoices sent via the Peppol network. German public authorities reachable via Peppol accept Peppol BIS 3.0 alongside XRechnung. The key practical difference is the delivery channel: OZG-RE or state portals for direct XRechnung submission, Peppol network for Peppol BIS 3.0. Both require the Leitweg-ID for German B2G invoicing.
How do I validate an XRechnung invoice for free?
KoSIT provides a free open-source XRechnung validator at the itplr-kosit repositories on GitHub. The ELSTER viewer at e-rechnung.elster.de provides free visual rendering of XRechnung XML files so invoice data can be verified before submission. The Facturwise validator accepts XRechnung files and produces an instant EN 16931 compliance report with no account required and no cost. Validating before submission is critical as invalid invoices are rejected without payment processing.
What is XRechnung 4.0 and should I prepare now?
XRechnung 4.0 was announced by KoSIT in March 2026, based on EN 16931-1:2026. It removes the one-order, one-delivery, one-invoice constraint of version 3.0, adds fields for multiple payment terms, early payment discounts and late payment penalties, and aligns with Peppol BIS 4.0. A preliminary test version was released in 2026. No mandatory adoption date has been confirmed. Businesses using XRechnung 3.0.x remain fully compliant. Planning for the multi-order invoice data model changes is advisable for businesses with complex B2G supply chains.
Generate XRechnung invoices with Facturwise
Facturwise generates compliant XRechnung files automatically for submission to German federal and state authorities via the OZG-RE portal. Every invoice is validated against KoSIT rules before it is available for download, with support for both UBL and CII syntaxes. Leitweg-ID handling is built in, and the same account also generates ZUGFeRD for B2B clients, so B2G and B2B invoices come out of the same workflow. No XML configuration, no separate tools, no extra steps. Create your first XRechnung for free.
This article is informational and does not constitute legal, tax, or compliance advice. The Wachstumschancengesetz, §14 UStG implementation details, the XRechnung specification, OZG-RE portal requirements and state-level B2G rules continue to evolve, and details may change after publication. For decisions affecting your business, consult a qualified tax advisor (Steuerberater), accountant, or your AP/IT integration partner.