It has now become almost a tradition: On October 15th, the Federal Ministry of Finance publishes a letter regarding E-bill. In 2024 came the policy letter, in 2025 the first supplement, and now, on October 15, 2026, the third one. Two and a half months before the day when companies with more than 800,000 euros in previous year sales will only be allowed to issue their B2B invoices as e-invoices.
Those who hoped that BMF If the deadline is pushed back again, people will be disappointed. January 1, 2027, remains. What the letter instead provides is a mix of real relief for special cases and a requirement that is not yet cleanly met in many SAP systems today: The performance description must be in the structured XML part, not in the PDF view.
We have reviewed the ten-page document and tell you what is really important for SAP users – and where you should look in the coming weeks.
What writing is – and what it is not
The letter with the case number III C 5 – S 7287-a/00019/021/017 does not replace the two predecessors. It supplements them in the places that have provided the basis for discussions in practice and amends nine places in the VAT application decree. The additional regulations are set out in the footnotes 1 to 28, and the VAT AE changes begin at footnote 29.
Three things to note in advance so that no false expectations arise:
- No new deadline. From January 1, 2027, companies with a total turnover of more than 800,000 euros in the previous year must issue e-invoices for domestic B2B sales. The relevant threshold is the total turnover in 2026. Starting January 1, 2028, the obligation applies to all other companies.
- No new format. The document does not introduce a new XRechnung version or a new ZUGFeRD profile; it explains tax requirements, not technical standards.
- No claims until the end of the year. E-invoices issued by December 31, 2026 remain exempt from withholding tax if they meet the requirements of the 2024 and 2025 letters. The additional requirements from 2026 therefore take effect on January 1, 2027 – along with the obligation to issue them.
The Central Association of the German Crafts had called for the start for larger companies to be postponed to 2028 in June. The BMF did not accept this. The grace period applies to substantive details, not to the introduction itself.
The central refinement: The performance description belongs in XML
This is the point that takes the most work in SAP projects. In an e-invoicing project, the structured dataset is crucial – in XInvoice the XML file, in ZUGFeRD the XML embedded in the PDF. What is displayed in the view does not count for tax purposes.
The BMF now specifies in the footnotes 10 to 12 what must be included in the structured part: type of benefit, scope of benefit, benefit amount and, if applicable, the place of benefit delivery. This is specified in such a clear way that it alone can be used to assess whether a delivery or other service exists, where it was provided, whether the tax rate is correct and whether the recipient is generally entitled to the tax deduction. The BMF calls this the control function of the Invoice.
Specifically, this means that terms like „consulting services,“ „assembly,“ „service according to the agreement,“ or „service as specified in the PDF file“ are no longer sufficient. From 2027 onwards, anyone who issues an invoice with such a position and has the details in the contract or in a separate document risks not receiving the input tax deduction from their customer. An insufficient description of the service is not a formal error, but an internal error.
What is allowed in the appendix – and how
The good news: Not every detail has to be included in the XML fields. Additional information, such as the breakdown of hourly payments or a distribution key, may be included in an attachment. However, there are two conditions:
- The appendix must embedded in the e-invoice His – as a base64-encoded document in XML (Business Group BG-24) or as an embedded file in the ZUGFeRD PDF. A second file in the same email explicitly does not meet this requirement.
- In the structured part, it must clearly referred to the appendix become.
The information required for the control function must nevertheless remain in the structured part. The annex supplements, it does not replace.
In this context, the BMF explicitly recommends the assignment table of KoSIT and FeRD, which assigns each sales tax-related mandatory entry under §§ 14 and 14a UStG to a specific field of EN 16931. Those who want to check whether their own mapping is correct have the reference to do so.
The relief: Where the BMF takes the pressure off
A large part of the writing answers questions that have been asked of us in recent months in almost every project. The answers are mostly pragmatic.
Advance payment and deposit invoices do not need to be paid again (item 2). Anyone who still allows a bill of materials in paper or PDF format in December 2026 will not have to submit an e-invoice for this – even though the delivery and payment will not take place until 2027. The change of year brings a lot of uncertainty, especially for project business with long lead times.
Final calculations: two ways of presenting the data by mid-2030 (paragraphs 3–4). Part payments already received and the corresponding sales tax must be deducted from the final calculation. The BMF accepts two variants for this: Either the sum of the paid deductions is entered in field BT-113 („Paid amount“) and the necessary details are entered in the free-text field BT-22, or the deduction is made in an embedded appendix that is referred to in the structured part. The previously limited appendix solution will thus be extended by two and a half years until the end of 2027.
Construction works: The scope and amount of work are sufficient (paragraphs 13–14). Extensive performance lists cannot currently be represented in the core data model of EN 16931. Therefore, in the structured part, it is sufficient to list the individual trades with their sums; the detailed performance list follows as an embedded, readable appendix. An additional structured file, for example in GAEB format, is possible. The BMF deliberately does not specify a fixed end date here.
Gross price calculations: lump sum solution until the end of 2027 (Items 17–19). The EN 16931 calculates from a net basis. Those who have gross prices – the classic example being priced books – receive rounding differences in the calculation. Therefore, until December 31, 2027, the structured part may only include the total amounts per tax rate, while the individual items are presented in an embedded appendix. For the trade sector, this is one of the most relevant statements in the letter.
Discounts, bonuses, and deductions (Items 15–16). If the amount of a agreed reduction in remuneration is not yet fixed at the time of invoicing, a general reference to the written agreement is sufficient. If the agreement changes later, the invoice does not need to be corrected.
Mass business (Items 5–7). In the case of continuous debt relationships with a mixed customer structure – the BMF refers to energy deliveries – it is sufficient to clarify the customer’s entrepreneurial status at the start of the contract or when changes are made. Regular inquiries during the term of the contract are not necessary.
Fees notices (Items 26–27). Decisions on public-law taxes that are also calculated in this way may be issued as other invoices until June 30, 2030. Relevant for municipal companies and associations.
Red validation message, correction, fine: three clarifications with an asterisk
Business regulatory errors are not automatically tax errors (Paragraphs 22–23)
Anyone who has ever sent an XInvoice through the KoSIT validator knows this: The file is marked as invalid because a business rule of the core data model is violated – for example, a sum rule or a missing mandatory field that is not relevant from a tax perspective. The BMF now explicitly distinguishes between technical compliance with the standard and its classification for VAT purposes. A file with business rule errors but no format errors remains, in principle, an e-invoice from a tax perspective. A tax error only occurs when the violation concerns a mandatory requirement.
The catch: This helps the invoice issuer fiscally, but not operationally. An official portal or an automated system would be more effective. Invoice receipt When presented to the customer, a file that does not conform to technical specifications is still rejected. For the invoice entry, the opposite is true: A red alert is not a reason to reflexively reject a supplier invoice; it is a reason to look at the relevant field. This is exactly what validation in the entry process requires, which can distinguish between „technically unsightly“ and „taxationally inadequate“.
Corrections: The chain must remain readable (paragraphs 20–21)
If there is an obligation to issue an e-invoice, the correction must also be made as an e-invoice with the appropriate invoice type. The BMF does not prescribe any specific technical procedure. What matters is that the original invoice and all corrections together clearly show the most recent information. A correction invoice without a discernible link to the original document prevents this clarity. It has also been newly added that a correction can also be made as a credit by the recipient of the service – if this has been previously agreed upon and the credit clearly refers to the original invoice.
No fine – but no license to operate (Paragraph 28)
The question has arisen in every webinar in recent months: What happens if, despite the requirement, I send a PDF invoice starting in 2027? The BMF now clarifies that there is no violation of the law under § 26a, paragraph 2, no. 1 of the Value Added Tax Act (UStG).
Anyone who reads this as a warning is reading it incorrectly. The invoice will then not be a proper invoice. Both parties bear the consequences: For the recipient, the pre-tax deduction is at risk; he has a civil law claim for a proper invoice, and in the tax audit the deficiency can be identified. The risk shifts from the fine list into the customer relationship – and that is more expensive in practice.
What this means specifically in the SAP system
Tax advisor blogs explain what writing requires. We explain where it breaks down in the system. From our CBCS and CICS projects, we know the places where the new requirements typically arise.
The position texts. In SD, the position description usually comes from the material brief – 40 characters, often cryptic, understandable to people in sales, but not to an operations auditor. In FI invoices that are generated directly via FB70 or from billing schedules, there is often only the booking text. Both end up in field BT-153 („Item name“) and usually do not suffice for the control function. The solution rarely lies in modifying the master data, but in mapping the position brief and header texts to BT-154 („Item description“) and BT-22 („Invoice note“). This is mapping work, not development work – but it has to be done, and that applies to each type of document.
The performance location. For deliveries, the delivery address is included in SD and can be included in the BG-13 delivery group. For other services – advice, maintenance, installation – there is often no field in the standard system that indicates the location of the service. It is necessary to clarify where the information comes from: from the customer order, the service order, or from a customer text.
The attachments. Anyone who today sends hourly invoices, performance lists or distribution keys as separate PDFs by e-mail no longer meets the requirement from 2027 onwards. The documents must be embedded in the XRechnung (BG-24) or ZUGFeRD PDF. This requires that the document be available at the time of conversion – from the DMS, from an invoice generation workflow, or from the output management. This exact link is the reason why we CBCS and the SmartDocs The annex must be attached to the document before the electronic invoice is generated.
Deposit and final bill. The SD standard with advance payment requirements and advance billing in the final invoice works – but the debits must be represented correctly in the XML. The BT-113 solution with details in BT-22 is the simpler way in most projects, because it works without an embedded attachment. Those who have previously relied on the attachment solution can keep it thanks to the extension until mid-2030.
Gross prices in retail. For retail customers with gross prices, the lump-sum solution is the practical bridge until the end of 2027. It avoids the discussion about rounding differences in BT-114, but only buys time. By 2028 at the latest, a clean net logic or a format that natively supports gross prices will be needed.
Correction chains. Cancellation, credit note and correction invoice in SD generate their own documents, but the reference to the original document does not automatically end up in BT-25 („Preceding invoice reference“). Without this reference, the correction chain in the XML is not readable. This is a mapping point that almost always appears in test cases.
Invoice entry: The validation must be able to distinguish between format errors, business rule errors without a tax-related connection, and violations of mandatory information requirements. An entry solution that rejects the proof for every red alert will produce unnecessary follow-up questions from suppliers starting in 2027.
If you are unsure about whether your system supports these points today: Take three typical output invoices, run them through the converter and look at the XML – not the PDF. It will take an hour and will tell you more than any checklist.
All deadlines at a glance
| Starting date | What applies |
|---|---|
| 31.12.2026 | End of the general transition period. E-invoices issued by then will remain valid if they meet the requirements of 2024 and 2025. |
| 01.01.2027 | Exhibition obligation for companies with a total turnover of more than €800,000 in 2026. The additional requirements of the 2026 letter apply. |
| 31.12.2027 | End of the extended transition period for companies with up to €800,000 in previous year sales and for EDI procedures with the consent of the recipient. End of the lump-sum solution for gross price invoices. |
| 01.01.2028 | Exhibition obligation for all domestic B2B sales, regardless of the sales volume. |
| 30.06.2030 | End of the relief for the deduction of deductions in final accounts and for fee notices as other invoices. |
| from 01.07.2030 | ViDA: Digital reporting obligations for intra-community B2B sales replace the Summary Report. A national reporting system for domestic sales is being prepared. |
The BMF does not specify an end date for the construction performance rule; it is valid until further notice.
The writing is fair – but it shifts the work to XML
One cannot blame the BMF for ignoring the practice. The concessions for advance payments, construction work, gross prices and mass sales target exactly the cases that have caused the most friction in the transition. And clarifying business rules errors takes the wind out of a debate that has cost unnecessary time in many projects.
At the same time, writing something clearly makes it clear: Starting January 1, 2027, the XML will be the proof. Not the PDF, not the printout, not the attachment in the email. Anyone who previously had the performance description in the view and considered the XML as a technical annex must think again – and that within the next nine weeks.
Our recommendation in three steps:
- Go through the types of documents. Which of your original invoices contain position texts that do not explain what was actually paid? What documents do external parties have today? Which final invoices include deductions?
- Read XML, not PDF. For each type of document involved, generate a test invoice and check the fields BT-22, BT-153, BT-154, BG-13, BG-24 and BT-25 against the KoSIT assignment table.
- Customize the mapping before the requirement takes effect. The non-charging until the end of the year is exactly designed for that purpose.
Whether you are even subject to the obligation from 2027 is determined by our e-Invoice Mandate Checker in two minutes. The format that suits your customers is shown by the Format decision-maker. And if you want to know what your invoices look like in XML before a verifier does it: Contact us. We will look together at your test invoices.


