E-Invoice: Legal Provisions Simply Explained
March 19, 2026 | Reading time: Approx. 8 minutes

Product Manager at FIS
How to properly fulfill the e-invoice obligation – and what does it mean in legal terms? This blog clearly explains what legal provisions apply, why structured data is decisive and how companies successfully master the implementation step by step.

Who does the e-invoice obligation apply for?
Basically, the legal provisions apply for all companies receiving or issuing invoices. There are some transitional rules; however, there is no getting around the complete implementation of electronic invoicing in the long run.
As far as the e-invoice obligation is concerned, it is important to differentiate between two roles:
It is often underestimated in practice that the obligation to accept is the first and most important step. Even companies that (still) do not issue invoices in an electronic format, must be able to receive such invoices.
What are the legal requirements with regard to e-invoices?
The statutory provisions from the e-invoice regulations can be broken down to four core elements:
The crucial point: The legal requirements do not only concern a specific file format but a functioning and lawful business process with consistent electronic processing.
What does it mean to be able to receive e-invoices?
Many companies believe they are prepared because they can technically open e-invoices, for instance as XML files. However, this is not legally sufficient for business transactions.
E-invoices must:
This does not only concern IT but also, above all, corporate accounting, purchasing and the user departments. This is exactly where, in practice, the largest uncertainties occur when implementing the e-invoice obligation.
What does it mean that electronic invoices must be readable?
Electronic invoices must be issued in such a way that they can be technically processed in an electronic format and, at the same time, be technically understood. It is crucial that the relevant information is clearly visible to the employees.
This means:
A mere technical processing without professional visual inspection does not fulfill the legal requirements concerning electronic processing.
What does completeness and traceability of e-invoices mean?
It is part of the legal obligation that an invoice contains all statutory specifications and that its issuing is traceable. This does not only concern the individual document but the entire verification and editing process.
This means in practice:
Only if this process is transparent can invoices be safely checked also at a later date, for instance as part of internal controls or external checks.
What does the proper archiving of an e-invoice mean?
Electronic invoices must be stored in such a way that they are trackable, readable and unchanged at any time. Therefore, archiving is an essential part of the legal requirements.
For invoicing parties and recipients this means concretely that
Usually, a simple storage on a disk drive or in the e-mail inbox is not sufficient for this purpose.
What does the technical e-invoice verification in invoice receipt look like in practice?
In the daily business, the statutory regulations concerning e-invoices are complied with in invoice receipt, where invoices are actually edited. Irrespective of how they are received, i.e. as structured e-invoice, PDF document or in paper form, they must be technically checked, transparently edited and correctly transferred to Financial Accounting.
In practice, this means that all different input formats must be combined, parked and checked according to standardized technical criteria. The type of document does not matter. What matters is a clearly structured process that creates transparency and makes deviations specifically visible.
Invoice receipt solutions support exactly this approach. They enable the technical and content-related verification of incoming invoices directly in the SAP system, irrespective of the input form. Here, structured e-invoice formats, such as XRechnung or ZUGFeRD, can be processed as well as paper invoices entered via OCR or PDF invoices.
This is particularly relevant for the access to electronic invoicing. At first, companies implement a stable and lawful invoice receipt by parking and checking invoices and edit them according to the “management by exception” principle. Invoices without deviations can be posted directly whereas differing processes are transferred to the responsible user departments in a targeted and transparent way.
As a result, the e-invoice is not treated as a special case but as a regular component of a controlled invoice receipt process, i.e. precisely where the legal requirements of the Federal Administration have to be practically implemented.
What happens next?
Once the invoice receipt process is stable, further steps for invoice exchange can be clearly planned:
The legal requirements provide a framework for issuing and receipt. How efficiently you fill this framework is your decision. Further information concerning a suitable e-invoicing solution can be found here.
Conclusion
The e-invoice is no isolated Federal Administration provision but a legal obligation which was first implemented in B2G for public authorities and now also increasingly concerns the B2B sector. It is therefore far more than just a question of IT: it concerns both invoice receipt and invoicing.
It is not enough to reduce the e-invoice to file formats such as XML instead of PDF or individual tools.
What is crucial:
In this way, the obligation to digitize becomes a controllable process and uncertainty turns into a manageable project.

Questions about this topic? Our team will be happy to assist you personally.

Read, take a look, inform yourself
In our download section, you will find a large number of SAP contents worth knowing – expert talks, white papers and flyers. To find right away what you are looking for, please use the filter function for topics and content type.