1. U4 ERPx
  2. Business cases
  3. Customer record creation from CRM

Customer record creation from CRM

Automatically synchronise newly created customer accounts from CRM (e.g.:Microsoft Dynamics 365) into the ERPx when a Sales Opportunity is won. This ensures consistent customer master data across platforms, supports the Accounts Receivable process, and maintains accurate customer identification, address, and reference data.

Key APIs used

  • GET /v1/objects/clients - Retrieve available ERPx clients to determine the target customer master company.

  • GET /v1/objects/customers?companyId={{companyId}} - Retrieve existing customers to check for duplicates before synchronisation.

  • GET /v1/custom-fields/A5?companyId={{companyId}} - Retrieve flexi-fields used for CRM-to-ERPx reference data (customer ID, D-U-N-S number).

  • PATCH /v1/custom-fields/A5?companyId={{companyId}} - Update customer flexi-fields with CRM identifiers and reference numbers.

  • POST /v1/customers?companyId={{companyId}} - Create a new customer in ERPx based on the customer data received from CRM.


Integration workflow

sequenceDiagram
    participant DYN as CRM (e.g. MS Dynamics)
    participant EIT as Integration/Extension Toolkit
    participant ERP as ERPx API

    Note over DYN,ERP: Trigger: Customer Account is created, and Sales Opportunity is won

    DYN->>EIT: 1. Customer account data (ID, address, D-U-N-S)
    EIT->>ERP: 2. GET /v1/objects/clients
    ERP-->>EIT: ERP clients list

    EIT->>DYN: 3. Validate target ERP company (preconfigured list)
    DYN-->>EIT: Valid company confirmed

    EIT->>ERP: 4. GET /v1/customers (duplicate check)
    ERP-->>EIT: No duplicate found

    EIT->>ERP: 5. POST /v1/customers?companyId={companyId}
    EIT-->>ERP: Create new customer using CRM data
    ERP-->>EIT: Customer created (ERPx Customer ID)

    EIT->>ERP: 6. PATCH /v1/custom-fields/A5
    EIT-->>ERP: Store Dynamics customer ID + D-U-N-S number

    Note over ERP,EIT: Customer is now available for Accounts Receivable 

For detailed API specifications, request/response formats, and authentication details, refer to: