Cette page n’est pas disponible en Français.
Si vous souhaitez en savoir plus à propos de TIE Kinetix, vous pouvez visiter notre page Enterprise. Vous pouvez aussi découvrir nos Clients et nos Partenaires. Pour en apprendre encore plus sur nos solutions ou sur certaines problématiques, consultez la section Ressources
Vous ne trouvez toujours pas ce que vous cherchiez ? Envoyez-nous un message sur notre page Contact
EDI X12 Transaction Sets 805-897
December 9th, 2020
When trading partners complete all of their business transactions electronically, their internal systems need to understand each other for accurate processing. With mass amounts of data flowing in and out of most organizations daily, these exchanges are much easier when all that data is structured in the same, commonly understood format. This holds true for electronic transactions between both business-to-business (B2B) and business-to-government (B2G) organizations, and that’s why EDI standards have been introduced—to simplify business operations and processes.
There are a few major EDI standards used in various parts of the world, and the American National Standard’s Institute’s X12 is one of them. So basically, if you’re exchanging invoices and other business documents electronically in North America, ANSI’s X12 is on your radar.
For your convenience, here’s a list of all X12 EDI Transaction Sets from 805-897, with definitions sourced directly from the official X12 dictionary:
EDI X12 805 – Contract Pricing Proposal
The EDI 805 Contract Pricing Proposal Transaction Set enables the transmission of cost and pricing data for a given contract action and provides pricing support detail data or references where that data can be found in the proposal.
EDI X12 806 – Project Schedule Reporting
The EDI 806 Project Schedule Reporting Transaction Set provides for the transmission of planning, scheduling, and status information. The purpose of this transaction set is to establish an initial plan, report progress against the plan, and report changes to the plan. It is designed to serve the needs of government agencies, prime contractors and their subcontractors.
EDI X12 810 – Invoice
The EDI 810 Invoice Transaction Set can be used to provide for customary and established business and industry practice relative to the billing for goods and services provided.
EDI X12 811 – Consolidated Service Invoice/Statement
The EDI 811 Consolidated Service Invoice/Statement Transaction Set provides for the billing or reporting of complex and structured service invoice/statement detail.
This standard can be used by organizations who are interested in sending or receiving either consolidated or standalone invoices for service arrangements which require processing other than that done for the typical product invoice.
The Consolidated Service Invoice/Statement can be used as a credit/debit memo to differentiate between payable invoice items and information-only memo items. This transaction set should not be used as a standalone notification of a credit/debit adjustment.
EDI X12 812 – Credit/Debit Adjustment
The EDI X12 Credit/Debit Adjustment Transaction Set can be used to notify a trading partner of an adjustment or billback and may be used to request an adjustment or billback. It identifies and contains the details and amounts covering exceptions, adjustments, credits, or debits for goods or services. This transaction set is multidirectional between trading partners.
EDI X12 813 – Electronic Filing of Tax Return Data
The EDI 813 Electronic Filing of Tax Return Data Transaction Set can be used by tax filers to electronically file tax returns with a federal, state, or local taxing authority and which may initiate payments related to the tax return.
EDI X12 814 – General Request, Response or Confirmation
The EDI 814 General Request, Response or Confirmation Transaction Set can be used to request actions to be performed, to respond to a request for actions to be performed or to confirm information related to actions performed.
EDI X12 815 – Cryptographic Service Message
The EDI 815 Cryptographic Service Message Transaction Set can be used to provide the data format required for cryptographic key management including the automated distribution and exchange of keys. The mechanism uses X12 structures and data formats and is based on existing standards such as X509 and ANSI X3 and X9 developed by the Accredited Standards Committees (ASCs) X9 and X12. The standard provides an X12 format for key distribution and exchange. The Cryptographic Service Message (CSM) transaction conveys the pertinent keying material for use in the EDI environment. The business requirements addressed in this standard for the key management data encompasses distribution and exchange of keying material in support of authentication, encryption and assurances.
EDI X12 816 – Organizational Relationships
The EDI 816 Organizational Relationships Transaction Set can be used to transmit pertinent information about a parent organization, its members and the relationship of a member to another member, and/or to the parent organization. A parent organization could be an association, a multi-hospital system, a chain of retail stores, a holding company, etc.
The EDI 816 transaction set can be used to convey the identity and relationship of members to a parent organization; identify eligibility to purchase under the terms and conditions negotiated by a parent organization on behalf of its members; and to update application databases.
EDI X12 818 – Commission Sales Report
The EDI 818 Commission Sales Report Transaction Set can be used to allow a retailer to advise a trading partner of commission sales and salary information. Commission data enables a trading partner to reconcile commission payments and salary support.
EDI X12 819 – Joint Interest Billing and Operating Expense Statement
The EDI 819 Joint Interest Billing and Operating Expense Statement Transaction Set can be used to transmit periodic expense details from the operator of an asset to the various owners of that asset (e.g., the operation of a petroleum lease or property having multiple owners).
EDI X12 820 – Payment Order/Remittance Advice
The EDI 820 Payment Order/Remittance Advice Transaction Set can be used to make a payment, send a remittance advice, or make a payment and send a remittance advice.
This transaction set can be an order to a financial institution to make a payment to a payee. It can also be a remittance advice identifying the detail needed to perform cash application to the payee's accounts receivable system. The remittance advice can go directly from payer to payee, through a financial institution, or through a third party agent.
EDI X12 822 – Account Analysis
The EDI 822 Account Analysis Transaction Set can be used to transmit detailed balance, service charge and adjustment detail primarily from a bank to its corporate clients. However, this transaction set can also be used between or within corporations.
EDI X12 823 – Lockbox
The EDI 823 Lockbox Transaction Set can be used to transmit lockbox (incoming payments) information and totals from a bank or any other lockbox service provider to a company.
EDI X12 824 – Application Advice
The EDI 824 Application Advice Transaction Set can be used to provide the ability to report the results of an application system's data content edits. The results of editing transaction sets can be reported at the functional group, an entire transaction set, or any portion of a transaction set, in either coded or free-form format. The EDI X12 824 transaction is designed to accommodate the business need of reporting the acceptance, rejection, acceptance with change, or partial acceptance or rejection of any transaction set. The EDI X12 824 Application Advice should not be used in place of a transaction set designed as a specific response to another transaction set (e.g., purchase order acknowledgment sent in response to a purchase order).
EDI X12 826 – Tax Information Exchange
The EDI 826 Tax Information Exchange Transaction Set is bi-directional and can be used to exchange tax information between various tax agencies and other authorized parties.
EDI X12 827 – Financial Return Notice
The EDI 827 Financial Return Notice Transaction Set can be used to report to the originator the inability to process, or modifications to, the original payment order.
EDI X12 828 – Debit Authorization
The EDI 828 Debit Authorization Transaction Set can be used to provide information from the paying entity to the financial institution regarding debits that the paying entity has authorized against its account. The financial institution would hold this information then match it against incoming debits to determine whether those debits have been authorized by the account holder.
This transaction set can be used to add new authorizations or cancel existing authorizations. With regard to electronic debits, this would be used for ACH debit processing only. This transaction set can also be used for paper-based debits (i.e., checks). In the paper-based world, this transaction set would serve the purpose of the "issuance file" or "check register" used in account reconciliation applications.
Either one-time or recurring debits can be authorized with this transaction set.
One transaction set can be used to identify multiple debit authorization details against one bank account.
EDI X12 829 – Payment Cancellation Request
The EDI 829 Payment Cancellation Request Transaction Set can be used to cancel a previously transmitted electronic payment between an originating company and its originating financial institution before funds are released.
EDI X12 830 – Planning Schedule with Release Capability
The EDI 830 Planning Schedule with Release Capability Transaction Set can be used to provide for customary and established business practice relative to the transfer of forecasting/material release information between organizations.
The planning schedule ANSI X12 830 transaction may be used in various ways or in a combination of ways, such as: (1) a simple forecast; (2) a forecast with the buyer's authorization for the seller to commit to resources, such as labor or material; (3) a forecast that is also used as an order release mechanism, containing such elements as resource authorizations, period-to-date cumulative quantities, and specific ship/delivery patterns for requirements that have been represented in "buckets," such as weekly, monthly, or quarterly. The order release forecast in the ANSI X12 830 may also contain all data related to purchase orders, as required, because the order release capability eliminates the need for discrete generation of purchase orders.
EDI X12 831 – Application Control Totals
The EDI 831 Application Control Totals Transaction Set can be used to transmit totals associated with a collection of like transactions.
The items reported in this transaction set must be of the same transaction set ID code.
EDI X12 832 – Price/Sales Catalog
The EDI 832 Price/Sales Catalog Transaction Set can be used to provide for customary and established business and industry practice relative to furnishing or requesting the price of goods or services in the form of a catalog.
EDI X12 833 – Mortgage Credit Report Order
The EDI 833 Mortgage Credit Report Order Transaction Set can be used by a mortgage originator to request, track, and cancel a series of value-added, investigative credit reports which are typically required in mortgage lending. It is a collection of borrower information that is needed to order a mortgage credit report.
EDI X12 834 – Benefit Enrollment and Maintenance
The EDI 834 Benefit Enrollment and Maintenance Transaction Set can be used to establish communication between the sponsor of the insurance product and the payer. Such transaction(s) may or may not take place through a third party administrator (TPA).
For the purpose of this standard, the sponsor in the EDI 834 transaction file format is the party or entity that ultimately pays for the coverage, benefit or product. Also in the 834 file format, a sponsor can be an employer, union, government agency, association, or insurance agency.
The payer in the EDI 834 transaction refers to an entity that pays claims, administers the insurance product or benefit, or both. A payer can be an insurance company, health maintenance organization (HMO), preferred provider organization (PPO), government agency (Medicare, Medicaid, Champus, etc.), or an entity that may be contracted by one of these former groups.
For the purpose of the EDI 834 transaction set, a third party administrator (TPA) can be contracted by a sponsor to handle data gathering from those covered by the sponsor if the sponsor does not elect to perform this function itself.
There are some common issues that you may run into when processing an EDI 824 transaction. For example, the data contained in an EDI 834 is often ordered in a way that doesn’t make sense. This leads to another example—manual intervention. Although inconvenient and time consuming, it is sometimes necessary to intervene due to the finicky EDI 834 file layout.
EDI X12 835 – Health Care Claim Payment/Advice
The EDI 835 Health Care Claim Payment/Advice Transaction Set can be used to make a payment, send an Explanation of Benefits (EOB) remittance advice, or make a payment and send an EOB remittance advice only from a health insurer to a health care provider either directly or via a financial institution.
Both 835 and 837 EDI transactions are specific to the healthcare industry, and they are often confused. When it comes to 835 vs. 837, however, it’s important to remember that while both EDI 835 and 837 files pertain to claims data, the EDI 835 claims data involves actual payment while the EDI 837 includes only payment information.
Note: There are many free services online that offer ANSI 835 readers, as well as readers for other ANSI X12 transaction sets. Be overly cautious when using these free services. Better yet, avoid these readers altogether. It’s also wise to be wary of EDI 837 sample file downloads as these downloads may contain viruses.
EDI X12 836 – Procurement Notices
The EDI 836 Procurement Notices Transaction Set can be used by the buyer to notify the seller or other interested parties of the award or pending award of a contract which may contain some indefinite features, such as delivery schedule, location, and/or quantities. This transaction set can also be used for purchasing actions such as the notification of intent to award or actual award of a small business set-aside purchase, notification of being outside of the competitive range, notice of receipt of protest, notice of receipt of a late bid, notice of bid rejection, notice of the disposition of an unsolicited proposal, public notice of the abstract of bids, and the notification of the award of a requirements type contract.
EDI X12 837 – Health Care Claim
The EDI 837 Health Care Claim Transaction Set can be used to submit health care claim billing information, encounter information, or both, from providers of health care services to payers, either directly or via intermediary billers and claims clearinghouses. The EDI 837 file can also be used to transmit health care claims and billing payment information between payers with different payment responsibilities where coordination of benefits is required or between payers and regulatory agencies to monitor the rendering, billing, and/or payment of health care services within a specific health care/insurance industry segment.
For purposes of the EDI 837 standard, providers of health care products or services may include entities such as physicians, hospitals and other medical facilities or suppliers, dentists, and pharmacies, and entities providing medical information to meet regulatory requirements. In the 837 file format, the payer refers to a third party entity that pays claims or administers the insurance product or benefit or both. For example, a payer may be an insurance company, health maintenance organization (HMO), preferred provider organization (PPO), government agency (Medicare, Medicaid, Civilian Health and Medical Program of the Uniformed Services (CHAMPUS), etc.) or an entity such as a third party administrator (TPA) or third party organization (TPO) that may be contracted by one of those groups. A regulatory agency is an entity responsible, by law or rule, for administering and monitoring a statutory benefits program or a specific health care/insurance industry segment.
This transaction set may be further specified. The ANSI X12 837 Q2 specification indicates that this transaction set is used as a Dental Health Care Claim transaction.
EDI X12 838 – Trading Partner Profile
The EDI 838 Trading Partner Profile Transaction Set can be used to request, change, verify or transmit business profile information to or from a trading partner. This information can be used by the receiver to facilitate the processing of the sender's business transactions.
The transaction set may be used to convey government survey information, business classification, general survey information, summary supplier ratings, changes in the EDI environment information, tax information, entity relationships, and general business profile information to update automated information data bases between trading partners.
EDI X12 839 – Project Cost Reporting
The EDI 839 Project Cost Reporting Transaction Set provides the transmission of cost and schedule information to support performance measurement (earned value), program management reporting, and contract funds status reporting. This transaction set will also support the Department of Defense (DoD), Department of Energy (DoE), NASA, and other government agency Cost/Schedule Control Systems Criteria (C/SCSC) and funds status reporting requirements. It is designed to serve the needs of government agencies, prime contractors, and their subcontractors.
EDI X12 840 – Request for Quotation
The EDI 840 Request for Quotation Transaction Set can be used to provide potential buyers with the ability to solicit price, delivery schedule, and other items from potential sellers of goods and services.
EDI X12 841 – Specifications/Technical Information
The EDI 841 Specifications/Technical Information Transaction Set can be used to transmit or request specifications or technical information between trading partners. It can be used to transmit engineering change and engineering change requests. It can also be used to allow EDI trading partners the ability to exchange a complete or partial technical description of a product, process, service, etc. over the same path as any other EDI transaction. The detail area can include graphic, text, parametric, tabular, image, spectral, or audio data. A transmission includes identification information to assist the receiver in interpreting and utilizing the information included in the transaction.
Further action as a consequence of the receipt and initial processing of the specification or other technical data may or may not require human intervention. The transmission and receipt of the data may require private agreement between the trading partners to automate the receipt of the data.
The total transaction must be in the general form of all ASC X12 transactions so that an EDI computer system will be able to automatically recognize it as a Specification/Technical Information Transaction Set and pass it on for processing of the data itself. The transaction set is not media dependent.
The detail area of the Specification/Technical Information Transaction Set provides a structure which allows for the exchange of a variety of specification information. For example, if the transaction contains
information describing a complete assembly, it would be necessary to include the assembly model, the models for each of the individual parts, and the associated specifications. In the case of a process it may be necessary to transmit the specification of the product along with the specifications of the process and raw materials. This transaction set can also be linked to other transaction sets.
This transaction set is not limited to a specific transmission protocol and uses other standards as applicable where they do not conflict with these requirements for specification transaction.
EDI X12 842 – Nonconformance Report
The EDI 842 Nonconformance Report Transaction Set can be used to report products and processes that do not fulfill specifications or requirements.
The Nonconformance Report Transaction Set provides the ability for the sender to report the nonconformance at the level of detail that is required. It also provides the ability to report the specific nonconformances of a component/part while identifying the assembly as the product that is in nonconformance. The Nonconformance Report Transaction Set may be used to report, initiate, or request actions related to the nonconformance being reported. Financial and accounting information is provided for reporting purposes only.
The Nonconformance Report Transaction Set has the capability to report the cause of the nonconformance and to state the proposed action to be followed to prevent a repetition of the problem.
EDI X12 843 – Response to Request for Quotation
The EDI 843 Response to Request for Quotation Transaction Set can be used to provide potential buyers with price, delivery schedule, and other terms from potential sellers of goods and services, in response to a request for such information.
EDI X12 844 – Product Transfer Account Adjustment
The EDI 844 Product Transfer Account Adjustment Transaction Set can be used to transmit specific data in the form of a debit, credit, or request for credit relating to pre-authorized product transfer actions.
EDI X12 845 – Price Authorization Acknowledgment/Status
The EDI 845 Price Authorization Acknowledgment/Status Transaction Set can be used by a vendor or manufacturer to transmit specific data relative to the status of or changes to outstanding price authorizations.
EDI X12 846 – Inventory Inquiry/Advice
The EDI 846 Inventory Inquiry/Advice Transaction Set can be used in the following ways: (1) for a seller of goods and services to provide inventory information to a prospective purchaser, with no obligation to the purchaser to acquire these goods or services; (2) for a representative of a seller of goods and services to supply inventory information to that seller; (3) for one location to supply another location with inventory information; and (4) for an inquiry as to the availability of inventory with no obligation on the seller of goods and services to reserve that inventory.
As far as EDI 852 vs. 846, EDI 852 is more focused on accurate inventory calculations, planning, and forecasting, while EDI 846 is an inquiry into the true inventory status.
EDI X12 847 – Material Claim
The EDI 847 Material Claim standard provides trading partners a means to advise each other of costs and charges involved in fabricated or purchased material or both which has been deemed damaged, unusable, or obsolete. This transaction set is not to be used to submit claims against transportation or insurance carriers. The Material Claim Transaction Set (847) can be used in the following ways: (1) for a seller of material to advise the buyer of costs and charges resulting from order cancellation or change and must be based on the buyer's authorization to fabricate or purchase material or both; (2) for a buyer of material to advise the seller of costs and charges resulting from material which was deemed damaged or unusable.
EDI X12 848 – Material Safety Data Sheet
The EDI 848 Material Safety Data Sheet Transaction Set can be used to communicate chemical characteristics, hazards, and precautions for the safe handling and use of a material. The transaction set is intended to convey the information required for a Material Safety Data Sheet (MSDS) as defined by the Occupational Safety and Health Administration (OSHA) Hazard Communication Standard, 29 CFR 1910.1200 in the United States, and Workplace Hazardous Materials Information System (WHIMS) in Canada, and various state, province, and local requirements under right-to-know legislation.
The MSDS provides the receiver with detailed information concerning material identity, emergency response, chemical and physical characteristics, toxicology, and industrial hygiene procedures.
State and federal law dictate who is obligated to provide the MSDS and to whom it should be issued. In addition, third-party providers or others with no statutory obligation may voluntarily provide an MSDS to anyone.
This transaction set allows for transmission of MSDS data in a structured, unstructured, or semi-structured form.
CAUTION: With this transaction set, text format is critical due to the MSDS's primary role as a vehicle for hazards communication. The risk if this information is not transmitted clearly and accurately could be harmful to human life, harmful to the environment, could cause mishandling of product, could result in regulatory non-compliance, and could result in liability.
Trading partners need to agree on how to interpret, store, and display/print MSDS text, especially text contained in the MSG and SD1 segments. For example, a sender may wish to format text so that one print line is mapped to one MSG segment. Segment terminator and data element delimiter characters shall not appear in any MSDS data.
WARNING: Alteration of the original document will occur if the EDI translator or application software converts characters to uppercase. This may adversely affect the appearance, effectiveness, clarity, readability, and communicability of the printed MSDS document.
EDI X12 850 – Purchase Order
The EDI X12 850 Purchase Order Transaction Set can be used to provide for customary and established business and industry practice relative to the placement of purchase orders for goods and services. This transaction set should not be used to convey purchase order changes or purchase order acknowledgment information.
It is important to emphasize the point above. The EDI 850 Purchase Order (commonly referred to as EDI 850 PO, or simply PO) is meant for EDI orders only. In a traditional EDI 850 layout, each individual product is listed as a line item and the order total to be invoiced is calculated at the bottom. The layout also includes typical sender and receiver information, such as company name and contact information, for example.
Note: The EDI 855 Purchase Order Acknowledgment is used to inform the sender of PO receipt, as well as to convey alterations to the order.
EDI X12 851 – Asset Schedule
The EDI 851 Asset Schedule Transaction Set provides for the customary and established business and industry practice relative to establishing a schedule of assets and the contractual terms and conditions relating to those assets agreed upon between lessor, lessee, buyer, seller, or any other party needing to establish a precise list of assets.
EDI X12 852 – Product Activity Data
The EDI 852 Product Activity Data Transaction Set can be used to advise a trading partner of inventory, sales, and other product activity information. Product activity data enables a trading partner to plan and ship, or propose inventory replenishment quantities, for distribution centers, warehouses or retail outlets.
The receiver of the transaction set will maintain some type of inventory/product movement records for its trading partners to enable replenishment calculations based on data provided by the distributor, warehouse or retailer.
The data contained within the EDI 852 transaction set (commonly used to exchange pharmaceutical data) is often compared with that of an EDI 867 Product Transfer and Resale Report, which provides information on product movement between locations and how that relates back to the end customer. EDI 852 and 867 are often viewed together for a more detailed overview.
As previously noted, as far as EDI 852 vs. 846, EDI 852 is more focused on accurate inventory calculations, planning, and forecasting, while EDI 846 is an inquiry into the true inventory status.
EDI X12 853 – Routing and Carrier Instruction
The EDI 853 Routing and Carrier Instruction Transaction Set provides the sender with the capability to transmit detailed routing and carrier information pertinent to a route. This transaction set only provides routing information and does not convey information about a shipping event or provide shipping authorization.
EDI X12 854 – Shipment Delivery Discrepancy Information
The EDI 854 Shipment Delivery Discrepancy Information Transaction Set is used to enable a carrier to notify a shipper or consignee of discrepancies between tendered freight and actual delivered freight. Delivery discrepancy data enables a party to track and control damages, overages, and shortages. This transaction set is not used to acknowledge receipt of goods.
EDI X12 855 – Purchase Order Acknowledgment
The EDI 855 Purchase Order Acknowledgment Transaction Set can be used to provide for customary and established business and industry practice relative to a seller's acknowledgment of a buyer's purchase order, hence the name Purchase Order Acknowledgment. The EDI 855 transaction set can also be used as notification of a vendor generated order. This usage advises a buyer that a vendor has or will ship merchandise as prearranged in their partnership.
Note: The EDI 855 Purchase Order Acknowledgment definition above does not clearly state that this transaction set also contains information on whether or not the order has been accepted, rejected, or accepted with changes. This information is presented as an EDI 855 rejection code in the EDI document.
EDI X12 856 – Ship Notice/Manifest
The EDI 856 Ship Notice/Manifest Transaction Set can be used to list the contents of a shipment of goods as well as additional information relating to the shipment, such as order information, product description, physical characteristics, type of packaging, marking, carrier information, and configuration of goods within the transportation equipment. The transaction set enables the sender to describe the contents and configuration of a shipment in various levels of detail and provides an ordered flexibility to convey information.
The sender of this transaction is the organization responsible for detailing and communicating the contents of a shipment, or shipments, to one or more receivers of the transaction set. The receiver of this transaction set can be any organization having an interest in the contents of a shipment or information about the contents of a shipment.
EDI X12 857 – Shipment and Billing Notice
The EDI 857 Shipment and Billing Notice Transaction Set can provides the recipient of a shipment with data for both receipt planning and payment generation.
EDI and telecommunications technologies suggest efficiencies in the way business data is processed. For example, the sender of a shipment may send the recipient's receiving function a Ship Notice/Manifest (856), and the payables function an Invoice (810), even though the contents of these two documents may be largely redundant. In certain business environments, the Shipment and Billing Notice permits the consolidation of these two documents into one.
Specifically, this transaction set is appropriate where the shipment data, when it includes terms and item prices, can be used both to plan receipts and to generate payment. In this environment, the exact prices for the items shipped may not be known in advance by both parties. This transaction set is not appropriate in so-called Evaluated Receipts Settlement (ERS) environments, in which the exact prices for the items shipped have been agreed upon by, and are known to, both parties in advance.
This transaction set is not to be used to replace the Ship Notice/Manifest (856) or Invoice (810) individually, but only to replace both, together. For example, do not use this transaction set in place of a Ship Notice/Manifest while continuing to send either paper or electronic invoice.
EDI X12 858 – Shipment Information
The EDI 858 Shipment Information Transaction Set can be used to provide the sender with the capability to transmit detailed bill-of-lading, rating, and/or scheduling information pertinent to a shipment. This transaction set can also be used to exchange Government Bills of Lading (GBLs), Commercial Bills of Lading (CBLs), Transportation Control and Movement Documents (TCMDs), and Personal Property Government Bills of Lading (PPGBLs). It may be used by the U.S. Civilian Government, U.S. Department of Defense, and any of their trading partners to exchange information about the shipment of freight, household goods, and passengers. This transaction set fulfills information requirements established by U.S. Government transportation movement rules and regulations.
EDI X12 859 – Freight Invoice
The EDI 859 Freight Invoice Transaction Set can be used to provide the sender with the capability to transmit an invoice, including charges, allowances, and details, for transportation services rendered.
This transaction set can also be used to exchange transportation services invoice information based on services provided in accordance with Government transportation rules and regulations. It may be used by the U.S. Civilian Government, U.S. Department of Defense, and any of their trading partners to exchange invoice information resulting from the shipment of freight, household goods, and passengers. This transaction set fulfills financial information requirements established by the U.S. Government.
EDI X12 860 – Purchase Order Change Request - Buyer Initiated
The EDI 860 Purchase Order Change Request - Buyer Initiated Transaction Set can be used to provide the information required for the customary and established business and industry practice relative to a purchase order change. This transaction can be used: (1) by a buyer to request a change to a previously submitted purchase order or (2) by a buyer to confirm acceptance of a purchase order change initiated by the seller or by mutual agreement of the two parties.
EDI X12 861 – Receiving Advice/Acceptance Certificate
The EDI 861 Receiving Advice/Acceptance Certificate Transaction Set can be used to provide for customary and established business and industry practice relative to the notification of receipt or formal acceptance of goods and services.
But if you really want to understand what an EDI 861 is, we can better tell you that this message is sent from the receiver to the shipper to inform them that the order has arrived at its intended destination. The EDI 861 message also informs the shipper if the contents received differ from the contents listed on other documents in the same transaction, such as the EDI 850 Purchase Order.
EDI X12 862 – Shipping Schedule
The EDI 862 Shipping Schedule Transaction Set can be used by a customer to convey precise shipping schedule requirements to a supplier, and is intended to supplement the planning schedule transaction set (830). The shipping schedule transaction set will supersede certain shipping and delivery information transmitted in a previous planning schedule transaction, but it does not replace the 830 transaction set. The shipping schedule transaction set shall not be used to authorize labor, materials or other resources.
The use of this transaction set will facilitate the practice of Just-In-Time (JIT) manufacturing by providing the customer with a mechanism to issue precise shipping schedule requirements on a more frequent basis than with the issuance of a planning schedule transaction, e.g., daily shipping schedules versus weekly planning schedules. The shipping schedule transaction also provides the ability for a customer location to issue shipping requirements independent of other customer locations when planning schedule transactions are issued by a consolidated scheduling organization.
EDI X12 863 – Report of Test Results
The EDI 863 Report of Test Results Transaction Set can be used to transmit the results of tests performed to satisfy a specified product or process requirement. This includes, but is not limited to, test data such as inspection data, certification data, and statistical process control measurements.
EDI X12 864 – Text Message
The EDI 864 Text Message Transaction Set can be used to provide users with a capability to electronically move messages, contracts, explanations, and other one-time communications.
The intent of the EDI 864 transaction set is to provide electronic communication (messages) for people, not for computer processing. The use of the transaction set to transmit quasi or unique transaction set standards is discouraged.
The use of the Text Message transaction set demands of the sender certain detailed information about the recipient. The EDI 864’s purpose is to provide communication to the recipient in some human-readable form. The recipient's network will dictate what capabilities are available for delivery of the information. It is the responsibility of the sender to obtain this information and include it in the transmission.
It is common for trading partners to seek information on how to implement the EDI 864 transaction set into their exchanges. Most EDI implementation guides provided by your EDI services provider will explain how to successfully use the EDI 864 Text Message.
EDI X12 865 – Purchase Order Change Acknowledgment/Request - Seller Initiated
The EDI 865 Purchase Order Change Acknowledgment/Request - Seller Initiated Transaction Set can be used by the seller to convey acceptance or rejection of changes to a previously submitted purchase order from the buyer. The transaction set is used by the seller to accept, reject, or modify a purchase order. Also, the transaction set can be seller-initiated to change a purchase order.
EDI X12 866 – Production Sequence
The EDI 866 Production Sequence Transaction Set can be used to provide for the receiver of goods to request the order in which shipments of goods arrive at one or more locations, or to specify the order in which the goods are to be unloaded from the conveyance method, or both. This specifies the sequence in which the goods are to enter the materials handling process, or are to be consumed in the production process, or both. This transaction set shall not be used to authorize labor, materials, or other resources. This transaction set shall not be used to revise any product characteristic specification.
EDI X12 867 – Product Transfer and Resale Report
The EDI 867 Product Transfer and Resale Report Transaction Set can be used to: (1) report information about product that has been transferred from one location to another; (2) report sales of product from one or more locations to an end customer; or (3) report sales of a product from one or more locations to an end customer, and demand beyond actual sales (lost orders). Report may be issued by either buyer or seller.
EDI X12 868 – Electronic Form Structure
The EDI 868 Electronic Form Structure Transaction Set can be used to provide a structure for transfer of EDI standards, or portions thereof, in an electronic form. These EDI standards include but are not limited to: ANSI X12 standards, approved ASC X12 Transaction Sets, UN/EDIFACT standard messages, and industry EDI conventions and guidelines. It is intended to provide users with the following:
The ability to send and receive EDI standards data which can be used to update application or translation software.
The ability to exchange data maintenance information with trading partners about transaction sets, segments, composite data structures, elements and codes that will be used for EDI transmissions.
The ability to transmit complete or partial EDI standards or conventions.
EDI X12 869 – Order Status Inquiry
The EDI 869 Order Status Inquiry Transaction Set can be used to request all pertinent information relative to an entire purchase order, selected line items on a purchase order, or selected products/services on a purchase order. Inquiry can also be made for all or a selected portion of the customer's ordered items, all or a selected portion of the customer's unshipped items, or all or a selected portion of the customer's shipped items.
EDI X12 870 – Order Status Report
The EDI 870 Order Status Report Transaction Set can be used to report on the current status of a requirement forecast, an entire purchase order, selected line items on a purchase order, selected products/services on a purchase order, or purchase orders for a specific customer in their entirety or on a selection basis. EDI 870 is formatted in a way so that it can also be used to report on the current status of single or multiple requisitions. The report format allows for the inclusion of "reasons" relative to the status. The EDI 870 transaction set may also be used to update the supplier's scheduled shipment or delivery dates. This transaction set can result from either an inquiry or a prearranged schedule agreed to by the trading partners.
EDI X12 872 – Residential Mortgage Insurance Application
The EDI 872 Residential Mortgage Insurance Application Transaction Set can be used by a mortgage originator to request mortgage insurance and to provide supporting information needed to obtain a mortgage insurance commitment on one or several residential mortgage loans. It can also be used, in conjunction with other transaction sets, to provide information needed to obtain an automated underwriting decision from a residential real estate automated underwriting system.
EDI X12 873 – Commodity Movement Services
The EDI 873 Commodity Movement Services Transaction Set can be used to convey request and response information for commodity movement services. This transaction is not to be used for product sales or purchases.
EDI X12 874 – Commodity Movement Services Response
The EDI 874 Commodity Movement Services Response standard can be used to return validation information in response to the Commodity Movement Services Transaction Set (873).
EDI X12 875 – Grocery Products Purchase Order
The EDI 875 Grocery Products Purchase Order Transaction Set can be used to provide for customary and established grocery industry practice relative to the placement of purchase orders for finished goods in a retail or wholesale consumer market. This standard can be used by a retailer or wholesaler organization to request delivery of finished goods from a broker or supplier organization. This transaction set should not be used to convey purchase order changes or purchase order acknowledgment information.
EDI X12 876 - Grocery Products Purchase Order Change
The EDI 876 Grocery Products Purchase Order Change Transaction Set can be used to provide for customary and established grocery industry practice relative to the changing of purchase orders for finished goods in a retail or wholesale consumer market. This standard can be used by a retailer or wholesaler organization to request a change to a previously submitted purchase order.
Changes are accomplished by restating the value of the data elements to be changed rather than indicating the difference between the old and new value. Deletions are handled by restating the values to zeros or blanks. If an item is to be deleted, the quantity ordered is restated to zero.
EDI X12 877 - Manufacturer Coupon Family Code Structure
The EDI 877 Manufacturer Coupon Family Code Structure Transaction Set can be used by a manufacturer or third party agent to notify a distributor or third party agent relative to coupon family code structures and their associated product codes.
EDI X12 878 - Product Authorization/De-authorization
The EDI 878 Product Authorization/De-authorization Transaction Set can be used to advise a trading partner of products authorized at store or warehouse level.
EDI X12 879 - Price Information
The EDI 879 Price Information Transaction Set can be used to enable a manufacturer, supplier, broker, or agent to provide a trading partner with pricing information.
EDI X12 880 - Grocery Products Invoice
The EDI 880 Grocery Products Invoice Transaction Set can be used to provide for customary and established grocery industry practice relative to billing details for finished goods in a retail or wholesale consumer market. The transaction set can be used by the supplier or broker organization to request payment from a retailer or wholesaler organization. This transaction set is to be used for standalone detail billing and cannot be used for statement billing or credit/debit adjustments.
EDI X12 881 - Manufacturer Coupon Redemption Detail
The EDI 881 Manufacturer Coupon Redemption Detail Transaction Set can be used by a manufacturer or manufacturer's agent to communicate coupon redemption detail and the associated store tag detail necessary for reconciliation to a distributor's or distributor's clearinghouse invoice.
EDI X12 882 - Direct Store Delivery Summary Information
The EDI 882 Direct Store Delivery Summary Information Transaction Set can be used to summarize detailed delivery, return and adjustment information which was previously reconciled at time of delivery in a retail direct store delivery environment, and also to request payment for the products delivered. This transaction set will provide only a summary of direct store deliveries and adjustments without product detail.
EDI X12 883 - Market Development Fund Allocation
The EDI 883 Market Development Fund Allocation Transaction Set is initiated by a manufacturer and provides for customary and established business and industry practice relative to informing a broker or retailer/wholesaler how funds should be allocated in a market development program.
EDI X12 884 - Market Development Fund Settlement
The EDI 884 Market Development Fund Settlement Transaction Set provides for customary and established business and industry practice relative to communicating settlement information associated with a single market development fund event. This transaction set is multidirectional between trading partners.
EDI X12 885 - Retail Account Characteristics
The EDI 885 Retail Account Characteristics Transaction Set is used to enable a retailer, wholesaler or broker to provide detailed attributes of a retail store such as store number, size of store, class of trade, product category information, customer demographic information, or marketing, etc. to a trading partner.
EDI X12 886 - Customer Call Reporting
The EDI 886 Customer Call Reporting Transaction Set can be used to enable a broker or manufacturer to communicate retail store level information such as condition of products, shelf space allocation, store conditions, marketing programs in effect, information on competitor products, selective pricing information, display information, etc.
EDI X12 887 - Coupon Notification
The EDI 887 Coupon Notification Transaction Set is used by a manufacturer to notify a distributor, retail clearing house, manufacturer's agent or broker of the issuance of coupons and to provide information necessary for processing.
EDI X12 888 - Item Maintenance
The EDI 888 Item Maintenance Transaction Set is used to enable a manufacturer, supplier, broker, or agent to provide detailed finished goods product information to a partner in a consumer goods market. This transaction set can be used to provide information about new products or changes in existing product specifications. Price changes will not be sent with this transaction set, but can be sent with the Price Change Transaction Set (879).
EDI X12 889 - Promotion Announcement
The EDI 889 Promotion Announcement Transaction Set can be used by a broker, distributor or manufacturer and provides for customary and established business and industry practice relative to the announcement of promotion allowance amounts, dates and performance conditions that may apply; the replacement of a previously transmitted promotion in its entirety; the cancellation of a previously transmitted promotion; changes to promotion dates; or acceptance of a promotion offered by a broker or supplier. This transaction set is multidirectional between trading partners.
EDI X12 890 - Contract & Rebate Management Transaction
The EDI 890 Contract & Rebate Management Transaction X12 Transaction Set can be used to confirm, in an electronic format, the details of a contract that has been negotiated between two or more Foodservice parties. Information conveyed in the transaction includes trade party name, address and contact information; trade party role(s), identification of the contract program(s) and the specifics of the program(s) - including specific deals, date(s), contract performance requirements, volume measurements, benchmarks, rebate/billback information, and identification of the product(s), product classification, services(s), and equipment.
EDI X12 891 - Deduction Research Report
The EDI 891 Deduction Research Report Transaction Set can be used by a seller to request information about a deduction from an invoice. It can also be used by a seller's agent or buyer to provide complete details needed to resolve deduction amounts.
EDI X12 892 - Trading Partner Performance Measurement
The EDI 892 Trading Partner Performance Measurement message allows a trading partner to indicate a level of service desired or achieved for specified performance objectives pertaining to a trading partner relationship. The transaction supports any business relationship where performance measures have been identified and the parties wish to share desired goal or achieved performance information in order to improve the levels of service.
EDI X12 893 - Item Information Request
The EDI 893 Item Information Request Transaction Set can be used by distributors and brokers to request complete item information from the manufacturers, suppliers, brokers, or agents. The item information will be returned using the Item Maintenance Transaction Set (888). This transaction set can be used also to request product activity. The product activity will be returned using the Product Activity Data Transaction Set (852).
EDI X12 894 - Delivery/Return Base Record
The EDI 892 Trading Partner Performance Measurement message allows a trading partner to indicate a level of service desired or achieved for specified performance objectives pertaining to a trading partner relationship. The transaction supports any business relationship where performance measures have been identified and the parties wish to share desired goal or achieved performance information in order to improve the levels of service.
EDI X12 895 - Delivery/Return Acknowledgment or Adjustment
The EDI 895 Delivery/Return Acknowledgment or Adjustment Transaction Set can be used to enable a distributor or Direct Store Delivery (DSD) vendor to communicate adjustments to a DSD delivery or to acknowledge the completion of a delivery.
EDI X12 896 - Product Dimension Maintenance
The EDI 896 Product Dimension Maintenance Transaction Set can be used to provide information about the physical characteristics of items for use in computerized shelf space management systems.
EDI X12 897 - Data Synchronization
The EDI 897 Data Synchronization Transaction Set can be used to provide for customary and established business and industry practice relative to furnishing or requesting information pertaining to data synchronization for products or services.
Want to Know More EDI Transaction Sets?
Read about EDI 100-199 here: Part I: X12 EDI Transaction Sets 100-199
Read about EDI 200-290 here: Part II: X12 EDI Transaction Sets 200-290
Read about EDI 300-392 here: Part III: X12 EDI Transaction Sets 300-362
Read about EDI 400-494 here: Part IV: X12 EDI Transaction Sets 400-494
Read about EDI 500-568 here: Part V: X12 EDI Transaction Sets 500-568
Read about EDI 601-650 here: Part VI: X12 EDI Transaction Sets 601-650
Read about EDI 715-754 here: Part VII: X12 EDI Transaction Sets 715-754
Read about EDI 920-999 here: Part IX: X12 EDI Transaction Sets 920-999
You can find all X12 Transaction Sets (sorted by industry) on the official X12 website here.