This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| setting_up_a_new_contract [2025/06/18 18:03] – tina.robles | setting_up_a_new_contract [2025/09/18 17:37] (current) – tina.robles | ||
|---|---|---|---|
| Line 344: | Line 344: | ||
| __Contract Management: Key Functional Tabs__ | __Contract Management: Key Functional Tabs__ | ||
| - | **Products** | + | __**Products**__ |
| Purpose: Input SKUs/ | Purpose: Input SKUs/ | ||
| - | **Lumpsum** | + | __**Lumpsum**__ |
| Function: Record event-based financial allocations | Function: Record event-based financial allocations | ||
| Application: | Application: | ||
| - | **Distributors** | + | __**Distributors**__ |
| Relevance: Applicable to contracts with deviated rebates (indicated by blue columns on the product tab) | Relevance: Applicable to contracts with deviated rebates (indicated by blue columns on the product tab) | ||
| Purpose: Designate eligible distributors for the contract | Purpose: Designate eligible distributors for the contract | ||
| - | **Exclusions** (Autopay contracts only) | + | __**Exclusions** (Autopay contracts only)__ |
| - | Function: Specify partial | + | __Purpose__: Exclusions modify standard contract rates for specific entities within the contract, accommodating tiered memberships |
| - | **Backouts** (Autopay contracts only) | + | **Important**: |
| - | Purpose: Define percentage-based | + | The contractee (primary contract holder) |
| + | A distributor that falls under the contractee' | ||
| + | |||
| + | What Are Exclusions? Exclusions allow you to define situations where companies under a contract that normally receive the standard rate (X rate) instead receive a reduced rate or no earnings for some or all products. This accommodates scenarios where certain contractees or distributors require different payment structures. | ||
| + | |||
| + | Example Scenario: In buying group contracts with tiered memberships, | ||
| + | |||
| + | __Configuration Process__ | ||
| + | |||
| + | **Company-Level Exclusions: | ||
| + | * Use the filter tools to locate the company | ||
| + | * Select and drag the company row to the grid | ||
| + | |||
| + | **Specific Exclusions: | ||
| + | * Company-Product: | ||
| + | * Company-Product Grouping: Select company and relevant product group | ||
| + | * Drag selected combinations to the grid | ||
| + | |||
| + | **Exclusion Configuration Results** | ||
| + | |||
| + | Upon successful entry, the grid will display: | ||
| + | * Company details | ||
| + | * Product information | ||
| + | * Percentage adjustment fields for each entry row | ||
| + | |||
| + | **Rate Reduction Calculation Guide** | ||
| + | |||
| + | The entered reduction percentage decreases the standard contract rate proportionally. | ||
| + | |||
| + | Example: | ||
| + | * Standard Contract Rate: 4% | ||
| + | * Desired Rate: 3% | ||
| + | * Required Reduction: 25% | ||
| + | |||
| + | 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)__ | ||
| + | |||
| + | __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: | ||
| + | |||
| + | |||
| + | What Are Backouts? Backouts adjust earnings on the current contract | ||
| + | |||
| + | Scenario Example: USF Corp contract backout | ||
| + | * Any cheese volume claimed on Outback billbacks by USF distributors | ||
| + | * During the USF Corp contract period | ||
| + | * Will be deducted from earnings on the USF Corp contract | ||
| + | |||
| + | This ensures USF Corp doesn' | ||
| + | |||
| + | __Configuration Process__ | ||
| + | |||
| + | **Company-Level Backouts: | ||
| + | * Utilize filter tools to locate the relevant | ||
| + | * Select and drag the company row to the grid | ||
| + | |||
| + | **Specific Backouts: | ||
| + | * Company-Product: | ||
| + | * Company-Product Grouping: Select company and applicable product group | ||
| + | * Drag selected | ||
| + | |||
| + | **Backout Entry Results** | ||
| + | |||
| + | Upon completion, the grid displays: | ||
| + | * Company information | ||
| + | * Product details | ||
| + | * Percentage adjustment fields per row | ||
| + | |||
| + | **Backout Rate Calculation Guide** | ||
| + | |||
| + | The entered reduction percentage decreases the standard contract rate proportionally for backout calculations. | ||
| + | |||
| + | Example: | ||
| + | * Standard Contract Rate: 4% | ||
| + | * Desired Backout Rate: 3% | ||
| + | * 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 | Nature: Customizable fields as per manufacturer requirements | ||
| Function: Capture contract-specific data points | Function: Capture contract-specific data points | ||
| - | **History** | + | __**History**__ |
| Purpose: Comprehensive log of all contract modifications | Purpose: Comprehensive log of all contract modifications | ||
| - | **Notes & Attachments** | + | __**Notes & Attachments**__ |
| Function: Repository for original contract documentation and internal communications | Function: Repository for original contract documentation and internal communications | ||
| Users: Contract creators and approvers | Users: Contract creators and approvers | ||
| - | **Letters** | + | __**Letters**__ |
| Content: Contract type-specific correspondence options | Content: Contract type-specific correspondence options | ||
| Availability: | Availability: | ||
| Note: Varies by manufacturer | Note: Varies by manufacturer | ||
| - | **Contact** | + | __**Contact**__ |
| Purpose: Track customer communication details for future reference | Purpose: Track customer communication details for future reference | ||
| Fields: Email, Name, Phone Number | Fields: Email, Name, Phone Number | ||
| Status: Optional information | Status: Optional information | ||
| - | **Exposure** | + | __**Exposure**__ |
| Content: Projected exposure, actual figures, and stacked reporting data | Content: Projected exposure, actual figures, and stacked reporting data | ||
| - | **Claims** | + | __**Claims**__ |
| Function: Display all claims generated under the current contract | Function: Display all claims generated under the current contract | ||
| Line 1571: | Line 1653: | ||
| * System Verification: | * System Verification: | ||
| + | {{: | ||
| + | |||
| + | **__Incomplete Data Handling and Validation Protocols__** | ||
| + | |||
| + | __Partial Data Import Processing__ | ||
| + | |||
| + | **Incomplete Field Management** | ||
| + | * System Behavior: New products with missing required fields trigger "Bad Row" validation warnings | ||
| + | * Import Processing: Despite validation warnings, products are still integrated into the contract configuration | ||
| + | * Data State: Items exist within the contract but remain in incomplete status pending required field completion | ||
| + | |||
| + | __Contract Save Validation__ | ||
| + | |||
| + | **Required Field Verification** | ||
| + | * Save Process: Contract save operation initiates comprehensive data validation | ||
| + | * System Notification: | ||
| + | * User Guidance: Clear messaging directs users to specific fields requiring completion | ||
| + | * Save Prevention: Contract cannot be finalized until all required fields are properly populated | ||
| + | |||
| + | __Data Integrity Management__ | ||
| + | |||
| + | **Two-Stage Validation Process:** | ||
| + | * Import Stage: Allows partial data entry with warning notifications | ||
| + | * Save Stage: Enforces complete data requirements for contract finalization | ||
| + | |||
| + | **Business Benefits:** | ||
| + | * Workflow Flexibility: | ||
| + | * Error Prevention: Multiple validation checkpoints prevent incomplete contract deployment | ||
| + | * Data Quality: Ensures all contracts meet minimum data requirements before activation | ||
| + | |||
| + | __User Action Requirements__ | ||
| + | |||
| + | **Post-Import Tasks:** | ||
| + | * Field Completion: Address all flagged required fields identified during import validation | ||
| + | * Data Review: Verify accuracy and completeness of all imported product information | ||
| + | * Contract Finalization: | ||
| + | |||
| + | {{: | ||