.png)
Account Management
Customer Account Creation
Customer Accounts in Zilliant CPQ CRM can be created through two distinct processes:
Automatic synchronization from the Price Manager Customer Master Data, applicable to existing customers.
Manual creation by sales representatives for new prospects.
The key differentiator between these two types is the “Account Prospect” toggle field:
Set to “Yes” (and non-editable) when the account is a prospect manually created by sales.
Set to “No” when the account is created via integration from Price Manager.
Key Fields in the Account Object
Field Name | Description |
|---|---|
Title * | Customer name |
ID | Customer ID (ASO2 ID), Populated for synchronized accounts, empty for prospects |
Geographic Account | Indicates the geographic zone of the customer |
Payment Terms | Default payment terms (can be overridden in quotes) |
TMA2 | Categorization of the customer based on business segmentation |
Status | Defines if the account is Active or Inactive |
Currency | set to Default “EUR” |
(*) Required Fields
Optional Fields
The remaining standard fields in the Account object are considered optional and can be used when needed.
The following standard fields have been renamed and reused for the project
Custom name | Original name | |
|---|---|---|
TMA2 | Industry | |
ID | ERP ID | to store ASO 2 ID |
Geographic Account | ???? |
Contact and address creation
Contacts
The contacts are managed within each Account and created manually by the Seales person, the Can inherit the address from Account or have their own.
Addresses
Sales person can define two types: Bill-To and Ship-To (one can act as both). Addresses will be linked to Accounts and reused during quoting.
Parent-Child Account Management
Only Parent accounts will be used in Zilliant CPQ CRM. Child accounts will not be imported or managed in CPQ. Hence, conditions and pricing are applied at the Parent level.
Customer Data Integration & Aggregation
Customer data is pulled from Price Manager throu and API integration and a logic required to aggregate multiple rows per customer into one account.
Pending decision: whether aggregation logic lives in Price Manager or within the CPQ API.
Diagram
The Diagram below shows the link between Account related objects