Validator tutorial

How to use the EDI Validator

Understand what is checked, review errors and warnings, connect issues to the source or converted output, and export a validation report. Ready to begin? Open the EDI Validator.

Validation runs locally in your browser. Your EDI files and converted values are not uploaded to a validation server.
1

Convert a file and open the workspace

Validation runs as part of the converted-results workflow. Open the EDI Data Workspace and look for the Validation status bar at the bottom.

EDI Data Workspace with the collapsed Validation status bar at the bottom
The collapsed bar summarizes the current result, such as “No issues,” “1 warning,” or an error count. Click any tutorial image to view it full size.
Select the Validation bar or Review issues to expand the full results panel.
2

Understand what is being validated

The validator uses high-confidence structural, formatting, and consistency checks. It evaluates both the original parsed EDI segments and the converted output.

Envelope structure

Checks that ISA/IEA, GS/GE, and ST/SE are paired; control numbers match; and reported group, transaction, and segment counts agree with the parsed file.

Source EDI values

Applies transaction-specific structural, requiredness, dependency, date, number, selected-code, acknowledgment, adjustment, purchase-order, purchase-order-acknowledgment, invoice, ship-notice, warehouse-shipping-order, warehouse-shipping-advice, inventory-inquiry/advice, product-activity, and functional-acknowledgment checks across supported 835, 837P/I/D, 834, 270, 271, 277CA, 999, 850, 855, 810, 856, 940, 945, 997, 846, and 852 boundaries. Coverage varies by family.

Converted output

Checks unsafe export values, numeric and nonnegative fields, real and correctly ordered dates, unique generated row IDs, and complete 835 adjustment reason/amount pairs.

Edited output and headers

Rechecks applicable edited cells and confirms visible export headers are not blank or duplicated.

The validator intentionally avoids rules that cannot be checked reliably without a complete implementation guide, authoritative external code set, or payer-specific policy.
3

Read the Validation Results table

Each row explains one detected issue and where it was found.

Expanded Validation Results panel showing a source warning
This example detects a source 837P claim charge that does not match the complete service-line total.
File/outputIdentifies the source file or converted output group affected by the issue.
LocationShows the source segment and element, converted row, or output-group location.
Field/elementNames the mapped field or EDI element involved.
Current value and issueShows what the validator read and the reason it needs review.
Error

A high-confidence structural, requiredness, formatting, or output-consistency problem that should be reviewed before relying on the result.

Warning

A condition that deserves review but may be valid in context. Warnings are not automatically treated as file rejection.

4

Open an issue for more detail

Select an issue row or its action button to see the full explanation, expected value, internal rule ID, and suggested review action.

Validation issue detail showing current value, expected value, rule ID, and suggested action
Issue details give you the evidence needed to compare the validator result with the source file and your trading-partner requirements.
  • Source details explains the originating EDI segment issue.
  • Jump to issue navigates to a mapped converted row when one exists.
  • The Rule ID helps identify the exact check in exported reports.
  • The suggested action is guidance—not an automatic source-file correction.
5

Filter results and mapped rows

Use the controls above the issue table when a file produces many results.

Errors / WarningsFocus the table on a single severity.
SourceShows issues detected directly in parsed EDI segments.
Edited outputShows applicable issues involving values changed in the Data Editor.
File/output selectorLimits results to one source file or converted output group.
Show mapped rows with issues only uses the existing Data Editor filtering system. It is disabled for source-only envelope or segment issues that do not map safely to converted rows.
6

Re-run validation or export a report

Use Re-run validation after reviewing changes or whenever you want to refresh source and converted-output checks. Export the current validation report as CSV, Excel, or JSON for review and recordkeeping. Validation-report XML export is not available.

  • Reports include severity, rule ID, location, current and expected values, message, and suggested action.
  • Exporting a report does not alter the EDI file or converted data.
  • Cell edits remain separate from the source EDI file.
  • Use the report filters on screen to investigate before exporting.
7

Know what “No issues found” means

No issues found means the file passed the validator’s currently supported high-confidence checks. It does not guarantee payer acceptance or complete compliance with every X12 implementation-guide or trading-partner rule.

Not a payer responseThe validator does not replace a 999, 277CA, clearinghouse edit report, or payer adjudication result.
Not every code setExternal CARC, RARC, diagnosis, procedure, and payer-specific code validation requires authoritative versioned references.
Context still mattersA warning may be acceptable depending on transaction subtype, contract, implementation guide, or trading partner.
Keep your sourceEditing converted output does not repair or regenerate the original EDI file.

Validate an EDI File

Convert the file, open the Data Workspace, and expand Validation.

Validate an EDI File