What is New in the GEFEG.FX 2023-Q4 Release

With the new GEFEG.FX quarterly release 2023-Q4, the following new or enhanced functionalities are available for use.

New data packages in GEFEG.FX

    • UN/EDIFACT D.23A
  • ISO20022: External code lists update
  • DK Guidelines 3.7: pain.001, pain.002 and pain.008
  • GS1 eCom Standards: GS1 XML 3.6

New filter function for Notes in GEFEG.FX – More organised overview with the new notes filter in the models and schemas editors

Notes filter in the GEFEG.FX view

The use of notes offers every user the opportunity to enhance their guides or standards with additional, valuable information and is an essential aspect of specifying guides with GEFEG.FX. This can include validation rules, mapping IDs, internal notes, customer descriptions and much more. Notes in GEFEG.FX are used for output in documentation in MS Word/HTML format, but also for executing special functions, such as validation. In the case of comprehensive commenting, navigation in the Notes section can become time-consuming due to the large number of Notes.

Thanks to the new Notes filter function, you now have the option of only displaying the notes relevant to your current task. This allows you to concentrate on the essentials when updating by hiding all notes that are not relevant to your current task. This is particularly useful for comprehensive guides in which the Notes section contains a wealth of information. For example, you can hide mapping IDs that are not relevant outside of mapping projects or focus specifically on validation rules.

Notes filter in the GEFEG.FX search

The filter function not only extends to the display, but can also be used effectively when searching. If you only want to include certain notes in a search, you can find the relevant results much more quickly by setting a filter. This further filter function can be called up and used via the search function. There you can easily select the notes you want to display or hide.

All in just one project: Create and update multilingual documentation centrally

Creating multilingual documentation has never been so easy! Previously, it was necessary to create a separate publishing project for each language. This also required reports and layouts for each language, which was associated with a high potential for errors during updates, as these files had to be maintained separately.

From now on, all languages can be managed in a single publishing project. This not only saves time during creation, but also for future updates. There are also fewer systematic errors if only one publishing project has to be maintained instead of several.

The new functionality is controlled via layouts. The layouts now have the “Languages” function at the top left. Here you can add the required languages and then select the desired language(s) to be taken into account when generating new documentation. Individual fields can also be linked to a specific language.

Does existing documentation need to be updated?

No, it is not absolutely necessary to change existing publishing projects. The new function is primarily recommended for customers who want to create new multilingual documentation.

If you already manage multilingual documentation in GEFEG.FX, you can of course simply retain the layouts and report files already in use or switch to the new language function later as part of a publishing project update.

In the middle of 2023, the World Customs Organization released a new major version of its Data Model. GEFEG.FX users of the WCO Data Model version 4.0.0 can now access the new version publication.

What is new in v4.0.0? Regulatory data requirements due to new or amended legislation submitted as change requests by Customs authorities and WCO Data Model implementers have been added and/or modified.

Furthermore, this major version release addresses pending critical cosmetic and breaking correctional activities since the last major version to improve the efficiency and usage of the WCO Data Model.

The involvement of Customs authorities globally supports an important objective of the WCO Data Model: Requirements of national and regional legislations or guidelines for implementation are considered and incorporated into the WCO Data Model. There are changes in the Information Packages (BIP), i.e. two of the major BIPs have been merged to create a new Additional Information Package (AIP). Please note that this type of change, amongst others, makes this release version non-backwards compatible with previous versions.

Customs authorities around the globe further strive for effectiveness and efficiency

It is an important objective for the WCO to provide and further develop its global standard for seamless cross-border transactions for all Customs administrations worldwide.

What are the benefits of the WCO Data Model, which is intended to be the basis for information exchange of cross-border regulatory processes in a global supply chain?

  • The Data Model opens the possibility for Customs authorities to achieve interoperability and collaboration in Single Window and other implementations.
  • Data flow and integration of business data for Customs procedures are simplified and harmonized.
  • The main components of the WCO Data Model consist of “Base Information Packages” and “Additional Information Packages”.

Information Packages compile information submitted by trading parties on one side and processed by Customs authorities for typical Customs processes and procedures on the other side. Customs processes cover Single Window, or other implementations, including those at the virtual border. This includes, for example, declaration of goods movement, licenses, permits, certificates, or other types of regulatory cross-border trade documents.

Delivery of the WCO Data Model in a structured and reusable format in GEFEG.FX

In cooperation with the World Customs Organization, GEFEG has been delivering the WCO Data Model with GEFEG.FX software since the early 2010s. Thus, new possibilities for joint development work and user-specific usage of the WCO Data Model opened up for Customs authorities, governmental organizations, traders and other parties involved in cross-border regulatory processes. For users, the reuse of the WCO Data Model is simplified and streamlined with GEFEG.FX. A ready-to-use WCO Data Model compliant XML schema export also contributes to this.

Easy and effective use of the WCO Data Model

Many users of the WCO Data Model packages in GEFEG.FX have been impressed by the simple and efficient methods for reusing the WCO Data Model to plan and implement their country and/or regional specific Customs data requirements based on legislation. With each new release, it is important for users to determine if their existing implementations need to be modified to incorporate the latest WCO definitions of objects and Customs procedures to ensure compliance with the Data Model.

In this release, changes have been applied as submitted by member administrations plus corrective changes from WCO intersessional development work approved and maintained by the WCO Data Model Project Team and incorporated into GEFEG.FX by the GEFEG Implementation Support Team.

Join the WCO DM 4.0.0 Webinar

GEFEG invites all interested users of the WCO Data Model to join our webinar on the deliverables and changes in the latest published version 4.0.0 of the WCO Data Model with GEFEG.FX. The webinar will also address the potential impact of the new version and its implementations by business and technical implementers. In addition, GEFEG will present the “How-to” documents delivered with the new release to assist all users in applying all the typical steps when implementing the new version of the WCO Data Model. In the 15-minute question and answer session, participants will have the opportunity to express wishes, questions and comments.

GEFEG.FX – New in the 2023-Q3 Update

With the new GEFEG.FX GEFEG.FX Quartarly Release 2023-Q3, the following new or further developed functionalities are available for use.

New data packages in GEFEG.FX

    • UN/EDIFACT D.22B
    • UN/EDIFACT D.22A
    • UNECE / ISO code lists update
    • UN Locode 2022-2
  • ISO 20022
    • Model & schema 2023-07
    • External code lists 2023-07
    • Models and schemas 2023-03-21
    • Code lists update
  • GS1 eCom standards
    • GS1 Semantic Data Dictionary (SDD): Despatch Advice
    • GS1 XML 3.5.1
    • GS1 Application Guidelines 9.3
    • GS1 XML update for code lists and example values
    • GS1 XML enriched with codes, as of 3.0

Using JSON schema for EDI: Advanced integration with the new GEFEG.FX JSON Editor

Times change and this is usually accompanied by new requirements. This naturally also affects the electronic exchange of business data, and here in particular new technical exchange formats as a supplement to the classic EDI and XML formats. For some time now, GEFEG.FX’s range of services has been enriched by its own API Editor.

With the new release, a JSON editor is now also available and offers a powerful way to design, customise and reuse customer specific data structures in JSON format.

For more information, see the following article: Now ready for use for GEFEG.FX users: The JSON Editor

UN/EDIFACT syntax versions consolidated!

With the publication of the UN/EDIFACT Syntax Verison 3 Part 11, users of the UN/EDIFACT standard will be able to use selected fields of syntax version 4 in syntax version 3, among others. This new syntax is implemented in GEFEG.FX as of the D.22A release.

Users now have the possibility to choose between the following syntaxes:

  • Syntax 3,
  • Syntax 4 and
  • Syntax 3 Part 11

In short, the new syntax allows compatibility between the previous syntaxes.

We would be happy to discuss what this means for your EDIFACT based guides and whether there is a need for action in a non-binding meeting. Get in touch with us!

New functions require new data format versions

What would software be without constant further developments, functional enhancements, bug fixes and, in the case of GEFEG.FX, new data modules? Of course, this is a purely rhetorical question, because we are constantly implementing new customer requirements or expanding existing functions.
Sometimes you as a user will be prompted by a pop-up to update the data format version in your GEFEG.FX version due to an innovation: If possible, always save your GEFEG.FX Guides in a current data format version immediately in order to be able to use the newly provided functions and improvements.

You can read the current data format version of your GEFEG.FX object in the GEFEG.FX information area.

Screenshot from GEFEG.FX showing the current data format version of a GEFEG.FX object

The next practical case will follow with the next release. With regard to EDI guides and EDI standards in particular, the following applies: With the next 2023-Q4 release, these will only be able to be processed with the data format version from 2019-Q3. GEFEG recommends that you update the data format version of your files before the next release upgrade so that you can continue to work seamlessly with your EDI guides.

Please also note the following information:

Regardless of the specific situation of the 2023-Q4 Release, we would like to point out, in connection with the data format version that all GEFEG.FX users within an organization should use the same GEFEG.FX release version to avoid compatibility problems. Under certain circumstances, it could otherwise happen that GEFEG.FX objects saved with a newer GEFEG.FX version cannot be opened with older GEFEG.FX versions.

With the rapid expansion of the internet came the ever-increasing need to standardise communication between web applications and their users. For this reason, JSON was developed in 2001 to facilitate communication between a client and server as an open file format. Because of its ease of use and great versatility, JSON became established as the central exchange format on the Internet.

Though JSON was first used on the web, this data format is also becoming increasingly popular in electronic data exchange. As with all exchange formats, JSON files must be read, evaluated and verified by the recipient. For this reason, JSON Schema was developed. In a JSON schema, rules and conditions are defined that must be observed by JSON data. Typically, such criteria are, among others, properties, references, and types.

Also with JSON, an understanding of the underlying business processes is necessary. Thus, software is needed that effectively handles these challenges. For these reasons, we have developed the JSON schema editor as an extension to our GEFEG.FX software solution. The new editor now offers all companies the possibility to effectively manage all these challenges.

Powerful JSON schema design

GEFEG’s JSON Schema Editor provides a powerful solution to design JSON schemas. Companies can now intuitively design complex data structures that meet the requirements of their specific business processes. The editor’s user-friendly interface allows users to easily define and organise JSON objects and their properties. This not only facilitates the design phase, but also ensures a consistent and clear presentation of the data – a big plus for smooth cooperation with partners and customers.

Efficient editing of JSON schemas

GEFEG.FX’s JSON Schema Editor offers a comprehensive range of editing tools that allow organisations to precisely customise JSON schemas. Whether it’s updating existing schemas or adding new elements, the editor makes the process easier than ever. With the ability to create and modify complex hierarchies, users are in control of their data structures and can make changes with ease.

Converting XML files into JSON schemas

Another notable feature of GEFEG’s JSON Schema Editor is the ability to convert XML files into JSON schema structures. XML files are widely used and are an important technical format for data exchange. By converting XML files, a JSON schema is available with one click, which organisations can use, for example, for use in databases and processing procedures, without having to laboriously re-enter the XML schema in JSON-format.

Since experience shows that companies are using multiple data exchange formats and need to orchestrate the interplay of multiple syntaxes, this step enables a smooth migration to a more modern data exchange landscape and facilitates the adaptation to the latest EDI trends. In addition, the conversion from XML to JSON schema helps to improve interoperability between different systems and platforms, resulting in seamless and efficient data exchange.


In the dynamic world of EDI, innovative solutions are critical to meet the demands of the modern business world. The GEFEG.FX JSON Schema Editor complements the existing functional areas and offers a powerful way to design, customise and reuse customer-specific data structures in JSON format. This fulfils important current requirements in the electronic exchange of business data. GEFEG continues to provide critical functionality that businesses need to succeed in an ever-evolving digital landscape.

We look forward to presenting the features and benefits of the new JSON editor to you and supporting you in its use. You would like to learn more about the JSON editor? Please contact us!

Over the last 30 years, a number of standards for electronic data exchange between business partners have been created in order to standardise it, often with the aim of adapting it to the business processes of an industry. These standards, which are now well established, have contributed significantly to the fact that companies today save costs by using standardised data exchange formats. After this successful innovation push through B2B standards in electronic data exchange, the search continues for new, innovative and more efficient solutions to further optimise data exchange.

GS1 has taken the next step with the development and publication of the “GS1 Semantic Data Dictionary” (SDD). The semantic data model was developed to define all business-relevant data needed for the exchange of EDI messages in the supply chain, such as purchase order, order confirmation, invoice and other messages. Unlike syntaxes such as UN/EDIFACT, XML Schema, X12, the message structure does not matter: GS1 SDDs focus on the semantic content of the business processes. This creates a comprehensive, higher-level data model that acts as a dictionary and library.

How does the GS1 SDD model benefit users?

Generally speaking, any number of subsets can be derived from the GS1 SDD model and/or the subsets for the supply chain processes. Users leverage the GS1 SDD data model to develop data models tailored to their own use case, containing only the information that the user actually needs. Irrespective of the technical aspects of data exchange, this further improves harmonisation, maintainability, consistency and interoperability of the data. In GEFEG.FX, these subsets can be created as model guides and used with the usual range of functions such as documentation, structural adjustments, mapping options.
Based on the data model, users can develop their APIs or, in the next step, they can link the user-specific data model with a logical mapping to the data formats of the eBusiness standards used, e.g. GS1 EANCOM® or GS1 XML.
Another advantage for users: In case of future updates of the data model, changes can be transferred to the already linked data formats with little effort. Users can manage their interfaces with business partners even more efficiently.

GS1 SDD as a new data module in the GEFEG Distribution

With great commitment, GEFEG has participated in the development process of the GS1 SDD and contributed to the release of this data model. As of now, we offer the GS1 SDD data model as an additional data module in the distribution of GEFEG.FX. The data package also contains the model subsets of the Orders, Invoice and Order Response processes. In addition, it contains detailed mappings for supply chain messages to the GS1 EANCOM®, GS1 XML and SCRDM CII data formats of the same name.

The new data package allows you to easily integrate the GS1 SDD into your existing message formats using the included mappings and to communicate smoothly between different data formats.

Should you require further information or support, we will be happy to assist you. We look forward to introducing you to the advantages of the new GEFEG.FX data package and assisting you with the implementation.

The World Customs Organisation has published the latest version of its data model at the end of 2021. GEFEG.FX users can now obtain the latest version 3.11 of the WCO data model via an update of the GEFEG distribution.

What is new in version 3.11?

Data requirements due to new or amended legislation submitted as amendments by customs authorities and WCO data model implementers have been added and/or amended.

In this release there are 5 new Compositions, 5 new Attributes, 8 new Classes and 3 new Codelists approved and maintained by the WCO Data Model Projects Team and provided by the GEFEG Implementation Support Team in GEFEG.FX. Learn more about the details in our webinar.

The involvement of customs authorities worldwide supports an important goal of the WCO data model

Data requirements of national and regional legislations or implementation guidelines are taken into account and incorporated into the latest WCO data model, which in turn takes into account feedback and input from customs authorities around the world. This version is backwards compatible with previous versions as it does not include or remove any new information packages or business processes. Extensive changes are expected in the next major version of the WCO data model, which is currently scheduled for release in mid-2023.

Improve the effectiveness and efficiency of customs authorities around the world

It is an important goal of the WCO to provide and further develop its global standard to enable seamless cross-border transactions for all customs administrations worldwide.

How do you benefit from using the WCO data model as a basis for the information exchange of cross-border regulatory processes in a global supply chain?

  • The WCO data model opens the possibility to achieve interoperability and cooperation in Single Window and other implementations by customs authorities.

  • Simplified and harmonised data flow and integration of business data for customs procedures

  • The “Base Information Packages” are central components of the WCO data model. These information packages compile information for typical customs processes and procedures in single window implementations or at the virtual border. This is information that has to be submitted by the trading parties and processed by the customs authorities. These include, for example, declarations of goods movements, licences, permits, certificates or other types of documents for cross-border trade.

Output of the WCO data model in a structured and reusable format in GEFEG.FX

In cooperation with the World Customs Organization, GEFEG has been providing the WCO data model with the GEFEG.FX software since the beginning of 2010. This opens up new opportunities for customs authorities, governmental organisations, traders and others involved in cross-border regulatory processes for joint development work and user-specific use of the WCO data model. For users, GEFEG.FX simplifies and streamlines the reuse of the WCO data model, whether for national customs implementations or for use by government partner agencies. A ready-to-use XML schema export also contributes to this goal.

Easy and effective use of the WCO data model

Many users of the WCO data model packages in GEFEG.FX are impressed by the simple and efficient methods of reusing the WCO data model to plan and implement their country and/or region-specific customs data requirements based on legislation. With each new release, it is important for users to determine whether their existing implementations need to be modified to incorporate the latest WCO definitions of objects and customs procedures to ensure consistency with the data model. If a migration to the latest version of the WCO data model is required, this can easily be carried out in GEFEG.FX.

Join the WCO Data Model 3.11 Webinar

GEFEG invites all interested users of the WCO data model and all other interested parties to join our webinar on the new features and changes in the latest version 3.11 of the WCO data model with GEFEG.FX. The webinar will also address the potential impact of the new version and its implementations by business and technical implementers. In addition, GEFEG will present the “how-to” documents that are updated and delivered with each new version to help all users to perform all typical steps when implementing the new version of the WCO data model. During the 15-minute question and answer session, participants have the opportunity to ask questions, express wishes and make comments.

What is new in the quarterly-release 2022-Q1?

This is how you achieve “Creating a New Version” in GEFEG.FX faster than before

When you have published a development status of data, it makes sense to “freeze” it and initiate the next development stage with a new data package. For this new version of the data package, the function Create new version is often used. In this case, all existing properties and references are transferred to the new objects in GEFEG.FX and only a new alias (short name, version, variant) is assigned. If this function is executed from a folder, several objects can also be created at the same time. Within this folder, all connected objects are automatically adjusted to the new names. This also applies to reports and publishing projects. So from now on, you no longer have to check all objects individually and adjust the properties subsequently and individually.

The Create New Version function has also been extended to allow you to append, prefix, replace, partially replace, or suffix replace for all elements of the version name – i.e. short name, version, or variant.

More comfort when creating a new version in GEFEG.FX

Suppose you have several models and associated EDI standard code lists in a folder. All of them have the suffix “preview” and the version “v1.0” in the short name. You are now using the improved function Create New Version and want to assign a new status for editing version v2.0. This should also no longer have the status Preview, so you want to remove the string “preview” in the short name and replace the version with “v2.0”.

In the wizard, to customize the short name, use the “Replace suffix” option and delete the “preview” text, leaving the field empty. To change the version name, use the “Replace” option from old “v1.0” to new “v.2.0”. With the start of the function now on the one hand the aliases themselves are adapted and on the other hand these new names are taken over also in the connected objects automatically.

Try it out: A really helpful and time-saving function when creating new data packages.


Update large working copies in GEFEG.FX now at high speed

Many users successfully use the repository functions of GEFEG.FX to develop data together in a team. You benefit from the advantages of this approach compared to the usual document use in network drives.

  • Version control: Restore previous work statuses and file versions with just a few clicks
  • Tracking: Check the logs to see which folders and files were last edited
  • Access: All users of the repository access the latest editing status of a file

When using Subversion (SVN) repositories, you can use GEFEG.FX as a Subversion client and do not need any additional version control software. The first step in using repositories on a daily basis is to update your working copies in GEFEG.FX to retrieve the latest changes to files locally for yourself. Depending on the size of the repository and the size and type of files, this process sometimes took quite a long time.

We are pleased to report that we have achieved a major performance improvement at this point: Customers report that the update time for large repositories has improved by about 50%.

We will continue to optimise the work with repositories. Feel free to share your experiences with us: What’s going well? What concrete suggestions do you have for improvements?


Conveniently define settings for the comparison of EDI standards with the new wizard

Even though the functional scope of GEFEG.FX is quite comprehensive, the creation of a company- or organisation-specific EDI guide remains one of the most important tasks. EDI guides are primarily used for human-readable documentation, logical mappings to other formats or for the validation of test messages. As a basis for an EDI Guide, users first select the appropriate EDI standard, for example a UN/EDIFACT Directory provided by GEFEG.FX, or they develop their standard themselves by creating a company-specific flat file standard in GEFEG.FX.

Since EDI standards are updated regularly, it is necessary to check frequently whether and how standards differ:

  • Have all the desired changes actually been implemented in the new release?
  • What are the differences between the currently used standard and a new release of the same standard?
  • Two standards have the same name: Are they actually identical or have changes been made to one standard?
  • Do these two standards use the same code lists and code repository?

With the new release, a wizard guides you through the settings of the EDI standard comparison. The wizard dialogue assists you with the settings and then records the differences between two EDI standards. As a result, you receive, for example, a decision-making aid as to which of two possible EDI standards you want to use for your EDI Guides.

Our recommendation: From now on, use the wizard for comparing EDI standards and avoid the more tedious manual comparison in the EDI standard editor.

By the way: Users are now also guided through the settings in the check dialog for EDI standards with a wizard.


New data packages in GEFEG.FX


  • New version
  • UN Locode 2021-2 included

GS1 EANCOM® Implementation guidelines 9.2

  • New: In agreement with GS1 Germany, the application recommendations in GEFEG.FX are now provided as a separate module.

ISO 20022

  • Model/Schemas 2021-08
  • ISO 20022 External code lists 2021-11
  • ISO 20022 External code lists 2022-03

VDA Recommendations

  • Current status of the VDA recommendations 2021
  • VDA Invoice form

Also read our Release-Notes

From now on, GEFEG.FX supports the development of APIs on the basis of OpenAPI 3.x. And the best thing is: you can reuse your data in APIs and use your existing messages.

GEFEG.FX is known as the ‘hidden champion’ for design, documentation and mapping software when it comes to classic EDI(FACT) messages, XML messages, data models and standards. In short: GEFEG has been supporting the digitalisation of companies around the globe for almost four decades. Therefore, it is the natural next step to also accompany the transformation into the world of web APIs. With the new version of GEFEG.FX, you can reuse your data in APIs.

Successful pilot projects from automotive to BlockChain to marketing

When it comes to developing and setting standards, this must be optimally supported by the software used. GEFEG.FX is permanently being further developed and new functionalities added. However, the support of APIs has been a major step. A separate programme area has been created and is still being expanded. It is therefore particularly important for GEFEG to offer the usual reliability and quality here. We were able to win several pilot projects in which we were able to successfully test the new modules. The feedback from our customers was thus immediately incorporated into the development and ensured the usability of the new API module.

Support of OpenAPI 3.0 and OpenAPI 3.1 in Swagger and YAML format

For many, “Swagger” is a household name. Why? Because for many years Swagger was one of the standards on the web for APIs. Therefore, there is still a lot of software on the market that supports the Swagger 2.0 format. But this format has been obsolete for a few years and OpenAPI is the successor. Since spring 2021, OpenAPI is available in version 3.1. Of course, GEFEG.FX fully supports the new standard, but can also export the Swagger 2.0 format.

What makes GEFEG.FX different?

The strength of GEFEG.FX lies in its design-time support for electronic data exchange. Governance is on everyone’s lips today – and has been standard at GEFEG.FX for decades. Thus, data models or a message can of course be developed from scratch. In addition, existing standards can also be used or imported. Transparently tailored to the respective profile or mutually mapped to each other, this results in a significant advantage when using GEFEG.FX. It becomes easily and immediately apparent whether and where gaps exist or what special features the respective implementation requires. GEFEG.FX transfers this strength to the world of APIs.

So how can I reuse my data models in APIs?

Existing standards can also be used for APIs. Existing APIs in OpenAPI or Swagger format can be easily imported into GEFEG.FX. Either directly or via GIT and SVN support.

In addition, however, the UML data models or the UN/CEFACT reference data models as well as any XML format can be used to define an API from them. And the special thing: The connection remains intact. If the underlying data model or the linked message structure is updated, this can directly affect the API if desired.

A central point for the maintenance of data models, XML and API

This means, in particular, that GEFEG.FX can effectively be used on several tracks. If there is a need to change the electronic connection of the business partners, it is no longer necessary to adapt each mapping and each profile individually. The adjustment can be made centrally and has an immediate effect on the data models, XML messages and the API specification. This is how simple the implementation of compliance requirements can be.

What is New in the Quarterly Release 2021-Q3?

New data packages in GEFEG.FX

    • New version
  • GS1 EANCOM® Implementation Guidelines
    • New: In coordination with GS1 Germany, the application recommendations in GEFEG.FX are now provided as a separate module.

Easily transform EDI to APIs? Reuse your data models in APIs now. Think model-First with GEFEG.FX

From now on, GEFEG.FX supports the development of APIs on the basis of OpenAPI 3.x. And the best thing is: you can reuse your data in APIs and use your existing messages.

Read more

Clearer error messages and further improvements in message validation

For a business process to run smoothly, a message must be error-free – that is, compliant with company-specific EDI guidelines. For this reason, checking incoming or outgoing business messages for errors is a standard task for EDI teams. Our GEFEG.FX software supports EDI teams in this task, for example, by allowing messages to be validated in a test environment, by systematically checking test scenarios, or by providing error messages that clearly and unambiguously indicate the error. The following advancements support you even better in validation and testing.

Faster correction of errors through more understandable error messages!

The result of a validation in GEFEG.FX is an error log that outputs human-readable error messages in addition to technical meta information. Based on the error message, the user not only recognizes the position where an error occurred, but also immediately understands the deviation in content from the specification. In GEFEG.FX, the note “Check” is used for the error message as well as for the output of the error location. For example, a standard error description for the date format reads like this:
“The date format is incorrect. Specify “ram: DateTimeString” in the format CCYYMMDD.”

As of the current GEFEG.FX, you can describe error messages even more precisely. Build understandable identifiers into your “Check” note by embedding a link to any other note in the error message. If you describe a date field more precisely with a GEFEG.FX note, for example with the information “Delivery date” from the note “Definition”, the above error message would be output with the following text:
“The date information is incorrect. Specify the “delivery date” in the format CCYYMMDD. “

Thus, the error message is more understandable and the correction will be faster, since the user will immediately recognize the correct place in the message.

Document your test messages with one click!

Usually messages, and mostly also test messages of data formats of the classic EDI, for example ASC X12, EDIFACT, IDOC, Flatfile etc. are opened in a text editor.

As a GEFEG.FX user, you can also visualize your test messages using GEFEG.FX reports, in particular the GEFEG.FX Transaction Analyzer: Both experienced EDI experts and EDI beginners can use the crosscheck between the sample message and the standard to evaluate the contents of the message, interpret them more accurately and read off any errors.

GEFEG.FX Transaction Analyzer vs. Texteditor
GEFEG.FX Transaction Analyzer vs. Texteditor: Present messages in a comprehensible way!

From now on, you can also conveniently generate the GEFEG.FX Transaction Analyzer report from the reports directory of the test data folder and create the test message similar to the EDI segment report as documentation.

No XML file ready for testing? Create your XML test files from your GEFEG.FX schema!

Validation in the XML schema environment involves checking whether an XML file, often also called an XML instance, meets the specifications of a schema, i.e. is valid in the sense of the XML syntax. If the XML test file cannot be provided by the EDI partner or internal applications, GEFEG.FX can help with the following XML export: XML sample file.

This export generates an XML file based on the structure of the GEFEG.FX schema. If example values for elements and attributes have been specified in the GEFEG.FX schema, these are taken over and output as element and attribute values of the XML file.

This procedure has now been extended. From now on, you can also control the output of sample values for element and attribute variants. With variants you create slightly different versions of elements, for example buyer and seller for the party roles. Decide whether to output examples for all variants, i.e. buyer AND seller, or only for the first variant, i.e. buyer only. We recommend outputting the example values for all variants, so that there is as large a representation as possible of the possible elements in the XML file.

Would you like further explanations about variants in XML Schemas? Our support team will be pleased to assist you.

How do I recognize unused data elements and data element groups?

The EDI Guide Editor in GEFEG.FX lists the message structure as a data tree in the data area. Unused data elements and data element groups at the end of a segment are grayed out and therefore immediately visible. But how can I recognize unused data elements that are present in the middle of a segment? Until now, this was only recognizable via the GEFEG.FX note “Status”. An “N” or “X” marks the non-use of a data element or data element group.

With the current release you will find the following innovation: with the status assignment “N” or “X” a cross is shown at the data element or data element group, so that the non-use is made clear at first glance. Especially when revising an EDI Guide or in a mapping project, it is now possible to quickly determine whether a data element is used or not.

In the following example, the action code is not needed in the ORDERS Guide: The status is therefore set to “N”. The cross next to the data element tag 1229 visualizes the non-use.

Ticked boxes show unused elements
Ticked boxes show unused elements

What is New in the Quarterly Release 2021-Q2?

New and updated data packages in GEFEG.FX

VDA-Standards (VDA Recommendation 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

  • In the code lists an English translation was added


  • New: a consolidated separated code list that is used by all guides.

ZUGFeRD 2.0.1 and 2.1.1

XRechnung 2.0.0 and 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 and thus facilitate 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. Ask for a workshop or presentation on the following topic:

Documenting EDI guidelines – GEFEG.FX’s publishing functions let you do much more!