EDI Management Services

EDI Services Company - 857 Shipment and Billing Notice x12 edi provided by gedims.com

 

  • Home
    • AboutUs
    • FAQ's
    • Trading Partners
  • EDI Services
    • EDI Services
    • EDI Mapping
    • EDI Connectivity
    • EDI Compliance
    • Support
    • EDI Data Types
      • EDIFACT Transaction Sets
      • x12 EDI Transaction Sets
        • 100 Series x12 EDI
        • 200 Series x12 EDI
        • 300 Series x12 EDI
        • 400 Series x12 EDI
        • 500 Series x12 EDI
        • 600 Series x12 EDI
        • 700 Series x12 EDI
        • 800 Series x12 EDI
        • 900 Series x12 EDI
  • Industries
    • Industries
    • Accounting EDI
    • Aerospace EDI
    • Automotive EDI
    • Education EDI
    • Financial EDI
    • Government EDI
    • Grocery EDI
    • Healthcare Supply EDI
    • Healthcare Insurance EDI
    • Legal EDI
    • Logistics EDI
    • Real Estate EDI
    • Retail EDI
  • Solutions
    • EDI Solutions
    • Data Translation Solutions
  • Contact Us

x12 857 Shipment and Billing Notice

857 Specifications

 The x12 Transaction Set contains the format and establishes the data contents of the Shipment and Billing Notice Transaction Set (857) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set 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.

857 Example

 


main version