broad-erp-tech
Broad ERP/Tech
E-invoicing standards: formats and networks
Understand e-invoicing standards, formats and networks so your NetSuite setup is ready to scale across Europe.
netsuite-articles
Summarise the article with your AI:

Germany’s e-invoicing mandate has already started. The mistake is to treat it as a 2027 deadline only.
Since 1 January 2025, German businesses must be able to receive structured electronic invoices for domestic B2B transactions. From 1 January 2027, mandatory issuance begins for companies above €800,000 annual turnover, before extending to all in-scope businesses from 1 January 2028.
For finance leaders, this is not just a technical format change. It is a shift in how invoice data is created, exchanged, received, stored and audited. The companies that understand the regulatory framework early will be better prepared to adapt their finance systems without rushing implementation.
This guide explains what the German e-invoicing mandate requires, who is affected, which dates matter, and what finance teams should know before moving into detailed preparation.
The Germany e-invoicing mandate requires in-scope businesses to use structured electronic invoices for domestic B2B transactions. The rules were introduced through the Wachstumschancengesetz, also known as the Growth Opportunities Act, which updated German VAT invoicing rules for transactions carried out after 31 December 2024.
The German Ministry of Finance explains that, from 1 January 2025, electronic invoices must generally be used for transactions between domestic businesses, with transition rules applying during the rollout period. Private end consumers are not affected by these B2B rules.
The key change is the definition of an invoice. A standard PDF may be digital, but it is not automatically an e-invoice under the mandate. A compliant e-invoice must contain structured data that can be processed electronically.
Germany is introducing mandatory B2B e-invoicing progressively. The reception requirement comes first, followed by phased issuance obligations.
Since November 2020, e-invoicing has already been mandatory for many B2G transactions in Germany. Invoices to public authorities typically require XRechnung, Germany’s public-sector e-invoicing format.
Since 1 January 2025, German businesses must be able to receive structured e-invoices that comply with EN 16931, the European standard for electronic invoicing. This means the mandate is already operational from a reception perspective.
From 1 January 2027, businesses with annual turnover above €800,000 must issue structured electronic invoices for domestic B2B transactions.
From 1 January 2028, the issuance obligation extends to all in-scope businesses for domestic B2B transactions.
This phased timeline creates a practical challenge. Many companies are planning around the 2027 issuance date, but AP teams already need to handle incoming structured invoices.
The German B2B e-invoicing mandate applies to transactions between domestic businesses. In practical terms, it is relevant for companies with German entities, German VAT registrations, or domestic B2B invoice flows in Germany.
For international companies, the question is often broader than “Do we have a German subsidiary?” Finance teams also need to understand whether invoices are issued locally, whether suppliers send invoices to German entities, and whether customer or public-sector requirements already impose structured invoicing.
The mandate is especially relevant for companies with:
In Germany, a compliant e-invoice must be issued, transmitted and received in a structured electronic format. The reference standard is EN 16931, which defines the semantic model for electronic invoices in Europe.
This matters because the mandate is not simply about sending invoices electronically. It is about making invoice data machine-readable and suitable for automated processing.
A PDF sent by email may still be used in some contexts during transition periods, but it is not the same as a structured e-invoice when the mandate applies. The German rules point toward structured formats such as XRechnung and ZUGFeRD, provided they meet the relevant requirements.
The simple way to explain it is this: the visual invoice is no longer the whole story. The structured data becomes the key compliance layer.
Germany already has an established B2G e-invoicing framework. For invoices sent to public authorities, XRechnung has been mandatory since November 2020 in many public-sector scenarios. These invoices are typically exchanged through public-sector channels, often involving Peppol or government platforms.
The B2B mandate is different. It introduces structured electronic invoicing for transactions between domestic businesses, with mandatory reception from 2025 and phased issuance from 2027 and 2028.
This distinction matters because finance teams should not assume that one process covers every case. A B2G invoice may require different routing information, identifiers or delivery channels than a standard B2B invoice.
For companies serving both public-sector and private-sector customers in Germany, B2G and B2B flows should be reviewed separately.
Germany mainly relies on two e-invoicing formats: XRechnung and ZUGFeRD. This article keeps the explanation high-level, because the detailed comparison between PDF, XRechnung and ZUGFeRD should be handled in a separate article.
XRechnung is Germany’s EN 16931-compliant, XML-based e-invoicing standard. Widely used for public-sector invoicing (B2G), it is also one of the main compliant formats for domestic B2B e-invoicing, alongside ZUGFeRD. Designed for automated processing, it does not require a human-readable PDF, although PDFs can be embedded as supplementary attachments. The structured XML data remains the authoritative invoice. XRechnung invoices can be transmitted by email or through the Peppol network for automated system-to-system delivery, provided the recipient is registered to receive invoices via Peppol.
ZUGFeRD is a hybrid format. It combines a human-readable PDF/A-3 document with embedded structured XML data. This makes it practical for many B2B situations because it supports both human review and automated processing.
Both formats are linked to the European e-invoicing framework and must be handled carefully from a data, validation and archiving perspective.
For finance teams, the main question is not only “Which format is legal?” It is “Which format applies to which invoice flow, customer type and delivery channel?”
Peppol is important in Germany, especially for public-sector invoicing, but it is not generally mandatory for all B2B e-invoicing.
The German B2B obligation focuses on structured electronic invoices that comply with the required standard. The delivery channel may vary depending on the transaction, the recipient, the format and the agreed exchange process.
For B2G transactions, Peppol is more common because public-sector invoicing often depends on structured routing and access points. For B2B transactions, Novutech’s e-invoicing solution simplifies delivery: when the recipient is found in the Peppol Directory, an XRechnung is automatically sent through the Peppol network.
This is one of the reasons why e-invoicing is both a legal and an operational topic. The format, the channel and the underlying ERP process need to work together.
A compliant e-invoice must include the legally required invoice data in structured form. This includes information such as seller and buyer tax identifiers, invoice number, invoice date, invoice lines, VAT details and relevant references such as purchase orders or contracts where applicable.
This is where the mandate starts to affect day-to-day finance operations. If the structured invoice depends on ERP data, then incomplete or inconsistent ERP data can become a compliance issue.
Typical data areas include:
German e-invoices must be archived digitally and preserved in a compliant way. Based on the documentation reviewed for this article, structured invoices must be retained in their original structured format for 8 years, in line with GoBD expectations around integrity, readability and accessibility.
For hybrid ZUGFeRD documents, the structured XML is the tax-relevant element. The PDF is useful for human readability, but the structured data must remain available and unaltered.
For finance teams, this means archiving should be considered part of the e-invoicing process from the beginning. It is not enough to generate or receive the invoice. The business must also be able to retrieve the legally relevant file later for audit or tax purposes. With Novutech’s solution, the e-invoice XML is available and stored in NetSuite, which can remain the archiving platform. In addition, Invopop also archives the e-invoice for the required retention period.
Germany’s current mandate focuses on structured e-invoicing. Digital reporting is expected to evolve in connection with the EU’s VAT in the Digital Age, or ViDA, initiative.
The European Commission states that Digital Reporting Requirements will affect cross-border B2B transactions from 1 July 2030. Member States with domestic real-time digital reporting obligations will also need to align with the EU model by 2035.
For Germany, the exact future domestic reporting model is not fully defined yet. The direction is clear, however: structured invoice data will become increasingly important for VAT reporting and tax transparency.
This is why finance teams should avoid treating the German mandate as a one-off compliance task. The 2025–2028 rollout is part of a broader European move toward structured invoice data. Novutech’s solution already covers e-reporting in countries where it is required, including Spain’s SII and e-reporting in France. This makes it easier to scale to future compliance requirements and build a setup that can adapt as regulations evolve.
The German e-invoicing mandate creates legal obligations, but the real impact sits inside finance operations.
Invoices will need to move through systems in structured formats. Customer and vendor data will need to be complete. Finance teams will need to understand which flows are in scope, which formats apply, how invoices are delivered, and where the legally relevant files are stored.
For companies using NetSuite or another ERP, this means the ERP cannot remain disconnected from the e-invoicing process. The invoice lifecycle should be visible where finance teams already work.
At Novutech, we see e-invoicing as part of finance transformation, not only compliance. The right setup should help companies stay compliant while improving control, traceability, scalability and operational efficiency across finance processes.
Before moving into detailed preparation, finance leaders should align internally on a few regulatory and operational questions.
First, identify which German entities and invoice flows are in scope. B2B, B2G and cross-border flows may follow different requirements.
Second, clarify which formats are relevant for your business. Some customers may expect XRechnung. Others may accept or prefer ZUGFeRD. Public-sector flows may have specific routing requirements.
Third, review whether your systems can receive and preserve structured invoice files. Since reception has been required since 2025, this is already relevant for AP teams.
Fourth, confirm who owns the topic internally. E-invoicing sits between finance, tax, IT and operations. Without clear ownership, decisions around data, systems and compliance can move slowly.
Novutech helps European growth companies transform finance operations by aligning people, processes and technology. Our teams support NetSuite implementation, optimization, integrations, automation and long-term finance transformation across Europe.
For Germany e-invoicing, Novutech connects NetSuite with Invopop to support e-invoice creation and delivery. When the recipient is found in the Peppol Directory, an XRechnung can be sent automatically through the Peppol network. Alongside this solution, our team advises on regulatory scope and invoice flows and supports implementation within your ERP and finance processes.
With 250+ customers across Europe, 65+ experts in 8 countries, 100+ certifications and long-term NetSuite experience, Novutech brings both finance process knowledge and technical implementation expertise to e-invoicing projects.
Germany’s e-invoicing mandate is already underway. The earlier finance teams understand the scope, timeline and data implications, the easier it becomes to prepare without last-minute complexity.
If you use NetSuite and need to understand how the German mandate could affect your finance operations, our experts can help you assess the right next steps.
German businesses must be able to receive structured e-invoices since 1 January 2025. Issuing becomes mandatory from 1 January 2027 for businesses with annual turnover above €800,000, and from 1 January 2028 for all in-scope businesses.
The mandate applies to domestic B2B transactions between German businesses. It is especially relevant for companies with German entities, German VAT registrations, or domestic invoice flows in Germany. Private consumers are not affected by the B2B rules.
A standard PDF is not enough when structured e-invoicing is required. A compliant e-invoice must contain structured data that can be processed electronically, typically through formats such as XRechnung or ZUGFeRD.
XRechnung is an XML-based format widely used for German public-sector invoicing. ZUGFeRD is a hybrid format that combines a readable PDF/A-3 with embedded structured XML. Both are relevant to German e-invoicing.
Peppol is commonly used in B2G scenarios, but it is not generally mandatory for all B2B e-invoicing in Germany. B2B delivery depends on the format, customer requirements and agreed exchange channel.
Let's discuss how we can help you move from complexity to clarity.