What is New in the Quarterly Release 2021-Q2?
New and updated data packages in GEFEG.FX
VDA standards (VDA Recommendations Flatfile)
- Corrections to format, length and status according to descriptive text
- Messages, fields and code lists marked with version or variant, if they are not one-to-one across all standards
- In the code lists an English translation was added
VDA standards (VDA Recommendations EDIFACT)
- Released D.20B replaces the previous draft version
- An English translation was added to the code lists
- New: a consolidated separated code list that is used by all guides.
ZUGFeRD 2.0.1 und 2.1.1
XRechnung 2.0.0 und 2.0.1
ZUGFeRD 2.x and XRechnung 2.x
Invoices are increasingly being received and sent electronically, replacing paper invoices more and more. This is not least due to legal guidelines and requirements, such as the e-invoice regulation. In principle, all public sector customers must accept electronic invoices if they conform to the European standard EN16931. In Germany, the obligation to send invoices electronically is regulated at federal and state level. Currently, invoices to federal or state public-sector customers in Bremen must be sent electronically.
In addition to legal reasons, the use of electronic invoices also makes sense in terms of interoperability. With the EN16931 standard, a standard exists that standardizes the understanding of an invoice and thus ensures efficiency in invoice processing, for example by specifying the mandatory fields of an invoice.
With the current format versions of ZUGFeRD and XRechnung, two electronic e-invoice formats are now available in GEFEG.FX. Use these ZUGFeRD and XRechnung schemas and create:
- customer-specific invoice fields via customization of the ZUGFeRD and XRechnung structures.
- documentation (PDF, DOC) in company-specific design
- special verification rules, in addition to already integrated business rules of the EN standard EN16931
You can find more information on the topic of e-invoicing at:
In focus: You want more than simple documentation of your EDI guidelines?
With the publishing functions of GEFEG.FX, much more is possible
By publishing documentation, you support your EDI partners in providing exactly the information that is required, thus facilitating the implementation of business messages. The core of a documentation consists of the specifications of message structure, formats or mandatory fields. Less technical aspects, such as the usage rules for a message or a process description, can also be output in supplementary sections. Your documentation is then not only aimed at technical EDI experts, but also supports business-oriented team members in particular in understanding the technical content of the EDI specifications.
You decide what the scope of your documentation will be, with the following options available in GEFEG.FX:
Generation of simple documentation at the click of a mouse
If you do not want to issue a comprehensive application recommendation, but decide to document a subsection, for example a structure overview, select this individual report and generate a Word or PDF file with a mouse click. Likewise, you can start a preview of your documentation at the click of a button to generate changes before the final generation.
Generation of extended documentation via Publishing Project
Use the Publishing Project in GEFEG.FX to output both the technical description of your specification (GEFEG.FX Guide) and external, static documents (PDF, DOC). This allows you, for example, to include a company profile in the introduction to the documentation to illustrate your competencies and activities. Or you can place an externally created process description in front of your specification to explain in more detail in which context the described message is used.
Generating exports using publishing projects
In many cases, GEFEG.FX guides are exported in order to make the GEFEG.FX work results available to other applications and interfaces. Exports can be used, for example, to fill internal systems (middleware) with data or to supply EDI partners with XSD and CSV formats.
If you now revise message structures in your GEFEG.FX guides, exports must be regenerated. Depending on the number of your GEFEG.FX specifications and the frequency of changes, export generation can quickly become very complex and unnecessarily time-consuming.
Including the respective export option in the publishing project makes exporting easier, faster and almost automatic. Include all GEFEG.FX guides and all desired export interfaces in the publishing project and generate all exports, for example XSDs, sample messages or separator-separated text files, at the click of a button. In summary: You update your specification(s) and receive all documentation and export output at the click of a button.
We will shortly present the full scope of the Publishing Project functions in a webinar, so that you can obtain complex documentation quickly, automatically and conveniently. Join our webinar