1. Examples of business usage scenarios
As a standard after-sales process of an enterprise, customers will initiate a refund application due to return or other reasons. After receiving this application, the salesperson needs to submit a financial approval. Only after the financial confirmation can the customer be refunded.
Corresponding to the sales amount, the system records the refund amount data, which is an important part of the company's daily operating data and provides data basis for the company's business decisions.
2. Detailed introduction of refund
2.1 Refund default scenario
- all:
- The person in charge is the current user or his subordinates
- or related team members include the current user or his subordinates
- Or the data of the department responsible for the approval of the current user as the refund financial role (for example, user A has the role of "refund finance" and is responsible for approving the refund records submitted by department B, then user A can view all responsible persons belonging to department B refund records).
- Or configure the "Data Sharing" rule for refund in "Data Rights Management" to share the data of the person in charge or the department of the person in charge with the current employee or the department of the current employee or the user group of the current employee
- or "My department's" data.
- I am responsible for: The person responsible for the refund is the current user
- I am involved in: The current user is included in the relevant team members
- My subordinates are responsible for: The person in charge of the refund is the subordinate of the current user
- My Subordinates Participated in: The relevant team members include the user's subordinates
- Shared to me: Configure the "Data Sharing" rule of the refund in "Data Rights Management" to share the data of the person in charge or the department of the person in charge with the current employee or the department of the current employee or current employee's user group
- I am in charge of the department:
- The current user is the department head of the main department
- At the same time, the main department of the relevant team members in the record is this department.
- Remarks: Whether the responsible department includes all subordinate data is determined by "CRM Management-Rule Settings-Basic Settings-Superior Visible Data Scope".
Remarks:
- "CRM Admin" can view all data.
- All records whose status is "Obsolete" can only be seen by "CRM administrator", and other personnel are not visible.
2.2 Business operation of refund
2.2.1 Create a new refund
- Create a refund method
- manually created
- Entry: [Refund] list page
- Associated object【Customer】details page-【Refund】
- Associated object【Sales Order】details page-【Refund】
- Import, see Import for details
- manually created
- Business supplement when creating a new refund.
- Confirmation process: Since the refund involves the financial information of the company, it needs to be approved and confirmed by relevant financial personnel. After creating a new refund, the process will automatically flow to the person corresponding to the "Refund Finance" role for confirmation.
2.2.2 Refund Approval Process
- Business Description: Since the refund involves the financial information of the company, it needs to be approved and confirmed by relevant financial personnel.
- Approval process definition: The system presets that the creator of the refund submits it to the financial confirmation of the refund.
- Approval Process Processing: After saving the newly created refund, you can check the pending refund transferred to the "Refund Finance" in "CRM Reminder - Refund to be Confirmed", click to process, or click "Refund " list to open refund details processing.
- Confirmation: The approval is passed and completed.
- Rejection: After rejection, mark the refund status as "Rejected", and you need to modify the refund information and submit it again.
- Remark:
- Only refunds whose "Status" is "Refunded" will be included in the "Total Refund" calculation.
- Regardless of whether the approval status of the refund is confirmed or not, it can be referenced by related objects.
2.2.3 Refund general business operation
- See Common List Operations for common operations on the list page
- Add sales records, see sales records for details
- Common business operations, including changing the person in charge, adding relevant team members, printing, importing, exporting, editing, voiding, deleting, etc., see Common business operations
- Business operations combined with collaborative office, including forwarding, scheduling, reminders, making phone calls, sending emails, etc., see Common business for details Action