Skip to content

E-Invoice: Legal Provisions Simply Explained

Author: Jens Wolf
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.
Home | Blog | E-Invoice: Legal Provisions Simply Explained

E-Invoice: Legal Provisions Simply Explained

March 19, 2026 | Reading time: Approx. 8 minutes

data & process management
finances
market & innovations

Jens Wolf

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.

The e-invoice obligation is no longer a future vision but has already become reality both in the B2G and B2B area. It is true that many companies know by now that they must process electronic invoices but not exactly what this means in legal terms and how best to start.

This article clearly explains the legal requirements and provides compact information on electronic invoicing. It also explains the legal bases from e-invoice regulations and shows how to implement e-invoicing successfully in practice.

What is an e-invoice in the legal sense?

An e-invoice is not just a PDF file sent via e-mail. Legally, it is a structured e-invoice presented in a required electronic format that can be read automatically. This standardizes the exchange of invoices between companies and makes it much more suitable for automation.

It is based on the European CEN standard EN 16931, which defines the structure of an electronic invoice. In Germany, this obligation has first been implemented in the public procurement sector, in particular for vendors of the Federal Administration. Now, comparable provisions also apply for the B2B area so that the structured electronic invoice exchange between companies gets more and more compulsory.

The crucial point: The invoice does not only consist of a “readable document” but also of structured data of an invoice data model that IT systems can process without manual interim steps. Exactly this structure is the prerequisite for the efficient and legally compliant execution of invoice verification, posting and archiving.

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:

  • erstensInvoice recipient: Companies must be able to receive e-invoices and process them properly.
  • zweitensInvoicing party: In the future, any person issuing invoices, i.e. acting as an invoicing party, must be able to provide an invoice as structured electronic invoice as well, irrespective of the consent of the invoice recipient, if the legal requirements provide for this.

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:

  • erstensAbility to accept
    Companies must be able to receive electronic invoices both in technical and organizational terms.
  • zweitensReadability and technical verifiability
    The invoice must be issued in such a way that employees can verify its content. Just “opening” the invoice does not suffice.
  • drittensCompleteness and traceability
    All statutory invoice specifications must be included and verifiable.
  • viertensProper archiving
    E-invoices must be stored in an audit-proof and unchangeable manner.

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: 

  • reach the company
  • be sent in such a way that they can be read by the user departments
  • be verified technically (content, sales volumes, reference to service)
  • then be further processed correctly.

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:

  • invoice contents need to be presented clearly
  • mandatory information such as invoice number, date, amounts or tax rates must be clearly identifiable
  • invoice contents must be verifiable, e.g. in comparison with purchase order or service

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:

  • the invoice data completely includes all mandatory information
  • changes, checks and releases are documented
  • the way of an invoice from receipt to posting is traceable

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

  • invoices must not be changed at a later date
  • the original electronic form must be retained
  • invoices must be available during the entire retention period

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:

  • targeted automation where it is really useful, e.g. optimization of electronic invoicing
  • deliberate manual inspection points where technical control remains necessary
  • stepwise extension instead of complex complete changeovers

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:

  • to clearly understand the legal provisions and requirements
  • to consider invoice receipt as a central process and
  • to start the implementation of e-invoices in a structured way and with a clear and realistic first step.

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.