Validate & correct EDI files

The fastest and most reliable way to validate and correct your EDI files. A missing element, wrong EDI code, or invalid character can cause an entire EDI transaction to be rejected. Once you have identified the errors, they can be easily corrected directly in either the EDI or the JSON editor. Cross-reference with the interactive specification for X12, EDIFACT, and their sub-standards.

Validate EDI files

Upload and validate X12 or EDIFACT files automatically. All interchanges, groups and transactions in an EDI file are validated according to their specifications, displayed in separate tabs for quick viewing and reference.

All errors are visually highlighted directly in the EDI document, with detailed error messages at the beginning of each segment.

Learn more

Configure validation

Using the syntax set forth by the EDI standard and version, the configurable EDI validation rules cover mandatory/optional usage, syntax notes and conditional elements, out-of-order segments, EDI codes, segment/element repeats and loop counts, element data formats, discrepancies between headers and trailers, duplicate transactions, min/max character widths, etc.

Learn more

Common questions about EDI validation

How accurate is your validation?

The validation, structure, and general format of any EDI transaction are driven by its EDI specification/mapping. We use OpenAPI to create a machine-friendly version of the specs; for example, here is an interactive view of the 837 P professional claim model.

All our pre-built models match the official specifications to the letter (X12, EDIFACT, HIPAA, EANCOM, IATA, VDA). You can configure your own custom versions or create new ones from scratch, by importing EDI specs/mappings in any of the following formats: SEF (Standard Exchange Format), EdiFabric (EDI Templates) and our native OpenAPI 3, in JSON or YAML.

Are the validation rules configurable?

Yes, all rules can be edited in the YAML/JSON model for the transaction. Download the model from the relevant EDI standard library (X12, EDIFACT, HIPAA, etc.) and then import it in EDI model builder under a different name. Apply the required modifications following the rules in the OpenAPI EDI format, and update the model. Then go back to the validator and select to use the new model from the settings menu.

Which of the HIPAA SNIP levels are supported?

The following HIPAA SNIP levels are supported: 1, 2, 5 (edit EDI model to add/modify partner-specific EDI codes), 6, 7 (edit EDI model to add/modify the structure to adhere to partner-specific requirements). Levels 3 (balancing) and 4 (situational segments) are not supported. Level 4 is partially supported for 270, 271, 276, and 277.

Scroll to top