Quickly create EDI specifications from scratch, or edit existing ones to match any implementation guideline. Effortlessly deploy new EDI models on the fly with a single click.
EdiNation's powerful EDI model editor allows you to build and modify EDI specifications, and then deploy them to your subscription for immediate use. All EDI models represent their respective implementation guidelines, or mappings, in our free OpenAPI format. Edit them in either JSON or YAML layout, and safely release the modifications straight away.
The main purpose of EDI is to alleviate the communication between businesses by providing well-defined business document formats.
EDI model builder allows you to define these formats and to represent the structure of any X12 or EDIFACT transaction, such as an invoice or medical claim, in a common, computer-friendly, and shareable format.Learn more
Build from scartch or import and edit an existing EDI model directly in the web editor, in either JSON or YAML layout. The web editor ensures that you don't introduce an invalid EDI format.
Once you are happy with the changes, release the new or updated model for immediate use.Learn more
EDI models are schema objects in OpenAPI format that represent EDI transactions. For example, an invoice, or 810 in X12, INVOIC in EDIFACT, is represented as an invoice schema object, one for each EDI standard and version. EDI models define the structure of EDI transactions and match the format set out in the EDI specification or implementation guideline.
Yes, all standard models can be downloaded from the EDI models library, imported in the EDI model builder, and modified, for example, to introduce a new segment, to set a maximum loop repeat count, or add new EDI codes for a data element.
The entire syntax of a transaction is editable, and you can either use the provided web editor or download the model and edit it locally with your favorite JSON or YAML application.
EdiNation offers a free EDI models library covering most of the popular EDI standards, versions, and transactions. You would be just fine if you use them as they are without having to change anything.
There are three main cases when you would need to edit an EDI model: 1. When a trading partner requests a custom transaction format. For example, they've added an extra data element to the NM1 segment for address line three or four. You'll then export the standard EDI model, import it under a different name, edit it to add the extra element, and finally deploy it to be used when translating EDI files to/from this particular partner. 2. When X12 or EDIFACT publish a new version of a transaction which EdiNation doesn't yet support. 3. When you have old specifications, in SEF or EdiFabric format, and want to use it in EdiNation.