EDIFACT ↔ X12 Mapper
Find the EDIFACT ↔ X12 counterpart for 30 common message pairs in one click. Key segments and mapping notes included.
Case-insensitive lookup. Press Enter to map.
How it works
Pick the mapping direction (EDIFACT → X12 or back), type the message
code (for example ORDERS or 850), then press
Enter. Lookup is case-insensitive. The tool surfaces:
- The counterpart message, its label and its typical version.
- Three to seven key segments (for example
UNH ↔ ST,BGM ↔ BEG,NAD ↔ N1+N3+N4). - A note explaining model differences (hierarchy, code lists, granularity).
- The primary source URL (GS1 EANCOM, X12.org, UN/CEFACT, vendor crosswalks).
When the code does not exist in the table, the mapper offers up to three suggestions ranked by Levenshtein distance.
Supported mappings (30 pairs)
| EDIFACT | X12 | Usage |
|---|---|---|
ORDERS | 850 | Purchase Order |
ORDRSP | 855 | PO Acknowledgement |
DESADV | 856 | Despatch Advice / ASN |
INVOIC | 810 | Invoice |
PAYORD | 820 | Payment Order |
REMADV | 820 | Remittance Advice |
PRICAT | 832 | Catalogue |
INVRPT | 846 | Inventory Report |
DELFOR | 830 | Delivery Schedule (forecast) |
DELJIT | 862 | Just-In-Time Schedule |
IFTMIN | 204 | Load Tender |
IFTMBC | 990 | Tender Response |
IFTSTA | 214 | Transport Status |
CONTRL | 997 | Functional Acknowledgement |
APERAK | 824 | Application Advice |
QUOTES | 843 | RFQ Response |
RECADV | 861 | Receiving Advice |
FINSTA | 822 | Account Statement |
SLSRPT | 867 | Sales Report |
PAXLST | 286 | Passenger Manifest |
CUSDEC | 309 | Customs Declaration |
IFTMAN | 211 | Arrival Notice / BOL |
BANSTA | 822 | Banking Status |
DEBADV | 820 | Debit Advice |
CREEXT | 820 | Extended Credit Advice |
GENRAL | — | General Message (no direct X12) |
PARTIN | 838 | Trading Partner Profile |
REQDOC | — | Document Request (no direct X12) |
STATAC | 822 | Statement of Account |
MEDPID | — | Patient Identification (no direct X12) |
Limits
- Segment mapping, not element mapping. The mapper gives the segment-to-segment correspondence. For element-by-element mapping (DE 1001 BGM ↔ BEG02 for instance), use the GS1 EANCOM Implementation Guide or the vendor mapping of your platform (Cleo, OpenText, SPS, TIE Kinetix).
- No runtime translation. This tool documents the mappings; it does not convert an EDIFACT message to X12 or vice versa. Actual conversions require a full grammar and element-by-element mapping.
- Variable granularity. Some pairs (820 ↔ PAYORD/REMADV/DEBADV/CREEXT, 822 ↔ FINSTA/BANSTA/STATAC) have cardinality 1→N. The mapper returns the first pair matching the requested code.
- Releases. Listed segments follow UN/EDIFACT D.96A (the release most used in B2B retail / FMCG) and X12 versions 4010 / 5010. Other releases may differ marginally.
Privacy
Related documentation
- EDIFACT — overview of UN/EDIFACT and its messages.
- X12 — overview of ANSI ASC X12 and its transaction sets.
- GS1 EANCOM: gs1.org — EANCOM.
- ASC X12 — Standards: x12.org — Standards.