Knowledge · E-invoicing
E-invoicing mandate 2027: what your software must be able to do by 1 January
Invoices your software must issue as e-invoices from 2027
The obligation depends on two characteristics: the customer who issues the invoice and the individual invoice. You will find the deadlines and thresholds in detail in the factsheet E-Invoicing in Germany.
| Invoice case | In 2027 | From 1 January 2028 |
|---|---|---|
| Domestic B2B invoice, issuer with more than €800,000 total turnover in 2026 | E-invoice or, with the recipient’s consent, EDI | E-invoice; EDI only with extraction in line with EN 16931 |
| Domestic B2B invoice, all other issuers | Paper or, with the recipient’s consent, PDF or EDI | E-invoice; EDI only with extraction in line with EN 16931 |
| Invoice from a small business under § 19 UStG | no obligation (§ 34a UStDV) | no obligation |
| Small-amount invoice up to €250 (§ 33 UStDV) | no obligation | no obligation |
| Travel ticket (§ 34 UStDV) | no obligation | no obligation |
| Tax-exempt supply under § 4 nos. 8 to 29 UStG | no obligation | no obligation |
| Invoice to private individuals (B2C) | no obligation | no obligation |
Sources: German Federal Ministry of Finance (BMF), FAQ on e-invoicing and IHK Region Stuttgart.
Your software therefore needs a flag per customer and a rule per invoice.
Flag in the company master data
A flag in the company master data (“E-invoicing mandatory from”) shows from when a customer must issue e-invoices and allows you to notify them in good time. Regardless of this, the feature itself should be available to all customers, because customers below €800,000 may already issue e-invoices in 2027.
Accounting and ERP software can derive the previous year’s total turnover from the posted revenue. In doing so, it must include all of the company’s turnover, not only the turnover recorded in its own client.
Invoicing programs without accounting should ask for the value during onboarding and store it. As total turnover for 2026 is only fixed after the end of the year, activation on 1 January 2027 is the safe route for customers close to the threshold.
Rule per invoice
The exceptions in the table release customers from the obligation, but they do not rule out the e-invoice. It therefore makes sense to generate e-invoices for all invoices to domestic businesses, including small-amount invoices, travel tickets and tax-exempt supplies. The recipient’s consent is not required for this. That way every invoice meets the obligation, even if an exception has been classified incorrectly. Your customers then run just one process for all B2B invoices.
For recipients abroad, your software can check before sending whether the recipient can be reached via Peppol and then, with the recipient’s consent, transmit the invoice as an e-invoice via Peppol. Invoices to private individuals and to recipients abroad who cannot be reached are still generated the previous way.
E-invoicing features of your software
Generating e-invoices
An e-invoice is a structured file in line with the EN 16931 standard. Permitted formats include XRechnung, Peppol BIS Billing 3.0 and ZUGFeRD from version 2.0.1, except for the ZUGFeRD profiles MINIMUM and BASIC-WL. Your software can transmit all three formats via Peppol, by email or via portals. Which format makes sense when is compared in our article XRechnung, ZUGFeRD and BIS Billing 3.0.
All mandatory information under sections 14 and 14a UStG must be in the structured data record. A reference to an attached PDF file or a link is not sufficient. Check your data model against the mandatory fields of the standard, for example seller and buyer details with tax number or VAT ID (BT-31, BT-32, BT-48), invoice number and date, delivery date (BT-72) or service period (BT-73, BT-74) and the tax breakdown per tax rate (BG-23).
For tax-exempt supplies, a note on the tax exemption is mandatory; for reverse charge, a note that the recipient of the service is liable for the tax (§ 14a (5) UStG). Both notes are given in the structured data record as the exemption reason (BT-120).
Mapping invoice types
The obligation applies to all invoice types your software generates. Each type needs the right document type (BT-3) from the UNTDID 1001 code list.
| Case | Document | Type code (BT-3) |
|---|---|---|
| Invoice, including advance and final invoices | Invoice | 380, advance invoice 386 |
| Invoice correction that replaces an incorrect invoice | Corrected invoice with reference to the original invoice (BG-3) | 384 |
| Reduction or cancellation of an invoice | Credit note with reference to the original invoice (BG-3) | 381 |
| Recipient of the service issues the invoice (self-billing) | Self-billed invoice (Gutschrift) in the VAT sense | 389 |
An invoice correction can also be made as a self-billed invoice if self-billing was agreed in advance and the document clearly refers to the original invoice. If the taxable amount is reduced only by rebates, cash discounts or other price reductions, no invoice correction is required. Your software does not have to generate one in these cases.
For a final invoice, your software must deduct the advance payments received and the tax attributable to them (§ 14 (5) UStG). The individual advance payments may be listed in an attachment that the invoice refers to (section 14.8 (8) UStAE). According to a BMF letter of 23 February 2026, this is also possible as an unstructured attachment for e-invoices until 30 June 2030, provided the structured part of the invoice refers to the attachment. Your software should therefore be able to embed attachments in the data record.
According to the BMF FAQ, advance invoices issued before the respective deadline do not have to be e-invoices. A final invoice in 2027 can therefore refer, as an e-invoice, to advance invoices that were still sent as PDFs.
For the recipient’s software to match a corrected invoice or a credit note, it needs the reference to the original invoice in BG-3 with the invoice number (BT-25) and invoice date (BT-26). If this reference is missing, the recipient may post the document as an additional invoice. Your software should therefore treat BG-3 as a mandatory field for type codes 381 and 384, even if the standard does not require the reference in every case.
For recurring invoices, for example for rent or maintenance, a one-off e-invoice is sufficient as long as the price and service do not change. For contracts that serve as an invoice before 1 January 2027, an e-invoice is only required once something changes. Subscription and contract software should therefore store per contract whether an e-invoice already exists.
Maintaining recipient master data
For sending, your software needs additional master data per recipient. This includes the address for incoming invoices, the Peppol ID, the preferred format and the buyer reference (BT-10). The XRechnung format requires a buyer reference in every invoice, but many recipients in B2B business do not specify one. In this case, your software should alert the user before sending.
Validating before sending
Your software should check every generated invoice against the XML schema, the business rules of EN 16931 and the rules of the selected profile before it leaves the system, and store the validation report with the invoice. To classify the messages, the BMF has distinguished three error classes since its letter of 15 October 2025.
Format errors are violations of the syntax, for example of the XML schema. They turn the file into an “other invoice” and should therefore stop the sending.
Business rule errors are only relevant if they affect mandatory information. Only these should stop the sending; all other messages can be shown as notes.
Content errors, such as a wrong tax rate, are not always detected by validation. It only checks tax rate, tax category and amounts for consistency. Factual correctness remains the job of your invoicing logic.
How to evaluate the messages is shown in our article Validating e-invoices and reading the validation report correctly.
Transmitting
The legislator does not prescribe a transmission channel. Email, interfaces, portals or the Peppol network are all permitted. Peppol is an approved channel, but not mandatory. An email inbox is sufficient for receiving. Your customers agree with their business partners on which channel they use.
Your software should therefore offer at least two channels. Sending as an email attachment can reach any recipient. Sending via Peppol also provides a delivery status per invoice and makes the transmission more secure. The Access Points are certified by OpenPeppol and transmit every invoice signed and encrypted.
Recipients are registered in the network via their Peppol ID. This makes fake invoices and manipulated bank details, as they can occur with email sending, more difficult.
The AS4 receipt in the Peppol network confirms receipt by the recipient’s Access Point, not processing in the recipient’s system. Whether a document could be processed by the target system is reported by a “Message Level Status” (MLS). This new procedure in the Peppol network is in its introduction phase until mid-2027 and is not yet supported by all service providers.
Whether a recipient can be reached via Peppol and can receive the document type is shown by a lookup of their Peppol ID before sending, for example with the Peppol ID lookup.
Receiving and processing
Since 1 January 2025, receiving e-invoices has been mandatory for all domestic businesses, including small businesses. Your software should read incoming XML files, process the XML part of hybrid formats as the authoritative content and display the invoice in a readable form for the user. If the XML part and the PDF image differ, the XML part applies. Your software should also validate incoming e-invoices and store the validation report with the invoice.
For your customers to receive e-invoices via Peppol, they need their own Peppol ID registered in the network. Your software should therefore include registration in onboarding.
Archiving
E-invoices must be retained for eight years (§ 14b UStG). What has to be retained is the structured data record in its original format, unchanged and machine-readable. Storing only the PDF image is not sufficient. Your software should store the XML file, validation report and delivery status together with the invoice, regardless of whether the archive is in the product or in a connected DMS.
Six steps to e-invoicing by 1 January 2027
We recommend starting with the customers who must issue e-invoices from 1 January 2027.
-
Flag affected customers
Set the flag in the company master data for all customers who must issue e-invoices from 1 January 2027. Inform these customers early and select some of them as pilot customers so that you can try out the feature under real conditions before the deadline.
-
Complete generation and validation
Generate a test invoice for each invoice type and validate it against EN 16931 and the selected profile. The validation reports show which mandatory fields are still missing in your data model.
-
Connect the sending channel
Connect email sending with an XML attachment. For customers who need a delivery status, add sending via Peppol. Before every Peppol sending, check whether the recipient can be reached there and which formats the recipient supports. If in doubt, talk to your service provider.
-
Take pilot customers live
Have your pilot customers send real invoices to real recipients. Evaluate the feedback and adjust the error messages so that users understand them without specialist knowledge.
-
Rollout and user help
Activate the feature for all affected customers. Help texts on the error classes and on the recipient’s consent help your customers classify messages correctly and can reduce queries to your support team.
-
Prepare for 2028
Activate e-invoice sending on 1 January 2028 for all remaining customers, unless they already use it. Point out to customers with EDI connections that EDI remains permitted with the recipient’s consent until 31 December 2027, regardless of turnover, and from 2028 only if the invoice details can be extracted from it correctly and completely into a format in line with EN 16931 (§ 14 (1) sentence 6 no. 2 UStG). This leaves your customers the year 2027 to agree the switch with their business partners.
How to test the e-invoicing features of your software
Generation
Generate a test invoice for each invoice type and each tax case, i.e. for the standard tax rate, reduced rate, tax-exempt supplies, reverse charge, intra-Community supplies and invoices from small businesses.
Also test credit notes and corrected invoices with a reference to the original invoice, final invoices with deduction of advance payments, and invoices with allowances and charges at document level, because totalling and rounding errors can occur there.
Check every file with a validator against the XML schema, EN 16931 and the profile. The e-invoice validator checks individual files without registration.
Sending
Test sending by email and via Peppol with real recipients. Also check the cases in which sending fails, for example when a recipient cannot be reached via Peppol or validation reports a format error. Your software should then stop the sending or offer another channel and clearly show the user what to do.
Receiving
Test receiving with invoices from third-party systems, for example XRechnung in CII and UBL syntax, Peppol BIS Billing 3.0 and ZUGFeRD in several profiles. Also check faulty invoices and hybrid invoices in which the PDF image and XML part differ. For hybrid invoices, your software should process the XML part.
Archiving
Check whether the XML file, validation report and delivery status are stored unchanged with the invoice and can still be retrieved after an update of your software.
Rule set updates
Integrate validation into your build pipeline so that every change to the invoice export is checked against the current rule set. Peppol BIS Billing 3.0 receives a new release twice a year, in May and November, and new versions of XRechnung are also published. Check your test invoices again after every new release.
Tasks InvoiceRails can take over
If you do not want to build the technical implementation yourself, you can outsource most of it to a Peppol Access Point. With InvoiceRails, you generate and validate e-invoices via API, check whether the recipient can be reached before sending, and receive delivery status and incoming invoices via webhook.
InvoiceRails also handles the registration of your customers in the Peppol network and the ongoing maintenance of the validation rules. You connect one interface and offer e-invoicing to all your customers, without operating an Access Point, certificates and directory services yourself.