With EdiNation, you can view, format, and validate EDI files for compliance with the guidelines. You can visually inspect all errors and cross-reference them with the EDI specifications for quick troubleshooting. All operations, such as parsing, validation and acknowledgment are based on Web Assembly, and run locally in your browser. Your sensitive data remains on your machine and never leaves the browser.

Paste or upload EDI files

To begin, navigate to EdiNation EDI Portal. Then, either paste (in the text editor under the button bar) or upload an EDI file by clicking the plus button:

You can also load one of the pre-configured examples (by clicking the arrow-down button to select an example) to begin with:

The file contents are displayed in the text editor.

View and format EDI files

The contents of your EDI file are loaded in the EDI editor exactly as they originally are and are not manipulated in any way. To format and process the EDI file, click the Parse button.

The parsing operation always formats all segments to a new line. To be able to correctly locate errors and cross-reference with the EDI specification, do not add empty spaces between the segments, or join segments to the same line.

When your file is correctly parsed, a PARSED status is displayed next to a green indicator:

When your file has parsing errors, such as missing segment parts or an incorrect segment identifier, a PARSING FAILED status is displayed next to a red indicator:

In this case, the parsing errors are listed under Errors, and you can click on the error for details:

All EDI messages are automatically matched to their corresponding EDI spec. You can use a custom guideline by building or importing a new EDI model from either SEF or OpenEDI. This custom model must then be configured in the settings.

Cross-reference with the EDI specification

Clicking or moving the cursor on a segment tag shows the details for that segment:

Selecting a data element displays its specification:

You can also manually click on any of the "Loops", "Any of", or messages to view their details:

Parse EDI with an explicit or custom EDI model

Use a custom EDI model

By default, EdiNation matches all EDI transactions to their corresponding system EDI models. You can create your own versions of the EDI models to match any partner-specific requirement.

Copy the model name from EDI Spec Builder and paste it in the box to the right of the Parse button:

This way, all files you parse and validate will only be resolved according to the specifications in the custom model specified here.

Use an explicit EDI model

To bypass EdiNation's resolution logic that identifies the correct specification for your message types, you can explicitly specify a system model. This avoids any fallback or internal logic EdiNation uses to parse a message when an exact model is not found, using the closest model it can find.

Copy the model name from EDI Spec Library:

and paste it in the box to the right of the Parse button:

Clear the custom model when you have to revert to the automatic model resolution.

Next steps

To learn more about how to translate and validate EDI files with EdiNation, try these tutorials:

• Validate and debug EDI files
• Generate EDI acknowledgments
• Convert between EDI and JSON
• View and download EDI specs
• Create and import EDI specs