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 881 Manufacturer Coupon Redemption Detail

The X12 document a manufacturer or agent uses to send coupon redemption detail for reconciling a distributor's or clearinghouse's invoice.

Sent by
Manufacturer or its agent
Received by
Distributor or distributor's clearinghouse
Standard
ANSI ASC X12

What is an EDI 881?

The EDI 881 Manufacturer Coupon Redemption Detail is the ANSI X12 transaction set a manufacturer or its agent uses to communicate coupon redemption detail and the associated store tag detail needed to reconcile a distributor's or clearinghouse's invoice.

When a retailer or distributor redeems coupons, it bills the manufacturer for the face value plus handling. The 881 gives the counterparty the detail of what the manufacturer accepted, coupon by coupon or store by store, so differences between the invoice and the payment can be explained and resolved.

How the EDI 881 worksDiagram of the EDI 881 Manufacturer Coupon Redemption Detail. Manufacturer or its agent sends it to distributor or distributor's clearinghouse. It usually starts the exchange. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BGN (Beginning Segment) and the required 0100 loop with N1 (Party Identification), detail: the required 0200 loop with G01 (Invoice Identification), QTY (Quantity Information), AMT (Monetary Amount Information) and the required 0220 loop with N1 (Party Identification) and summary: the required 0300 loop with LX (Transaction Set Line Number), QTY (Quantity Information) and AMT (Monetary Amount Information). 2 optional loops are listed by their first segment.How the EDI 881 worksManufacturer Coupon Redemption Detail: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 881SENDERManufacturer or itsagentRECEIVERDistributor ordistributor'sclearinghouse997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code CNGS … GETransaction set 881ST … SEHEADINGBGNBeginning SegmentRequired loop 0100 · repeats up to5N1Party IdentificationDETAILRequired loop 0200 · repeatsmany timesG01Invoice IdentificationQTYQuantity InformationAMTMonetary AmountInformationRequired loop 0220 · repeatsmany timesN1Party Identification+ 2 optional loops, starting with:G72REFSUMMARYRequired loop 0300 · repeats up to1LXTransaction Set LineNumberQTYQuantity InformationAMTMonetary AmountInformationBlue 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 881. Your trading partner's implementation guide adds its own requirements.
How the EDI 881 worksDiagram of the EDI 881 Manufacturer Coupon Redemption Detail. Manufacturer or its agent sends it to distributor or distributor's clearinghouse. It usually starts the exchange. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BGN (Beginning Segment) and the required 0100 loop with N1 (Party Identification), detail: the required 0200 loop with G01 (Invoice Identification), QTY (Quantity Information), AMT (Monetary Amount Information) and the required 0220 loop with N1 (Party Identification) and summary: the required 0300 loop with LX (Transaction Set Line Number), QTY (Quantity Information) and AMT (Monetary Amount Information). 2 optional loops are listed by their first segment.How the EDI 881 worksManufacturer Coupon Redemption Detail: whosends it, where it fits and what the standardmarks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 881SENDERManufacturer orits agentRECEIVERDistributor ordistributor'sclearinghouse997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code CN (GS … GE)Transaction set 881 (ST … SE)HEADINGBGNBeginning SegmentRequired loop 0100 · repeats upto 5N1Party IdentificationDETAILRequired loop 0200 · repeatsmany timesG01Invoice IdentificationQTYQuantity InformationAMTMonetary AmountInformationRequired loop 0220 · repeatsmany timesN1Party Identification+ 2 optional loops, starting with:G72REFSUMMARYRequired loop 0300 · repeats upto 1LXTransaction Set LineNumberQTYQuantity InformationAMTMonetary AmountInformationBlue 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 881. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 881, 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 881 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

  • Reconciling coupon redemption invoices
  • Reporting accepted and rejected coupons by store
  • Explaining differences between invoiced and paid amounts

Where it fits in the document flow

This document 881 Manufacturer Coupon Redemption Detail
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 881 (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
  • BGN
  • N1
  • G01
  • QTY
  • AMT
  • G72
  • REF
  • LQ
  • LX
  • SE

Practical example

The 881 in practice

A clearinghouse invoices a cereal manufacturer for coupons redeemed at a supermarket chain's stores. The manufacturer's redemption agent counts and validates the coupons, then sends the clearinghouse an 881 with the counts and amounts accepted by coupon and store and the coupons rejected as expired or misredeemed. The clearinghouse reconciles the payment to its invoice and passes the detail to the retailer.

Implementation

Implementation considerations for the 881

  • Reference the invoice being reconciled and the store tags used to batch coupons.
  • Use agreed reason codes for rejected coupons so retailers can address misredemption.
  • Align coupon identifiers with the coupon notification (887) data.
  • Plan for large volumes of detail lines during promotional periods.

How ECOM helps

Automate the 881 with ECOM

Industry

Consumer Goods

Retail, distributor, marketplace and direct-channel integration for consumer brands.

Industry

Retail

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

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 881?

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

Request a Demo Contact us