Customer / parties setup

Goal

Configure shared party policies that control customer (and supplier) create/archive behavior.

Who it is for

Tenant admins with party.admin (save options and catalogs). Viewing settings may also be allowed with party.view.

Preconditions

• You can open Directory → Parties setup.
• Catalog rows (relationship types, inactive reasons) should exist before you require inactive reasons on archive.

Steps

1. Open Directory → Parties setup (subtitle: Matching, required fields, numbering, and option catalogs.).
2. On Options:
   • Duplicate detection — Duplicate parties: Allow / Warn / Block; match persons on email/phone; match organizations on tax ID / registration number / email; fuzzy name match; reuse existing party on connector match.
   • Required fields — Require email for persons; tax ID for organizations; phone; billing address; party code when numbering is manual.
   • Numbering — Party code numbering: Manual or Auto (document sequences).
   • Archive — Require an inactive reason when archiving; optional default relationship type.
3. Save — toast Party options saved.
4. Tab Relationship types — add/update/deactivate how parties relate to you.
5. Tab Inactive reasons — maintain reasons used when archiving.

Result

New customer/supplier creates and archives follow these policies. Auto numbering uses document sequences for customer / supplier codes when Reference is empty.

Related

• Create a customer
• Create a supplier
• Users and roles
• Enable modules