EDI 857 - Shipment and Billing Notice

The EDI 857, also known as Shipment and Billing Notice, is a combined document that reports both shipment details and billing information in one transaction.

The EDI 857, also known as Shipment and Billing Notice, is a combined document that reports both shipment details and billing information in one transaction.

What is the Purpose of EDI 857 - Shipment and Billing Notice?

The EDI 857 transmits both shipping and billing information, commonly used in the grocery sector. It organizes shipment data into five main categories: order, pack, item, shipment, and pallet details.

What are the important elements of EDI 857 - Shipment and Billing Notice?

The EDI 857 (Shipment and Billing Notice) is a standardized electronic document used to communicate both shipping and billing information in a single transaction. Here are the key elements: 1. Header Information: - Document Reference Number - Transaction Date/Time - Purpose Code - Transaction Type Code - Shipment Date - Currency Code - Bill of Lading Number 2. Partner Information: - Shipper Information (name, ID, address) - Consignee Information - Bill-to Party - Ship-from Location - Ship-to Location - Carrier Information 3. Shipment Details: - Shipment ID - Mode of Transport - Routing Information - Equipment Details - Estimated Delivery Date - Delivery Instructions - Weight Information - Package Count 4. Billing Information: - Invoice Number - Invoice Date - Payment Terms - Total Charges - Tax Information - Freight Charges - Additional Charges - Payment Due Date 5. Product Information: - Line Item Numbers - Product Identifiers - Item Descriptions - Quantities Shipped - Unit Price - Extended Amount - Unit of Measure - Product Weight 6. Charge Details: - Freight Charges - Handling Charges - Insurance Charges - Tax Charges - Fuel Surcharges - Additional Fees - Total Amount Due 7. Reference Numbers: - Purchase Order Numbers - Sales Order Numbers - Customer Reference Numbers - Shipping References - Contract Numbers - Account Numbers 8. Additional Elements: - Special Instructions - Handling Requirements - Hazardous Material Information - Temperature Requirements - Insurance Information - Documentation Requirements 9. Control Segments: - Transaction Set Control Numbers - Segment Counts - Hash Totals - Control Totals The EDI 857 is crucial for combining shipping and billing information into a single document, streamlining the communication process between trading partners.

What are the potential issues with EDI 857 - Shipment and Billing Notice?

Here are the potential issues that can occur with EDI 857 (Shipment and Billing Notice) transmissions: 1. Shipment Information Problems: - Incorrect shipment quantities - Wrong weight information - Invalid package counts - Missing tracking numbers - Wrong carrier details - Incorrect routing information - Invalid delivery schedules 2. Billing Information Issues: - Wrong invoice amounts - Invalid charge calculations - Missing tax information - Incorrect freight charges - Wrong currency codes - Invalid payment terms - Missing discount details 3. Product Detail Problems: - Wrong item numbers - Invalid product descriptions - Missing unit prices - Incorrect extended amounts - Wrong unit of measure - Invalid product weights - Missing commodity codes 4. Reference Number Issues: - Missing bill of lading numbers - Invalid purchase order references - Wrong sales order numbers - Incorrect shipment numbers - Missing invoice numbers - Wrong customer references - Invalid contract numbers 5. Date and Time Problems: - Wrong shipment dates - Invalid delivery dates - Missing invoice dates - Incorrect payment due dates - Wrong processing dates - Invalid effective dates - Missing required dates 6. Format and Structure Issues: - Missing mandatory segments - Invalid segment sequence - Wrong element usage - Incorrect qualifiers - Version/release mismatches - Character set problems - Wrong hierarchical structure 7. Trading Partner Information: - Wrong shipper details - Invalid consignee information - Missing bill-to party - Incorrect carrier information - Wrong location codes - Invalid contact details - Missing address information 8. System Integration Challenges: - TMS system incompatibilities - ERP integration problems - Translation errors - Interface failures - Database synchronization - Data transformation errors - Mapping discrepancies 9. Documentation Problems: - Missing required documents - Invalid proof of delivery - Wrong certification details - Incorrect customs information - Missing hazmat documentation - Wrong insurance certificates - Invalid compliance documents These issues can impact shipping and billing accuracy, requiring careful validation and error handling procedures.

EDI 857 - Shipment and Billing Notice

The EDI 857, also known as Shipment and Billing Notice, is a combined document that reports both shipment details and billing information in one transaction.

What is the Purpose of EDI 857 - Shipment and Billing Notice?

The EDI 857 transmits both shipping and billing information, commonly used in the grocery sector. It organizes shipment data into five main categories: order, pack, item, shipment, and pallet details.

What are the important elements of EDI 857 - Shipment and Billing Notice?

The EDI 857 (Shipment and Billing Notice) is a standardized electronic document used to communicate both shipping and billing information in a single transaction. Here are the key elements: 1. Header Information: - Document Reference Number - Transaction Date/Time - Purpose Code - Transaction Type Code - Shipment Date - Currency Code - Bill of Lading Number 2. Partner Information: - Shipper Information (name, ID, address) - Consignee Information - Bill-to Party - Ship-from Location - Ship-to Location - Carrier Information 3. Shipment Details: - Shipment ID - Mode of Transport - Routing Information - Equipment Details - Estimated Delivery Date - Delivery Instructions - Weight Information - Package Count 4. Billing Information: - Invoice Number - Invoice Date - Payment Terms - Total Charges - Tax Information - Freight Charges - Additional Charges - Payment Due Date 5. Product Information: - Line Item Numbers - Product Identifiers - Item Descriptions - Quantities Shipped - Unit Price - Extended Amount - Unit of Measure - Product Weight 6. Charge Details: - Freight Charges - Handling Charges - Insurance Charges - Tax Charges - Fuel Surcharges - Additional Fees - Total Amount Due 7. Reference Numbers: - Purchase Order Numbers - Sales Order Numbers - Customer Reference Numbers - Shipping References - Contract Numbers - Account Numbers 8. Additional Elements: - Special Instructions - Handling Requirements - Hazardous Material Information - Temperature Requirements - Insurance Information - Documentation Requirements 9. Control Segments: - Transaction Set Control Numbers - Segment Counts - Hash Totals - Control Totals The EDI 857 is crucial for combining shipping and billing information into a single document, streamlining the communication process between trading partners.

What are the potential issues with EDI 857 - Shipment and Billing Notice?

Here are the potential issues that can occur with EDI 857 (Shipment and Billing Notice) transmissions: 1. Shipment Information Problems: - Incorrect shipment quantities - Wrong weight information - Invalid package counts - Missing tracking numbers - Wrong carrier details - Incorrect routing information - Invalid delivery schedules 2. Billing Information Issues: - Wrong invoice amounts - Invalid charge calculations - Missing tax information - Incorrect freight charges - Wrong currency codes - Invalid payment terms - Missing discount details 3. Product Detail Problems: - Wrong item numbers - Invalid product descriptions - Missing unit prices - Incorrect extended amounts - Wrong unit of measure - Invalid product weights - Missing commodity codes 4. Reference Number Issues: - Missing bill of lading numbers - Invalid purchase order references - Wrong sales order numbers - Incorrect shipment numbers - Missing invoice numbers - Wrong customer references - Invalid contract numbers 5. Date and Time Problems: - Wrong shipment dates - Invalid delivery dates - Missing invoice dates - Incorrect payment due dates - Wrong processing dates - Invalid effective dates - Missing required dates 6. Format and Structure Issues: - Missing mandatory segments - Invalid segment sequence - Wrong element usage - Incorrect qualifiers - Version/release mismatches - Character set problems - Wrong hierarchical structure 7. Trading Partner Information: - Wrong shipper details - Invalid consignee information - Missing bill-to party - Incorrect carrier information - Wrong location codes - Invalid contact details - Missing address information 8. System Integration Challenges: - TMS system incompatibilities - ERP integration problems - Translation errors - Interface failures - Database synchronization - Data transformation errors - Mapping discrepancies 9. Documentation Problems: - Missing required documents - Invalid proof of delivery - Wrong certification details - Incorrect customs information - Missing hazmat documentation - Wrong insurance certificates - Invalid compliance documents These issues can impact shipping and billing accuracy, requiring careful validation and error handling procedures.

Curious about other types?

Search transaction type

More articles

Our platform is designed to empower businesses of all sizes to work smarter and achieve their goals with confidence.

Oct 27, 2026

A 997 confirms an EDI file parsed cleanly. The order answer comes in the 855. See what the MDN, 997, 999 and 855 each confirm, plus a go-live checklist.

Orange 3D question mark floating above an isometric cream document with a yellow checkmark, on a light blue triangle grid.

Oct 27, 2026

Tips and best practices for building a reliable and efficient task management process.

Orange 3D question mark floating above an isometric cream document with a yellow checkmark, on a light blue triangle grid.

Oct 23, 2026

What EDI 824 Application Advice and 864 Text Message rejections mean, how to read them, and how to fix the invoice, ASN, and PO errors behind them.

Illustration of a stack of documents with a red X on the top page, representing rejected EDI documents.

Oct 23, 2026

Tips and best practices for building a reliable and efficient task management process.

Illustration of a stack of documents with a red X on the top page, representing rejected EDI documents.

Oct 21, 2026

How the EDI 832 Price/Sales Catalog works, segment by segment, plus the item data errors that cause rejections and chargebacks across retailers and distributors.

Isometric illustration of a central item catalog document linked by dashed lines to three retail stores on a teal grid.

Oct 21, 2026

Tips and best practices for building a reliable and efficient task management process.

Isometric illustration of a central item catalog document linked by dashed lines to three retail stores on a teal grid.

Oct 27, 2026

A 997 confirms an EDI file parsed cleanly. The order answer comes in the 855. See what the MDN, 997, 999 and 855 each confirm, plus a go-live checklist.

Orange 3D question mark floating above an isometric cream document with a yellow checkmark, on a light blue triangle grid.

Oct 23, 2026

What EDI 824 Application Advice and 864 Text Message rejections mean, how to read them, and how to fix the invoice, ASN, and PO errors behind them.

Illustration of a stack of documents with a red X on the top page, representing rejected EDI documents.

Oct 21, 2026

How the EDI 832 Price/Sales Catalog works, segment by segment, plus the item data errors that cause rejections and chargebacks across retailers and distributors.

Isometric illustration of a central item catalog document linked by dashed lines to three retail stores on a teal grid.

Oct 19, 2026

How the EDI 845, 844, and 849 work together for distributor contract pricing and chargebacks, with a worked dollar example and the errors that cause denied claims.

Coins linked by a dashed path to a checkmarked green box and shipping boxes, showing payment, approval, and shipment steps.

Let's connect!

Let's connect!

Let's connect!