ediverse Explore the platform

Spotlight PEPPOL BIS Billing 3.0 The EU e-invoicing mandate is here — France Sept 2026, Belgium Jan 2026, Germany 2025.

EDIFACT Validator

Validate the syntax of your EDIFACT messages locally, in your browser.

Paste an EDIFACT message to validate it.

Also checks the list of allowed segments for the declared message type (ORDERS, etc.).

How it works

The validator applies ISO 9735 syntax rules — every check that can reasonably be automated without semantic knowledge of the message:

  1. Optional detection of a leading UNA service string advice to redefine separators.
  2. Segment tokenisation honouring the release character (default ?).
  3. Presence of both UNB and UNZ.
  4. Reference consistency between UNB and UNZ.
  5. For each message, a paired UNH / UNT with the same reference.
  6. The count declared in UNT must match the actual segment count (UNH and UNT included).
  7. The count declared in UNZ must match the actual number of messages.

Privacy

Semantic validation (V1.1)

Semantic validation remains opt-in: by default only ISO 9735 syntax rules apply (V1). Checks on qualifiers (BGM[1]=220, NAD[1]=BY, DTM[1]=137…) and on the completeness of mandatory components inside a segment will follow in a later iteration.

  • EDIFACT — the standard overview.
  • ORDERS D.96A — the full structure of an ORDERS message, with example.

Last updated: May 13, 2026