Organizational relationship transactions

The Organizational Relationships transaction is a master data message used to share structured information about organizational hierarchies, relationships, and identifiers between trading partners. It defines how companies, business units, and locations relate to one another—such as parent–subsidiary, company–location, or owner–partner relationships—and includes key data such as names, addresses, contacts, and identifiers like GLNs, DUNS numbers, or internal codes.

The organizational relationship helps ensure that all operational transactions—such as purchase orders (POs), advance ship notices (ASNs), invoices, and chargebacks reference consistent and aligned entities across systems. By centralizing and standardizing this information, it eliminates the need to repeat full organizational details in every transaction, reducing manual entry, minimizing errors, and improving data accuracy throughout the supply chain.

The organizational relationship is sent by the trading partner that owns or manages the authoritative organizational master data—such as a retailer, manufacturer, Marketing Authorization Holder (MAH), distributor, 3PL, or a centralized master data hub. It is received by partners who must align to this structure, including contract manufacturers (CMOs), suppliers, wholesalers, and logistics providers. The direction of the transaction depends on who maintains the master data and who needs to adopt it, and it can flow in either direction based on the partnership context.

The organizational relationship is commonly exchanged during partner onboarding, data alignment efforts, or when there are updates to organizational structures, relationships, or address changes. To ensure smooth and accurate downstream processing, the transaction must follow the organizational relationship format, include all required identifiers and relationship types, and comply with partner-specific implementation guidelines. It must also be kept up to date to reflect current organizational structures.

By implementing the organizational relationship transaction, trading partners can streamline onboarding, improve transaction accuracy, reduce redundant data entry, and maintain alignment across interconnected systems—supporting operational efficiency and regulatory compliance.

Organizational relationship(X12)

Organizational Relationships transaction is a master data message used to share structured information about organizational hierarchies, relationships, and identifiers between trading partners.

Contact your TraceLink Services representative for more information about integrating with this message.

  • Message Type: MPC_ORGANIZATIONAL_RELATIONSHIP
  • X12 Format: ORGANIZATIONALRELATIONSHIP
  • Transform Names:

    • B2B_EDI_X12_816_OrganizationalRelationships_IB_V1

    • B2B_EDI_X12_816_OrganizationalRelationship_OB_V1

    Input Element OccursLengthDescriptionExample
    ISA1…1-Required. ISA interchange envelope.-
     ISA011…12/2Required. Qualifier for authorization control number in ISA02.00
     ISA021…110/10Required. Information used for additional identification or authorization of the interchange sender or the data in the interchange/ 10 spaces a valid entry.-
     ISA031…12/2Required. Qualifier for security information in ISA04.00
     ISA041…110/10Required. Identifies security information about the interchange sender or data.-
     ISA051…12/2

    Required. Interchange sender partner ID qualifier.

    • 01 – Duns (Dun & Bradstreet).
    • 02 – Standard Carrier Alpha Code.
    • 03 – Federal Maritime Commission.
    • 04 – International Air Transport Association.
    • 07 – Global Location Number (GLN).
    • 08 – UCC EDI Communications ID (Comm ID).
    • 09 – X.121 (CCITT).
    • 10 – Department of Defense (DoD) Activity Address Code.
    • 11 – Drug Enforcement Administration identifier.
    • 12 – Telephone Companies.
    • 13 – Used for UCS Transmissions. Includes Area Code and Telephone Number of a Modem.
    • 14 – Duns Plus Suffix.
    • 15 – Petroleum Accountants Society of Canada Company Code.
    • 16 – DINS Number With 4-Character Suffix.
    • 17 – American Bankers Association (ABA) Transit Routing Number (Including Check Digit, 9 Digit).
    • 18 – Association of American Railroads (AAR) Standard Distribution Code.
    • 19 – EDI Council of Australia (EDICA) Communications ID Number (COMM ID).
    • 20 – Health Industry Number (HIN).
    • 21 – Integrated Postsecondary Education Data System.
    • 22 – Federal Interagency Commission on Education, or FICE.
    • 23 – National Center for Education Statistics Common Core of Data 12-Digit Number for Pre-K-Grade 12 Institutes.
    • 24 – The College Board's Admission Testing Program 4-Digit Code of Postsecondary Institutes, or ATP.
    • 25 – 4-Digit Code of Postsecondary Institutions.
    • 26 – Statistics of Canada List of Postsecondary Institutions.
    • 27 – Carrier Identification Number as assigned by Health Care Financing Administration (HCFA).
    • 28 – Fiscal Intermediary Identification Number as assigned by Health Care Financing Administration (HCFA).
    • 29 – Medicare Provider and Supplier Identification Number assigned by Health Care Financing Administration (HCFA).
    • 30 – U.S. Federal Tax Identification Number.
    • 31 – Jurisdiction Identification Number Plus 4 assigned by the International Association of Industrial Accident Boards and Commissions (IAIABC).
    • 32 – U.S. Federal Employer Identification Number (FEIN).
    • 33 – National Association of Insurance Commissioners Company Code (NAIC).
    • 34 – Medicaid Provider and Supplier Identification Number as assigned by individual State Medicaid Agencies in conjunction with Health Care Financing Administration (HCFA).
    • 35 – Statistics Canada Canadian College Student Information System Institution Codes
    • 36 – Statistics Canada University Student Information System Institution Codes.
    • 37 – Society of Property Information Compilers and Analysts (SPICA).
    • 38 – The College Board and ACT, Inc. 6-Digit Code List of Secondary Institutions.
    • AM – Association Mexicana del Codigo de Producto (AMECOP) Communication ID.
    • NR – National Retail Merchants Association (NRMA) - Assigned.
    • SA – User Identification Number as assigned by the Safety and the Fitness Electronic Records (SAFER) System.
    • SN – Standard Address Number.
    • ZZ – Mutually Defined.
    		07
     ISA061…115/15

    Required. Interchange sender identification mapping to:

    • fileSenderNumber with party type defined in ISA05.

    • linkIdentifier

    • x12InterchangeControlEnvelope for sender in X12 control file header.

    		7777776067344
     ISA071…12/2

    Required. Interchange receiver partner ID qualifier.

    • 01 – Duns (Dun & Bradstreet).
    • 02 – Standard Carrier Alpha Code.
    • 03 – Federal Maritime Commission.
    • 04 – International Air Transport Association.
    • 07 – Global Location Number (GLN).
    • 08 – UCC EDI Communications ID (Comm ID).
    • 09 – X.121 (CCITT).
    • 10 – Department of Defense (DoD) Activity Address Code.
    • 11 – Drug Enforcement Administration identifier.
    • 12 – Telephone Companies.
    • 13 – Used for UCS Transmissions. Includes Area Code and Telephone Number of a Modem.
    • 14 – Duns Plus Suffix.
    • 15 – Petroleum Accountants Society of Canada Company Code.
    • 16 – DINS Number With 4-Character Suffix.
    • 17 – American Bankers Association (ABA) Transit Routing Number (Including Check Digit, 9 Digit).
    • 18 – Association of American Railroads (AAR) Standard Distribution Code.
    • 19 – EDI Council of Australia (EDICA) Communications ID Number (COMM ID).
    • 20 – Health Industry Number (HIN).
    • 21 – Integrated Postsecondary Education Data System.
    • 22 – Federal Interagency Commission on Education, or FICE.
    • 23 – National Center for Education Statistics Common Core of Data 12-Digit Number for Pre-K-Grade 12 Institutes.
    • 24 – The College Board's Admission Testing Program 4-Digit Code of Postsecondary Institutes, or ATP.
    • 25 – 4-Digit Code of Postsecondary Institutions.
    • 26 – Statistics of Canada List of Postsecondary Institutions.
    • 27 – Carrier Identification Number as assigned by Health Care Financing Administration (HCFA).
    • 28 – Fiscal Intermediary Identification Number as assigned by Health Care Financing Administration (HCFA).
    • 29 – Medicare Provider and Supplier Identification Number assigned by Health Care Financing Administration (HCFA).
    • 30 – U.S. Federal Tax Identification Number.
    • 31 – Jurisdiction Identification Number Plus 4 assigned by the International Association of Industrial Accident Boards and Commissions (IAIABC).
    • 32 – U.S. Federal Employer Identification Number (FEIN).
    • 33 – National Association of Insurance Commissioners Company Code (NAIC).
    • 34 – Medicaid Provider and Supplier Identification Number as assigned by individual State Medicaid Agencies in conjunction with Health Care Financing Administration (HCFA).
    • 35 – Statistics Canada Canadian College Student Information System Institution Codes
    • 36 – Statistics Canada University Student Information System Institution Codes.
    • 37 – Society of Property Information Compilers and Analysts (SPICA).
    • 38 – The College Board and ACT, Inc. 6-Digit Code List of Secondary Institutions.
    • AM – Association Mexicana del Codigo de Producto (AMECOP) Communication ID.
    • NR – National Retail Merchants Association (NRMA) - Assigned.
    • SA – User Identification Number as assigned by the Safety and the Fitness Electronic Records (SAFER) System.
    • SN – Standard Address Number.
    • ZZ – Mutually Defined.
    		01
     ISA081…115/15

    Required. EDI receiver ID mapping to file control header and to ServiceLinkId.

    Interchange receiver identification mapping to ediInterchangePartyValue for receiver in X12 control file header.

    		888888404358877
     ISA091…16/6Required. Interchange date in 6 char YYMMDD format.231020
     ISA101…14/4Required. Interchange time in 4 char HHMM format.1420
     ISA111…11/1

    Required. This value is dependent on X12 version.

    • Version 4012 and earlier, this is the interchange control standards identifier. Valid value is U.

    • Version 4020 and later, this is the repetition separator, a delimiter that separates repeated occurrences of a data element or composite data structure, which must be different than the data element separator, component separator, and segment terminator."

    		^
     ISA121…15/5Required. Interchange control version number. This could be any X12 version.00501
     ISA131…19/9

    Required. Interchange Control Number mapping to:

    • file control header

    • X12 control file header interchangeControlIdentifier

    		0000000000619827
     ISA141…11/1

    Required. Interchange level acknowledgment requested.

    Valid values:

    • 0 - No acknowledgment requested

    • 1 - Interchange level acknowledgment requested

    		0
     ISA151…11/1

    Required. Indicates whether the interchange is for production, test, or information purposes.

    Valid values:

    • I - Information

    • P - Production data

    • T - Test data

    		P
     ISA161…11/1Required. Component element separator. Delimiter that separates data elements within a composite data structure. Must be different than the data element separator and segment terminator.>
    GS1…*-GS group functional envelope. Child of ISA. Only one GS group expected per interchange.-
     GS011…12/2Required. GS group function code. Valid value is AGShipping instruction Information.AG
     GS021…12/15Required. Application Sender's Code.2222224043588
     GS031…12/15Required. Application Receiver's Code.TRACELINK
     GS041…18/8Required. Current date stamp in 8 char X12 date format YYYYMMDD.20241020
     GS051…14/8Required. Current time stamp in 6 char X12 time format HHMMSS.142000
     GS061…11/9Required. Group Control ID Number.619827
     GS071…11/2

    Required. Responsible Agency Code.

    Valid values:

    • T - Transportation Data Coordinating Committee (TDCC)

    • X - Accredited Standards Committee X12

    		X
     GS081…11/12Required. X12 message version code. This could be any X12 version.005010
    ST1…*-ST transaction set envelope. Child of GS group. Only one ST transaction expected.-
     ST011…13/3Required. Transaction set identifier code.816
     ST021…14/9Required. Transaction set ID number. Counter for each ST segment beginning with 1.0001
     BHT1…1-Required. BGN Beginning Segment.-
      BHT011…14/4

    Required. Identifies the type of hierarchical structure applied in the transaction, defining how hierarchical levels are related to one another.

    Valid values:

    • 0065 - Structure type is company and its operating unit.

    • 0057 - Structure type is supergroup its subgroup and member

    		0065
      BHT021…12/2

    Required. Transaction Set Purpose Code identifying purpose of transaction set.

    • 00 – Original document, create in target.
    • 01 – Cancel order.
    • 02 – Create document or item from message.
    • 03 – Delete document or item.
    • 04 – Changes to document header.
    • 05 – Replace entire document.
    • 06 – Document is a confirmation.
    • 07 – Duplicate transaction.
    • 08 – Document or item status.
    • 11 – Response message.
    • 13 – Request message.
    • 16 – Proposed document or item.
    • 17 – Message canceled and reissued.
    • 22 – Information only.
    • 24 – Document is in draft state.
    • 45 – Followup message.
    • CO – Document or item has been corrected.
    		00
      BHT030…11/80Reference identifier defined for a particular transaction set. The sender's internal number used to identify this transaction set within the sender's application system.8475
      BHT040…18/8Date the original transaction was generated in the sender's business application system, in X12 date format YYYYMMDD.20160129
      BHT050…14/8Transaction time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD.223344
     DTM0...*-Transaction document date or other header level dates.-
      DTM011…13/3

    Required. Date type related to shipment events at port, in date format YYYYMMDD and time format (IDoc/ X12) HHMMSS.

    • 002 - Delivery requested by date

    • 003 - Invoice date

    • 004 - Purchase order date

    • 007 - Effective date

    • 008 - Purchase order received date

    • 009 - Processing date

    • 010 - Shipment requested by date

    • 011 - Date shipped

    • 015 - Promotion start date

    • 016 - Promotion end date

    • 017 - Estimated delivery date

    • 018 - Product availability date

    • 020 - Check date

    • 023 - Promotion order start date

    • 024 - Promotion order end date

    • 025 - Promotion ship start date

    • 026 - Promotion ship end date

    • 035 - Date of delivery document, ASN

    • 036 - Expiration date

    • 037 - Not before shipment date

    • 038 - Not later shipment date

    • 040 - Status (After and Including)

    • 041 - Status (Prior and Including)

    • 050 - Date goods receipt posted (received into available inventory)

    • 058 - Customs Clearance date

    • 061 - Cancel by date

    • 067 - Current scheduled delivery date

    • 068 - Scheduled shipment date

    • 069 - Date of promised delivery

    • 070 - Delivery schedule date

    • 074 - Requested delivery date

    • 079 - Promised for shipment date

    • 090 - Report start date

    • 091 - Report end date

    • 092 - Contract effective date

    • 093 - Contract expiration date

    • 094 - Manufacturing date

    • 097 - Transactional date creation

    • 102 - Date goods issue posted

    • 133 - Account receivable date

    • 139 - Estimated

    • 140 - Actual date

    • 146 - Closing date

    • 161 - Loaded on vessel date

    • 166 - Message date

    • 168 - Release date

    • 184 - Inventory Update date

    • 188 - Credit advice date

    • 189 - Debit advise date

    • 196 - Date Start

    • 197 - End date

    • 208 - Lot expiration date

    • 311 - Latest receiving / cutoff date

    • 324 - Returned date

    • 369 - Estimated Departure Date

    • 370 - Actual Departure date

    • 371 - Estimated Arrival date

    • 372 - Actual arrival date

    • 472 - Date services rendered

    • 510 - Date packed

    • 512 - Warranty date

    • 514 - Transfer date

    • 649 - Document due date

    • 813 - Customs entry date

    • 814 - Payment due date

    • 922 - Date of original receipt

    • 938 - Order date

    • 964 - Billing date

    • 999 - Document date

    • AAG - Due date

    • VLU - Validity date

    		999
      DTM020…18/8Date defined by referenced date type in date format YYYY-MM-DD. Transform will pass thru whatever it finds in IDoc date and time fields.20241215
      DTM030…14/8Time expressed in 24-hour clock time as follows.-
      DTM040…12/2Time zone for referenced dates.ES
      DTM050…12/3

    Describes the date format, time format, or date and time period format type.

    • D6 - YYMMDD

    • D8 - CCYYMMDD

    • DD - DAYOFMONTH

    • DT - CCYYMMDDHHMM

    • MD - MMDD

    • T - MMDDYY

    • TM - HHMM

    • TQ - MMYY

    • TS - HHMMSS

    • TT - MMDDYY

    • YM - YYMM

    		DT
      DTM060…11/35Describes the date format, time format, or date and time period.-
     REF(1)0…100-Reference segment for mapping to the transaction reference identifiers.-
      REF011…12/3Required. Reference identification qualifier for the contract clas. Valid values include: CT
      REF020…11/80Reference identifier value: 123456
      REF030…11/80Description defined by qualifier code in REF02sub-340B
     REF(2)0…30-Reference segment for mapping to the transaction references.-
      REF011…12/3Required. Reference identification qualifier for the contract clas. Valid values include: IA = Internal Vendor numberIA
      REF020…11/80Reference identifier value: 123456
      REF030…11/80Description defined by qualifier code in REF02-
     N1 Loop1…*-N1 segment loop at header for party address and reference information.-
      N11…1-Required. Party identification-
       N1011…12/3Required. Entity qualifier for the Sender or Receiver party identifier and address information. Valid values include: - FR = Sender - TO = Receiver SU
       N1020…11/60Name Pharma customer
       N1030…11/2Identifier code qualifier. Valid values include: 1 = DUNS 2 = SCAC 9 = DUNS+4 11 = Drug Enforcement Agency registration number 21 = Health Industry Number 91 = Company identifier 92 = Company location identifier UL = Global Location NumberUL
       N1040…12/80Party identifier as qualified by N103 mapping to companyIdentifierValue.3333331013655
      N20…2-N2: Additional names: Child of customer party N1 name segment., we do support one iteration of N2-
       N2011…11/60Required. Additional name 2Pharma name2
       N2020…11/60Additional name 2Pharma name2
      N30…2-N3: Address: Child of customer party N1 name segment.-
       N3011…11/55Required. Street address 1555 Neelan Road
       N3020…11/55Street address 2Suite 123
      N40…1-N4: Geographic Location. Child of customer party N1 name segment.-
       N4010…12/30City nameSacramento
       N4020…12/2State or province code. Code (Standard state/province) as defined by appropriate government agencyCA
       N4030…13/15Postal code. Code defining international postal zone code excluding punctuation and blanks.95833
       N4040…12/3Country codeUS
       N4050…11/2Type of locationCA
       N4060…11/30Specific location95833
       N4070…11/3Country subdivisionUS
      REF(1)0…12-Reference segment for mapping to the transaction reference identifiers-
       REF011…12/3Required. Reference identification qualifier for the contract clas. Valid values include: CT
       REF020…11/80Reference identifier value: 123456
       REF030…11/80Description defined by qualifier code in REF02sub-340B
      REF (2)0…12-Reference segment for mapping to the transaction references.-
       REF011…12/3Required. Reference identifier qualifier. Code identifies the type of ID number sent in REF02. For Wal-Mart, qualifier IA is required for their internal vendor number. Valid values include: IA = Internal Vendor numberIA
       REF020…11/80Reference identifier value: 123456
       REF030…11/80Description defined by qualifier code in REF02-
      PER0…3-PER segment explains about contact information for party business or location-
       PER011…12/2Required. Contact type. Valid values include: - IC = Information contact - FC = Forwarder contact - RP = Responsible contactIC
       PER020…11/60Contact nameGrame Smith
       PER030…12/2Communication qualifierTE
       PER040…11/2048Contact phone number'897654
       PER050…12/2Communication qualifierEM
       PER060…11/2048Contact email addressgsmith@gmail.com
     HL Loop1…*-Line item loop start for Organizational relationship, referring a line number in a transaction set-
      HL1…1-Required. Organizational hierarchical level for to denote its reporting level-
       HL011…11/12Required. Hierarchical level counter. Increment each instance by 1 from the last.1
       HL020…11/12Hierarchical identifier for the parent level of the curreent level. If there is no parent level this value would be the same as the current hierarchicalIdentifier.2
       HL031…11/2Required. Code identifying the hierarchical level of the hierarchical group in the organization . Valid values include: - 35 = Company or corporate level - BE = Business entity level - 24 = Super group level - 36 = Operating unit, such as store, warehouse35
       HL040…11/1Code indicating if there are child data segments subordinate to the current HL level. Valid values: - 1 = a child line item segment follows - 0 = no child line item segment follows1
      N1 Loop1…*-N1 segment loop at items for organizational entities relationships and address and reference information.-
       N11…1-Required. Party identification-
        N1011…12/3Required. Entity qualifier for the Sender or Receiver party identifier and address information. Valid values include: - CQ = Sender - TO = Receiver SU
        N1020…11/60Name Pharma customer
        N1030…11/2Identifier code qualifier. Valid values include: 1 = DUNS 2 = SCAC 9 = DUNS+4 11 = Drug Enforcement Agency registration number 21 = Health Industry Number 91 = Company identifier 92 = Company location identifier UL = Global Location NumberUL
        N1040…12/80Party identifier as qualified by N103 mapping to companyIdentifierValue.3333331013655
       N20…2-N2: Additional names: Child of customer party N1 name segment., we do support one iteration of N2-
        N2011…11/60Required. Additional name 2Pharma name2
        N2020…11/60Additional name 2Pharma name2
       N30…2-N3: Address: Child of customer party N1 name segment.-
        N3011…11/55Required. Street address 1555 Neelan Road
        N3020…11/55Street address 2Suite 123
       N40…1-N4: Geographic Location. Child of customer party N1 name segment.-
        N4010…12/30City nameSacramento
        N4020…12/2State or province code. Code (Standard state/province) as defined by appropriate government agencyCA
        N4030…13/15Postal code. Code defining international postal zone code excluding punctuation and blanks.95833
        N4040…12/3Country codeUS
        N4050…11/2Type of locationCA
        N4060…11/30Specific location95833
        N4070…11/3Country subdivisionUS
       PER0…3-PER segment explains about contact information for party business or location-
        PER011…12/2Required. Contact type. Valid values include: - IC = Information contact - FC = Forwarder contact - RP = Responsible contactIC
        PER020…11/60Contact nameGrame Smith
        PER030…12/2Communication qualifierTE
        PER040…11/2048Contact phone number'897654
        PER050…12/2Communication qualifierEM
        PER060…11/2048Contact email addressgsmith@gmail.com
       REF(1)0…100-Reference segment for mapping to the transaction reference identifiers-
        REF011…12/3Required. Reference identification qualifier for the contract clas. Valid values include: CT
        REF020…11/80Reference identifier value: 123456
        REF030…11/80Description defined by qualifier code in REF02sub-340B
       REF(2)0…30-Reference segment for mapping to the transaction references.-
        REF011…12/3Required. Reference identification qualifier for the contract clas. Valid values include: - DNS = Duns plus sufix number - AEM = Distribution Center Number - ST = Store numberDNS
        REF020…11/80Reference identifier value: 123456
        REF030…11/80Description defined by qualifier code in REF02-
       DTM0...*-Dates, Effective date of organization entity data changes-
        DTM011…13/3Required. Date type related to shipment events at port, in date format YYYYMMDD and time format (IDoc/ X12) HHMMSS. Valid values include: - 007 = Effective date007
        DTM020…18/8Date defined by referenced date type in date format YYYY-MM-DD. Transform will pass thru whatever it finds in IDoc date and time fields.20241215
        DTM030…14/8Time expressed in 24-hour clock time as follows-
        DTM040…12/2Time zone for referenced datesES
        DTM050…12/3Describes the date format, time format, or date and time period format type. Valid values are: - DT = CCYYMMDDHHMM - T = MMDDYYDT
        DTM060…11/35Describes the date format, time format, or date and time period.-
       ASI0…1-Indicates type of action to be taken or taken on the organization data-
        ASI011...1'1/2Required. Identifies the business action to be performed or that has been performed on an entity, valid values inlcude: - 1 = Adding - 2 = Update the record in master data. - 3 = Deleting the record 1
        ASI021...1'3/3Required. Specifies the type or scope of maintenance applied when performing the action, such as full replacement or selective update of entity data, valid values: - 001 = Existing item record is being updated - 002 = This item should no longer exist / be used - 003 = This is a brand-new item — create it001
        ASI030...1'3/3Indicates the reason or justification for the action or status change of the entity. Note: No sample values were found in the guidelines.-
    SE1…1-Required. ST … SE transaction set trailer envelope. Child of GS group. Only one ST transaction expected.-
     SE011…11/10Required. Total count of segments in ST … SE transaction set including ST and SE segments.10
     SE021…14/9Required. Transaction set control number0001
    GE1…1-Required. GS … GE functional group trailer envelope. Child of ISA interchange. Only one GS group expected.-
     GE011…11/6Required. Number of transaction sets in functional group5
     GE021…11/9Required. Functional group control number619827
    IEA1…1-Required. ISA … IEA interchange control trailer envelope. Only one interchange expected per transmission.-
     IEA011…11/5Required. Number of functional groups in interchange.1
     IEA021…19/9Required. Interchange control number0000000000619827