EDI - Connecting your Accounting to a World of Trading Partners
Next Steps
Contact me
Request more information
Have an eBridge Representative contact me:
(* required.)
* Name:
* Company:
* Phone:
* Email:
Current Accounting Package:
*Feel free to send us your questions, comments or system requirements below:
Periodically send me information on eBridge products and services.  

EDI Document Type - 856 Advance Ship Notice/Manifest

What is an 856 Advance Ship Notice/Manifest?

One of the most common EDI document types is the EDI 856 Advance Ship Notice/Manifest.  The 856 document type is an electronic version of a paper Advance Ship Notice/Manifest.  Standard EDI formats include X12, ANSI, EDIFACT and its subsets. Click here to read more about supported EDI Standards.


The 856 EDI document type is used by the supplier to indicate to the buyer the contents of the shipment it is associated with.  Specific details such as order information, physical characteristics and product descriptions, and carrier information will be represented in the document.  The 856 EDI document will also contain marking, packaging information, and configuration of goods in the transportation equipment.

What makes up the 856 Advance Ship Notice/Manifest document?

An 856 EDI Advance Ship Notice/Manifest is organized into the following segment and data elements.  A segment can contain at least one data element.  Each data element contains a data field.  Data elements could include order information, product descriptions, carrier information, and packaging information identical to a paper shipping manifest.  There are an infinite number of possibilities available for a company to include data on an 856 Advance Ship Notice/Manifest.

How is it used?

The 856 Advance Ship Notice/Manifest is most often sent when the shipment is first en route to the destination. After the 856 Advance Ship Notice/Manifest is received by the buyer, a 997 Functional Acknowledgment is sent back from the buyer indicating that the Advance Ship Notice/Manifest was successfully received. 

The Process and Standards

An EDI solution is required to process the EDI documents received into a financial system (click here to view all available financial systems eBridge integrates into) or into a readable format for manual entry.  Each trading partner will have an EDI Implementation guide outlining the specific segments, data elements, values accepted, and the applicable business rules to be followed. 

Click here to find your trading partner

Why eBridge Software?

Integration with Sage MAS 90, MAS 200, MAS 500, PFW, Business Vision, Sage Pro and more
EDI integration with Microsoft Dynamics Navision, Microsoft Dynamics Axapta and more
 
Integration with Epicor Enterprise, Vantage and iScala
 

Click here for information on benefits, pre-configured trading partner connections, EDI document types and more