TRANXACT.AI मदत

Parties: one record behind every customer, supplier and worker

Every customer, customer contact, supplier, worker, candidate, faculty member, clinical provider, student and patient has a party behind it, holding the roles it plays, its names, identifiers, contact points, addresses, relationships, owner and source.

Nothing changes on the customer, supplier or HR screens: a record made there gets its party and role automatically, renaming it renames the party, and deleting it ends the role. Existing records were each given a party of their own when 20261031 was installed. Nothing is merged automatically; two parties that are the same person or company are joined by a data steward.

  • Platform › Master Data Management › Parties & Roles › Parties lists every party (PTY-000001…) with the roles it holds. Party 360 opens the party's page: What this party is lists every role with the record it is — STU-000001 Grace Mbeki, EMP-0003 Dr. Anita Shah — one click from that record, and its 360° view also shows what its records say about other parties, its relationships, who is accountable, and parties that may be the same one.
  • Every record a party can be — customer, contact, supplier, employee, candidate, faculty member, provider, student, patient — shows Who this is at the top of its own 360° view: its party, and what else that party is (the customer who is also a supplier). Every link adds a step to the trail at the top of the page, named by number and name, so Back to … returns to where you started.
  • Join: a party suggests others with the same name, identifier, phone or e-mail under May be the same party. Open each to compare; a data steward presses Join into this party. The other party's roles and details move here, it is kept marked merged so links to it still lead here, and the join is in the audit log. Nothing is joined automatically.
  • Who may: the Data Steward role holds the party screens and Join; a Compliance Officer role reads Regional Compliance and keeps pack bindings and applicability assessments. Any of these screens can be granted to any role on Platform › Access & Security › Roles.
  • Party Roles: a party can be a customer, a supplier and a partner at once, each role with its own status and dates; a supplier blocked for payment is still a customer in good standing. Customer, supplier, worker and the other record roles come from their own screens; Guardian, Authority, Partner, Referrer, Legal entity and Beneficial owner are added here. A record’s own role is ended (status Ended), not deleted.
  • Relationships: employs, contact of, subsidiary of (with a percentage), owns a share of, branch of, signs for, guardian of, referred, affiliate of, each dated.
  • Platform › Master Data Management › Party Details: names in any script (Arabic, Japanese, Chinese are kept as written, with language and script), identifiers by scheme (a sensitive one, such as an SSN, PAN, national ID or passport, keeps only its last four characters once saved, and a leading zero is never lost), contact points with marketing consent per channel, addresses from the Address Book (a protected address is never shown through the party), and websites and social profiles with whether they are verified.
  • Platform › Master Data Management › Ownership & Provenance: Record Owners keeps exactly one accountable owner per record and responsibility; Transfer ends the current owner and starts the next, so earlier owners stay on record. Acquisition says how a record was won (referral, campaign, partner) separately from how it was loaded (import, API, migration). Record Sources keeps the key a record has in each other system and which source is most authoritative.
  • Privacy: a patient’s or student’s party carries no name and is not listed, counted or opened by anybody who may not open patients or students on their own screens.

The Address Book (Platform › Configuration › Classification) also gained optional structured parts: kind (physical, PO box, mailing, site, registered), house or building number, street, PO box, subdivision code, and the language and script of the local-script address.