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 · Catalogs and pricing

EDI 883 Market Development Fund Allocation

The X12 document a manufacturer uses to tell a broker, retailer or wholesaler how market development funds are allocated for a program.

Sent by
Manufacturer
Received by
Broker, retailer or wholesaler
Standard
ANSI ASC X12

What is an EDI 883?

The EDI 883 Market Development Fund Allocation is the ANSI X12 transaction set a manufacturer initiates to inform a broker, retailer or wholesaler how funds should be allocated in a market development program. Market development funds pay for activities such as advertising, displays and promotions that help sell the manufacturer's products.

The 883 states the program, the participating accounts, the products covered, the funding amounts or rates and the dates. The settlement of what was actually spent and earned follows in an 884.

How the EDI 883 worksDiagram of the EDI 883 Market Development Fund Allocation. Manufacturer sends it to broker, retailer or wholesaler. It usually starts the exchange. It is usually followed by 884 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BMA (Beginning Segment for Market Development Fund Allocation), N1 (Party Identification) and G62 (Date/Time). 3 optional loops are listed by their first segment.How the EDI 883 worksMarket Development Fund Allocation: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 883SENDERManufacturerRECEIVERBroker, retailer orwholesaler997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY884Market Development FundSettlement997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code DFGS … GETransaction set 883ST … SEHEADINGBMABeginning Segment for Market Development FundAllocationN1Party IdentificationG62Date/TimeDETAIL+ 3 optional loops, starting with:LINN1LXBlue 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 883. Your trading partner's implementation guide adds its own requirements.
How the EDI 883 worksDiagram of the EDI 883 Market Development Fund Allocation. Manufacturer sends it to broker, retailer or wholesaler. It usually starts the exchange. It is usually followed by 884 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BMA (Beginning Segment for Market Development Fund Allocation), N1 (Party Identification) and G62 (Date/Time). 3 optional loops are listed by their first segment.How the EDI 883 worksMarket Development Fund Allocation: whosends it, where it fits and what the standardmarks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 883SENDERManufacturerRECEIVERBroker, retaileror wholesaler997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY884Market Development Fund Settlement997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code DF (GS … GE)Transaction set 883 (ST … SE)HEADINGBMABeginning Segment forMarket Development FundAllocationN1Party IdentificationG62Date/TimeDETAIL+ 3 optional loops, starting with:LINN1LXBlue 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 883. Your trading partner'simplementation guide adds its own requirements.

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

  • Allocating marketing funds to retail accounts
  • Announcing the terms of a market development program
  • Changing allocations during a program

Where it fits in the document flow

This document 883 Market Development Fund Allocation
Usually followed by 884 Market Development Fund Settlement997 Functional Acknowledgment

Structure

Mandatory segments in the 883 (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
  • BMA
  • N1
  • G62
  • LIN
  • UIT
  • LX
  • SE

Practical example

The 883 in practice

A beverage company sets aside funds for a summer display program. It sends each participating grocery wholesaler an 883 stating the program dates, the products covered and the amount per case available to each account. The wholesalers plan the displays and later settle the earned funds with an 884.

Implementation

Implementation considerations for the 883

  • Give each program a unique identifier that settlement documents can reference.
  • State funding rates and caps clearly to avoid disputes at settlement.
  • Coordinate fund allocations with promotion announcements (889).
  • Track allocations against settlements to know what remains open.

How ECOM helps

Automate the 883 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.

Industry

Food and Beverage

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

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

Related transactions

Related catalogs and pricing documents

All 21 catalogs and pricing documents

Need help with the EDI 883?

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

Request a Demo Contact us