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

EDIFACT message guide · Planning and inventory

PRODEX Product exchange reconciliation

The UN/EDIFACT message used between partners that lend products to each other to report movements and reconcile outstanding balances.

Sent by
Trading partner in a product exchange agreement
Received by
The other partner
Standard
UN/EDIFACT · Batch message
X12 equivalent
No direct equivalent

What is the EDIFACT PRODEX message?

PRODEX is the UN/EDIFACT product exchange reconciliation message. The directory describes it as a communication between two trading partners with agreements to lend products to each other, providing information about movements of products to and from locations on particular dates, and about the outstanding balance.

Exchange agreements are common for bulk products such as fuels and chemicals, where companies supply each other's customers from the nearest terminal and settle in product rather than cash. PRODEX lets both sides reconcile who owes whom how much.

How the EDIFACT PRODEX message worksDiagram of the UN/EDIFACT PRODEX Product exchange reconciliation message. Trading partner in a product exchange agreement sends it to the other partner. It usually starts the exchange. It is usually followed by INVOIC. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message), DTM (Date/time/period), MEA (Measurements) and NAD (Name and address) and body and segment groups: the required SG1 loop with RFF (Reference) and the required SG2 loop with IMD (Item description). 1 conditional segment groups are listed by their trigger segment.How the EDIFACT PRODEX message worksProduct exchange reconciliation: who sends it, where it fits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangePRODEXSENDERTrading partner in aproduct exchangeagreementRECEIVERThe other partnerCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYINVOICInvoice2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDsUNB … UNZMessage PRODEXUNH … UNTSTART OF MESSAGEBGMBeginning of messageDTMDate/time/periodMEAMeasurementsNADName and addressBODY AND SEGMENT GROUPSMandatory group SG1 · repeats up to 5RFFReferenceMandatory group SG2 · repeats up to 99IMDItem description+ 1 conditional group, starting with:LINBlue box: mandatory segment group. Conditional groups are listed by the trigger segment that starts them; a group is sent only when its data applies.Conditional segments outside groups are not drawn.Structure: mandatory segments and groups in the UN/EDIFACT directory D.21A listing for PRODEX. Your trading partner's implementation guide adds itsown requirements.
How the EDIFACT PRODEX message worksDiagram of the UN/EDIFACT PRODEX Product exchange reconciliation message. Trading partner in a product exchange agreement sends it to the other partner. It usually starts the exchange. It is usually followed by INVOIC. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message), DTM (Date/time/period), MEA (Measurements) and NAD (Name and address) and body and segment groups: the required SG1 loop with RFF (Reference) and the required SG2 loop with IMD (Item description). 1 conditional segment groups are listed by their trigger segment.How the EDIFACT PRODEXmessage worksProduct exchange reconciliation: who sends it,where it fits and what the directory marksmandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangePRODEXSENDERTrading partnerin a productexchangeagreementRECEIVERThe otherpartnerCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYINVOICInvoice2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDs(UNB … UNZ)Message PRODEX (UNH … UNT)START OF MESSAGEBGMBeginning of messageDTMDate/time/periodMEAMeasurementsNADName and addressBODY AND SEGMENT GROUPSMandatory group SG1 · repeats upto 5RFFReferenceMandatory group SG2 · repeats upto 99IMDItem description+ 1 conditional group, starting with:LINBlue box: mandatory segment group. Conditionalgroups are listed by the trigger segment thatstarts them; a group is sent only when its dataapplies. Conditional segments outside groups arenot drawn.Structure: mandatory segments and groups in theUN/EDIFACT directory D.21A listing for PRODEX.Your trading partner's implementation guide adds itsown requirements.

How to read this diagram: the top row shows who sends PRODEX, to whom, and which messages usually come before and after it. The lower part shows what the directory D.21A itself requires: the envelopes around PRODEX and the segments and segment groups it marks mandatory. Conditional groups are listed by their trigger segment rather than drawn in full. This is the directory's minimum, not a trading partner's requirement: a message implementation guide, such as an industry subset or a partner’s own guide, usually makes some conditional groups mandatory, restricts the codes and may use an older directory.

Expand diagram Download SVG

When it is used

  • Reporting product lifted under an exchange agreement
  • Reconciling exchange balances between partners
  • Settling differences at period end

Where it fits in the message flow

This message PRODEX Product exchange reconciliation
Usually followed by INVOIC Invoice

Structure

Mandatory segments in PRODEX (directory D.21A)

In UN/EDIFACT directory D.21A, the PRODEX message has 19 segment positions arranged in 4 segment groups. These are the segments and segment groups marked mandatory at message level, in order; a mandatory group is shown with the segment that starts it. Segments inside conditional groups are needed only when the group is used. This is the directory’s requirement, not your trading partner’s: each partner’s message implementation guide names the directory it uses, often an older one such as D.96A or D.01B where the structure can differ, makes some conditional segments mandatory and restricts the codes.

  • UNH
  • BGM
  • DTM
  • MEA
  • NAD
  • SG1 (RFF)
  • SG2 (IMD)
  • UNT

Practical example

PRODEX in practice

Two fuel distributors exchange product: each lifts diesel at the other's terminal near its customers. At month end each sends the other a PRODEX listing every lifting, the volumes, terminals and dates, and the running balance. The partners agree the net balance and settle the difference in product the following month.

Implementation

Implementation considerations for PRODEX

  • Agree units, temperature correction and measurement bases for bulk volumes.
  • Reconcile each movement, not only the totals.
  • Settle differences on the schedule in the agreement.
  • Keep exchange movements separate from ordinary sales.

How ECOM helps

Automate PRODEX with ECOM

Industry

Manufacturing

Customer schedules, supplier connectivity and shipping integrated with the ERP for manufacturers.

Industry

Trucking and Transportation

Load tenders, responses, status and freight invoices for carriers, brokers and shippers, integrated with the TMS.

Solution

Supply Chain Visibility

Track orders, shipments and invoices across partners and catch exceptions early.

Compare X12 and EDIFACT, or see answers to general questions in the EDI FAQ.

Related messages

Related planning and inventory messages

All 6 planning and inventory messages

Need help with PRODEX?

ECOM maps, tests and monitors EDIFACT messages for your trading partners and integrates them with your ERP.

Request a Demo Contact us