In this in-depth EDI standards guide you’ll learn:
Let’s dive right in!
EDI standards began to emerge in the mid-1980s and were purposely designed to be entirely separate (not dependent upon) changes in communication and software technologies.
EDI standards ultimately define the rules to be considered for the issuance and interpretation of a particular EDI business transaction.
In this chapter, we will discuss the following topics:
- Definition of EDI Standards
- History of EDI Standards
- - EDI Standards Adoption by Various Industries
10 Common EDI Communication Standards
Let’s dive right in!
EDI communication standards are the requirements for the format and composition of EDI documents. EDI standards delineate the correct order and location of units of data in each EDI document.
Ever since EDI came onto the scene in 1960, many industries have attempted to standardize B2B communications. Due to various business requirements, many industries have optimized their own standards and formats which resulted in more than a dozen popular EDI standards in use today. EDI standards began to emerge in the mid-1980s and were purposely designed to be entirely separate (not dependent upon) changes in communication and software technologies.
EDI is based on the use of message standards, ensuring that all participants are using a common language. A message standard consists of uniform formats for business documents, which have been adopted for electronic transmission. It also includes security and control elements, as well as other rules and conventions relating to the use of transaction sets/documents that all users agree to follow. This electronic communication means you are efficiently and effectively providing your trading partners with accurate and complete business requirements.
Because EDI documents must be processed by computers rather than humans, a standard format must be used so that the computer will be able to read and understand the documents. In this guide, we are going to discuss the 10 common EDI communication standards
In this chapter, we will talk about the importance of ANSI ASC X12 EDI standard.
It was originally developed to support companies across different industry sectors in North America
In the following chapters, we will discuss some of the important benefits of EDI Standards
Let's get started!
American National Standard Institute (ANSI) founded the Accredited Standards Committee (ASC) in 1979 to develop uniform standards for the inter-industry electronic exchange of business transactions, namely electronic data interchange (EDI). This standard is also sometimes called ANSI X12 Standard or just simply X12.
ANSI X12 was originally developed to support companies across different industry sectors in North America however, today there are more than 300,000 companies worldwide using X12 EDI standards in daily business transactions.
Each EDI X12 transaction type is differentiated by a unique 3-digit number and there are more than 300 different types of X12 EDI standards for various industries from finance, government, healthcare, insurance, banking, transportation, and many more. ASC also contributes to UN/EDIFACT messages that are used widely outside of the United States and develop standards for CICA (Context Inspired Component Architecture) and XML schemas.
Here is the list of some of the common EDI X12 transaction types used by various industries,
| EDI X12 Transaction Number | EDI Transaction Name / Document Type | |
|---|---|---|
|
EDI 180 |
Return Merchandise Authorization and Notification |
|
|
EDI 290 |
Cooperative Advertising Agreements |
|
|
EDI 810 |
Invoice |
|
|
EDI 816 |
Organizational Relationships |
|
|
EDI 832 |
Price/Sales Catalog |
|
|
EDI 846 |
Inventory Inquiry/Advice |
|
|
EDI 850 |
Purchase Order |
|
|
EDI 855 |
Purchase Order Acknowledgment |
|
|
EDI 856 |
Ship Notice/Manifest |
|
|
EDI 857 |
Shipment and Billing Notice |
|
|
EDI 860 |
Purchase Order Change Request – Buyer Initiated |
|
|
EDI 865 |
Purchase Order Change Acknowledgement/Request – Seller Initiated
|
|
|
EDI 869 |
Order Status Inquiry |
Read More |
|
EDI 870 |
Order Status Report |
Read More |
|
EDI 875 |
Grocery Product Purchase Order |
Read More |
|
EDI 876 |
Grocery Products Purchase Order Change |
Read More |
|
EDI 877 |
Manufacturer Coupon Family Code Structure |
Read More |
|
EDI 880 |
Grocery Products Invoice |
Read More |
|
EDI 881 |
Manufacturer Coupon Redemption Detail |
Read More |
|
EDI 885 |
Retail Account Characteristics |
Read More |
|
EDI 887 |
Coupon Notification |
Read More |
|
EDI 888 |
Item Maintenance |
Read More |
| EDI X12 Transaction Number | EDI Transaction Name / Document Type | |
|---|---|---|
|
EDI 180 |
Return Merchandise Authorization and Notification |
|
|
EDI 290 |
Cooperative Advertising Agreements |
|
|
EDI 810 |
Invoice |
|
|
EDI 816 |
Organizational Relationships |
|
|
EDI 832 |
Price/Sales Catalog |
|
|
EDI 846 |
Inventory Inquiry/Advice |
|
|
EDI 850 |
Purchase Order |
|
|
EDI 855 |
Purchase Order Acknowledgment |
|
|
EDI 856 |
Ship Notice/Manifest |
|
|
EDI 857 |
Shipment and Billing Notice |
|
|
EDI 860 |
Purchase Order Change Request – Buyer Initiated |
|
|
EDI 865 |
Purchase Order Change Acknowledgement/Request – Seller Initiated
|
| EDI X12 Transaction Number | EDI Transaction Name / Document Type |
|---|---|
|
EDI 100 |
Business Entity Filings |
|
EDI 150 |
Tax Rate Notification |
|
EDI 151 |
Electronic Filing of Tax Return Data Acknowledgment |
|
EDI 152 |
Statistical Government Information |
|
EDI 153 |
Unemployment Insurance Tax Claim or Charge Information |
|
EDI 154 |
Uniform Commercial Code Filing |
|
EDI 175 |
Court and Law Enforcement Notice |
|
EDI 176 |
Court Submission TYPE |
|
EDI 185 |
Royalty Regulatory Report |
|
EDI 195 |
Federal Communications Commission (FCC) License Application |
|
EDI 251 |
Pricing Support |
|
EDI 256 |
Periodic Compensation |
|
EDI 280 |
Voter Registration Information |
|
EDI 870 |
Order Status Report |
|
EDI 875 |
Grocery Product Purchase Order |
| EDI X12 Transaction Number | EDI Transaction Name / Document Type | |
|---|---|---|
|
EDI 104 |
Air Shipment Information |
|
|
EDI 106 |
Motor Carrier Rate Proposal |
|
|
EDI 107 |
Request for Motor Carrier Rate Proposal |
|
|
EDI 108 |
Response to a Motor Carrier Rate Proposal |
|
|
EDI 110 |
Air Freight Details and Invoice |
|
|
EDI 204 |
Motor Carrier Load Tender |
|
|
EDI 210 |
Motor Carrier Freight Details and Invoice |
|
|
EDI 211 |
Motor Carrier Bill of Lading |
|
|
EDI 212 |
Motor Carrier Delivery Trailer Manifest |
|
|
EDI 213 |
Motor Carrier Shipment Status Inquiry |
|
|
EDI 214 |
Transportation Carrier Shipment Status Message |
|
|
EDI 215 |
Motor Carrier Pick-up Manifest |
|
|
EDI 216 |
Motor Carrier Shipment Pick-up Notification |
|
|
EDI 217 |
Motor Carrier Loading and Route Guide |
|
|
EDI 218 |
Motor Carrier Tariff Information |
|
|
EDI 240 |
Grocery Products Purchase Order Change |
|
|
EDI 250 |
Purchase Order Shipment Management Document |
|
|
EDI 601 |
U.S. Customs Export Shipment Information |
|
|
EDI 602 |
Transportation Services Tender |
|
|
EDI 714 |
Intermodal Group Loading Plan |
|
|
EDI 920 |
Loss or Damage Claim – General Commodities |
|
|
EDI 990 |
Accept or Decline 204 Shipment |
| EDI X12 Transaction Number | EDI Transaction Name / Document Type |
|---|---|
|
EDI 248 |
Account Assignment/Inquiry and Service/Status |
|
Invoice |
|
|
EDI 811 |
Consolidated Service Invoice/Statement |
|
Credit/Debit Adjustment |
|
|
EDI 818 |
Commission Sales Report |
|
EDI 819 |
Operating Expense Statement |
|
Payment Order/Remittance Advice |
|
|
EDI 821 |
Financial Information Reporting |
|
EDI 822 |
Account Analysis |
|
EDI 823 |
Lockbox |
|
Application Advice |
|
|
EDI 827 |
Financial Return Notice |
|
Debit Authorization |
|
|
EDI 829 |
Payment Cancellation Request |
|
EDI 831 |
Application Control Totals |
|
EDI 859 |
Freight Invoice |
|
EDI 980 |
Functional Group Totals |
100% EDI Compliance Guaranteed!
In this chapter, we will discuss about TRADACOMS,
It was originally introduced in 1982.
It is primarily used in the UK retail sector.
Let’s begin!
Tradacoms (Trading DAA Communications) is an early EDI standard that was originally introduced in 1982 and was primarily used in the UK retail sector. It was maintained and extended by the UK Article Numbering Association, now called GS1 UK. Slowly this standard become less obsolescent as its development of it effectively ceased in 1995. Despite this, it has proved durable and most of the retail EDI traffic in the UK still uses it today.
TRADACOMS uses multi messages instead of relying on a format of single messaging. TRADACOMS communication is comprised of 26 messages structured in a hierarchy. Each TRADACOMS message, much like EDIFACT, is given a six-letter application reference. For example, an invoice message is INVFIL, a payment order is PAYORD, a utility bill is UTLHDR, and so on.
A list of Tradacoms document standards is provided below
| Application Reference | Message Type |
|---|---|
|
ACKHDR |
Acknowledgement |
|
AVLHDR |
Availability Report |
|
BTOHDR |
Book Trade Orders |
|
PVUHDR |
Book Trade Price/Availability Update |
|
CAKHDR |
Claims Acknowledgement |
|
CLAHDR |
Claims Message |
|
CORHDR |
Complex Order |
|
CREHDR |
Credit Note |
|
CREADV |
Credit Advice |
|
CUSHDR |
Customer Information |
|
DEBADV |
Debit Advice |
|
DLCHDR |
Delivery Confirmation |
|
DELHDR |
Delivery Notice |
|
DYEHDR |
Dye Instruction |
|
GENHDR |
General Communication |
|
HSOHDR |
Home Shopping Orders |
|
INVFIL |
Invoice |
|
ISSUES |
Issues |
|
LPRHDR |
Location Planning Report |
|
PICHDR |
Picking Instruction |
|
ORDHDR |
Purchase Order |
|
PAYORD |
Payment Order |
|
PRIHDR |
Price Information |
|
PROHDR |
Product Planning Report |
|
RDAHDR |
Retailer Database |
|
RDBHDR |
Retail B, 1-4 Retailer Database |
|
RIFHDR |
Retail Issues File |
|
SADHDR |
Stock Adjustment |
|
SNPSTS |
Stock Snapshot |
|
SRMHDR |
Statement & Remittance Details |
|
SORDET |
Supply and Returns Details |
|
SORDAY |
Supply and Returns Summary |
|
SRSHDR |
Supply and Returns Summary |
|
RIFHDR |
Retail Issues File |
|
UCNHDR |
Uplift Confirmation |
|
UPLHDR |
Uplift Instruction |
|
UTLHDR |
Utility Bill |
In this chapter we will discuss information related to UN/EDIFACT.
- UN/EDIFACT was developed by the United Nations
- EDIFACT is widely used across Europe
- Maintenance and further development of this standard is done through UN/CEFACT
Lets go in more detail.
UN/EDIFACT (United Nations/Electronic Data Interchange for Administration, Commerce, and Transport is the international standard that was developed by the United Nations). Comprise a set of internationally agreed standards, directories, and guidelines for the electronic interchange of structured data, between independent computerized information systems. The work of maintenance and further development of this standard is done through the United Nations Centre for Trade Facilitation and Electronic Business (UN/CEFACT) under the UN Economic Commission for Europe.
Principles for trade data interchange
The principles for the establishment of any trade data interchange method or system may be summarized as follows:
Data elements in the United Nations Trade Data Elements Directory (UNTDED) are used in the segments specified in the present United Nations Trade Data Interchange Directory (UNTDID) and are also, in a condensed form for this purpose, including in a special directory (UNEDED).
The EDIFACT standard provides a set of syntax rules to structure, an interactive exchange protocol, and provides a set of standard messages which allow multi-country and multi-industry exchange of electronic business documents. EDIFACT is widely used across Europe, mainly since many companies adopted it very early on. EDIFACT has seen some adoption in the ASPAC region, however, there are currently more XML-based standards being used in this region today.
A list of UN/EDIFACT document standards is provided below:
| Application Reference | Message Type |
|---|---|
|
APERAK |
Application error and acknowledgement message |
|
AUTHOR |
Authorization message |
|
AVLREQ |
Availability request – interactive message |
|
AVLRSP |
Availability response – interactive message |
|
BALANC |
Balance message |
|
BANSTA |
Banking status message |
|
BAPLIE |
Bayplan/stowage plan occupied and empty locations message |
|
BAPLTE |
Bayplan/stowage plan total numbers message |
|
BERMAN |
Berth management message |
|
BMISRM |
Bulk marine inspection summary report message |
|
BOPBNK |
Bank transactions and portfolio transactions report message |
|
BOPCUS |
Balance of payment customer transaction report message |
|
BOPDIR |
Direct balance of payment declaration message |
|
BOPINF |
Balance of payment information from customer message |
|
BUSCRD |
Business credit report message |
|
CALINF |
Vessel call information message |
|
CASINT |
Request for legal administration action in civil proceedings message |
|
CASRES |
Legal administration response in civil proceedings message |
|
CHACCO |
Chart of accounts message |
|
CLASET |
Classification information set message |
|
CNTCND |
Contractual conditions message |
|
COACSU |
Commercial account summary message |
|
COARRI |
Container discharge/loading report message |
|
CODECO |
Container gate-in/gate-out report message |
|
CODENO |
Permit expiration/clearance ready notice message |
|
COEDOR |
Container stock report message |
|
COHAOR |
Container special handling order message |
|
COLREQ |
Request for a documentary collection message |
|
COMDIS |
Commercial dispute message |
|
CONAPW |
Advice on pending works message |
|
CONDPV |
Direct payment valuation message |
|
CONDRA |
Drawing administration message |
|
CONDRO |
Drawing organization message |
|
CONEST |
Establishment of contract message |
|
CONITT |
Invitation to tender message |
|
CONPVA |
Payment valuation message |
|
CONQVA |
Quantity valuation message |
|
CONRPW |
Response of pending works message |
|
CONTEN |
Tender message |
|
CONWQD |
Work item quantity determination message |
|
COPARN |
Container announcement message |
|
COPAYM |
Contributions for payment |
|
COPINO |
Container pre-notification message |
|
COPRAR |
Container discharge/loading order message |
|
COREOR |
Container release order message |
|
COSTCO |
Container stuffing/stripping confirmation message |
|
COSTOR |
Container stuffing/stripping order message |
|
CREADV |
Credit advice message |
|
CREEXT |
Extended credit advice message |
|
CREMUL |
Multiple credit advice message |
|
CUSCAR |
Customs cargo report message |
|
CUSDEC |
Customs declaration message |
|
CUSEXP |
Customs express consignment declaration message |
|
CUSPED |
Periodic customs declaration message |
|
CUSREP |
Customs conveyance report message |
|
CUSRES |
Customs response message |
|
DEBADV |
Debit advice message |
|
DEBMUL |
Multiple debit advice message |
|
DEBREC |
Debts recovery message |
|
DELFOR |
Delivery schedule message |
|
DELJIT |
Delivery just in time message |
|
DESADV |
Dispatch advice message |
|
DESTIM |
Equipment damage and repair estimate message |
|
DGRECA |
Dangerous goods recapitulation message |
|
DIRDEB |
Direct debit message |
|
DIRDEF |
Directory definition message |
|
DMRDEF |
Data maintenance request definition message |
|
DMSTAT |
Data maintenance status report/query message |
|
DOCADV |
Documentary credit advice message |
|
DOCAMA |
Advice of an amendment of a documentary credit message |
|
DOCAMI |
Documentary credit amendment information message |
|
DOCAMR |
Request for an amendment of a documentary credit message |
|
DOCAPP |
Documentary credit application message |
|
DOCARE |
Response to an amendment of a documentary credit message |
|
DOCINF |
Documentary credit issuance information message |
|
ENTREC |
Accounting entries message |
|
FINCAN |
Financial cancellation message |
|
FINPAY |
Multiple interbank funds transfer message |
|
FINSTA |
Financial statement of an account message |
|
GENRAL |
General purpose message |
|
GESMES |
Generic statistical message |
|
HANMOV |
Cargo/goods handling and movement message |
|
ICASRP |
Insurance claim assessment and reporting message |
|
ICSOLI |
Insurance claim solicitor’s instruction message |
|
IFCSUM |
Forwarding and consolidation summary message |
|
IFTCCA |
Forwarding and transport shipment charge calculation message |
|
IFTDGN |
Dangerous goods notification message |
|
IFTFCC |
International transport freight costs and other charges message |
|
IFTIAG |
Dangerous cargo list message |
|
IFTICL |
Cargo insurance claims message |
|
IFTMAN |
Arrival notice message |
|
IFTMBC |
Booking confirmation message |
|
IFTMBF |
Firm booking message |
|
IFTMBP |
Provisional booking message |
|
IFTMCA |
Consignment advice message |
|
IFTMCS |
Instruction contract status message |
|
IFTMFR |
International Forwarding And Transport |
|
IFTMIN |
Instruction message |
|
IFTRIN |
Forwarding and transport rate information message |
|
IFTSAI |
Forwarding and transport schedule and availability information me |
|
IFTSTA |
International multimodal status report message |
|
IFTSTQ |
International multimodal status request message |
|
IHCEBI |
Interactive health insurance eligibility and benefits inquiry and |
|
IHCLME |
Health care claim or encounter request and response – interactive |
|
IMPDEF |
EDI implementation guide definition message |
|
INFCON |
Infrastructure condition message |
|
INFENT |
Enterprise accounting information message |
|
INSDES |
Instruction to dispatch message |
|
INSPRE |
Insurance premium message |
|
INSREQ |
Inspection request message |
|
INSRPT |
Inspection report message |
|
INTCHG |
Interchange Control Structures |
|
INVOIC |
Invoice message |
|
INVRPT |
Inventory report message |
|
IPPOAD |
Insurance policy administration message |
|
IPPOMO |
Motor insurance policy message |
|
ISENDS |
Intermediary system enablement or disablement message |
|
ITRRPT |
In transit report detail message |
|
JAPRES |
Job application result message |
|
JINFDE |
Job information demand message |
|
JOBAPP |
Job application proposal message |
|
JOBCON |
Job order confirmation message |
|
JOBMOD |
Job order modification message |
|
JOBOFF |
Job order message |
|
JUPREQ |
Justified payment request message |
|
LEDGER |
Ledger message |
|
LREACT |
Life reinsurance activity message |
|
LRECLM |
Life reinsurance claims message |
|
MEDPID |
Person identification message |
|
MEDPRE |
Medical prescription message |
|
MEDREQ |
Medical service request message |
|
MEDRPT |
Medical service report message |
|
MEDRUC |
Medical resource usage and cost message |
|
MEQPOS |
Means of transport and equipment position message |
|
MOVINS |
Stowage instruction message |
|
MSCONS |
Metered services consumption report message |
|
ORDCHG |
Purchase order change request message |
|
ORDERS |
Purchase order message |
|
ORDRSP |
Purchase order response message |
|
OSTENQ |
Order status enquiry message |
|
OSTRPT |
Order status report message |
|
PARTIN |
Party information message |
|
PASREQ |
Travel tourism and leisure product application status request |
|
PASRSP |
Travel tourism and leisure product application status response |
|
PAXLST |
Passenger list message |
|
PAYDUC |
Payroll deductions advice message |
|
PAYEXT |
Extended payment order message |
|
PAYMUL |
Multiple payment order message |
|
PAYORD |
Payment order message |
|
PRICAT |
Price/sales catalogue message |
|
PRIHIS |
Pricing history message |
|
PROCST |
Project cost reporting message |
|
PRODAT |
Product data message |
|
PRODEX |
Product exchange reconciliation message |
|
PROINQ |
Product inquiry message |
|
PROSRV |
Product service message |
|
PROTAP |
Project tasks planning message |
|
PRPAID |
Insurance premium payment message |
|
QALITY |
Quality data message |
|
QUOTES |
Quote message |
|
RDRMES |
Raw data reporting message |
|
REBORD |
Reinsurance bordereau message |
|
RECADV |
Receiving advice message |
|
RECALC |
Reinsurance calculation message |
|
RECECO |
Credit risk cover message |
|
RECLAM |
Reinsurance claims message |
|
RECORD |
Reinsurance core data message |
|
REGENT |
Registration of enterprise message |
|
RELIST |
Reinsured objects list message |
|
REMADV |
Remittance advice message |
|
REPREM |
Reinsurance premium message |
|
REQDOC |
Request for document message |
|
REQOTE |
Request for quote message |
|
RESETT |
Reinsurance settlement message |
|
RESMSG |
Reservation message |
|
RESREQ |
Reservation request – interactive message |
|
RESRSP |
Reservation response – interactive message |
|
RETACC |
Reinsurance technical account message |
|
RETANN |
Announcement for returns message |
|
RETINS |
Instruction for returns message |
|
RPCALL |
Repair call message |
|
SAFHAZ |
Safety and hazard data message |
|
SANCRT |
International movement of goods governmental regulatory message |
|
SKDREQ |
Schedule request – interactive message |
|
SKDUPD |
Schedule update – interactive message |
|
SLSFCT |
Sales forecast message |
|
SLSRPT |
Sales data report message |
|
SOCADE |
Social administration message |
|
SSIMOD |
Modification of identity details message |
|
SSRECH |
Worker’s insurance history message |
|
SSREGW |
Notification of registration of a worker message |
|
STATAC |
Statement of account message |
|
STLRPT |
Settlement transaction reporting message |
|
SUPCOT |
Superannuation contributions advice message |
|
SUPMAN |
Superannuation maintenance message |
|
SUPRES |
Supplier response message |
|
TANSTA |
Tank status report message |
|
TAXCON |
Tax control message |
|
TIQREQ |
Travel tourism and leisure information inquiry request – interactive |
|
TIQREQ |
Travel tourism and leisure information inquiry request – interactive |
|
TIQRSP |
Travel tourism and leisure information inquiry response – interactive |
|
TPFREP |
Terminal performance message |
|
TSDUPD |
Timetable static data update – interactive message |
|
TUPREQ |
Travel, tourism and leisure data update request – interactive message |
|
TUPRSP |
Travel, tourism and leisure data update response – interactive message |
|
UTILMD |
Utilities master data message |
|
UTILTS |
Utilities time series message |
|
VATDEC |
Value added tax message |
|
VESDEP |
Vessel departure message |
|
WASDIS |
Waste disposal information message |
|
WKGRDC |
Work grant decision message |
|
WKGRRE |
Work grant request message |
ODETTE is a group that represents the interests of the automotive industry in Europe.
The great strength of ODETTE is that they are created by people who are experts in their field.
Provides robust security via encryption methods and digital certificates
Lets get started,
ODETTE EDI Standards
Organization of Data Exchange by Tele Transmission in Europe also known as ODETTE is a group that represents the interests of the automotive industry in Europe. Just like AIAG (Automotive Industry Action Group) in North America. ODETTE developed two communication standards/protocols such as OFTP and OFTP2. These communication standards provide robust security via encryption methods and digital certificates to communicate with various software securely and efficiently to successfully exchange EDI data.
ODETTE mission is to improve the efficiency and enhance the competitiveness of the European automotive industry within the global economy. To realize this mission, Odette develops standards and provides tools and services which support the digitalization of logistics management and supply chain communications throughout the world. Thousands of automotive companies use Odette standards and depend on the integrity, reliability, and security of Odette services.
The great strength of our standards is that they are created by people who are experts in their field and know the real needs of the companies they represent. They are regularly reviewed to ensure that they remain relevant in the ever-evolving automotive world and new ones are developed to meet fresh challenges as they arise.
We know, however, that the value of standards lies in wide-scale adoption, so we make them freely available to the whole community.
| Application Reference | Message Type |
|---|---|
|
DELINS |
Delivery Forecast / Delivery |
|
EXHAND |
For Delivery Schedule Exception Handling |
|
CALDEL |
JIT Delivery |
|
SYNCRO |
Sequenced Delivery |
|
KANBAN |
KANBAN Delivery
|
|
FORDIS |
‘Ready for Dispatch’ Advice
|
|
AVIEXP |
Dispatch Advice
|
|
INVOIC |
Invoice
|
|
STOACT |
Inventory Report
|
|
TRINAD |
Forwarding Instruction
|
|
CONSUM |
Consignment Consolidation
|
|
ORDERR |
Purchase Order |
|
ORDCHG |
Order Change
|
|
REPORD |
Order Response
|
|
PRILST |
Price List Based
|
|
REMADV |
Remittance Advice
|
|
STATAC |
Account Statement
|
EANCOM was originally developed for the retail sector.
But now found in a variety of other industry sectors such as healthcare, construction, and publishing
EANCOM was originally developed for the retail sector and has subsequently grown to become the most widely used UN/EDIFACT subset and is now found in a variety of other industry sectors such as healthcare, construction, and publishing.
EANCOM standard messages can be divided into four categories,
Master Data Messages:
These messages contain data that rarely changes such as product measurements, names, addresses, etc. This includes ‘The party information message’ and ‘The product information messages’
The party information message: It identifies all the locations such as name, contact person, address financial accounts, EAN location numbers, etc.) associated with subsequent commercial transactions and their related operational information
The product information messages: These messages provide information such which is descriptive, logistical, and financial of a product or a service.
Commercial Transactions Messages
There are four types of commercial transaction messages which cover basic trading cycle messages such as quotation requests to remittance advice:
Reports and Planning
This type of message includes trading reports which allow partners to plan the future. They provide up-to-date reports and forecasts concerning delivery, sales, and stocks which enables business partners to exchange critical information to understand each other requirements and enable the partners involved to plan their activities and marketing strategies.
Benefits of ENCOM
Since its inception in 1986, VICS has operated as an independent entity, with the support and assistance of GS1 US
In 2012, GS1 US and VICS signed a memorandum of understanding to merge their operations
VICS stands for The Voluntary Inter-Industry Commerce Standard. Since its inception in 1986, VICS has operated as an independent entity, with the support and assistance of GS1 US. VICS has enabled companies in the retail and consumer-focused industries to eliminate billions of dollars of waste and delay. By creating voluntary guidelines, often referred to as “standards,” VICS has created new best practices that ultimately lead to lower costs and better availability of products for consumers. VICS’ volunteer members improve the flow of products and information throughout retailing and the consumer-focused industries that supply retail.
The Association provides leadership and an environment in which executives can make a difference in their industry, their company performance – and their personal commitment to make the world work a little bit better. VICS’ members help define the next best practices in the industries and thus anticipate and optimize business processes and costs.
In 2012, GS1 US and the Voluntary Interindustry Commerce Solutions (VICS) Association have signed a memorandum of understanding to merge their operations. The merger is designed to streamline the standards adoption process for industry and give the not-for-profit organizations’ members access to standards for a broader range of supply-chain functions.
The joint GS1 US-VICS initiative will reside in the GS1 US Apparel and General Merchandise group, opening the door for cross-industry synergies, and providing expanded resources, technical expertise, and global reach.
VDA serves the needs of the German automotive industry by developing standards and best practices
The VDA has developed over thirty messages to meet the need of companies such as VW, Audi, Bosch, Continental, and Daimler AG
The German Association of the automotive industry (VDA) has its headquarters in Berlin, Germany. VDA serves the needs of the German automotive industry by developing standards and best practices. VDA consists of more than 620 companies involved in production for the automotive industry in the Federal Republic of Germany. The members are divided into three manufacturer groups automobile manufacturers, automotive suppliers, and trailers, special bodies, buses.
These three manufacturer groups find their representation in three divisions each assigned a managing director. More than 80 employees in 20 departments actively pursue the interests of the German automotive industry.
The VDA has developed over thirty messages to meet the need of companies such as VW, Audi, Bosch, Continental, and Daimler AG. Further information about these messages can be found via the link below.
A list of VDA document standards is provided below:
| Application Reference | Message Type |
|---|---|
|
4902 |
AcknowledgTransport Label Barcode-enabled incl. VDA 4913
ement |
|
4905 |
Call off
|
|
4905/2 |
Call off – Delivery Instruction (Odette Message DELINS)
|
|
4906 |
Invoice |
|
4907 |
Remittance Advice |
|
4908 |
Credit Advice
|
|
4911 |
Prices |
|
4912 |
Delivery Note incl. VDA 4913
|
|
4913 |
Delivery Note |
|
4914 |
Odette specification for file transfer |
|
4915 |
Detailed Call Off (JIT) |
|
4916 |
Call Off Just-in-sequence |
|
4918 |
Vehicle Identification and Transport Data |
|
4919 |
Vehicle Arrival and Departure Notification |
|
4920 |
Forwarding Instruction |
|
4921 |
Delivery Data |
|
4922 |
Forwarding Instruction incl. VDA 4913 |
|
4923 |
Enquiry (Odette Message ENQIRY) |
|
4924 |
Offer/Quotation (Odette Message OFFERR) |
|
4925 |
Purchase Order |
|
4926 |
Acknowledgement of Order (Odette Message REPORD)
|
|
4927 |
Equipment Statement and Equipment Movement
|
|
4929 |
Delivery Note (Odette Message AVIEXP) |
|
4932 |
Invoice (Odette-Nachricht INVOIC) |
|
4951 |
Engineering Data Message (ENGDAT) |
|
4970 |
Delivery Forecast |
|
4971 |
Collection Order |
|
4972 |
Dispatch Note ex Works/Plant |
|
4973 |
Vehicle Arrival |
|
4974 |
Vehicle Departure |
|
4975 |
Change / Information Note |
|
4976 |
Change / Information Confirmation |
|
4977 |
Damage Note |
|
4978 |
Repair Start / End Note |
|
4979 |
Ready for Dispatch Note |
|
4980 |
Loading Instructions |
A key component of HIPAA is the establishment of national standards for electronic health care transactions and national identifiers for providers, health insurance plans, and employers
It protect sensitive patient health information from being disclosed without the patient’s consent or knowledge
HIPPA stands for The Health Insurance Portability and Accountability Act was enacted by the U.S congress in 1996. It’s a federal law that required the creation of national standards to protect sensitive patient health information from being disclosed without the patient’s consent or knowledge. It generally prohibits healthcare providers and healthcare businesses, called covered entities, from disclosing protected information to anyone other than a patient and the patient’s authorized representatives without their consent. With limited exceptions, it does not restrict patients from receiving information about themselves. It does not prohibit patients from voluntarily sharing their health information however they choose, nor – if they disclose medical information to family members, friends, or other individuals not a part of a covered entity – legally require them to maintain confidentiality.
The act consists of five titles,
Title 1 – Health Care Access, Portability, and Renewability
Title 2 – Preventing Health Care Fraud and Abuse, Administrative Simplification, Medical Liability Reform
Title 3 – Tax-related health provisions governing medical savings accounts
Title 4 – Application and enforcement of group health insurance requirements
Title 5 – Revenue offset governing tax deductions for employers
A key component of HIPAA is the establishment of national standards for electronic health care transactions and national identifiers for providers, health insurance plans, and employers. The standards are meant to improve the efficiency and effectiveness of the North American health care system by encouraging the widespread use of EDI in the U.S health care system.
The HIPAA EDI transaction sets are based on X12 and the key message types are described below.
| EDI X12 Transaction Number | EDI Transaction Name / Document Type |
|---|---|
|
EDI 835 |
EDI Health Care Claim Payment/Advice Transaction Set
|
|
EDI 834 |
EDI Benefit Enrollment and Maintenance Set
|
|
EDI 820 |
Payment Order/Remittance Advice |
|
EDI 270 |
Eligibility, Coverage or Benefit Inquiry |
|
EDI 271 |
Eligibility, Coverage or Benefit Information |
|
EDI 276 |
Health Care Claim Status Request |
|
EDI 277 |
Health Care Claim Status Notification |
|
EDI 278 |
Health Care Services Insurance/Benefit Review Information |
|
EDI 997 |
Functional Acknowledgment |
The RosettaNet standard is widely spread in the global semiconductor industry, but also in electronic components, consumer electronics, telecommunication, and logistics
RosettaNet is a subsidiary of GS1 US, formerly the Uniform Code Council, Inc. (UCC). RosettaNet is a non-profit consortium aimed at establishing standard processes for the sharing of business information (B2B). This consists of a consortium of major computer, consumer electronics, semi-conductor manufacturers, telecommunications, and logistics companies working together to create and implement industry-wide, open e-business process standards. These standards form a common e-business language, aligning processes between supply chain partners on a global basis.
The standard is widely spread in the global semiconductor industry, but also in electronic components, consumer electronics, telecommunication, and logistics. RosettaNet originated in the USA and is widely used there, but it is also well accepted and even supported by governments in Asia. Due to the widespread use of EDIFACT in Europe, RosettaNet is used less, but it is growing.
The RosettaNet document standard is based on XML and defines message guidelines, business processes interface and implementation frameworks for interactions between companies. Using RosettaNet Partner Interface Processes (PIPs), business partners of all sizes can connect electronically to process transactions and move information within their extended supply chains.
RosettaNet covers a broad range of logistics and financial transactions, including purchase orders, shipment notices, invoices, return requests, quotes, and more. Further information about
RosettaNet PIP documents can be found at the link below.
| Application Reference | Message Type |
|---|---|
|
3A1 |
Request Quote |
|
3A2 |
Request Price and Availability
|
|
3A3 |
Request Shopping Cart Transfer
|
|
3A4 |
Request Purchase Order |
|
3A5 |
Query Order Status |
|
3A6 |
Distribute Order Status
|
|
3A7 |
Notify of Purchase Order Update |
|
3A8 |
Request Purchase Order Change
|
|
3A9 |
Request Purchase Order Cancellation |
|
3A10 |
Notify of Quote Acknowledgement |
|
3A13 |
Notify of Purchase Order Information |
|
3A14 |
Distribute Planned Order |
|
3B1 |
Distribute Transportation Projection |
|
3B2 |
Notify of Advance Shipment |
|
3B3 |
Distribute Shipment Status |
|
3B4 |
Query Shipment Status |
|
3B5 |
Request Shipment Change |
|
3B6 |
Notify of Shipments Tendered |
|
3B11 |
Notify of Shipping Order |
|
3B14 |
Request Shipping Order Cancellation |
|
3B18 |
Notify of Shipment Documentation
|
|
3C1 |
Return Product
|
|
3C2 |
Request Financing Approval |
|
3C3 |
Notify of Invoice
|
|
3C4 |
Notify of Invoice Reject
|
|
3C5 |
Notify of Billing Statement
|
|
3C6 |
Notify of Remittance Advice |
|
3C7 |
Notify of Self-Billing Invoice |
SWIFT operates a worldwide financial messaging network that exchanges messages between banks and financial institutions.
As of 2022, SWIFT linked 10K+ financial institutions across 200+ countries
SWIFT stands for The Society of Worldwide Interbank Financial Telecommunication. It was formed in 1973 and is headquartered in Brussels. SWIFT operates a worldwide financial messaging network that exchanges messages between banks and financial institutions. SWIFT also markets software and services to financial institutions, much of it for use on the SWIFTNet Network.
SWIFTNet is the infrastructure used to exchange these documents and FIN, InterAct and FileAct are used to encode the SWIFT documents for transmission. Most interbank messages use the SWIFT network. As of 2022, SWIFT linked 10K+ financial institutions across 200+ countries. The SWIFT document standard is split into four areas,
| Documentary Credits & Guarantees | |
|---|---|
|
700 |
Issue of Documentary Credit
|
|
705 |
Pre-Advice of a Documentary Credit
|
|
707 |
Amendment to a Documentary Credit
|
|
710 |
Advice of a 3rd Bank’s Documentary Credit
|
|
730 |
Acknowledgement
|
|
732 |
Advice of Discharge
|
|
734 |
Advice of Refusal |
|
740 |
Authorization to Reimburse
|
|
742 |
Reimbursement Claim |
|
747 |
Amendment to an Authorization to Reimburse
|
|
750 |
Advice of Discrepancy |
|
752 |
Authorization to Pay, Accept or Negotiate
|
|
754 |
Advice of Payment/Acceptance/Negotiations
|
|
756 |
Advice of Reimbursement or Payment
|
|
760 |
Guarantee/Standby LC |
|
767 |
Guarantee/ Standby LC Amendment
|
|
768 |
Acknowledgement of a Guarantee/ Standby LC Message
|
|
769 |
Advice of Reduction or Release
|
| Cash Management & Customer Status | |
|---|---|
|
900 |
Confirmation of Debit
|
|
920 |
Request Message
|
|
935 |
Rate Change Advice
|
|
940 |
Customer Statement Message
|
|
941 |
Balance Report
|
|
942 |
Interim Transaction Report
|
|
950 |
Statement Message
|
|
960 |
Request for Service Initiation Message
|
|
961 |
Request for Service Initiation Message
|
|
961 |
Initiation Response Message
|
|
962 |
Key Service Message
|
|
963 |
Key Acknowledgement Message
|
|
964 |
Error Message
|
|
965 |
Error in Key Service Message
|
|
966 |
Discontinue Service Message
|
|
967 |
Discontinuation Acknowledgement Message
|
|
970 |
Netting Statement
|
|
971 |
Netting Balance Report
|
|
973 |
Netting Request Statement
|
|
985 |
Status Enquiry
|
|
986 |
Status Report
|
| Treasury Markets–Foreign Exchange, Money Markets & Derivatives | |
|---|---|
|
300 |
Foreign Exchange Confirmation
|
|
303 |
Forex/Currency Option Allocation Instruction
|
|
305 |
Foreign Currency Option Confirmation
|
|
306 |
Foreign Currency Option Confirmation |
|
307 |
Advice/Instruction of a 3rd Party FX Deal |
|
308 |
Instruction for a Gross/Net Settlement of 3rd Party FX deals
|
|
320 |
Fixed Loan/Deposit Confirmation |
|
321 |
Instruction to Settle a 3rd Party Loan /Deposit
|
|
330 |
Call/Notice (Loan/Deposit Confirmation) |
|
304 |
Forward Rate Agreement Confirmation
|
|
341 |
Forward Rate Agreement Settlement Confirmation |
|
341 |
Forward Rate Agreement Settlement Confirmation |
|
350 |
Advice of Loan/Deposit Interest Payment |
|
360 |
Forward Rate Agreement Settlement Confirmation |
|
361 |
Cross Currency Interest Rate Swap Confirmation
|
|
362 |
Interest Rate Reset/Advice of Payment |
|
364 |
Single Currency Interest Rate Derivative Confirmation
|
|
365 |
Cross Currency Interest Rate Swap Termination/Recouponing Confirmation
|
|
380 |
Foreign Exchange Order
|
|
381 |
Foreign Exchange Order Confirmation
|
| Customer Payments & Checks | |
|---|---|
|
101 |
Request for Transfer
|
|
102 / 102+ |
Multiple Customer Credit Transfer
|
|
103 / 103+ / 103 REMIT |
Single Customer Credit Transfer
|
|
104 |
Direct Debit and Request for Debit Transfer Message |
|
105 |
EDIFACT Envelope |
|
106 |
EDIFACT Envelope
|
|
107 |
General Direct Message |
|
110 |
Advice of Check(s)
|
|
111 |
Request for Stop Payment of a Check |
|
112 |
Status of a Request for Stop Payment of a Check |
|
121 |
Multiple Interbank Funds Transfer |
Here are some of the benefits of EDI standards:
- Improved data accuracy
- Reduce labor processing cost
- Reduce filing of paperwork
- Be complaint with trading partners
Read more!
The reason for implementing EDI standards is because suppliers and other trading partner facilities are increasingly more tactical rather than strategic, with speed and accuracy acting as the driving force behind this decision. Additional benefits include:
EDI standards are useful for electronically exchanging structured data between business partners. As discussed in this guide, there are different EDI standards. Some were developed specifically for industries, and others spread throughout more sectors or regions.
EDI standards ultimately define the rules to be considered for the issuance and interpretation of a particular EDI business transaction. Thus, purchase orders, shipping invoices, notices, or any other document to be exchanged must be generated in compliance with the standards defined by the EDI language used.
These standards establish the order in which the information must be presented, the minimum mandatory data to be shown in each message or document, the methodology to be used to label the different fields obtained in a message, etc.
A business should consider its industry, geographic location, and the standards used by its trading partners. Consulting with an experienced EDI provider can help determine the most appropriate standard to ensure compatibility and compliance with trading partners.
Yes, companies can implement multiple EDI standards to accommodate trading partners from different regions or industries. Advanced EDI systems often support various standards, enabling seamless communication regardless of the partner’s preferred format.
Different industries may use customized EDI standards or subsets of broader standards to meet their unique needs. For instance, the healthcare industry in the U.S. follows HIPAA EDI standards, while the retail industry may use variations of X12 or EDIFACT standards suited to inventory and order management.
Transaction sets are specific types of EDI documents defined within each standard, representing different business processes. For example, ANSI X12 includes transaction sets such as 850 (Purchase Order) and 810 (Invoice), each designed for a particular transaction type.
The main EDI standards include ANSI X12 (commonly used in North America), EDIFACT (primarily used internationally), and XML-based EDI. Each standard is suited to specific regions or industries, allowing for global and industry-specific compliance.
Unlock the full potential of your supply chain with our comprehensive EDI Buyer's Guide — your first step towards seamless, efficient, and error-free transactions
