EDI 810 is an invoice transaction set used for electronic billing, streamlining accounts payable processes and enhancing data accuracy.

Tag Archive for: EDI 810

Understanding ANSI ASC X12 EDI 810 Invoice: Definition, Key Data Elements, and Workflow

This post was updated to reflect current trends and information.

What is EDI 810?

EDI 810 Invoice – in international business practices, the 810 (Invoice) is an electronic document sent by the seller to the buyer to receive payment for goods or services provided.

The EDI X12 810 Transaction Set contains information about the goods and /or services, their quantity, and the price at which they were delivered to the buyer, the characteristics of the goods (color, weight, etc.), delivery terms and information about the sender and the recipient.

An electronic invoice can be generated in various standards, it all depends on which standard the partners agreed to use in order to exchange EDI. For example, in ANSI ASC X12, which is prevailing in North America, this document is called ANSI X12 Transaction Set 810 Invoice. You can also see various names for this document, for example, X12 810, EDI Invoice, EDI Invoice 810, ANSI X12 810, EDI X12 810, EDI 810, EDI 810 Document, 810 Transaction Set, etc.

“INVOIC” is an analog of the EDI 810 Invoice in the international UN / EDIFACT standard, which ispredominant outside of North America. INVOIC document (derived from the word “Invoice”, but limited to 6 letters, according to the EDIFACT rule).

The Key Data Elements of EDI 810 Invoice

A typical EDI 810 document often includes the following information:

  • Invoice number and date
  • Purchase order number
  • Delivery date
  • List of Items or services
  • Item price and identifier
  • Payment terms

Depending on the goods or services the company provides, additional information may also be included in the EDI 810 invoice.

How to Send and Receive an EDI 810?

Previously, many EDI transactions (including EDI 810), were carried out through a Value Added Network (VAN).

Currently, in order to provide an affordable and cost-efficient EDI exchange, most companies have switched to a point-to-point communication such as:

Cloud Services Provider AS2 exchange documents over the Internet by using digital certificates and encryption of the EDI data.

Cloud Services Provider FTP/SFTP – File Transfer Protocol/Secure File Transfer Protocol. These file transfer protocols allow businesses to connect with their partners via the Internet in order to exchange EDI documents.

Cloud Services Provider HTTP EDI Web Service (REST API) This EDI Web Service gains more and more popularity because is much more cost-effective and you can be up and running in less than an hour. EDI web Service meant for companies who got their technical resources to work with REST API (call and consume HTTP Rest Web services). The EDI2XML offers a free 15 days trial.

Learn more about EDI Web Service

One company can use different means or protocols to exchange EDI documents with its multiple trading Partners. (see picture below) Usually, this happens because each big company has its own requirements to exchange electronic messages or EDI.

EDI communication

EDI 810 Workflow

In typical and common business practice, the basic documents exchanged between trading partners are EDI 850 (Purchase Order) and EDI 810 (Invoice); this statement is partially true in the EDI world. Based on our more than 18 years of successful EDI Integration experience, we can tell you for sure that usually, the EDI process is much more complex. Between EDI 850 Purchase Order (or even before it) and Invoice 810, partners exchange a number of different documents. This is especially actual for retail companies.

Below you can find a possible EDI scenario in the retail industry.

Seller sends to the buyer an EDI 846 Inventory Inquiry message to advise about stock level status and availability. EDI846 can include also pricing information.

NOTE: EDI 846 is more often used in B2B e-commerce for more information about this transaction set please read the blog: What is EDI 846 document?

Based on the information received in EDI 846 the buyer generates a Purchase Order (EDI 850) which contains a list of goods that he wants to purchase from the supplier, including information about the quantities, shipping directives, and other details.

Upon receiving the Purchase Order seller send a Purchase Order Acknowledgement (EDI 855) to confirm goods are available to be sold.

In the next step, the buyer could send a seller a Purchase Order Change Request (EDI 860) to request a change to a previously submitted purchase order.

The seller responds with a Purchase Order Change Request/Acknowledgement (EDI 865) to notify of the acceptance or rejection of the change to the purchase order previously submitted by the buyer.

To send the contents of the shipment, the seller sends an EDI 856 Advance Ship Notice or EDI ASN. This EDI document must be transmitted before the arrival of the goods.

An invoice (EDI 810) can be transferred to the buyer after filling out and delivering the order or along with.

EDI 810 Invoice

Thus, you can notice, despite EDI X12 810 invoice is the most commonly exchanged electronic document, there are multiples EDI transactions sets supporting EDI 810.

Book a FREE one-on-one EDI consultation session with our in-house experts.

EDI X12 810 Invoice Sample

The following example details the format of an EDI 810 invoice.

ISA*00*          *00*          *12*5141231234     *12*5034564567     
*181122*1220*U*00501*000000001*0*T*> GS*IN*5141231234*504564567*20181122*122047*1*X*005010
ST*810*0001
BIG*20181122*I-0042537
N1*RI**92*10055500
N1*ST**92*00262
ITD*05*1*****100
DTM*011*20190120
IT1**2*EA*5.45**UP*888077648572
SDQ*EA*92*00682*1*70674*1
IT1**2*EA*5.45**UP*888077650123
SDQ*EA*92*00111*1*11356*1
IT1**3*EA*4.85**UP*888077648954
SDQ*EA*92*00682*1*11356*1*70674*1
IT1**3*EA*5.15**UP*888077649105
SDQ*EA*92*00011*2*00111*1
IT1**1*EA*5.9**UP*888077648867
SDQ*EA*92*00682*1
TDS*5770
CAD*A***FDEG
CTT*5
SE*20*0001
GE*1*1
IEA*1*000000001

EDI Specifications 810 – Invoice

Here is the specification of the EDI 810 transaction set given as an example above. You should note that like any other EDI document, 810 contains mandatory and optional data. Optional data depends of the business areas and the requirements of the trading partner.

  Segment name Purpose
ISA Interchange Control Header Marks the beginning of the transmission and provides the sender/receiver identification.
GS Functional Group Header Marks the beginning of the functional group and provides the sender/receiver identification.
ST Transaction Set Header To indicate the start of a transaction set and to assign a control number. There must be only one instance per transaction.
BIG Beginning Segment for Invoice To indicate the beginning of an invoice transaction set and transmit identifying numbers and dates.
N1 Name To identify a party by type of organization, name, and code ST- Ship To RI – Remit To The N1 is sent in conjunction with the SDQ when the N1 indicates the ship to location and the SDQ indicates the bill to locations.
ITD Terms of Sale/Deferred Terms of Sale To indicate a discount terms. Code 05 – Discount Not Applicable  
DTM Date/Time Reference To specify pertinent dates and times Code 011 Shipped
IT1 Baseline Item Data To specify the basic and most frequently used line item data for the invoice and related transactions
SDQ Destination Quantity To specify multiple locations and quantity detail.
TDS Total Monetary Value Summary To provide the total invoice amount
CAD Carrier Detail To specify transportation details for the transaction Code: FDEG  – FedEx (Ground Only)
CTT Transaction Totals Number of line items To transmit hash totals for a specific element in the transaction set. 5 – Total number of IT1 Items segments.
SE Transaction Set Trailer To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segment).
GE Functional GroupTrailer Marks the ending of the functional group and provides the sender/ receiver identification
IEA Interchange Control Trailer To define the end of an interchange of zero or more functional groups and interchange-related control segments

To learn more about the structure of ANSI ASC X12 read our Blogs:

EDI 810 Invoice Benefits

Like any EDI document, the EDI 810 provides faster communication between seller and buyer and reduces the risk of errors. Using EDI is much easier than traditional paper documents.

Thanks to EDI, the exchange of documents between trading partners is error-free.

Major benefits of EDI:

  • Reduce paper flow and increase business efficiency by reducing the time it takes for both parties to complete transactions.
  • Reduce administrative time spent manually submitting invoices and other essential documents.
  • Resolve manual data entry errors
  • Customer satisfaction is growing due to the rapid completion and delivery of your orders.
  • Faster payment from your customers

EDI 810 Integration

EDI2XML propose 2 options for EDI 810 transaction exchange with your business partners:

Option 1: Fully Managed EDI Service including translation and communication service offering to businesses of all sizes, from various industries. All processing of EDI files are done at our end, leaving customers with no on-site installation of software or hardware and an EDI project that is on time and within budget.

Option 2: EDI2XML web services is an HTTP service running over the internet, on EDI2XML own platform that is capable of receiving HTTP requests to translate EDI messages to XML, and XML messages (based on EDI2XML’s proprietary format) to EDI.

Contact us today for more information about EDI Integration and we will more than happy to assist you!

The most used EDI messages in the supply chain management

This post was updated to reflect current trends and information.

In this article, we want to talk about the top EDI messages commonly used by trading partners in supply chain management. We will explain the purpose of the EDI messages and their benefits.

What is EDI?

The acronym of EDI is Electronic Data Interchange. The main objective of EDI is to replace the exchange of paper-based business documents.

EDI is the exchange of structured business documents used in B2B. The implementation of EDI is almost limitless. EDI is present in every commercial activity:
– supply chain management
– e-commerce
– Warehousing
– Insurance
– Banking and finance
Electronic data interchange (EDI) is helping businesses to automate specific business processes, as well as to cover an entire cycle of logistics.

What does EDI mean in logistics?

In short terms, an EDI is a flow where one business partner can create digital and electronic “business documents”, compliant to a specific standard (i.e. X12, EDIFACT, Tradacom, RosettaNet,) and transfer to the second party in a secured telecommunication channel.

Useful: eBook:  EDI – Key Information You Need to Know

The most commonly used set of EDI messages

Top EDI messages

Following is the list of o the most commonly used EDI transaction sets used in today’s business space, from supply chain management to e-commerce, you will find the following documents as the basics for EDI exchange:

– EDI 846 Inventory status
– EDI 850 Purchase Order
– EDI 855 Purchase Order Acknowledgement
– EDI 856 Ship Notice/manifest (ASN)
– EDI 860 P/O Change
– EDI 810 Invoice

The above EDI messages, called “must-have” because they are necessary to automate the most important trading cycle in the supply chain management, eCommerce, and Drop-ship space.

Many companies do not limit themselves only on the above EDI messages, they can decide to leverage other transactions and business documents to improve their supply chain effectiveness; as an example, they can request to add the 753, 754, and other documents related to pickup and delivery…

Useful: EDI Transaction Types – Complete List of EDI Transactions

EDI messages types

EDI 846 Inventory status

Most trading partners in the supply chain and eCommerce space, request that their suppliers update them with their inventory status by sending the EDI 846 document. You can check the details about this document in this article.

EDI 850 Purchase Order

Often, this is the first type of EDI message that companies such as retail chains, manufacturers, warehouses, or 3PL-providers to exchange when they switch to EDI.

EDI 850 contains:

  • Order number
  • Required date and time of delivery
  • Reference to the contract or contract number
  • Price
  • Sender and customer information, the place of delivery
  • Information on the contents of the order (bar codes, quantity, the name of the goods, multiplicity of packaging).

With the EDI 850, the product ordering process goes faster and becomes cheaper as the number of people involved in the process is reduced. Thanks to the fast and guaranteed transfer of information about the order, the supplier improves the reliability of the deliveries.

EDI 855 Purchase Order Acknowledgement

EDI 855 response to the Purchase Order is a “couple” message for EDI 850. The supplier sends EDI 855 to the buyer in accordance with the order value or suggesting to make changes regarding order quantities. This helps to avoid disruption in the supply chain.

Useful reading: What is EDI 855 Purchase Order Acknowledgment?

EDI 856 Ship Notice/manifest or ASN

ASN is a pair of EDI 861 Receiving Advice.

These notifications are exchanged between the business partners at the stage of shipment and receipt of the goods.

The supplier sends ASN immediately after the shipment. This EDI message helps to simplify and speed up the process of acceptance of goods. EDI 856 Ship Notice/manifest contains detail shipment information:

  • Shipment information (bill of lading number, ship to, ship from, etc.)
  • Unit load information about a physical shipping item.
  • Order information such as purchase order number, buying place, division number, etc.
  • Tare information about the pallets.
  • Pack information about the shipping package (cartons, racks, bags, etc.,)
  • Item information about the shipped goods, such as SKU identification, quantity shipped, etc.

Companies that have implemented ASN significantly increase the speed of receiving goods and entering data into the business system – with EDI 856 you do not need to drive numbers manually from the invoices. ASN information can go directly to the business system.

For the big trading retailers, this type of EDI message is a vital necessity. Advance notification of the goods delivery helps to prepare for its acceptance. Even before the supplier’s truck arrives, the retailers already have a list of the goods sent.

EDI 860 Buyer triggered P/O change

EDI 860 is a transaction sent to the supplier advising him about a change in the Purchase order sent earlier. The change can be to increase/decrease/delete quantities on an order or to change dates.

EDI 810 Invoice

EDI 810 Invoice is an electronic invoice transaction sent by the supplier to the buyer.

Learn more about  x12 810 Invoice in this article: What is an ANSI ASC X12 EDI 810 invoice?

Becoming EDI Compliant

We will help you save on EDI, quickly perform the integration, configure the connection with any trading partner or supplier.

Contact us today for more information and for pricing.

Free Consultation
Related Posts:

What is EDI 846 document?

What is EDIFACT? | UN / EDIFACT standard overview

Electronic Data Interchange: Key Information You Need to Know

What Are the Differences Between ANSI X12 and UN/EDIFACT

EDI compliance and integration with Burlington Coat Factory

,

This post was updated to reflect current trends and information.

Company Overview of Burlington Coat Factory

Burlington Coat Factory is an American national off-price department store retailer and a division of Burlington Coat Factory Warehouse Corporation. The company operated 592 stores located in 45 states and Puerto Rico, inclusive of an internet store and has approximately 40 000 employees.

As per the company’s website, the first store was opened in Burlington, New Jersey in 1972, selling principally coats and outerwear.  Since then company diversified product categories by offering an extensive selection fashion-focused, labeled merchandise acquired directly from nationally recognized manufacturers and other suppliers.

Burlington Coat Factory EDI Standards

For all communications with their suppliers, Burlington Coat Factory use Electronic Data Interchange (EDI) including purchase orders, Advance Ship Notices (ASN), Invoices etc. The company is on EDI X12 v4010 standard.

Burlington Coat Factory EDI Specification

850 Purchase Order

Burlington Coat Factory sends 850 Purchase Orders via EDI, to inform their seller of a product request. A Purchase order 850 may be used to provide distribution requirements for receiving location(s), such as cross-dock, drop-ship, or direct to consumer as would be the case for the Burlington online store.

For each 850 Purchase Order, they indicate a purchase order number, a P/O date, the location of the ship to, provide a delivery time and product pricing.

856 Ship Notice/Manifest

Burlington Stores requires their seller to send an 856 Ship Notice/Manifest via EDI, to be advised of shipment information. The 856 transactions, includes order information, description of goods, types of packaging used, carrier information and more.

For a single purchase order, there can be or more shipments which would be followed by one or more 856 ASN Advance Ship Notice and possibly one or more 810 Invoices.

810 Invoice

The suppliers of Burlington Coat Factory have to comply with X12 810 Invoice to bill Burlington for products and services shipped to their stores.

Using an EDI 810 Invoice, permits Burlington to register payment-request information and update automatically their appropriate systems. The information included in the Invoice 810 provides automated cross-referencing of a purchase order and receiving information. This process is executed without manual intervention, thus eliminating further data entry.

824 Application Advice

Burlington Stores send 824 Application Advice via EDI, to notify the acceptance, rejection or acceptance with change of a trading partner’s transaction. The 824 transaction set contains information such as quantity and monetary amounts, dates, reference numbers, it also provides trading partner information, technical error descriptions in free-form text format.

852 Product Activity

The EDI message 852 Product Activity sent by Burlington to transmit product sales by location to the supplier. These messages inform a supplier about the items sold and items on hand at a store and its level. Burlington sends the EDI 852 message on a scheduled basis (e.g., weekly on Mondays) for input to a vendor’s sales and inventory management system.

997 Functional Acknowledgment

997 Functional Acknowledgment is required by Burlington, when sending or receiving EDI transactions. 997s, are an indication that a trading partner has successfully received a well-formed EDI message. The message Functional Acknowledgments 997 generated automatically for transmission back to the sending party.

Becoming EDI compliant with Burlington Coat Factory

EDI2XML offers full EDI integration with Burlington Coat Factory. From A to Z, a customer’s EDI requirements are handled by our team of EDI experts. We take care of EDI mapping, Trading Partner configuration, Standards maintenance, XML/CSV/TXT translation etc.

For more information Download our EDI2XML Translation Service Pricing Package here 

EDI2XML pricing packages

4 Challenges of EDI and Drop-Ship in eCommerce


This post was updated to reflect current trends and information.

EDI integration projects


The term “drop-ship” has been used quite a lot in recent years by retailers and manufacturers alike. This supply chain management method looks to be gaining in popularity going into 2019 and will likely be in high demand for years to come as well.

Let me first explain the meaning of drop shipping and how it has become so popular…

What is Drop Shipping?

“Drop-ship” is a fulfillment method where a merchant does not carry any inventory on hand. Instead they sell products to consumers via an online store (eCommerce), send the customers’ orders to the manufacturer and have the manufacturer ship the goods directly to the customer. The customer will never know the difference since they pay the merchant and receive their goods in a box with the merchant’s labels. This method eliminates the need for the merchant to handle the goods.

The Rise of Drop-Ship Popularity

Due to the fast evolution of eCommerce, coupled with the continuous challenges that businesses face to reduce costs and increase profitability, the drop-ship method is in high in demand by major retailers. You’ll find that eCommerce giants like Amazon.com, Costco.com, Cabelas.com, Sears.com and others, are increasing the pressure on their supply chain to adopt the drop-ship concept. Of course, they also require their business partners to comply with their EDI requirements and specs for a full automation of the entire sales cycle.

The Complexity behind Drop Shipping

If we take a behind-the-scenes look at drop shipping from 2 perspectives, from the eCommerce retailer, like Amazon or Cabela’s, and from the manufacturer of goods, we’ll find the simplicities and complexities behind each process.

From the perspective of the eCommerce retailer, the drop-ship method allows them to eliminate the need to carry any inventory and to ship their goods. Their process is rather simple, profitable and quick. All they need to do is sell products online and ensure that their partnered manufacturers are EDI and drop-ship ready. Once they sell products from their eCommerce site, they will send the orders via EDI to their manufacturer and the manufacturer takes it from there.

From the perspective of the manufacturer, we’ll find some of the complexities. However, if they are setup correctly from the get-go, then it becomes rather simple and quick. In this case, the drop-shipper (manufacturer or distributer) is entirely in charge of the fulfillment of all incoming eCommerce orders (from the retailer). They need to process the sale all the while complying with the retailer’s business specifications such as EDI. Let’s go over the top 4 challenges a manufacturer must overcome during a drop-ship EDI implementation;

Top 4 Challenges the Drop-Shipper Might Face

If you are a manufacturer and have recently partnered with an eCommerce retailer to sell your products, then you might already know that they will require you to drop ship and automate your sales process through EDI integration. I have listed below the top 4 challenges you might face as a drop shipper;

1.    Ability to submit accurate inventory feed (846) to the eCommerce retailer

When starting a new business relationship with an eCommerce retailer based on the drop-ship method, the first step will be to feed inventory & per-item stock statuses to the retailer in a timely manner. This inventory inquiry/advice document is called EDI 846. Major retailers such as Amazon.com, Cabelas.com, Costco.com and Wal-Mart.com require their Trading Partners to send them an 846 document at least twice a day so that their online store can properly show only available products, based on inventory available to ship. Most of the time, companies either don’t have an accurate inventory system or their stock status is not properly maintained, which can be a great challenge to overcome. Even if companies have accurate inventory statuses, many of their management software systems, even reputable and expensive systems such as JDE, do not have built-in capabilities to send the 846-inventory status in X12 format, as per the requirements of the retailers.

2.    Ability to receive and process EDI orders (850)

Another challenge comes in the form of receiving EDI purchase orders (document 850). Many companies struggle with the capability to receive EDI orders, process them and integrate them quickly into their management system before it is sent to the pick/pack/ship process down the line in the supply chain. Most software systems are still missing this integration capability and require end users to manually key-in orders received in EDI x12 format, to then be able to process and ship. This is a great challenge for many manufacturing and distribution businesses. Dealing with eCommerce Stores, orders are continuously coming in, at all hours, in high volumes. The client (retailer) typically expects the manufacturers to ship within 24 to 48 hours (at the latest!). Moreover, eCommerce retailers are expecting to receive a P/O acknowledgment (document 855) via EDI. Therefore, it’s extremely critical that the drop shipper is equipped with a fully integrated software solution where EDI orders can automatically come through in real-time, so that they are quickly processed.

3.    Ability to fulfill orders within a very short period of time

As previously mentioned, eCommerce retailers expect their partners to ship goods to the end-consumer within a very short time frame (24 to 48 hours). They expect them to package the products, print customized picking/packing slips to send with the goods and complete the shipping process in a very quick manner. In case of failure to comply, there is a risk the vendor will be eliminated from the program. At the logistics level, an important challenge is to have a management system and required resources to process orders, pick, pack and ship in the required time frame. Efficiency in this case is imperative since time is money.

4.    Ability to electronically submit Ship Notices (856) & Invoices (810)

Two other EDI x12 documents are sent out to the eCommerce retailer by the drop shipper; the Advance Ship Notice or ASN (document 856) and of course an invoice (document 810). Most companies don’t currently have the capability to turn those business documents into an x12 EDI format and submit to the Trading Partner, straight from their management system.

Overcoming Drop-Ship Challenges

Our team’s experience with EDI drop-ship has allowed us to overcome the above challenges in an efficient and timely manner. Since every project varies, it’s important to do the following;

  • Surround yourself with experts in EDI who have the experience in dealing with drop-ship projects. It’s important to have enough knowledge and expertise in these methods prior to beginning any EDI drop-ship project. It’s important to get organized internally before any major project.
  • Ask an EDI Provider, who offers flexible and affordable EDI & IT services, to help you streamline your processes and advise you on best practices.
  • Opt for a full EDI integration with your current management software solution, if possible. Of course, such an option is not always possible or provided by your Software provider but if it is, it’s our recommendation to go ahead with this since it will eliminate chargebacks and increase efficiency in your EDI projects so you are best capable of complying with your Trading Partners’ demands. Don’t forget, partner demands and specs can change at any moment. It’s best to ensure you can handle changes at a moment’s notice. (Flexibility is the way to go!)

If you’re looking to complete an EDI Drop-Ship project, contact us today. We’ve got the experts and the EDI2XML service to get you drop-ship ready. Contact us today for your FREE consultation to evaluate your EDI project.

Free EDI consultation