All about e-invoices in the public sector
Since November 2019, federal contracting authorities have been obliged to accept electronic invoices. In April 2020, this obligation came into force for all public invoice recipients at the state and municipal level. This means that authorities, administrations and public companies can no longer refuse electronic invoices and are obliged to accept and process them. On November 27, 2020, the e-invoice finally became mandatory. From this date, authorities will accept only electronic invoices that comply with the European standard (EN 16931). In this blog post, you can find out exactly what you need to bear in mind when using e-invoices for public contracts.
What is a even a “genuine” electronic invoice?
An e-invoice enables the electronic transmission, automated acceptance, and further processing of invoice information. This allows a seamless digital process from invoice creation to payment. In contrast to paper invoices or image files such as PDFs, e-invoices present the invoice content in a structured, machine-readable format.
Accordingly, a PDF format is unfortunately no longer sufficient in the public sector. The legally stipulated format for transmitting invoices is the XRechnung (i.e., a structured data set in accordance with the requirements of the European standard EN-16931). However, the ZUGFeRD format is also compatible with the EU specifications.
Electronic invoice with XRechnung
The XRechnung standard is a specific format for electronic invoices that is based on the text-based XML data format. The structure of the XRechnung, and therefore the e-invoice, is defined by the European standard EN-16931. Each country develops its own Core Invoice Usage Specifications (CIUS) in order to harmonize EN-16931 with national requirements. The XRechnung is therefore the national implementation of EN-16931 for Germany.
Electronic invoice with ZUGFeRD
The ZUGFeRD format is a combination of PDF and XML file. Here, invoices are sent as PDFs and contain the XML data record for extracting the invoice data. This makes the format suitable for both visual inspection and the automated transfer of data to IT systems.
There are exceptions in these cases
In principle, contractors have had to submit electronic invoices to the federal government since November 27, 2020. However, there are also exceptions, which are set out in the ordinance:
- Invoices up to an amount of €1,000 after fulfillment of a direct order.
- Invoices that are subject to the exceptions (e.g., data subject to confidentiality or matters relating to the foreign service and procurement abroad).
- Invoices that are issued in proceedings against restraints of trade.
- Irrespective of the legal obligation, there may also be an obligation to submit e-invoices arising from the respective order or contractual relationship .
How are e-invoices transmitted?
When issuing invoices, suppliers should check in advance whether the recipient is an authority of the indirect federal administration, the direct federal administration, or a state authority. This is because the ways in which the invoice is to be transmitted differ depending on the recipient.
Invoices to the direct federal administration are sent via the central invoice receipt platform (ZRE). On the other hand, invoices to the indirect federal administration are transmitted via the Online Access Act-compliant invoice receipt platform (OZG-RE).
Invoices to institutions of the indirect federal administration and cooperating federal states are submitted via the OZG-RE platform. However, contracting authorities of the indirect federal administration are not obliged to use OZG-RE. Therefore, in some cases, the federal states may have their own solutions in addition to OZG-RE. The contracting authorities then inform the invoice issuers which platform is to be used for submitting invoices. More detailed information such as the available platform can be obtained either via the underlying order or directly from the invoice recipient.
What is a routing ID for the e-invoice?
In order to send an electronic invoice correctly to the recipient, the recipient must be clearly identified and reachable. The routing ID plays a decisive role here. It enables the electronic addressing and forwarding of the e-invoice by the the central invoice receipt platforms of the federal government to the connected ERP or approval systems of the authorities and federal administration institutions.
Public institutions in Germany can be recognized by their routing ID within the Peppol network . Accordingly, public institutions must register at least one of their routing IDs in the Peppol Service Metadata Publisher (SMP) in order to receive electronic vouchers from their business partners. Otherwise, they will remain invisible to their business partners when they try to exchange electronic vouchers with them. The routing ID must therefore be recorded within the e-invoice in order to clearly identify the invoice recipient.
Consisting of a main address, a sub-address, and a check digit, the routing ID consists of 5–44 digits. The main address and check digit are mandatory components. The sub-address is optional. Here is an example:
The structure of the route ID is made up of required and optional elements. The first position of the required element is the two-digit code number of the respective federal state. In addition, the routing ID provides information about the administrative district and the federal and district code. In addition to the basic information, the routing ID can also contain optional key figures such as the municipal association, the municipal code, and precise sub-address.
Key figures of the federal states: Part 1
01 - Schleswig-Holstein
02 - Hamburg
03 - Lower Saxony
04 - Bremen
05 - North Rhine-Westphalia
06 - Hesse
07 - Rhineland-Palatinate
08 - Baden-Württemberg
09 - Bavaria
Key figures of the federal states: Part 2
10 - Saarland
11 - Berlin
12 - Brandenburg
13 – Mecklenburg-Western Pomerania
14 - Saxony
15 - Saxony-Anhalt
16 - Thuringia
99 - Federal administrative units; depending on the number after the 99, the invoice is to be issued via ZRE or OZG
E-invoicing in the federal states
Because the federal states have different regulations, they can decide for themselves which platform they want to use for electronic invoicing. The federal states can therefore be roughly divided into two groups:
Federal states that use OZG-RE:
- Berlin
- Brandenburg
- Mecklenburg-Western Pomerania
- Saxony
- Thuringia
Web capture, web upload, e-mail, De-Mail, and Peppol are used as transmission channels.
Federal states that use their own input channels for XRechnung:
- Baden-Württemberg: Baden-Württemberg service portal via web upload, e-mail, and Peppol
- Bavaria: e-mail because there is currently no invoice portal
- Bremen: zERIKA—transmission preferably Peppol; alternatively web capture, web upload, e-mail, or De-Mail
- Hamburg: Hamburg Service—-invoicing portal by e-mail, e-invoicing portal, and Peppol
- Hesse: Web capture, web upload, e-mail, and Peppol because there is no invoice portal
- Lower Saxony: NAVO via web upload, web capture, e-mail, and Peppol
- North Rhine-Westphalia: NRW via web capture, web upload, e-mail, De-Mail, and Peppol
- Rhineland-Palatinate: Central e-invoice receipt RLP via web upload, e-mail, and Peppol
- Saarland: Central e-invoice receipt RLP via web upload, e-mail, and Peppol
- Saxony-Anhalt: E-invoicing portal Saxony-Anhalt via web capture, web upload, e-mail, De-Mail, and Peppol
- Schleswig-Holstein: E-invoicing portal Schleswig-Holstein via web capture, web upload, e-mail, De-Mail, and Peppol
Ready to transform your financial processes?
Talk to us about your challenges in purchasing, accounting, and invoice processing.
We’ll show you how cisbox can take your company to the next level.
