Free online EDIFACT decoder

Decode EDIFACT messages instantly.

EDIFACT parser, JSON converter and business document viewer

Paste an EDIFACT message to inspect its structure, segments and qualifiers. See the result as clean JSON, XML, a readable business document, or transformed API data.

Messages are processed in memory and never stored or logged.
Supported
ORDERS, DESADV, INVOIC, CONTRL
EANCOM D.01B and UN/EDIFACT D96A
AS2 and SFTP message formats
Multi-line and single-line formats
Result

Paste a message and click decode

EDIFACT decoder and parser

Parse the syntax. Understand the business data.

An EDIFACT decoder turns a raw UN/EDIFACT message into something people and applications can understand. CleanEDI parses the interchange, identifies the message type and version, exposes segments and qualifiers, and maps supported messages into structured business data.

Unlike a segment-only EDIFACT parser, CleanEDI lets you move from raw syntax to canonical JSON, XML, a readable business document and transformed API data.

From raw EDI to application data
01Raw EDIFACT
02Parsed message
03Canonical JSON / XML
04Business document
05Your API transformation
Conversion and transformation

EDIFACT to JSON, XML and business data

Use the decoder to move from EDI syntax to the representation your team actually works with. The goal is not just to split a message into segments. It is to make the business information usable.

EDIFACT to JSON

See a canonical JSON representation of supported messages, organised around orders, invoices, shipments and other business concepts.

EDIFACT to XML

Generate XML from the canonical representation for applications and workflows that still require XML-based data exchange.

EDIFACT to API data

Use the Your API view to rename fields, translate values, compute fields, remove fields and inject static values before delivery.

Learn more about EDIFACT to JSON →
How it works

How to decode an EDIFACT message

You do not need to understand every EDIFACT segment before using the decoder. Start with the message you have and inspect the result step by step.

01

Paste the message

Paste the raw EDIFACT exactly as you received it.

02

Decode it

CleanEDI identifies the interchange, message type and version.

03

Inspect the result

Move between business view, JSON, XML, transformations and raw segments.

04

Use what you learned

Validate mappings, troubleshoot the message or discuss a production integration.

Decoder coverage

Supported EDIFACT message types

Decode common B2B EDI messages used for orders, despatch, invoicing and acknowledgements. Additional message types are being added as the platform expands.

ORDERS
Purchase Order
Decode buyer and supplier details, order references, line items, quantities, prices and delivery information.
DESADV
Despatch Advice
Inspect shipment details, packaging hierarchy, SSCCs, quantities, lots, dates and carrier information.
INVOIC
Tax Invoice
Parse invoice references, line amounts, tax, payment terms, buyer and supplier information.
CONTRL
Functional Acknowledgement
Inspect interchange and message acknowledgement information, including acceptance and error details.
ORDRSP
soon
Order Response
Supplier acceptance, rejection or conditional acceptance of a purchase order.
RECADV
soon
Receiving Advice
Buyer confirmation of received quantities, accepted or rejected lines and delivery references.
PRICAT
soon
Price / Sales Catalogue
Product listings, pricing and item attributes sent between suppliers and buyers.
DELFOR
soon
Delivery Schedule
Forward delivery schedules across dates, quantities and locations.
Explore all EDIFACT message types →Explain a message segment by segment →
EANCOM and UN/EDIFACT

Built around the EDIFACT messages businesses actually exchange.

EDIFACT is the underlying standard. EANCOM provides more specific business usage conventions for many retail and supply-chain scenarios. CleanEDI is designed around these real-world implementations rather than treating every message as an abstract syntax exercise.

UN/EDIFACT
International EDI standard
EANCOM
Retail and supply-chain usage
D96A
Common EDIFACT directory
D.01B
EANCOM / EDIFACT directory
Use cases

What can you use an EDIFACT decoder for?

Debugging an EDIFACT message

Find out what a trading partner actually sent. Inspect the envelope, message type, segments, qualifiers and mapped business fields without manually decoding the syntax.

Building an EDIFACT integration

Understand a message before writing integration code. Use the canonical JSON view to see how EDIFACT fields can be represented as application data.

Testing before production

Check partner messages before they reach your ERP or downstream services. Warnings can highlight unusual or unmapped data that deserves attention.

Trading partner onboarding

Use a real sample message to understand a new partner's implementation and validate the expected business fields before committing the mapping to production.

EDI data mapping

Move from raw EDIFACT syntax to business-oriented data. The Your API view lets you preview field renames, value translations, computed fields and static injections.

EDI troubleshooting

When an order, invoice or shipment does not look right, inspect the original message and compare the raw segments with the structured output.

From tool to production

The decoder is useful on its own. Production EDI is the bigger problem.

Use the decoder to understand a message today. When you need inbound and outbound processing automated across real trading partners, CleanEDI puts the same EDIFACT complexity behind a production integration boundary.

EDIFACT decoder FAQ

Questions about decoding EDIFACT

What is an EDIFACT decoder?

An EDIFACT decoder parses a raw UN/EDIFACT message into its segments, data elements and qualifiers so the message can be understood. CleanEDI goes further by presenting supported messages as structured business data, JSON, XML and a readable document view.

What is the difference between an EDIFACT decoder and parser?

The terms are often used interchangeably. In practice, an EDIFACT parser reads the message structure, while a decoder usually focuses on making that structure understandable to people or downstream systems. CleanEDI does both: it parses the message and presents the result as business data.

Can I convert EDIFACT to JSON?

Yes. CleanEDI converts supported EDIFACT messages into a canonical JSON representation organised around business data rather than raw segment syntax. Use the Canonical JSON tab to inspect the result.

Can I convert EDIFACT to XML?

Yes. The XML view generates XML from the canonical representation for supported messages.

How do I decode an EDIFACT message?

Paste the raw EDIFACT into the input box and select Decode message. CleanEDI identifies the message type, parses the interchange and displays the result in the available views. You can then inspect the business document, JSON, XML, transformed API data and raw segments.

What EDIFACT message types are supported?

The decoder currently supports ORDERS, DESADV, INVOIC and CONTRL. Additional message types are being added, including ORDRSP, RECADV, PRICAT and DELFOR.

Does the decoder work with EANCOM and UN/EDIFACT?

Yes. CleanEDI is designed for UN/EDIFACT-based business messages, including EANCOM implementations such as D.01B and common UN/EDIFACT versions such as D96A where supported by the decoder.

Is the EDIFACT decoder free?

Yes. The online decoder is available without an account or credit card and is intended for understanding, testing and exploring EDIFACT messages.

Is my EDIFACT data stored?

The decoder processes submitted messages in memory and does not retain the message content after processing. No account or message history is required.

Can I use the decoder to test messages before going live with a trading partner?

Yes. The decoder is useful for checking message structure and mapped fields before production. The Your API view can also help you preview how the data could be transformed for a downstream system.

How is CleanEDI different from a basic EDIFACT parser?

A basic parser typically stops at segment and data-element breakdown. CleanEDI also maps supported messages to a canonical business representation, renders them as documents, and provides transformation tooling so you can see how the data can reach an application API.

Does CleanEDI integrate with Dynamics 365, SAP or NetSuite?

CleanEDI is designed to deliver clean application data through APIs, webhooks and event-driven integrations. Microsoft Dynamics 365 is currently the primary ERP integration focus, with additional ERP connectors planned.

New to EDIFACT? Read the plain-English EDIFACT guide →

Need more than a decoder?

Turn EDIFACT handling into a production API.

The decoder helps you understand the problem. CleanEDI helps your team stop owning it. Tell us about your trading partners, message types and existing systems and we can discuss a focused proof of concept.

Discuss your integrationSee pricing