Home > Knowledge Base > What are the Most Common EDI Transaction Codes by Industry?

What are the Most Common EDI Transaction Codes by Industry?

Automotive

ANSI X12 Standards

EDI 810 – Invoice
This is an electronic version of a paper invoice. It typically contains invoice details – invoice number and date, product details – item number and quantity. It also contains the shipping details, payment details like rate and discounts and payer details (customer code). An EDI 810 is usually sent out in response to the Purchase Order (EDI 850) or after the order is fulfilled and an Advance Shipping Notice (EDI 856) is sent out.

EDI 820 – Payment Order/Remittance Advice
This is an electronic version of the Cash Receipt that is typically issued by a buyer after the receipt of an 810 document (Invoice). Basically, an EDI 820 is equivalent to sending your supplier a notice of intent to pay an invoice.

EDI 824 – Application Advice
This is an electronic version of Application Advice that checks the integrity of the data. It states the status of a previous transaction as to whether it was accepted, rejected or accepted with changes. Thereby, the sender of the transaction can be wary of any errors in their next transmission.

EDI 830 – Planning Schedule with Release Capability
The EDI 830 Planning Schedule with Release is sent by a buyer to communicate anticipated demand for products for a set amount of time

EDI 850 – Purchase Order
This is an electronic version of Purchase Order that is used for requesting goods. It contains information such as the details of shipping, product names, prices corresponding to each item and the number of quantities required along with the terms of payment.

EDI 855 – Purchase Order Acknowledgement
This is an electronic version of Purchase Order Acknowledgement that eliminates the need of a confirmation call or fax by the seller to confirm the receipt of an 850 from a buyer. In addition to this, the EDI file also contains additional information on whether the purchase order was accepted or rejected.

EDI 860 – Purchase Order Change- Buyer Initiated
This is an electronic version of Purchase Order Change that is used for making changes in the Purchase Order before the supplier ships the items. The changes may include changes in items, quantity, price, and delivery date.

EDI 861 – Receiving Advice
This transaction is used to report the receipt of shipments or as a formal acceptance of returned defective items. 

EDI 865 – Purchase Order Change Acknowledgement
This transaction is used to acknowledge changes to customer’s orders after an EDI 855 transaction set has been sent

EDI 862 – Shipping Schedule
This document is used to transmit a detailed shipping schedule requirements to a supplier, and can supplement the 830 Planning Schedule document.

EDI 866 – Production Sequence
This document provides the receiver of goods with the ability to request the order in which shipments or goods arrive at one or more locations and/or specify the order in which they are to be unloaded.

EDI 856 – Advance Shipping Notice
This is an electronic version of Advance Shipping Notice that specifies the contents of the shipment that is about to reach the trading partner’s facility. ASN notifies the trading partner about the barcode information, tracking details, date of delivery, and time of shipment.

EDI 997 – Functional Acknowledgement
This is electronic version of Functional Acknowledgement that is sent as a response to every EDI transaction document that has been received. Its purpose is to indicate whether the transacted document has been received and translated successfully. It does not, however, state whether the information received in the transacted documents is accurate or sufficient

EDIFACT Standards

DESADV- Dispatch Advice
This message is transmitted to the customer to advise them that the products are dispatched from the supplier as they leave the supplier dock. This message is similar to the Advance Ship Notice (EDI 856) in ANSI X12 standard. It contains packaging information including pallet details, number of container packages and serial numbers associated with the containers and pallets.

Grocery/Retail

EDI 810 – Invoice
This is an electronic version of a paper invoice. It typically contains invoice details – invoice number and date, product details – item number and quantity. It also contains the shipping details, payment details like rate and discounts and payer details (customer code). An EDI 810 is usually sent out in response to the Purchase Order (EDI 850) or after the order is fulfilled and an Advance Shipping Notice (EDI 856) is sent out.

EDI 816 – Organizational Relationships
This is an electronic version of the Organizational Relationships document that is used to provide the location information of a company, its related entities, and their corresponding code reference. It also depicts the organizational relationship between the different entities e.g. by service or operation, distribution centers, product return center or service centers, or member and parent relationship.

EDI 820 – Remittance Advice
This is an electronic version of the remittance advice that notifies the seller that payment from the buyer for good or services rendered has been issued through an ACH or a check

EDI 824 – Application Advice
This is an electronic version of Application Advice that checks the integrity of the data. It states the status of a previous transaction as to whether it was accepted, rejected or accepted with changes. Thereby, the sender of the transaction can be wary of any errors in their next transmission.

EDI 846 – Inventory Inquiry/Advice
This is an electronic version of Inventory Inquiry/Advice. It is most commonly used by retailers to inquire about a supplier’s inventory levels and for suppliers to advise on the number of units they have on hand.an electronic version of Application Advice, checks the integrity of the data.

EDI 850 – Purchase Order
This is an electronic version of Purchase Order that is used for requesting goods. It contains information such as the details of shipping, product names, prices corresponding to each item and the number of quantities required along with the terms of payment.

EDI 855 – Purchase Order Acknowledgement
This is an electronic version of Purchase Order Acknowledgement that eliminates the need of a confirmation call or fax by the seller to confirm the receipt of an 850 from a buyer. In addition to this, the EDI file also contains additional information on whether the purchase order was accepted or rejected.

EDI 856 – Advance Shipping Notice
This is an electronic version of Advance Shipping Notice that specifies the contents of the shipment that is about to reach the trading partner’s facility. ASN notifies the trading partner about the barcode information, tracking details, date of delivery, and time of shipment.

EDI 860 – Purchase Order Change
This is an electronic version of Purchase Order Change that is used for making changes in the Purchase Order before the supplier ships the items. The changes may include changes in items, quantity, price, and delivery date.

EDI 864 – Text Message
This is an electronic version of a Text Message. The EDI 864 facilitates the exchange of one time messages such as notifications, contract information, etc. They are intended to be human-readable messages rather than being processed by computers.

EDI 875 – Grocery Products Purchase Order
This is an electronic version of a grocery purchase order similar to EDI 850. This is sent by is sent by grocers, wholesalers, retailers or trading partners to grocery suppliers requesting finished goods.

EDI 876 – Grocery Products Purchase Order Change
This is an electronic version of Purchase Order Change sent by suppliers notifying their buyer of any changes to the initial order received known as an EDI 875 Grocery Products Purchase Order.

EDI 880 – Grocery Products Invoice
This is an electronic version of grocery products invoice that is sent by grocery suppliers requesting payment for rendered goods from grocers, wholesalers and trading partners.

EDI 940 – Warehouse Shipping Order,
This is an electronic version of Warehouse Shipping Order, is used to instruct a remote warehouse to ship the necessary goods to the buyer which is usually the retailer. It contains information such as the number of goods, shipment information and manufacturer details. It also specifies the date of shipment, the time taken for delivery and item specifications. The 940 also finds use in canceling and modifying an order.

EDI 945 – Warehouse Shipping Advice
This is an electronic version of Warehouse Shipping Advice that is sent out by third-party warehouses to the supplier. It states that the items requested by the buyer have been shipped to them. It contains the date of shipment, the time taken to deliver the items, quantity, and specification of the items shipped. The EDI 945 is sent in response to an EDI 940.

EDI 997 – Functional Acknowledgement
This is electronic version of Functional Acknowledgement that is sent as a response to every EDI transaction document that has been received. Its purpose is to indicate whether the transacted document has been received and translated successfully. It does not, however, state whether the information received in the transacted documents is accurate or sufficient.

EDI 944 – Warehouse Stock Transfer Receipt Advice
This is an electronic version of Warehouse Stock Transfer Receipt Advice that is used to inform the supplier that their shipment has been received and verified. This EDI document contains information such as supplier details, Warehouse location, time and date of receiving the shipment etc.

Healthcare

EDI 270 – Healthcare eligibility/benefit inquiry
This transaction set is used by healthcare institutions to transmit inquiries for healthcare benefits and subscriber eligibility to financial institutions and government agencies. 

EDI 271 – Healthcare eligibility/benefit response.
This transaction set is used to respond to request inquiries about the healthcare benefits and eligibility associated with a subscriber or dependent.

EDI 276 – Healthcare claim status request
This transaction is used by healthcare providers to request or verify the status of healthcare previously submitted to a payer, such as an insurance company.

EDI 277 – Healthcare claim status notification
This transactions is used by healthcare payers and insurance companies to report on the status of claims (EDI 837 transactions) previously submitted by providers. 

EDI 278 – Healthcare service review Information
This transaction is used by hospitals to request an authorization from a payer, such as an insurance company.

EDI 820 – Payroll deducted and other group premium payment for insurance products
This transaction serves to make premium payments for insurance products and is used by healthcare institutions to send information to financial organizations.

EDI 834 – Benefits enrollment and maintenance set
This transaction is used by employers, unions, government agencies, insurance agencies, associations, or healthcare organizations paying claims. Its aim is to enroll members in a healthcare benefit plan. 

EDI 835 – Healthcare claim payment/advice transaction set
This transaction is used by insurers to make payments and send Explanation of Benefits (EOB) remittance advice to healthcare providers.

EDI 837 – Healthcare claim transaction set.
This transaction is used by healthcare providers and patients to submit healthcare claim information and encounter information.

Transportation/Logistics

All data is communicated between the carrier, shipper, and the consignee in electronic EDI documents known as ANSI X12 “Transaction Sets”. The most commonly used EDI Transaction Sets in the Transportation Industry are:

EDI 997 – Functional Acknowledgement
This transaction set is sent in response to each transaction set received to indicate acceptance by shipper, carrier or payee. It is an acknowledgement by any party to another party of data received.