972-836-7750 Request a demo Talk to an expert
Talk to an expert Request a demo Call sales 972-836-7750

X12 transaction guide · Finance

EDI 882 Direct Store Delivery Summary Information

The X12 document a direct store delivery vendor uses to summarize reconciled deliveries, returns and adjustments and request payment.

Sent by
Direct store delivery vendor
Received by
Retailer's accounts payable
Standard
ANSI ASC X12

What is an EDI 882?

The EDI 882 Direct Store Delivery Summary Information is the ANSI X12 transaction set used to summarize detailed delivery, return and adjustment information that was already reconciled at the time of delivery in a retail direct store delivery (DSD) environment, and to request payment for the products delivered.

The 882 carries only summary totals by delivery, without product detail; the detail was exchanged and agreed at the store, typically through 894 delivery/return base records and 895 acknowledgments. It lets the retailer's head office pay for many store deliveries from one summary.

How the EDI 882 worksDiagram of the EDI 882 Direct Store Delivery Summary Information. Direct store delivery vendor sends it to retailer's accounts payable. It usually follows 895. It is usually followed by 820 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: G47 (Statement Identification) and the required 0100 loop with N1 (Party Identification), detail: the required 0200 loop with G48 (Statement/Invoice Identification) and G33 (Total Dollars Summary) and summary: G49 (Statement Total). 1 optional loops are listed by their first segment.How the EDI 882 worksDirect Store Delivery Summary Information: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWS895Delivery/ReturnAcknowledgment orAdjustmentEDI 882SENDERDirect store deliveryvendorRECEIVERRetailer's accountspayable997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY820PaymentOrder/Remittance Advice997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code IGGS … GETransaction set 882ST … SEHEADINGG47Statement IdentificationRequired loop 0100 · repeats up to10N1Party IdentificationDETAILRequired loop 0200 · repeats up to9,999G48Statement/InvoiceIdentificationG33Total Dollars Summary+ 1 optional loop, starting with:G72SUMMARYG49Statement TotalBlue box: required loop. Optional loops are listed by the segment that starts them; when a loop is used, that first segment is required. Optional segmentsoutside loops are not drawn.Structure: required segments and loops in the X12 008010 listing for the 882. Your trading partner's implementation guide adds its own requirements.
How the EDI 882 worksDiagram of the EDI 882 Direct Store Delivery Summary Information. Direct store delivery vendor sends it to retailer's accounts payable. It usually follows 895. It is usually followed by 820 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: G47 (Statement Identification) and the required 0100 loop with N1 (Party Identification), detail: the required 0200 loop with G48 (Statement/Invoice Identification) and G33 (Total Dollars Summary) and summary: G49 (Statement Total). 1 optional loops are listed by their first segment.How the EDI 882 worksDirect Store Delivery Summary Information:who sends it, where it fits and what thestandard marks required1 WHERE IT FITSUSUALLY FOLLOWS895Delivery/Return Acknowledgment orAdjustmentEDI 882SENDERDirect storedelivery vendorRECEIVERRetailer'saccountspayable997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY820Payment Order/Remittance Advice997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code IG (GS … GE)Transaction set 882 (ST … SE)HEADINGG47Statement IdentificationRequired loop 0100 · repeats upto 10N1Party IdentificationDETAILRequired loop 0200 · repeats upto 9,999G48Statement/InvoiceIdentificationG33Total Dollars Summary+ 1 optional loop, starting with:G72SUMMARYG49Statement TotalBlue box: required loop. Optional loops are listedby the segment that starts them; when a loop isused, that first segment is required. Optionalsegments outside loops are not drawn.Structure: required segments and loops in the X12008010 listing for the 882. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 882, to whom, and which documents usually come before and after it. The lower part shows what X12 release 008010 itself requires: the envelopes around the 882 and the segments and loops the standard marks as required, area by area. Optional loops are listed by the segment that starts them rather than drawn in full. This is the standard's minimum, not a trading partner's requirement: each partner's implementation guide usually makes some optional loops mandatory, restricts the codes and may use a different release.

Expand diagram Download SVG

When it is used

  • Requesting payment for reconciled store deliveries
  • Summarizing deliveries, returns and adjustments for a period
  • Supporting head-office settlement of DSD invoices

Where it fits in the document flow

Usually follows 895 Delivery/Return Acknowledgment or Adjustment
This document 882 Direct Store Delivery Summary Information
Usually followed by 820 Payment Order/Remittance Advice997 Functional Acknowledgment

Structure

Mandatory segments in the 882 (X12 release 008010)

The segments X12 release 008010 marks as mandatory at their level, in order. Segments inside optional loops are needed only when the loop is used. This is the standard's requirement, not your trading partner's: each partner's implementation guide names the release it uses, adds the optional segments it requires and restricts the values. The requirement status comes from one published X12 reference listing and has not been checked against a second source.

  • ST
  • G47
  • N1
  • G48
  • G72
  • G33
  • G49
  • SE

Practical example

The 882 in practice

A bakery delivers bread to 40 supermarkets daily, and each delivery is checked in and agreed at the store's back door. At the end of the week the bakery sends the chain's head office an 882 summarizing the delivery tickets, returns of stale product and adjustments, with totals per store. Accounts payable matches the summary to the store receiving records and pays the bakery.

Implementation

Implementation considerations for the 882

  • Make sure each summarized delivery was reconciled at the store, since the 882 has no item detail.
  • Reference the delivery ticket numbers the stores recorded.
  • Agree on the summary period and payment terms with the retailer.
  • Keep returns and adjustments separate from deliveries in the totals.

How ECOM helps

Automate the 882 with ECOM

Industry

Retail

Retail and eCommerce EDI for suppliers and retailers, from purchase order to payment, with compliance built in.

Industry

Food and Beverage

Grocery and foodservice EDI for food and beverage manufacturers, with lot, date and inventory data.

Solution

Financial Document Automation

Automate invoices, remittances, payment files and bank statements from capture to posting.

More general questions about EDI are answered in the EDI FAQ.

Related transactions

Related finance documents

All 58 finance documents

Need help with the EDI 882?

ECOM maps, tests and monitors X12 documents for your trading partners and integrates them with your ERP.

Request a Demo Contact us