Differences

This shows you the differences between two versions of the page.

--- setting_up_a_new_contract [2025/09/18 17:31] – tina.robles
+++ setting_up_a_new_contract [2025/09/18 17:37] (current) – tina.robles
@@ Line 344: / Line 344: @@
 __Contract Management: Key Functional Tabs__
-**Products**
+__**Products**__
 Purpose: Input SKUs/Product IDs associated with the contract
-**Lumpsum**
+__**Lumpsum**__
 Function: Record event-based financial allocations
 Application: Ideal for transactions not requiring specific SKU tracking upon claim submission
-**Distributors**
+__**Distributors**__
 Relevance: Applicable to contracts with deviated rebates (indicated by blue columns on the product tab)
 Purpose: Designate eligible distributors for the contract
-**Exclusions** (Autopay contracts only)
+__**Exclusions** (Autopay contracts only)__
 __Purpose__: Exclusions modify standard contract rates for specific entities within the contract, accommodating tiered memberships or existing manufacturer agreements. These adjustments can range from reduced rates to complete payment exclusions.
@@ Line 387: / Line 387: @@
 The entered reduction percentage decreases the standard contract rate proportionally.
 Example:
   * Standard Contract Rate: 4%
@@ Line 394: / Line 395: @@
 Formula: To achieve a lower target rate, enter the percentage reduction that will decrease the standard rate to the desired level.
-**Backouts** (Autopay contracts only)
+__**Backouts** (Autopay contracts only)__
-Purpose: Backouts reduce earnings for direct contractees under a direct deal by subtracting volume claimed under indirect contracts set up with exclusion companies (operators). This mechanism ensures accurate financial reconciliation across multiple agreements and prevents double-payment scenarios.
-Important: Contractees in backout configurations must be indirect (Operator) customers.
+__Purpose:__ Backouts reduce earnings for direct contractees under a direct deal by subtracting volume claimed under indirect contracts set up with exclusion companies (operators). This mechanism ensures accurate financial
+reconciliation across multiple agreements and prevents double-payment scenarios.
+**Important:** Contractees in backout configurations must be indirect (Operator) customers.
 What Are Backouts? Backouts adjust earnings on the current contract based on volume claimed under separate contracts, preventing double-payment scenarios when the same volume is claimed across multiple agreements. The system calculates reductions by identifying volume purchased by direct contractees that has already been claimed through indirect contracts with excluded operators.
 Scenario Example: USF Corp contract backout for Outback Corp on cheese products:
-Any cheese volume claimed on Outback billbacks by USF distributors
+  * Any cheese volume claimed on Outback billbacks by USF distributors
-During the USF Corp contract period
+  * During the USF Corp contract period
-Will be deducted from earnings on the USF Corp contract
+  * Will be deducted from earnings on the USF Corp contract
 This ensures USF Corp doesn't receive duplicate payments for the same cheese volume claimed under both their direct contract and the Outback indirect contract.
-Configuration Process
-Company-Level Backouts:
+__Configuration Process__
-Utilize filter tools to locate the relevant company
-Select and drag the company row to the grid
+**Company-Level Backouts:**
-Specific Backouts:
+  * Utilize filter tools to locate the relevant company
-Company-Product: Select both company and product rows
+  * Select and drag the company row to the grid
-Company-Product Grouping: Select company and applicable product group
-Drag selected combinations to the grid
+**Specific Backouts:**
-Backout Entry Results
+  * Company-Product: Select both company and product rows
+  * Company-Product Grouping: Select company and applicable product group
+  * Drag selected combinations to the grid
+**Backout Entry Results**
 Upon completion, the grid displays:
-Company information
+  * Company information
-Product details
+  * Product details
-Percentage adjustment fields per row
+  * Percentage adjustment fields per row
-Backout Rate Calculation Guide
+**Backout Rate Calculation Guide**
 The entered reduction percentage decreases the standard contract rate proportionally for backout calculations.
 Example:
-Standard Contract Rate: 4%
+  * Standard Contract Rate: 4%
-Desired Backout Rate: 3%
+  * Desired Backout Rate: 3%
-Required Reduction: 25%
+  * Required Reduction: 25%
 Formula: To achieve the target backout rate, enter the percentage reduction that will decrease the standard rate to the desired level.
 Note: The reduction percentage represents the proportion by which the original rate should be decreased, not the final backout rate itself. This ensures accurate adjustment of earnings based on cross-contract volume claims.
-**Client Defined Fields**
+__**Client Defined Fields**__
 Nature: Customizable fields as per manufacturer requirements
 Function: Capture contract-specific data points
-**History**
+__**History**__
 Purpose: Comprehensive log of all contract modifications
-**Notes & Attachments**
+__**Notes & Attachments**__
 Function: Repository for original contract documentation and internal communications
 Users: Contract creators and approvers
-**Letters**
+__**Letters**__
 Content: Contract type-specific correspondence options
 Availability: Enabled post-contract save
 Note: Varies by manufacturer
-**Contact**
+__**Contact**__
 Purpose: Track customer communication details for future reference
 Fields: Email, Name, Phone Number
 Status: Optional information
-**Exposure**
+__**Exposure**__
 Content: Projected exposure, actual figures, and stacked reporting data
-**Claims**
+__**Claims**__
 Function: Display all claims generated under the current contract

Telus TPM Documentation

User Tools

Site Tools

Differences

Page Tools