On March 23, 2026, Germany’s Federal Ministry of Finance (BMF) released an updated FAQ document on the upcoming mandatory B2B e‑invoicing rules. The revised guidance (in particular, questions 7a and 7b) provides important clarifications on what must be included in an electronic invoice (E‑Rechnung) and how to handle references to other documents. While these clarifications are consistent with the letter of the law and prior administrative guidance, they introduce a stricter interpretation that may present practical challenges for businesses.

Key Clarifications in the March 2026 FAQ

Complete information in the XML: The updated FAQs reiterate that all mandatory invoice information (as per German VAT law) must be included in the machine-readable XML portion of an e‑invoice. In practice, this means that fields such as the invoice date, invoice number, seller and buyer details, description of goods/services, and the amount and VAT breakdown cannot be provided only in a PDF or image attachment—they must be part of the structured data. The purpose of an “electronic invoice” is to enable automated processing; therefore, if any required detail is omitted from the XML and exists only in human-readable form, the invoice will not be considered a valid E‑Rechnung.

No external-only references: The FAQs go further by addressing how invoices can reference additional documentation. According to the new guidance, it is not sufficient to refer to a contract, statement of work, or delivery note unless that document is physically attached to the e‑invoice and forms part of the invoice file itself. In other words, an e‑invoice must be a self-contained package: any document that an invoice “points to” for details or supporting information should also be included as an annex within the same transmission (for example, as a PDF file embedded in a hybrid invoice). Simply providing a hyperlink or an email reference to an external document does not meet the requirements of the electronic invoicing mandate.

These clarifications in the March 2026 FAQ largely reflect the strict interpretation already set forth in the BMF’s binding administrative letter of October 15, 2025. That letter explicitly stated that a compliant e‑invoice must contain all required data in the structured format and that a reference in the XML to an external document (where the actual information resides) is not acceptable. It allowed supplementary information to be provided in an attachment within the e‑invoice (for instance, a detailed timesheet as a PDF) but warned that a link to an external source or any document not included with the invoice would not meet the legal requirements. The updated FAQ further elaborates these points through practical Q&A-style explanations and examples, covering scenarios such as summary invoices, invoice corrections, and project-based billing:

• Monthly summary invoices (Sammelrechnungen) remain permissible, meaning that a single e‑invoice can cover all deliveries in, for example, March 2026 by indicating “March 2026” as the performance period in the XML. This is not a change in policy; rather, the FAQ confirms that businesses may continue the practice of issuing one invoice per month, as long as the structured data clearly indicates the period of supply.
• Revising an e-invoice (Rechnungsberichtigung) must be done electronically once e‑invoicing is mandatory. The FAQ confirms that, after the transition period, a correction or credit note must itself be an e‑invoice, not a paper or PDF document. Notably, it clarifies that a correction can take the form of a follow-up e‑invoice referencing the original (for example, a negative line item or a separate adjustment document that cites the initial invoice number). During the current grace period (through 2026, or 2027 for small businesses), companies can still issue fixes in the old way, but they should prepare for a fully digital correction process going forward.
• Project invoices (construction, long-term contracts) are addressed with practical guidance. For instance, in construction invoices, the itemised breakdown of work can be provided in a PDF attachment (to avoid overloading the XML), as long as the e‑invoice’s XML contains a summary of each billed item or trade and explicitly references the attached document. Similarly, for final invoices that reconcile multiple prepayments, the new guidance confirms that it is sufficient to list the total of earlier payments as a deduction in the XML, while detailed schedules of those payments can be included in an attached document. The critical caveat is that these attachments must be transmitted with the e‑invoice and clearly referenced in the structured data. By contrast, any reference to documents not included (e.g. hosted on an external portal or sent separately) would render the invoice non-compliant.

Bottom line: The BMF’s FAQ update reinforces the principle that an e‑invoice should stand on its own as a complete, machine-readable record of the transaction, without relying on external documentation. This approach is understandable from a tax compliance and future digital reporting perspective—ensuring that tax authorities can rely on the XML data alone for audits or a potential real-time reporting system. However, it also introduces operational challenges for businesses.

Operational Concerns and Open Questions

The heightened requirements in the 2026 FAQ have prompted discussion within the business community. Several practical concerns have emerged:

• Potentially massive file sizes and transmission issues: 

By mandating the inclusion of annexes (contracts, statements of work, delivery notes, etc.) with each invoice, the file size of E‑Rechnungen will increase—in some cases significantly.

• A typical XML e‑invoice might be only a few kilobytes but adding a multi-page PDF contract or detailed timesheets could increase the file to several megabytes. 
• This raises questions about email delivery (as many mail systems impose attachment size limits) and the storage and archiving burden on both suppliers and buyers.

Companies may need to ensure that their e‑invoicing platforms and clients can handle larger files without errors.

• Unclear added value of embedding external documents: 

The requirement to attach every referenced document is seen by many as excessive. All the critical invoicing data—the information needed for VAT purposes and journal entries—is already required to be in the XML structure. 

• Attachments such as contracts or delivery notes are typically PDFs or images that are not machine-readable, and do not enhance automated processing.
• In current practice (and under existing legal precedent), invoices have often referenced external documents (e.g. “see contract #123 for details”) without including them, provided the reference was clear and the core VAT details were present. 
• The updated FAQ limits this long-accepted practice, despite prior tax court decisions that were more permissive.

This may create uncertainty as to whether all supporting documents, regardless of length or complexity, must now be included with the e-invoice.

• System and process readiness: 

These clarifications may require changes to how companies generate invoices. ERP and billing systems must be configured not only to populate all fields in the XML, but also to automatically attach supplemental documents where necessary. 

• This may require integration between invoicing systems and contract/document management platforms. 
• There is a compliance risk if an attachment is omitted or the references are unclear, potentially rendering invoices non-compliant. 
• Existing agreements with customers and suppliers may need to be revisited, as large attachments may not have been anticipated or agreed upon.
• Impact on efficiency: 

One of the promises of e‑invoicing is streamlined, automated processing. However, the need to embed all referenced documents may undermine this efficiency.

• Large files increase processing loads on accounts payable and receivable systems.
• Large attachments may slow down invoice transmissions and require additional data handling capacity on both ends. 
• Version control risks may arise if multiple versions of supporting documents exist.  

Organisations will need appropriate controls to ensure the attached documents are up to date and consistent with the XML references.

Conclusion

The BMF’s March 2026 FAQs provide much-needed clarity on Germany’s path to mandatory B2B e‑invoicing, but they also reflect a more stringent interpretation that may require businesses to adjust their processes. While the requirements for complete structured data and embedded attachments are rooted in the goal of maximizing electronic readability and auditability, their practical benefit may be questioned when weighed against potential operational impacts.

Companies operating in Germany should carefully assess these new clarifications and consider whether their invoicing systems are prepared to comply. In particular, firms may need to update invoice templates, integrate document management with invoicing software, and test the handling of invoices with large attachments to ensure smooth transmission and receipt.

It is worth noting that the FAQs themselves are not legally binding; they are an interpretative aid, albeit one that clearly reflects the BMF’s official expectations in line with the binding October 2025 administrative guidance. Many finance and tax professionals are now considering whether the tax authorities might adopt a pragmatic approach in enforcement or if further adjustments will be made, especially regarding the requirement to include all referenced documents in the invoice file. Given that these guidelines appear to extend beyond prior common practice (and even beyond what courts have traditionally allowed in paper invoicing), some flexibility or further clarification may be required to avoid unintended consequences.

From a broader perspective, these stringent measures indicate that Germany is laying the groundwork for a future real-time digital reporting system (as part of the EU’s “VAT in the Digital Age” initiative). The push for fully self-contained, data-rich invoices ensures that tax-relevant information is readily available for automation and analytics. However, until the systems and processes are fully aligned, businesses will need to balance compliance with practicality. It’s crucial for German companies – and foreign companies invoicing German customers—to proactively engage with these developments.

Executive takeaway: Ensure your e-invoicing solution meets the new criteria. All required fields belong in the XML, and if you reference any other document, plan to attach it. At the same time, be mindful of the impact on your operations. Investing in document management integration and robust invoice processing tools can help manage larger e‑invoice files and maintain compliance without sacrificing efficiency. In the coming months, as full implementation of the e-invoicing mandate approaches, staying informed and preparing for these nuanced requirements will be key. Businesses should also be ready to adapt if further official guidance or practical concessions emerge—for example, with additional clarity on when an attachment is required.

The updated FAQs have clarified the rules of the game; now it’s up to companies to play by those rules while finding smart ways to minimize disruption. As we often remind our clients: e‑invoicing is not merely an IT project—it’s about compliance, cash flow, and maintaining smooth operations. The challenge will be to implement these new rules in a manner that upholds tax compliance without undermining the efficiencies that digital invoicing promises.

Source: European Parliament, Deal reached on Union Customs Code reform, press release, 23 March 2026.