Relationships with customers, suppliers and partners
Counterparty roles, relationships, contact assignments and segmentation. The person or organization itself is reused by identity.
Bundle → Layer → Finding → Questions Filled
2 bundles · 3 layers · 5 findings · 11 questions
Party roles How one party takes on several commercial roles without new identities.
Commercial roles
Customer, supplier and partner roles over a reused party.
Role over party
Each role references the existing party rather than copying it.
- Which existing party does this commercial role reference?
- Does the same organisation already act as customer, supplier or partner?
- When did each role start and end?
Customer account
The account scope for a group of legal entities.
- Which legal entities does the customer account cover?
- Is the account B2B or B2C, and which profile rules apply?
Contacts and segments Who represents a relationship and how it is classified.
Contact assignments
People assigned to a relationship for a term and purpose.
Contact assignment
A person in a role for a relationship with a term.
- Which person is the contact, and in which role and context?
- For which period is the contact assignment valid?
Segmentation
Classification of relationships with its source.
Segment
A segment as a dated classification with a stated source.
- Which segment applies, and who or what assigned it?
- When was the segment last reviewed?
Relationship scope
Contracts and services that hang off the relationship.
- Which contracts relate to this relationship?
- Would a new role or contract create a duplicate party?
Classifiers Filled
- Family
- Enterprise profiles
- Category
- Enterprise subject
- Entry kind
- subject
- Domain
- EnterpriseCOM
- Industry
- Cross-industry
- Tags
- EM-COM-01W1subjectPartyRelationshipCustomerAccountSupplierRelationshipPartnerRelationshipContactAssignment
What it is Filled
Counterparty roles, relationships, contact assignments and segmentation. The person or organization itself is reused by identity.
Why it exists Filled
Counterparty roles, relationships, contact assignments and segmentation. The person or organization itself is reused by identity.
Distinguishing features Filled
- A commercial role references an existing party and never creates a new person or organisation.
- One organisation may be customer, supplier and partner at once under a single identity.
- A contact assignment has a term and a context, unlike the person record it points to.
- Distinct from sales interactions and contracts, which have their own records and owners.
What robots and AI may and may not do Filled
Must not
- Create a new organisation record after a first purchase by an existing party.
- Merge parties on name or email similarity alone.
- Keep contact assignments active after their term or the person's departure.
- Assign a segment without recording its source and date.
Only with a human decision
- Merging two party records into one.
- Changing the legal entities covered by a group customer account.
May
- Link a new commercial role to the existing party after matching by identity.
- Report all roles, contacts and contracts held by one party.
- Flag likely duplicate parties for review.
Moral aspects Filled
- Contact data about individuals must be kept to its purpose and corrected on request.
- Wrong merges or duplicates can misdirect money, contracts and communications.
Who is affected
- Customers and their contacts
- Suppliers and partners
- Sales and service staff
Owners Filled
Steward
The commercial director who answers for customer, supplier and partner relationships.
Master systems
- CRM
- Order management system
- Service desk
Links to other meta-models Filled
neighbor
- EM-COM-02
- EM-COM-03
- EM-OPS-02
- EM-ORG-02
- EM-PEO-01
references
- WM-ORG-014 - conceptual-candidate
- WM-ORG-015 - conceptual-candidate
- WM-PER-010 - conceptual-candidate
- WM-XCT-024 - conceptual-candidate
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- Identified by the party identifier plus role type and start date; for organisations by LEI or registry number where one exists.
Direct properties not applicable Not applicable
Not applicable
Enterprise record contour: physical properties belong to referenced world models.
Recognition optional Filled
- A relationship record names a party, a role, a term and assigned contacts.
- Often confused with the party record itself or with a single contract.
Capabilities and actions required Filled
- Shows the full commercial footprint of one party across roles.
- Supports deduplication by matching on registry identifiers.
Hazards and failure modes required Filled
- Duplicate identities after onboarding through a different channel.
- Stale contacts that keep receiving commercial or personal data.
- Segments used for decisions without a known source.
Standards and interfaces required Filled
- GLEIF Legal Entity Identifier (ISO 17442) for organisations.
- TM Forum SID party and customer entities.
- OASIS UBL party structures in trade documents.
Context of use required Filled
- Used in CRM, procurement and partner management across the organisation.
- Personal contact data falls under data protection law such as the GDPR.
Sources Filled
- TM Forum SID: party/customer/product/service
- OASIS UBL: trade documents and exchange
- CRM/CPQ/order management practice: stages and source boundaries
- OASIS Universal Business Language Version 2.3 - Checked live (HTTP 200) on 2026-10-07.
- OASIS Universal Business Language (UBL) Technical Committee - Checked live (HTTP 200) on 2026-10-07.
Open questions
- How does one organization become both a customer and a supplier?
- What does a customer account mean for a group of legal entities?
- Where is the boundary between B2B and B2C profiles?
- Установить границу и решение reuse/extend/new по действующим спецификациям.
- Подтвердить semantic crosswalk, права и source mastership.
- Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.
Machine files
Provenance
enterprise research programme · published
Built from: enterprise/models/em-com-01/brief.json, ver-cy/world-models/card-supplements/em-com-01.json
Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.