EDI Transactions


EDI transactions are standardized electronic business documents used by trading partners to send and receive business information, such as when one company wants to electronically send a purchase order to another organization.

EDI transactions were designed to be standardized and are independent of the communications used by companies or the software technology that sends and receives the EDI data.

Use this guide to understand why EDI software is critical to the supply chain and learn every EDI transaction code by industry.

You need to know about EDI transactions:

  • Electronic Data Interchange Definition
  • What are EDI Transactions?
  • What is an EDI Standard?
  • EDI Communication Standards
  • TCommon EDI Communication Options
  • EDI Transaction Codes by Industry
  • 5 EDI Terms You Should Know


Electronic Data Interchange (EDI) is the computer-to-computer exchange of business documents between trading partners. EDI allows one company to send and receive information from another company electronically and in a standardized format, thereby enabling paperless communication. The EDI process replaces postal mail, fax, and email to connect directly to business systems.


EDI 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 a given EDI document.

All electronic data interchange transactions are made up of the following parts:

Element -The data elements within an EDI document are individual lines of information. For example, a document like a purchase order or an invoice, will contain data elements such as city, state, item number, or cost. Elements are the smallest component in an EDI standard.

Segments - Segments are composed of a group of elements. In an EDI document, each section of the document is described by a particular segment. Examples of segments include the beginning of a purchase order, the company, street addresses, etc.

Transaction Sets - Also referred to as an EDI message or EDI transactions. Once segments are collected in a predetermined format, they form the completed EDI document or transaction sets.

Electronic data interchange works depending on which EDI standards are required to format a message. Ultimately, since EDI documents are managed and interpreted by computers, transferred data must be formatted in a way that computers of both parties can understand. The main purpose of EDI standard formats is to minimize communication complications and costs of redundancies or fines, often called chargebacks.


Essentially, an EDI transaction is just another term for a standardized business document. Companies and trading partners exchange these documents using EDI standards to automate and streamline purchase orders, invoices, acknowledgments, payments, tracking, and other reports.

Any EDI transaction document must contain a certain minimum amount of vital data. Without these requirements, an EDI document becomes useless. Adhering to strict EDI feed formatting rules helps define precisely how and where each part of data on the document will be found and used. Each document is assigned one of the dozens of transaction numbers from the EDI public format.

For example, a purchase order (PO) is given the EDI transaction number 850 and the invoice transaction number is 810. So, when an EDI translator receives an EDI 850 PO document, it instantly recognizes the order number, the company name of the buyer, items in the order, and the price per item.

It’s these streamlined EDI transactions that improve the overall data transfer process through the efficient integration and seamless automation of B2B integration platform workflows between internal and external systems, applications, and cloud ecosystems.

Some of the biggest corporations in the world – industry-dominating giants – like Walmart mandate the use of some form of EDI format, meaning most companies must be EDI capable. Anything you purchase, any insurance document you file, any government form you report, any text message you send – it all requires EDI in some way, shape, or form.

Because there are hundreds of EDI transaction types, organizations follow designated EDI standards to ensure uniform formats for the inter-industry electronic exchange of business documents between trading partners.


Turn to Bay X Networks multichannel EDI and eCommerce solutions for affordable, reliable, easy to use, scalable cloud-based solutions. Bay X Networks cloud-based EDI and eCommerce portal, WebEDI, allows you to easily connect to trading partners, maintain 100% EDI compliance, integrate with your business systems and applications from shipping services, eCommerce solutions, accounting programs, to ERPs, 3PLs and more, achieve workflow automation and expand your business portfolio.

Common EDI Communication Standards


ANSI (American National Standards) ASC (Accredited Standards Committee) X12 goes by more than one pseudonym. This standard is also sometimes called ANSI X12 Standard or just simply X12. But regardless of the terminology, ANSI ASC X12 includes EDI standards used to communicate digital B2B transactions for various global business processes. EDI X12 standards allow consistency among business documents and other kinds of enterprise functionality.

There are more than 300 different types of X12 EDI standards, all delegated by a different three-digit number, for numerous industries such as finance, government, health care, insurance, transportation, and others. ANSI ASC X12 also develops standards for CICA (Context Inspired Component Architecture) and XML schemas.


TRADACOMS (TRAding DAA COMmunicationS) is the primary EDI standard for domestic trading in the United Kingdom, specifically the UK retail industry. While somewhat similar to the EDIFACT standard, 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.


UN/EDIFACT, which is short for United Nations rules for Electronic Data Interchange for Administration, Commerce, and Transport, is a set of internationally standardized communication guidelines for exchanged data tags and message types between computer systems in different networks. UN/EDIFACT standards structure data into segments, segments into messages, and messages into an interactive exchange protocol.

The syntax rules for EDIFACT describe the message (nesting, character sets, structures, etc.) The data tags detail the different types of data being exchanged and how each is represented. The message types are also known as UNSMs (United Nations Standard Messages).


ODETTE stands for Organization of Data Exchange by Tele Transmission in Europe and creates data exchange and communications standards for the European automotive industry. It is similar to North America’s AIAG (Automotive Industry Action Group). ODETTE develops protocols such as OFTP and the more advanced OFTP2, which provides enhanced security through encryption methods and digital certificates for EDI data exchange.

Deploying B2B and MFT (managed file transfer) solutions that are ODETTE-certified for OFTP and OFTP2 allows a company to securely and efficiently communicate with various software to successfully exchange data.

The Importance of EDI Standards

One of the most common complaints those in the technology world have had about EDI is due to its rigid standardization. However, this very same standardization has helped EDI stick around for as long as it has and become a way of life for enterprises. Without standardization, it becomes difficult to maintain and scale B2B data exchanges.

A lack of true EDI standards that dictate a universal format is one reason that APIs have not replaced EDI when it comes to B2B-type data exchanges. APIs can be customized to do just about anything, which means developers a pretty wide range of what he or she can do to meet the requirements of the business. Such wide-ranging business rules tend to not scale well in most organizations.

EDI Communications Options

Every organization that needs to connect with trading partners must first ask themselves, “What is the best way to send and receive information and documents?” And while there are multiple avenues for a company to take business communication, data interchange ultimately comes down to AS2 vs. VAN.


With AS2 (applicability statement 2), data such as EDI, XML, and others are sent and received via the internet using an HTTP protocol (TCP/IP) through a certified server. AS2 offers a securely encrypted process without costly annual or transaction fees for unlimited data. In today's digital ecosystem, AS2 is considered the best way to integrate with trading partners and has been widely implemented across many industries.

AS2 can handle any type of file format and requires message disposition/delivery notifications (MNDs) to alert a trading partner when a document or data has been delivered or received. AS2 also can be deployed using in-house IT resources or outsourced through a cloud-based vendor.

With AS2, what it all comes down to is enabling a better way to send data securely and directly from one source to another.


An EDI VAN (value-added network) should efficiently deliver EDI transactions through a single connection. A hosted VAN service enables the communication between a traditional VAN and a private network or internet-connected trading partner. Simply put, a VAN is a communication channel that moves and manages data from point A to point B – kind like a post office. In a VAN, trading partners each possess a mailbox as data is delivered between each mailbox.

This streamlined method is meant to lower the document-by-document processing costs by way of a centralized system with real-time tracking, communication management, multiple connectivity options, local data integration, and rapid message delivery. However, relying on a VAN has become an outdated way of doing business, especially with more modernized and cost-effective technology options available that offer end-to-end connectivity and solutions to complex integration.

EDI Transaction Codes by Industry

Transportation and Logistics

  • 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 109: Vessel Content Details
  • EDI 110: Air Freight Details and Invoice
  • EDI 120: Vehicle Shipping Order
  • EDI 121: Vehicle Service
  • EDI 125: Multilevel Railcar Load Details
  • EDI 126: Vehicle Application Advice
  • EDI 127: Vehicle Baying Order
  • EDI 128: Dealer Information
  • EDI 129: Vehicle Carrier Rate Update
  • EDI 160: Transportation Automatic Equipment Identification
  • EDI 161: Train Sheet
  • EDI 163: Transportation Appointment Schedule Information
  • 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 Ship. 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 219: Logistics Service Request
  • EDI 220: Logistics Service Response
  • EDI 222: Cartage Work Assignment
  • EDI 223: Consolidators Freight Bill and Invoice
  • EDI 224: Motor Carrier Summary Freight Bill Manifest
  • EDI 225: Response to a Cartage Work Assignment
  • EDI 227: Trailer Usage Report
  • EDI 228: Equipment Inspection Report
  • EDI 240: Motor Carrier Package Status
  • EDI 250: Purchase Order Shipment Management Document
  • EDI 300: Reservation (Booking Request) (Ocean)
  • EDI 301: Confirmation (Ocean)
  • EDI 303: Booking Cancellation (Ocean)
  • EDI 304: Shipping Instructions
  • EDI 309: Customs Manifest
  • EDI 310: Freight Receipt and Invoice (Ocean)
  • EDI 311: Canada Customs Information
  • EDI 312: Arrival Notice (Ocean)
  • EDI 313: Shipment Status Inquiry (Ocean)
  • EDI 315: Status Details (Ocean)
  • EDI 317: Delivery/Pickup Order
  • EDI 319: Terminal Information
  • EDI 322: Terminal Operations and Intermodal Ramp Activity
  • EDI 323: Vessel Schedule and Itinerary (Ocean)
  • EDI 324: Vessel Stow Plan (Ocean)
  • EDI 325: Consolidation of Goods in Container
  • EDI 326: Consignment Summary List
  • EDI 350: Customs Status Information
  • EDI 352: U.S. Customs Carrier General Order Status
  • EDI 353: Customs Events Advisory Details
  • EDI 354: U.S. Customs Auto. Manifest Archive Status
  • EDI 355: U.S. Customs Acceptance/Rejection
  • EDI 356: U.S. Customs Permit to Transfer Request
  • EDI 357: U.S. Customs In-Bond Information
  • EDI 358: Customs Consist Information
  • EDI 359: Customs Customer Profile Management
  • EDI 361: Carrier Interchange Agreement (Ocean)
  • EDI 404: Rail Carrier Shipment Information
  • EDI 410: Rail Carrier Freight Details and Invoice
  • EDI 412: Trailer or Container Repair Billing
  • EDI 414: Rail Carhire Settlements
  • EDI 417: Rail Carrier Waybill Interchange
  • EDI 418: Rail Advance Interchange Consist
  • EDI 419: Advance Car Disposition
  • EDI 420: Car Handling Information
  • EDI 421: Estimated Time of Arrival & Car Scheduling
  • EDI 422: Equipment Order
  • EDI 423: Rail Industrial Switch List
  • EDI 424: Rail Carrier Services Settlement
  • EDI 425: Rail Waybill Request
  • EDI 426: Rail Revenue Waybill
  • EDI 429: Railroad Retirement Activity
  • EDI 431: Railroad Station Master File
  • EDI 432: Rail Deprescription
  • EDI 433: Railroad Reciprocal Switch File
  • EDI 434: Railroad Mark Register Update Activity
  • EDI 435: Standard Transportation Commodity Code Master
  • EDI 436: Locomotive Information
  • EDI 437: Railroad Junctions & Interchanges Activity
  • EDI 440: Shipment Weights
  • EDI 451: Railroad Event Report
  • EDI 452: Railroad Problem Log Inquiry or Advice
  • EDI 453: Railroad Service Commitment Advice
  • EDI 455: Railroad Parameter Trace Registration
  • EDI 456: Railroad Equipment Inquiry or Advice
  • EDI 460: Railroad Price Distribution Request or Response
  • EDI 463: Rail Rate Reply
  • EDI 466: Rate Request
  • EDI 468: Rate Docket Journal Log
  • EDI 470: Railroad Clearance
  • EDI 475: Rail Route File Maintenance
  • EDI 485: Ratemaking Action

Manufacturing and Retail

  • EDI 101: Name and Address Lists
  • EDI 140: Product Registration
  • EDI 141: Product Service Claim Response
  • EDI 142: Product Service Claim
  • EDI 143: Product Service Notification
  • EDI 159: Motion Picture Booking Confirmation
  • EDI 170: Revenue Receipts Statement
  • EDI 180: Return Merchandise Authorization & Notification
  • EDI 244: Product Source Information
  • EDI 290: Cooperative Advertising Agreements
  • EDI 503: Pricing History
  • EDI 504: Clauses and Provisions
  • EDI 620: Excavation Communication
  • EDI 625: Well Information
  • EDI 753: Request For Routing Instructions
  • EDI 754: Routing Instructions
  • EDI 816: Organizational Relationships
  • EDI 818: Commission Sales Report
  • EDI 830: Planning Schedule w/ Release Capability
  • EDI 832: Price/Sales Catalog
  • EDI 840: Request for Quotation
  • EDI 841: Specifications/Technical Information
  • EDI 842: Nonconformance Report
  • EDI 843: Response to Request for Quotation
  • EDI 845: Price Authorization Acknowledgment/Status
  • EDI 846: Inventory Inquiry/Advice
  • EDI 847: Material Claim
  • EDI 848: Material Safety Data Sheet
  • EDI 850: Purchase Order
  • EDI 851: Asset Schedule
  • 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 863: Report of Test Results
  • 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 873: Commodity Movement Services
  • EDI 874: Commodity Movement Services Response
  • EDI 875: Grocery Products Purchase Order
  • EDI 876: Grocery Products Purchase Order Change
  • EDI 877: Manufacturer Coupon Family Code Structure
  • EDI 878: Product Authorization/De-authorization
  • EDI 879: Price Information
  • EDI 881: Manufacturer Coupon Redemption Detail
  • EDI 882: Direct Store Delivery Summary Information
  • EDI 883: Market Development Fund Allocation
  • EDI 884: Market Development Fund Settlement
  • EDI 885: Retail Account Characteristics
  • EDI 886: Customer Call Reporting
  • EDI 887: Coupon Notification
  • EDI 888: Item Maintenance
  • EDI 889: Promotion Announcement
  • EDI 890: Contract & Rebate Management
  • EDI 891: Deduction Research Report
  • EDI 893: Item Information Request
  • EDI 894: Delivery/Return Base Record
  • EDI 895: Delivery/Return Acknowledgment or Adjustment
  • EDI 896: Product Dimension Maintenance
  • 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 130: Student Educational Record (Transcript)
  • EDI 131: Student Educational Record (Transcript) Acknowledgment
  • EDI 132: Human Resource Information
  • EDI 133: Educational Institution Record
  • EDI 135: Student Aid Origination Record
  • EDI 138: Education Testing and Prospect Request and Report
  • EDI 139: Student Loan Guarantee Result
  • EDI 144: Student Loan Transfer and Status Verification
  • EDI 146: Request for Student Educational Record (Transcript)
  • EDI 147: Response to Request for Student Educational Record (Transcript)
  • EDI 155: Business Credit Report
  • EDI 188: Educational Course Inventory
  • EDI 189: Application for Admission to Educational Institutions
  • EDI 190: Student Enrollment Verification
  • EDI 264: Mortgage Loan Default Status
  • EDI 265: Real Estate Title Insurance Services Order
  • EDI 266: Mortgage or Property Record Change Notification
  • EDI 191: Student Loan Pre-Claims and Claims
  • EDI 197: Real Estate Title Evidence
  • EDI 198: Loan Verification Information
  • EDI 199: Real Estate Settlement Information
  • EDI 200: Mortgage Credit Report
  • EDI 201: Residential Loan Application
  • EDI 202: Secondary Mortgage Market Loan Delivery
  • EDI 203: Secondary Mortgage Market Investor Report
  • EDI 205: Mortgage Note
  • EDI 206: Real Estate Inspection
  • EDI 245: Real Estate Tax Service Response
  • EDI 248: Account Assignment/Inquiry & Service/Status
  • EDI 259: Residential Mortgage Insurance Explanation of Benefits
  • EDI 260: Application for Mortgage Insurance Benefits
  • EDI 261: Real Estate Information Request
  • EDI 262: Real Estate Information Report
  • EDI 263: Residential Mortgage Insurance Application Response
  • EDI 810: Invoice
  • EDI 811: Consolidated Service Invoice/Statement
  • EDI 812: Credit/Debit Adjustment
  • EDI 814: General Request, Response, or Confirmation
  • EDI 819: Joint Interest Billing and Operating Expense Statement
  • EDI 820: Payment Order/Remittance Advice
  • EDI 821: Financial Information Reporting
  • EDI 822: Account Analysis
  • EDI 823: Lockbox
  • EDI 824: Application Advice
  • EDI 827: Financial Return Notice
  • EDI 828: Debit Authorization
  • EDI 829: Payment Cancellation Request
  • EDI 831: Application Control Totals
  • EDI 833: Mortgage Credit Report Order
  • EDI 844: Product Transfer Account Adjustment
  • EDI 849: Response to Product Transfer Account Adjustment
  • EDI 872: Residential Mortgage Insurance Application
  • EDI 880: Grocery Products Invoice

Communications and Controls

  • EDI 102: Associated Data
  • EDI 242: Data Status Tracking
  • EDI 815: Cryptographic Service Message
  • EDI 864: Text Message
  • EDI 868: Electronic Form Structure
  • EDI 993: Secured Receipt or Acknowledgment
  • EDI 997: Functional Acknowledgment
  • EDI 999: Implementation Acknowledgment

EDI Transactions You Should Know

Acknowledgment – A response to a command that is sent to the originator to confirm the message was received. There are different types of EDI acknowledgments, ranging from basic-communication level statuses to functional acknowledgment. A functional acknowledgment is a message sent from the receiver of a transmission to the sender to indicate that the message was accepted.

Advanced Shipping Notice – A common EDI transaction, an ASN is a notification of a pending delivery, its primary purpose is to provide tracking and packing information ahead of delivery. Some of the most common elements included in an ASN are purchase order number, ship notice number, and the location where the product will be shipped.

Invoice – An electronic version of a document that a vendor sends to a buyer indicating how much is owed for goods and/or services. Usually, it is sent in response to a purchase order, which is a request for payment once the goods or services have shipped. They typically contain shipping details, payment terms, information on the goods, and/or services.

RESTful Web Services – Representational State Transfer specifies constraints that when applied to a Web service improve performance. As APIs become more common, REST architectures are useful because they allow data to be transmitted over a standardized interface, such as HTTP. They are stateless, and often are compared to Simple Object Access Protocol (SOAP), but are viewed as a simpler alternative.

Translation – Common in EDI, translation is the process by which information is converted into different formats. The receiving computer has a translator that knows where to find the buyer’s company name, order number, purchase items, and price, among other things. After that, the information is delivered to the receivers’ order entry to eliminate any manual order entry and expedite the transaction.


We help you see the world differently, discover opportunities you may never have imagined.

In a time when the internet has every answer, trust and reliability are what one cannot gain easily. Bay X Networks is one of the best EDI service providers to big and small business firms, making it easy for them to exchange their important information securely.
Some of the reasons why Bay X Networks is different and better than the others:
  • Providing EDI and eCommerce solutions for more than two decades
  • You can get EDI solutions for almost every trading partner.
  • Get services for every sector across the globe.
Right now, Bay X Networks is working with some of the leading business firms like Amazon, Walmart, Kroger, and a lot more. In the future, we would like to continue craving our place in customers’ hearts to gain respect.
Bay X Networks is providing its esteemed customers and end-users with customization options as well. Businessmen from different industries can ask for EDI and eCommerce solutions as per their needs and requirements. And, our team will cater to their needs.