Customers

A customer who licensed three modules used to get three counterparty lists and expected one: Invoice & Billing and Offers each owned a customers table, CRM Lite its own companies, Procurement its own suppliers, and nothing reconciled them. PS-11 holds the party master record and, deliberately, nothing else — no pipeline, no activities, no notes. Parties are kinds: a customer is someone you sell to, a supplier someone you buy from, and matching never crosses the two. Modules resolve a party by external reference or by matching attributes, and merges keep the losing record resolvable so old links never break.

Responsibilities

• Party master records by kind, with customers and suppliers kept apart
• Resolve-or-create by external reference or matching attributes
• External references per source module, so each keeps its own ids
• Merge with the losing record left resolvable; archive and GDPR erase
• The one counterparty list a multi-module stack agrees on

API surface

• POST /api/parties/resolve
• GET/POST /api/parties · GET/PATCH /api/parties/:id
• POST /api/parties/:id/merge · /archive · /erase
• GET/POST /api/parties/:id/refs

CONSUMED BY MOD-04 Invoice & Billing, MOD-13 Offers, MOD-10 CRM Lite, MOD-06 Procurement. A Platform Service never depends on a Business Module.