{"id":108616,"date":"2020-03-16T12:44:08","date_gmt":"2020-03-16T11:44:08","guid":{"rendered":"https:\/\/easy-software.com\/?p=108616"},"modified":"2025-03-17T16:12:59","modified_gmt":"2025-03-17T15:12:59","slug":"electronic-invoice-formats-standard-confusion-in-europe","status":"publish","type":"post","link":"https:\/\/easy-software.com\/en\/newsroom\/electronic-invoice-formats-standard-confusion-in-europe\/","title":{"rendered":"Electronic invoice formats \u2013 standard confusion in Europe?"},"content":{"rendered":"
To allow the transfer of data to function smoothly, invoice standards are necessary, which means standardized invoice formats \u2013 have you heard of Facture X<\/strong> or XRechnung<\/strong>, Fatura PA<\/strong> or ZUGFeRD<\/strong>? These electronic invoice formats could also be of interest to you. Time to shed a little light on things.<\/p>\n\n\n\n The electronic invoice format was initiated and developed at the 23rd meeting of the IT Planning Council for the German Federal Government and Federal States on October 10, 2017; the title of the meeting was: \u201eEinf\u00fchrung der elektronischen Rechnung in Deutschland\u201c (The introduction of the electronic invoice in Germany). The reason and the occasion was, and is, EU Directive 2014\/55\/EU<\/a> dating from April 16, 2014. In this directive, an agreement was reached at the European level on electronic invoicing for public sector contracts. This demonstrates the political will<\/strong> to advance the use of digital invoicing in the countries of the EU. As is usual with EU directives, the specific implementation into national law is now the responsibility of the EU member states.<\/p>\n\n\n\n The stated objective in Germany is to achieve this with the XRechnung<\/strong> electronic invoice format <\/strong>. Since November 7, 2018 the introduction of the same format for all federal ministries as well as constitutional bodies has been binding, with the federal states and municipalities following approximately one year later. Read more about the topic of the XRechnung<\/a> invoice format. The leading body for the configuration and development of the electronic invoice format known as XRechnung is the Coordinating Office for IT Standards <\/em>(KoSIT).<\/em><\/p>\n\n\n\n Fatura PA (IT) , Facture X (FR), XRechnung and ZUGFeRD 2.0 (DE) \u2013 are the four names of national invoice formats that differ in details but are based on the European standard EN16931.<\/strong> The latter in turn provides for the XML standards UBL and UN\/CEFACT Cross Industry Invoice (CII) for the creation of structured invoices.<\/p>\n\n\n\n The XRechnung format stands for an XML-based semantic invoice format<\/strong>. It primarily has the purpose of issuing electronic invoices to public sector clients in Germany.<\/p>\n\n\n\n The XRechnung format is fully documented and product- and manufacturer neutral; it is based on the EU EN 16931 standard. The documentation is available to everyone at no cost. This is one of the key advantages of the XRechnung invoice format. In principle, anyone can read it and implement it.<\/p>\n\n\n\n As referred to above, the XRechnung invoice format is XML-based (Extensible Markup Language<\/strong>). XML is included among the machine-readable markup languages. XML results in two important advantages:<\/p>\n\n\n\n The approach of having created a public standard for electronic invoice formats is commendable. Anyone can read how it works, which means that anyone can implement it. The implementation via XML is also advantageous: not only due to the resulting possibility for checking the legal effect and validity, but also the connectivity in terms of digital signatures<\/a> with XML signatures<\/a>. For the time being, however, the latter is still considered a pipe dream. The smaller size of an XML document, and therefore the faster transfer of the invoice data, are also among the advantages of the XRechnung invoice format \u2013 at least in comparison with PDF invoice files. It is also clear that the X-invoice format also offers superior parsing options for further processing in accounting systems. The key disadvantage of the XRechnung format is that its area of use is limited to the public sector.<\/p>\n\n\n\n The acronym ZUGFeRD tends to make Germans smile, after all, the word \u201cZugpferd\u201d means \u201ccart horse\u201d in German. It actually stands for \u201cZentraler User Guide des Forums elektronische Rechnung Deutschland\u201d, or Central User Guide of the Electronic Invoice Forum, Germany<\/em>. If the creators of the specification of the ZUGFeRD <\/strong>invoice format are to be credited with sufficient humor and creativity, one of the key characteristics of this electronic invoice format is therefore clear: as a hybrid<\/strong> invoice format, it unites the aspiration to be readable by both machines and people. Put on the right horse, you push the electronic invoicing.<\/p>\n\n\n\n The Electronic Invoice Forum Germany (FeRD) developed the specification for the ZUGFeRD invoice format in cooperation with businesses, associations and government ministries. The development got off the ground on June 25, 2014 with the ZUGFeRD 1.0 invoice format. A little while later, Version 2.1.1 of the specification followed. It took place under the aegis of the German Federal Ministry for Economic Affairs and Energy (BMWi).<\/p>\n\n\n\n Incidentally, the political will to give the topic \u201celectronic invoice formats\u201d the appropriate degree of impetus cannot be overlooked either. The approach was somewhat unconventional, however. After all:<\/strong> One of the key objectives of the ZUGFeRD invoice format is to enable the exchanging of electronic invoices without bilateral coordination<\/strong>. In other words: The exchanging of invoices should work without the sender or recipient of the ZUGFeRD invoice format having reached an agreement in advance.<\/p>\n\n\n\n If you take a more detailed look at ZUGFeRD 2.0, you can see that the invoice format consists of two parts: on the one hand, the part which is responsible for the graphic or visual representation of the invoice, and on the other hand, the part that contains the invoice data. This allows for both the human and machine readability to be achieved. In short: The ZUGFeRD 2.0 invoice format presents an invoice to the individual person in the form of a PDF file, while it presents semi-structured invoice data in XML format to the machine. From a technical perspective, the ZUGFeRD 2.0 invoice format implements this with PDF\/A-3<\/a> as a container format. The PDF container enables random file formats to be embedded. In this way, the ZUGFeRD 2.0 achieves human and machine readability.<\/p>\n\n\n\n Assuming that the presentation of PDF files should no longer pose any problem in the 21st century \u2013 after all, PDF readers are a standard feature, regardless of the operating system \u2013 it should be possible for anyone to read an invoice in the ZUGFeRD invoice format. This means that the ZUGFeRD 2.0 also fulfills the aspiration of being able to send, receive and read electronic invoices without bilateral coordination<\/strong>. After all: the container format means that both are always sent. It is up to the recipient of the invoice to determine how and what is read or processed.<\/p>\n\n\n\n Here, the Forum Electronic Invoice Germany (FeRD) has made its decisions wisely. This is because the ZUGFeRD 2.0 invoice format implements the European EN16931 standard for electronic invoicing. Thus, ZUGFeRD 2.0 meets the requirements of the EU Directive 2014\/55\/EU. These are the same requirements that XRechnung also fulfills. This means that the ZUGFeRD 2.0 invoice format can be used in both national and European contexts. Update: Since 01.07.2020 ZUGFeRD 2.1.1 also supports the requirements of XRechnung in Germany. With the new XRechnung profile, ZUGFeRD 2.1.1 implements the German requirements, national business rules and administration-specific specifications as well as provisions for the XRechnung standard. Meanwhile, almost two years have passed again and the invoice format ZUGFeRD 2.2 has been published. You can find out more about this on the FeRD page corresponding to the update.<\/p>\n\n\n\n To conclude, nothing stands in the way of using digital invoice<\/a> formats. At present, everything still depends on the area of application. In this respect, the following rule of thumb applies: You can use XRechnung when issuing invoices to public authorities, i.e. in the business-to-government (B2G) sector. The ZUGFeRD 2.0 invoice format is fine for you to use in the business-to-business (B2B) sector, where the use of this format has become established.<\/p>\n\n\nThe XRechnung invoice format<\/h2>\n\n\n\n
Standards<\/strong><\/h3>\n\n\n\n
What exactly is the XRechnung invoice format?<\/h2>\n\n\n\n
<\/figure>\n\n\n\nWhat does a semantic data model mean in the context of the XRechnung invoice format?<\/h2>\n\n\n\n
\n
What else can be said about the XRechnung invoice format?<\/h2>\n\n\n\n
The ZUGFeRD 2.0 invoice format \u2013 a hybrid for man and machine<\/h2>\n\n\n\n
Who created the ZUGFeRD, and when?<\/h3>\n\n\n\n
Objectives of the ZUGFeRD invoice format<\/h2>\n\n\n\n
How does the ZUGFeRD concept and invoice format work?<\/h2>\n\n\n\n
<\/figure>\n\n\n\nZUGFeRD 2.0 and compatibility with the EN 16931 EU standard<\/h2>\n\n\n\n
The bottom line: electronic invoice formats<\/h2>\n\n\n\n