Author: Chad Symens

The EDI 867 transaction set represents the Product Transfer and Resale Report. EDI 867 is used to give information on a product that has been relocated to a new location within a company. It can also be used to report sales of a product from multiple locations to an end customer, such as point-of-sale, or POS data. This specific EDI transaction code can also be used to communicate returns from customers to retail locations or distribution centers.

Each 867 document includes the following information:

• Resale Information Or Product Transferred, can include contract details, quantity, purchase order, code types, etc.
• Transaction Totals (Line Items), can include weights, dimensions, other unit measurements.
• Organization Identification Details.

The 867 transaction set can be used in a wide range of different industries. While the retail industry is likely the most common to use it, it can also be used by manufactures, resellers, distributors and wholesalers.

We can give you a quick examples.

Utilities may use an EDI 867 to communicate meter readings, which may include metrics on how much electricity is being used. Wholesalers may use 867 to communicate to a manufacturer about product movements at their wholesale locations.

In many ways, 867 is similar to the EDI 852 transaction set, which is used by the top resellers in the world to provide detailed insights on product inventory and sales levels to the manufacturers of those products.

EDI 867 Format

ISA*01*0000000000*01*0000000000*ZZ*ABCDEFGHIJKLMNO*ZZ*123456789012345*101127*1719*U*00400*000003438*0*P*>
GS*PT*4405197800*999999999*20110127*1719*1421*X*005010VICS
ST*867*0001
BPT*22*ABC123*20120128*01
CUR*SE*USD
DTM*193*20120130
N1*SE*XYZ SUPPLIER*9*1234567890001
N1*DS*ABC DISTRIBUTION*9*9876543210001
PTD*IB***TF*TRANSFER 123
N1*TT*ABC DISTRIBUTION BRANCH 2*9*9876543210002
QTY*78*100*EA
LIN*0001*VC*P-8750*BP*12345
UIT*EA*5*PE
AMT*1*500
DTM*514*20120130
CTT*1*100
SE*16*0001
GE*1*1421
IEA*1*000006638

EDI 867 Specifications

This X12 Transaction Set contains the format and establishes the data contents of the Product Transfer and Resale Report Transaction Set (867) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to:

1. Report Sales Of A Product From One Or More Locations To End Customer
2. Report Sales Of A Product From One Or More Locations And Demand Beyond Sales To End Customer
3. Report Details About Product Being Transferred From One Area To Another

The EDI 861 transaction set is an electronic version of a Receiving Advice/Acceptance Certificate. This EDI transaction can be used to report shipment receipts or it can be used as a formal acceptance for defective items that are being returned. In the case third-party receiving, such as a drop-shipment, the sender may transmit an 861 to report to the purchaser that the shipment was received. Unlike the simple receipt acknowledgement, EDI 861 includes notifications for the disposition of the shipment as it’s received, which can include:

• When a portion or full shipment is received
• When a portion or full shipment is not received
• When a discrepancy in the content receive vs. ordered
• When an item received is damaged

The 861 transaction set is usually used in the retail industry, often used with automatic stock-replenishment programs that are managed by vendors. The use of RFID and encoded ID tags give the ability to track individual cartons. This can include;

• The specific location – As it moves through the distribution center
• Individual store location or number
• Status update – This could be on the sales floor, open box, layaway, reserve stock, etc.

When this type of information can be sent to the supplier via an 861, it allows retailers to provide their vendors with targeted visibility at various points in the supply chain. By doing so, it allows vendors to better manage production schedules, lead times and inventory levels. The 861 can also be useful for initiating proof of delivery and shipment tracking processes, and for carrier performance evaluations.

EDI 861 Format

ISA*01*0000000000*01*0000000000*ZZ*ABCDEFGHIJKLMNO*ZZ*123456789012345*101127*1719*U*00400*000003438*0*P*>
GS*RC*4405197800*999999999*20101127*1719*1421*X*004010VICS
ST*861*1002
BRA*1625791400*20010816*06*8
DTM*003*20010816
PRF*123
N1*ST**21*00KESTJ00
RCD**5*CA
LIN**IN*22970DCXXX493*VC*DB12
RCD**5*CA
LIN**IN*22970DCXXXY493*VC*DB13
CTT*2
SE*12*1002
GE*1*1421
IEA*1*000008638

EDI 861 Specifications

This X12 Transaction Set contains the format and establishes the data contents of the Receiving Advice/Acceptance Certificate Transaction Set (861) for use within the context of an Electronic Data Interchange (EDI) environment. EDI 861 can be used to for multiple business types and sets industry standards relative to the notification of receipt or formal acceptance of goods and services.

The 853 EDI document type is an electronic version of a paper Routing and Carrier Instruction.  The 853 EDI document type is used to wire detailed routing and carrier information relevant to a specific route. Now, EDI 853 doesn’t provide information about shipping events or any type of authorization.

An EDI 853 – Routing and Carrier Instruction document is organized into data and segment elements. For a segment, it can contain at least one data element. Each data element would contain a data field. Data elements can include a number of different things;

• List Of Shops
• Carrier
• Route
• Estimated Time Of Arrival (ETA)

There are an infinite number of possibilities available for a company to include data on an 853 – Routing and Carrier Instruction.

EDI 853 Specifications

This X12 Transaction Set contains the format and establishes the data contents of the Routing and Carrier Instruction Transaction Set (853) for use within the context of an Electronic Data Interchange (EDI) environment. This 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.

The EDI 865 transaction set is referred to as a Purchase Order Change Request/Acknowledgement Request.

Sellers of goods and services transmit 865 documents for 2 general purposes. For one, the 865 can be used as an acknowledgment to communicate order changes previously submitted that were accepted or rejected. Secondly, changes made by sellers to previously submitted purchase orders are communicated to the buyers in an 865 transaction (used as a Request).

The 865 represents one in a sequence of transactions in a typical business process involving a buyer (example: retailer) and a seller (example: manufacturer). That process would include the following exchanges;

• A buyer would submit a 850 Purchase Order to a seller to order products.
• The seller would respond with a 855 Purchase Order Acknowledgment transaction.
• A buyer that needs to make changes to the original Purchase Order would use a 860 Purchase Order Change Request to communicate the changes.
• The seller would accept or reject the buyer’s changes using a EDI 865 Acknowledgement transaction.
• The seller could request changes to the original purchase order also, using the 865 Request transaction.

Do keep in mind, an acknowledgement of a buyer’s purchase order change request can be communicated to the seller in two ways, with a 855 Acknowledge or with a 865 Acknowledgment. This is the buyer’s choice, they would likely follow their own EDI Guidelines to determine which it would be. The EDI 865 transaction usually includes the same information that appears in a purchase order (850 transaction set), such as shipping details, product descriptions, item quantities, terms and costs. In the scenario where changes are made, it may also include references to what is changed from the original purchase order. It will also include a code to indicate whether the document is being used as a Request or as an Acknowledgement.

EDI 865 Specifications

This X12 Transaction Set contains the format and establishes the data contents of the Purchase Order Change Acknowledgment/Request Transaction Set (865) for use within the context of an Electronic Data Interchange (EDI) environment. EDI 865 can be used to communicate the acceptance or rejection of changes to earlier submitted purchase orders by the seller. It can also be used to notify the buyer of changes initiated by the seller to a previously submitted purchase order by the seller.

The EDI 860 transaction set represents the electronic Purchase Order Change Request. It is used by buyers to request a change to a purchase order (EDI 850) they previously submitted. The 860 can be used by buyers for confirmation on changes accepted to purchase orders by the sellers. EDI 860 is very important as it ensures the final order is accurate and complete. This specific document also provides information about the original purchase order, as well as purchase order changes. These may include but are not limited to:

• Adding Items
• Changing Items
• Changing Quantities
• Changing Dates
• Changing Prices
• Rescheduling Order

EDI 860 Specifications

Once an EDI 860 Purchase Order Change Request is sent from a customer, the seller would then send an EDI 865 Purchase Order Acknowledgment with Change in response.

This X12 Transaction Set contains the format and establishes the data contents of the Purchase Order Change Request – Buyer Initiated Transaction Set (860) for use within compliance of the Electronic Data Interchange (EDI) environment.

EDI 860 can be used to provide the insights required for customary and established business to follow best industry practices relative to purchase order changes. This transaction can be used:

• By a buyer to request changes to the purchase order they originally sent over
• By a buyer to confirm the accepted changes to a purchase order initiated by the seller or by mutual agreement

Retail EDI Transactions: 850, 852, 855, 856, 857

There’s a number of retail EDI transactions you want to become familiar with, these include but are not limited to;

• Purchase Order (EDI 850)
• Product Activity Data (EDI 852)
• Purchase Order Acknowledgment (EDI 855)
• Shipment Notice/Manifest (EDI 856)
• Shipment and Billing Notice (EDI 857)

These retail EDI transactions are widely used in the supply chain industry and warehousing.

850 Purchase Order – This is one of the most common used transactions in EDI. The 850 EDI transaction is sent by a customer to the seller as a placement of purchase orders for goods and services. This transaction cannot be used for sending purchase order changes or purchase order acknowledgment information.

852 Product Activity Data – This transaction can be sent from one trading partner to another for providing information about product activity. This way another business partner can plan his warehouse inventory and shipping to distribution centers etc. 852 Product Activity Data helps to process inventory planning and calculations more exact and successfully.

855 Purchase Order Acknowledment – This transaction is sent by a customer to a seller to acknowledge the purchase order sent earlier. If it is preaaranged in business partnership regulations, 855 Purchase Order Acknowledment can be used as notification of a vendor generated order and the merchandised will be shipped as agreed.

856 Shipment Notice/Manifest – This electronic data interchange transaction is generated by the party responsible for goods shipment. The transaction set provides information as for the list of goods shipped, their description, quantity as well as packaging details, marking, carrier and transaportation information. There may be several receivers of the 856 Shipment Notice/Manifest – parties having interest in the information regarding the contents of the shipment.

857 Shipment and Billing Notice – This EDI transaction gives the information about receipt planning and payment generation as EDI supposes effective data processing. Let’s look at the example. The sender of the shipment can send to the recipient two transactions – Ship Notice/Manifest (856) and an Invoice (810) though these EDI documents are quite different. In some processing systems the the consolidation of these two documents into one Shipment and Billing Notice is possible. 857 Shipment and Billing Notice cannot to be used to replace the Ship Notice/Manifest (856) or Invoice (810) individually, but only to replace both, together.

EDI is nothing new, its been around for many years. For multiple industries, EDI plays a key role in their company. Many business owners choose EDI because it saves them money and while that’s normally the case, EDI has many more benefits you should know about.

In this article, we’re going to be discussing the benefits of EDI, some are well known, others not so much.

(1) Workflow Efficiency

• One of the biggest EDI benefits is how efficient it can be to your workflow.
• With EDI automation, you can avoid overstocking and under stocking.
• Productivity can increase because your team can focus on more important tasks.
• Since you won’t have staff focused on data and errors, you’ll be able to allow them to focus on workflow that adds to your bottom line.

(2) More Speed And Accuracy

• Manual tasks takes time and when you’re entering data manually, mistakes are going to be made. With EDI, you can reduce your mistakes and errors by 40 percent or more.
• If you’re not using EDI, transactions can take days, even weeks to be completed. If you have EDI, those transactions are going to be completed a lot faster.
• It’s also a big benefit to your business cycles, allowing you to speed them up by over 60 percent.
• EDI can shorten your order processing and delivery times as well, allowing you to reduce your inventory levels or replenish them as needed.

(3) Cost-Effective

• Yes, this is one you likely know but it’s one of the top benefits of EDI.
• When you go digital, you reduce and eliminate your need for paper, printing, filing, storage, postages.
• Lost orders and faxes can also lead to higher costs, EDI can lower these too.
• A large electronics manufacturer calculated the cost of processing an order manually at $38 compared to just $1.35 for an order processed using EDI, which is a huge savings.

(4) Strategies Using EDI

• For those of you that are thinking about growing your business, EDI gives you the opportunity to enter global markets.
• EDI can give you real-time data on the spot, exactly what you need to make strategic decisions for your company. You can see your EDI transactions as they’re made, giving you the opportunity to react immediately.
• Another benefit you don’t hear as much is that it shortens your lead times for new products.
• It’s also good for the environment as you’ll be reducing and eliminating your need for paper.

There’s no question about it, EDI can improve your business in many ways. Another way to improve your business with EDI is EDI 852. If you’re a retailer, you know what EDI 852 is. It’s referred to as a Product Activity Report. It gives you data on your products and inventory.

Working efficiently with EDI 852 data requires a good analysis tool like Accelerated Analytics^®. Otherwise, the merchandise planner is left to sort through line after line of data to find problems and opportunities. By using Accelerated Analytics^®, the routine tasks of formatting and consolidating data are eliminated, and exception logic can be used to save time.

The Accelerated Analytics^® team understands how to work with EDI 852 data. If you’re ready to see how EDI 852 can help your company thrive, reach out and let us show you. Click here and we’ll be in touch soon. If you want to see our demo, that’s fine also, just click here.

This X12 Transaction Set includes the format and data contents of the Shipment and Billing Notice Transaction Set (857) for use within the context of an Electronic Data Interchange (EDI) environment.

This EDI transaction code gives the recipient of the shipment data for generating payments and receipt planning. There’s no question about it, with EDI, processing data is faster and more efficient.

It’s not unheard of for companies to send an EDI 857 and EDI 810 together. The sender of a shipment may send the recipient’s receiving function a Ship Notice/Manifest (856), and the payables function an Invoice (810). Don’t these two docs include the same information? Yes and no. The two docs share a lot of information.

In some scenarios, the Shipment and Billing Notice allows the consolidation of EDI 857 and EDI 810. There’s a few different scenarios where this transaction set is appropriate with the shipment data;

• When it includes terms and item prices
• Used both to plan receipts and to generate payment

You can’t use this transaction set to replace the Ship Notice/Manifest (856) or Invoice (EDI 810) individually, but only to replace both of them together.

You wouldn’t want to use this transaction set in place of a Ship Notice/Manifest while continuing to send paper or electronic invoices. In this case, both parties may not know the exact prices for the items shipped. 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 with both parties knowing that in advance.

The EDI 830 Planning Schedule transaction set is known as an electronic sales forecast. This transaction code can only be used in 1 of 3 ways.

• Used as a Sales Forecast
• Used as a Forecast and Authorization for recipient to Commit To Resources
• Used as a Forecast that will also includes Order Release Levels

The senders of 830 Planning Schedules are usually manufacturers communicating with their suppliers. Due to this action, the trading partners would represent a buyer (manufacturer) and a seller (supplier). The Planning Schedule would allow the seller to plan resources such as labor and material, and to fulfill orders automatically based on the customer’s inventory levels.

830 transactions that include a Material Release are likely to include;

• Shipping and Delivery Patterns (Weekly, Monthly, Quarterly)
• Cumulative Quantities (Period-To-Date)
• Resource Authorizations

This can eliminate the need for the customer to generate separate Purchase Orders. This information in a single 830 transaction can relate to all production items sourced from a given supplier site. While the 830 transaction may include shipping information, it is based on forecasts.

EDI 830 Format

ISA*01*0000000000*01*0000000000*ZZ*ABCDEFGHIJKLMNO*ZZ*123456789012345*101127*1719*U*00400*000003438*0*P*>
GS*PS*1234567890 *999999999 *20120126*1211*1*T*004010
ST*830*0001
BFR*00**001*DL*A*19990607*19991029*19990611
N1*SU*STURGIS MOLDED PRODUCTS*92*C84A
N2*STURGIS MOLDED PRODUCTS *70343 CLARK STREET
N3*PO OX 246 *STURGIS, MI 49091
LIN**PC*AA017830-1441*PD*TERMINAL (AN PC )*PO*C01000*RN*001
UIT*EA
PO4*1*96*X4
REF*DK*A22
PER*EX*JOHN DOE*TE*4239827000*****12345
FST*1728*C*D*19990614
FST*1440*C*D*19990615
FST*1440*C*D*19990616
FST*1440*C*D*19990617
FST*1440*C*D*19990618
FST*7392*D*W*19990621
FST*7392*D*W*19990628
LIN**PC*AA017380-2030*PO*C50000*RN*001
UIT*PC
PO4*1*108*X4
REF*DK*A22
PER*EX*JOHN DOE*TE*4239827000*****12345
FST*108*C*D*19990614
FST*108*C*D*19990615
FST*108*C*D*19990616
FST*216*C*D*19990617
FST*108*C*D*19990618
FST*756*D*W*19990621
FST*756*D*W*19990628
CTT*2
SE*31*0001
GE*1*1
IEA*1*000000018

EDI 830 Specifications

This X12 Transaction Set contains the format and establishes the data contents of the Planning Schedule with Release Capability Transaction Set (830) for use within the context of an Electronic Data Interchange (EDI) environment.

The 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 transaction may be used in various ways or in a combination of ways, such as:

1. Just as a simple forecast
2. A forecast with the buyer’s authorization for a seller to commit to resources
3. A forecast used as an order release, including elements like period-to-date cumulative quantities, resource authorizations or shipping/delivery pattern requirements

The order release forecast 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.

The EDI 856 transaction is more commonly called an EDI Advance Ship Notice, also referred to by EDI ASN. This EDI transaction code is used to electronically communicate shipment contents to another trading partner. This code would be sent in advance of a shipment arriving at the a trading partner’s facility.

The 856 ship manifest transaction is mainly used in the retail industry, manufacturing and automotive industries, usually in response to transactions that include EDI 850, EDI 830, or EDI 862. While contents of a shipment are outlined, the EDI 856 transaction also includes order information, product descriptions, packaging types, carrier details and others.

An EDI ASN can include information on a few different things, which would include;

• Shipment Level Details – Like Tracking Numbers and Carrier Details
• Order Level Details – Like Purchase Order Numbers
• Item Level Details – Such as Items and Quantities
• Pack Level Details – Such as Printed Barcodes

The EDI 856 may be the most complicated document to implement for suppliers. Each trading partner can have very different requirements, which puts the burden on the supplier to support many different formats. The EDI ASN also becomes a data collection issue because of the volume of data points that must be captured and transmitted back to the trading partner. For example, each carton in a shipment may be assigned a unique barcode identifier that must be transmitted back to the trading partner.

EDI 856 Format

ISA*01*0000000000*01*0000000000*ZZ*ABCDEFGHIJKLMNO*ZZ*123456789012345*101127*1719*U*00400*000003438*0*P*>
GS*SH*4405197800*999999999*20111206*1045*49*X*004060
ST*856*0008
BSN*14*829716*20111206*142428*0002
HL*1**S
TD1*PCS*2****A3*60.310*LB
TD5**2*XXXX**XXXX
REF*BM*999999-001
REF*CN*5787970539
DTM*011*20111206
N1*SH*1 EDI SOURCE
N3*31875 SOLON RD
N4*SOLON*OH*44139
N1*OB*XYZ RETAIL
N3*P O BOX 9999999
N4*ATLANTA*GA*31139-0020**SN*9999
N1*SF*1 EDI SOURCE

EDI 856 Specification

This is a X12 transaction set, which contains the format and establishes the data contents of the Ship Manifest/Notice Transaction Set (856) for use within the context of an Electronic Data Interchange (EDI) environment.

EDI 856 can be used to list a number of different things, which may include;

• Contents of the Shipment
• Details relating to the Shipment
• Product Descriptions
• Order Details
• Packaging Types
• Carrier Information
• Specific Physical Characteristics

The transaction set allows the sender to define contents and the configuration of a shipment in a number of different levels of detail and gives you ordered flexibility to convey information. The sender of this transaction would be responsible for detailing and communicating the contents of a single shipment, or multiple shipments, to one or more receivers of the transaction set. The receiver can be any organization with an interest in the contents of a shipment or information about the contents of a shipment.