EDI 104 (Air Shipment Information) is an X12 transaction set used by the sender to transmit a detailed bill containing lading and rating information related to an air carrier’s shipment, such as sender information, shipment detail for one or more items, consignee, and third party information, shipment and other charges, and grand total.

EDI 204 (Motor Carrier Load Tender) is an X12 transaction set that shippers or other parties use to tender a shipment to full-load motor carriers. It includes shipping instructions, schedule details, equipment requirements, and commodities apposite a load tender. It is not used for less-than-truckload bills, pickup notifications, or manifest data.

EDI 210 (Motor Carrier Freight Details and Invoice) is an X12 transaction used for providing details for charges for services offered by a motor carrier. It can be used to send motor carrier invoices or details for motor freight shipment charges.

EDI 214 (Transportation Carrier Shipment Status Message) is an X12 transaction set that transportation carriers use to send shipment statuses, including time, date, location, route, identification numbers, and conveyance, to the shippers, consignees, and other parties.

EDI 810 (Invoice) is an X12 transaction set to send billing information for rendered goods and services as per customary and established business and industry practice.

EDI 810 (Invoice) is an X12 transaction set to send billing information for rendered goods and services as per customary and established business and industry practice.

EDI 820 (Payment Order/ Remittance Advice) is an X12 transaction set to make a payment, send remittance advice, or both. EDI 820 can be used as an order or remittance advice sent to the payer to pay the payee directly from a financial institution or a third-party agent.

EDI 850 (Purchase Order) is an X12 transaction set to place a purchase order for goods or services with a vendor as per customary and established business and industry practice.

EDI 860 (Purchase Order Change Request) is an X12 transaction set to send the information regarding the changes in a purchase order as per customary and established business and industry practice. It can be used by a buyer to request a change in the previous purchase order (EDI 850) or to confirm the changes in the purchase order requested by a seller.

EDI 990 (Response to a Load Tender) is an X12 transaction set used for general information requested for a specific shipment. EDI 990 is used as a response to EDI 204, which is used as a load tender.

Updating

EDI 810 (Invoice) is an X12 transaction set to send billing information for rendered goods and services as per customary and established business and industry practice.

EDI 850 (Purchase Order) is an X12 transaction set to place a purchase order for goods or services with a vendor as per customary and established business and industry practice.

EDI 204 (Motor Carrier Load Tender) is an X12 transaction set that shippers or other parties use to tender a shipment to full-load motor carriers. It includes shipping instructions, schedule details, equipment requirements, and commodities apposite a load tender. It is not used for less-than-truckload bills, pickup notifications, or manifest data.

EDI 210 (Motor Carrier Freight Details and Invoice) is an X12 transaction used for providing details for charges for services offered by a motor carrier. It can be used to send motor carrier invoices or details for motor freight shipment charges.

EDI 214 (Transportation Carrier Shipment Status Message) is an X12 transaction set that transportation carriers use to send shipment statuses, including time, date, location, route, identification numbers, and conveyance, to the shippers, consignees, and other parties.

EDI 824 (Application Advice) is an X12 transaction set to report results after edits have been made in an application system's database. The edits made in transaction sets can be reported in the functional group, a part of the transaction set, or a different transaction set. The result can be coded or free-format. EDI 824 is only used when there is a need to report acceptance, rejection, partial acceptance, or changes in a transaction set. It is not used as a response to another transaction set.

EDI 990 (Response to a Load Tender) is an X12 transaction set used for general information requested for a specific shipment. EDI 990 is used as a response to EDI 204, which is used as a load tender.

EDI 850 (Purchase Order) is an X12 transaction set to place a purchase order for goods or services with a vendor as per customary and established business and industry practice.

EDI 824 (Application Advice) is an X12 transaction set to report results after edits have been made in an application system's database. The edits made in transaction sets can be reported in the functional group, a part of the transaction set, or a different transaction set. The result can be coded or free-format. EDI 824 is only used when there is a need to report acceptance, rejection, partial acceptance, or changes in a transaction set. It is not used as a response to another transaction set.

EDI 856 (Shipment/Manifest) is an X12 transaction set to send a list of contents of an order with additional information relating to the shipment. It includes information such as item name, description, characteristics, packaging type, carrier information, and equipment and configurations for the item for transportation. It helps the sender to describe the item and arrange a suitable shipment.

EDI 810 (Invoice) is an X12 transaction set to send billing information for rendered goods and services as per customary and established business and industry practice.

EDI 820 (Payment Order/ Remittance Advice) is an X12 transaction set to make a payment, send remittance advice, or both. EDI 820 can be used as an order or remittance advice sent to the payer to pay the payee directly from a financial institution or a third-party agent.

EDI 824 (Application Advice) is an X12 transaction set to report results after edits have been made in an application system's database. The edits made in transaction sets can be reported in the functional group, a part of the transaction set, or a different transaction set. The result can be coded or free-format. EDI 824 is only used when there is a need to report acceptance, rejection, partial acceptance, or changes in a transaction set. It is not used as a response to another transaction set.

EDI 850 (Purchase Order) is an X12 transaction set to place a purchase order for goods or services with a vendor as per customary and established business and industry practice.

EDI 860 (Purchase Order Change Request) is an X12 transaction set to send the information regarding the changes in a purchase order as per customary and established business and industry practice. It can be used by a buyer to request a change in the previous purchase order (EDI 850) or to confirm the changes in the purchase order requested by a seller.