I. Business Use Case Examples

1. After a Sales Order is created and approved, sales representatives can create a Payment Collection plan based on the agreed timeline with the Account. Workflows can be configured to automatically send reminders on the scheduled due date.

2. For teams with Payment Collection management requirements, they can track the planned Payment Collection amount versus actual Payment Collection amount as an additional performance metric.

3. For orders requiring multiple Payment Collection installments, use the batch creation feature to set up recurring payments (e.g., monthly on the 10th) or custom payment cycles.

As a critical component of sales operations, planned Payment Collection serves as a key indicator for sales process management.

II. Payment Collection Plan Details

2.1 Preset Scenarios for Payment Collection Plans

• All:

  • Records where the current user or their subordinates are responsible

  • Or where the current user or their subordinates are included in Related Teams

  • Or where “Data Permission Management” configures Payment Collection sharing rules to grant access to the current employee, their Dept., or user group

  • Or data under “My Responsible Departments”

• My Responsibilities: Payment Collection plans where the current user is responsible

• Participated by Me: Records where the current user is included in Related Teams

• Responsible by My Subordinates: Payment Collection plans where subordinates are responsible

• Participated by Subordinates: Records where subordinates are included in Related Teams

• Shared With Me: Records shared via “Data Permission Management” rules with the current employee, their Dept., or user group

• My Responsible Departments:

  • Current user is the head of their primary Dept.

  • And the record’s Related Teams include members from that Dept.

  • Note: Whether superior roles can view subordinate data is determined by “CRM Settings > Rules > Basic Settings > Superior Data Visibility Scope”

Notes: - CRM administrators can view all data - Only CRM administrators can view records marked as “Voided”

2.2 Payment Collection Plan Operations

2.2.1 Creating Payment Collection Plans

• Creation methods:

  • Manual creation:

    • Entry points:

      • [Payment Collection] list page

      • [Payment Collection] section under related [Account] details

      • [Payment Collection] section under related [Sales Order] details
        (Includes batch creation functionality)

  • Copy: Duplicate existing records via the “Copy” option in record details

  • Import (see Import Guide)

• Business notes:

  • When creating a Payment Collection plan linked to a Sales Order, the system auto-populates the Suggested Payment Amount field (equal to outstanding balance)

2.2.2 Payment Collection Plan Approval Workflow

• Purpose: Teams requiring Payment Collection oversight can configure approval workflows

• Workflow Definition: No preset approvals - fully customizable

• Approval Process: After submission, pending approvals appear in “CRM Alerts > Pending Payment Collection Plans” or the Payment Collection list

  • Approve: Completes the approval process

  • Reject: Marks status as “Rejected” requiring plan revision and resubmission

• Notes:

  • When recording actual payments, each payment line can reference its Payment Collection plan

  • Managers can then compare planned vs. actual Payment Collection amounts to assess performance

2.2.3 Common Operations for Payment Collection Plans

• Standard list operations (see List Operations Guide)

• Adding sales activities (see Sales Activities Guide)

• Core business operations including:

  • Reassigning ownership

  • Adding Related Teams members

  • Printing

  • Import/Export

  • Edit/Void/Delete
    (See Common Operations Guide)

• Collaboration features:

  • Forwarding

  • Calendar integration

  • Alerts

  • Call/Email integration
    (See Common Operations Guide)