Internet EDI Solution

Communication of EDI messages via the Internet. Internet EDI is most often considered in contrast to doing EDI via a VAN (Value Added Network). In this situation, Internet EDI is simply a communications pathway, where EDI data is passed between trading partners using Internet protocols.

• Management capabilities for hundreds of trading partners
• MH10 shipping labels
• Access to a dedicated, experienced and knowledgeable service team
• Proactive notification email alerts
• Business rule validations
• Duplicate checking
• Access to Commport’s visibility tool, RouterLiNK
• Reports for all inbound transactions
• Retrievable archive
• Document import and export to enable partial integration

EDI compliance refers to a business's capacity to accurately send and receive EDI transactions according to the order data requirements of its EDI trading partners. Each document must adhere to a specific EDI format to ensure the successful exchange of EDI documents.

• EDI 204 Motor Carrier Load Tender
• EDI 210 Motor Carrier Freight Details and Invoice
• EDI 211 Motor Carrier Bill of Lading
• EDI 214 Transportation Carrier Shipment Status Message
• EDI 310 Freight Receipt and Invoice (Ocean)
• EDI 315 Status Details (Ocean)
• EDI 753 Request for Routing Instructions
• EDI 754 Routing Instructions
• EDI 810 Invoice
• EDI 811 Consolidated Service Invoice/Statement
• EDI 812 Credit/Debit Adjustment
• EDI 816 Organizational Relationships
• EDI 819 Joint Interest Billing and Operating Expense Statement
• EDI 820 Payment Order/Remittance Advice
• EDI 824 Application Advice
• EDI 830 Planning Schedule with Release Capability
• EDI 832 Price/Sales Catalog
• EDI 840 Request for Quotation
• EDI 843 Response to Request for Quotation
• EDI 844 Product Transfer Account Adjustment
• EDI 845 Price Authorization Acknowledgment/Status
• EDI 846 Inventory Inquiry/Advice
• EDI 849 Response to Product Transfer Account Adjustment
• EDI 850 Purchase Order
• EDI 852 Product Activity Data
• EDI 853 Routing and Carrier Instruction
• 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 861 Receiving Advice/Acceptance Certificate
• EDI 862 Shipping Schedule
• EDI 864 Text Message
• EDI 865 Purchase Order Change Acknowledgment/Request – Seller Initiated
• EDI 866 Production Sequence
• EDI 867 Product Transfer and Resale Report
• EDI 869 Order Status Inquiry
• EDI 870 Order Status Report
• EDI 875 Grocery Products Purchase Order
• EDI 879 Price Information
• EDI 880 Grocery Products Invoice
• EDI 888 Item Maintenance
• EDI 889 Promotion Announcement
• EDI 894 Delivery/Return Base Record
• EDI 930 Automotive Inspection Detail
• EDI 940 Warehouse Shipping Order
• EDI 943 Warehouse Stock Transfer Shipment Advice
• EDI 944 Warehouse Stock Transfer Receipt Advice
• EDI 945 Warehouse Shipping Advice
• EDI 947 Warehouse Inventory Adjustment Advice
• EDI 990 Response to a Load Tender
• EDI 997 Functional Acknowledgment
• APERAK Application error and acknowledgement message
• DELFOR Delivery schedule message
• DELJIT Delivery just in time message
• DESADV Despatch advice message
• INVOIC Invoice message
• INVRPT Inventory report message
• ORDERS Purchase order message
• RECADV Receiving advice message

ANSI ASC X12

In 1979, the American National Standards Institute (ANSI) chartered the Accredited Standards Committee (ASC) X12 to develop uniform standards for inter-industry electronic exchange of business transactions, namely electronic data interchange. ANSI X12 was originally conceived 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. ASC X12 also contributes to UN/EDIFACT messages that are used widely outside of the United States.

EANCOM

This standard was originally conceived in 1987 by the EAN General Assembly and was to be developed on the then emerging international UN/EDIFACT standard. The EANCOM messages, maintained by GS1, are more detailed in nature compared to the TRADACOMS message set. 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.

VICS

The Voluntary Inter-industry Commerce Standard is used by the general merchandise retail industry across North America. It is a subset of the ANSI ASC X12 national standard. VICS EDI is being utilized by thousands of companies, department and specialty retail stores, mass merchandisers and their respective suppliers. In 1988 GS1 US became the management and administrative body for VICS EDI. GS1 US also manages the ASC X12 derived Uniform Communication Standard (UCS) for the grocery industry and Industrial/Commercial Standard (I/C) for the industrial sector.

UN/EDIFACT

United Nations/Electronic Data Interchange for Administration, Commerce and Transport is the international standard that was developed by the United Nations. 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. 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 due to the fact that 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 particular region today.

ODETTE

The Organization for Data Exchange by Tele Transmission in Europe is a group that represents the interests of the automotive industry in Europe. They are the equivalent of the Automotive Industry Action Group (AIAG) in North America. The organization develops tools and recommendations that improve the flow of goods, services product data and business information across the whole automotive value chain. ODETTE has been responsible for developing communications standards such as OFTP and OFTP2.0, constant improvement processes such as Materials Management Operations Guideline / Logistics Evaluation (MMOG/LE) and automotive-specific document standards as defined via the link below.

Tradacoms

This is an early standard for EDI and was primarily used in the UK retail sector. It was originally introduced in 1982 as an implementation of the UN/GTDI syntax, one of the precursors of EDIFACT, and was maintained and extended by the UK Article Numbering Association, now called GS1 UK. The standard is more or less obsolescent since the development of it effectively ceased in 1995 in favor of the EDIFACT EANCOM subsets. Despite this it has proved durable and the majority of the retail EDI traffic in the UK still uses it today.

VDA

This organization develops standards and best practices to serve the needs of companies within 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.

HIPAA

The Health Insurance Portability and Accountability Act was enacted by the U.S congress in 1996. 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.

RosettaNet

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 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. Further information about RosettaNet PIP documents can be found from the link below.

SWIFT

The Society of Worldwide Interbank Financial Telecommunication was formed in 1973 and is headquartered in Brussels. SWIFT operates a worldwide financial messaging network which 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. The majority of interbank messages use the SWIFT network. As of November 2008, SWIFT linked 8740 financial institutions across 209 countries. The SWIFT document standard is split into four areas, Payments, Trade Services, Securities and Trading.