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 · Master data

PARTIN Party information

The UN/EDIFACT message used to exchange basic information about parties and locations, such as addresses, contacts and operational details.

Sent by
Any trading partner
Received by
Trading partner that maintains the party data
Standard
UN/EDIFACT · Batch message
X12 equivalent
No direct equivalent

What is the EDIFACT PARTIN message?

PARTIN is the UN/EDIFACT party information message. The directory defines it as a message for transmitting basic information about locations and the related operational, administrative, financial, manufacturing, registration and trading data.

Party data includes names, addresses, global location numbers, contacts, bank details, delivery and receiving hours and tax registrations. Exchanging it electronically keeps partners' master files consistent, which helps prevent misdirected deliveries, rejected invoices and payments sent to outdated accounts. Each party is usually identified by a global location number or another agreed code, which other messages then reference.

How the EDIFACT PARTIN message worksDiagram of the UN/EDIFACT PARTIN Party information message. Any trading partner sends it to trading partner that maintains the party data. It usually starts the exchange. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message) and DTM (Date/time/period) and body and segment groups: UNS (Section control). 3 conditional segment groups are listed by their trigger segment.How the EDIFACT PARTIN message worksParty information: who sends it, where it fits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangePARTINSENDERAny trading partnerRECEIVERTrading partner thatmaintains the partydataCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYNo business reply expected2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDsUNB … UNZMessage PARTINUNH … UNTSTART OF MESSAGEBGMBeginning of messageDTMDate/time/periodBODY AND SEGMENT GROUPSUNSSection control+ 3 conditional groups, starting with:RFFNADBlue 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 PARTIN. Your trading partner's implementation guide adds itsown requirements.
How the EDIFACT PARTIN message worksDiagram of the UN/EDIFACT PARTIN Party information message. Any trading partner sends it to trading partner that maintains the party data. It usually starts the exchange. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message) and DTM (Date/time/period) and body and segment groups: UNS (Section control). 3 conditional segment groups are listed by their trigger segment.How the EDIFACT PARTINmessage worksParty information: who sends it, where it fitsand what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangePARTINSENDERAny tradingpartnerRECEIVERTrading partnerthat maintainsthe party dataCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYNo business reply expected2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDs(UNB … UNZ)Message PARTIN (UNH … UNT)START OF MESSAGEBGMBeginning of messageDTMDate/time/periodBODY AND SEGMENT GROUPSUNSSection control+ 3 conditional groups, starting with:RFFNADBlue 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 PARTIN.Your trading partner's implementation guide adds itsown requirements.

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

  • Setting up a new trading partner relationship
  • Announcing new or changed delivery locations
  • Updating bank or tax details

Where it fits in the message flow

This message PARTIN Party information

No other message routinely comes directly before or after PARTIN; it is exchanged when the business event occurs. If the partners agree, the receiver confirms each interchange with a CONTRL syntax and service report.

Structure

Mandatory segments in PARTIN (directory D.21A)

In UN/EDIFACT directory D.21A, the PARTIN message has 50 segment positions arranged in 15 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
  • UNS
  • UNT

Practical example

PARTIN in practice

A grocery retailer opens three stores and a new distribution center. It sends its suppliers a PARTIN for each location with the GLN, address, receiving hours, dock restrictions and contacts. The suppliers add the locations to their customer master, so the first orders to the new stores are delivered correctly.

Implementation

Implementation considerations for PARTIN

  • Use location identifiers such as GLNs consistently with orders and invoices.
  • Verify bank detail changes through a second channel to prevent fraud.
  • Send changes with the date from which they take effect.
  • Decide which party owns each piece of master data.

How ECOM helps

Automate PARTIN with ECOM

Industry

Retail

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

Solution

Trading Partner Onboarding

EDI certification and automation onboarding for customers, suppliers and carriers, by whichever method each partner can support.

Solution

B2B Integration

Connect every customer, supplier, carrier and bank across EDI, API, file and portal channels.

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

Related messages

Related master data messages

All 11 master data messages

Need help with PARTIN?

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

Request a Demo Contact us