rebate-management-setup
Rebate Management setup: rebate types, payout calculations, accruals, partner rebates, program setup, compliance reporting. NOT for CPQ discounts on quotes (use revenue-cloud-cpq-setup). NOT for channel loyalty programs (use partner-loyalty-programs).
Best use case
rebate-management-setup is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Rebate Management setup: rebate types, payout calculations, accruals, partner rebates, program setup, compliance reporting. NOT for CPQ discounts on quotes (use revenue-cloud-cpq-setup). NOT for channel loyalty programs (use partner-loyalty-programs).
Teams using rebate-management-setup should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/rebate-management-setup/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How rebate-management-setup Compares
| Feature / Agent | rebate-management-setup | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Rebate Management setup: rebate types, payout calculations, accruals, partner rebates, program setup, compliance reporting. NOT for CPQ discounts on quotes (use revenue-cloud-cpq-setup). NOT for channel loyalty programs (use partner-loyalty-programs).
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Rebate Management Setup Activate when configuring Salesforce Rebate Management for channel incentive programs: volume rebates, growth rebates, market-development funds (MDF), SPIFs, and partner co-op programs. Rebate Management is a distinct feature from CPQ discounting — it calculates after-the-fact incentives based on transactions, not at quote time. ## Before Starting - **Confirm Rebate Management license.** It is a paid add-on; the object model (`Rebate_Program__c`, `Benefit__c`, `Rebate_Payout__c`, `Transaction__c`) only appears when provisioned. - **Identify the source of transactions.** Rebates calculate against transactions — could be Orders, Invoices, a POS feed, or a data warehouse extract. This source drives the ingestion pipeline. - **Know the finance control requirements.** Most rebate programs require accounting sign-off before payout. Approval routing and GL integration must be designed before program go-live. ## Core Concepts ### Program → Measure → Benefit → Payout `Rebate_Program__c` is the top-level container (e.g., "2026 Channel Volume Rebate"). `Rebate_Measure__c` defines what is measured (units, revenue, growth %). `Benefit__c` defines what the participant earns at each threshold. `Rebate_Payout__c` is an actual payout instance after the period closes. ### Accrual accounting Between the period start and close, Rebate Management posts **accruals** — estimates of the liability as transactions come in. On period close, accruals reconcile to actual payouts. Accrual frequency (daily, weekly, monthly) is a finance decision. ### Transaction ingestion `Transaction__c` records are the fuel. They come from: CG Cloud orders, Revenue Cloud invoices, Data Cloud feeds, CSV loads, or custom integrations. Schema matters — amount, participant, product family, and date are mandatory for rebate calculation. ## Common Patterns ### Pattern: Volume-tier rebate with quarterly payout `Rebate_Program__c` with `Benefit__c` records defining tier thresholds (1-1000 units → 2%, 1001-5000 → 3%, 5000+ → 5%). Transactions accumulate through the quarter. At period close, Rebate Calculation runs, Payouts are generated, Approval routes to finance, then GL posts. ### Pattern: Growth rebate vs prior period Benefit tied to % growth vs the same participant's prior quarter. Requires reference data on prior period baseline. Flow or a scheduled Apex sets the baseline at period start. ### Pattern: MDF with manual claim approval Participant submits an MDF claim (via portal LWC). Claim is a `Rebate_Payout__c` with a manual route rather than auto-calculation. Approval + receipt review before payout. ## Decision Guidance | Situation | Recommended Approach | Reason | |---|---|---| | Quote-time discount | CPQ discount schedules | Applied before deal signs | | After-sale volume rebate | Rebate Management | Calculates against delivered transactions | | MDF / co-op claims | Rebate Management with manual payout | Shipped claim workflow | | Loyalty point rewards | Loyalty Management | Distinct product | | Simple referral SPIF | Rebate Management flat benefit | Overkill for ad-hoc, use Rebate anyway for audit | ## Recommended Workflow 1. Provision the license; confirm Rebate Management objects are visible in Object Manager. 2. Map transaction source systems; build the `Transaction__c` ingestion job (daily recommended). 3. Design programs: volume, growth, MDF — one `Rebate_Program__c` per program for auditability. 4. Configure `Benefit__c` thresholds; validate with sample transactions through a scratch-org dry run. 5. Set accrual cadence and validate with finance; set up GL posting integration. 6. Build partner visibility: Experience Cloud page showing year-to-date accrued rebate, tier progress. 7. Run a full period-close dry run: accruals → calculation → approval → payout → GL post. ## Review Checklist - [ ] Rebate Management license provisioned and objects visible - [ ] Transaction ingestion validated end-to-end - [ ] Program + Measure + Benefit structure matches contract - [ ] Accrual cadence signed off by finance - [ ] Approval routing in place before first payout - [ ] Partner portal shows accurate year-to-date figures - [ ] Audit report: traceable from payout back to source transactions ## Salesforce-Specific Gotchas 1. **Rebate recalculation is not retroactive unless forced.** Fixing a Benefit threshold after accruals have posted requires a manual recalc job; partners may see shifting balances. 2. **Transaction date drives period assignment.** Out-of-order backfills can hit closed periods — either reopen for recalc or post as a next-period adjustment. 3. **Experience Cloud rebate widgets depend on the Benefit Accrual snapshot.** If the snapshot job fails, partner portals show stale numbers with no obvious error. ## Output Artifacts | Artifact | Description | |---|---| | Rebate program catalog | Active programs, benefit structures, participants | | Transaction ingestion spec | Source, schema, schedule, error handling | | Accrual and payout runbook | Period open/close procedure | | Partner visibility page | LWC / Experience Cloud layout showing YTD rebate | ## Related Skills - `admin/revenue-cloud-cpq-setup` — quote-time discount sibling - `admin/experience-cloud-site-setup` — partner portal host - `integration/integration-pattern-selection` — transaction ingestion
Related Skills
shield-kms-byok-setup
Configure Shield Platform Encryption with customer-supplied (BYOK) or customer-held (Cache-Only Key Service) tenant secrets, rotate them, and recover. NOT for Classic Encryption or field masking.
session-management-and-timeout
Use this skill when configuring session timeout values, concurrent session limits, session IP locking, or logout behavior in Salesforce. Covers org-wide session settings, profile-level overrides, Connected App session policies, and Metadata API SecuritySettings deployment. NOT for OAuth token refresh flows, login IP ranges, or MFA/identity-provider configuration.
oauth-token-management
Use when work depends on how Salesforce OAuth access and refresh tokens are issued, refreshed, rotated, revoked, or introspected for a Connected App or API client—including unexpected logouts, invalid_grant after refresh, or designing token incident response. NOT for choosing which OAuth grant or Connected App flow to implement (use integration/oauth-flows-and-connected-apps), Named Credential packaging (use integration/named-credentials-setup), or broad Connected App IP and PKCE policy hardening without a token-lifecycle angle (use security/connected-app-security-policies).
certificate-and-key-management
Use this skill when creating, uploading, or rotating certificates in Salesforce, configuring mutual TLS (mTLS) client authentication, managing the Java KeyStore for CA-signed certificates, diagnosing certificate expiry in JWT OAuth flows, or understanding which certificate types Salesforce supports and how to migrate them between orgs. NOT for Named Credential configuration (use named-credentials-setup skill), NOT for Shield Platform Encryption key management. Trigger keywords: Certificate and Key Management, self-signed certificate, CA-signed certificate, mutual TLS, mTLS, keystore, JKS, PKCS12, certificate rotation, certificate expiry, JWT certificate.
flexcard-state-management
Use when designing FlexCard actions, conditional visibility, and state that must survive navigation, refresh, or parent/child card transitions. Triggers: 'flexcard state', 'flexcard conditional visibility', 'flexcard actions', 'flexcard refresh', 'child flexcard state'. NOT for raw LWC state or for OmniScript step state.
lwc-state-management
Share state across LWCs using pub/sub, Lightning Message Service, @wire, and reactive stores. NOT for in-component reactivity.
lwc-focus-management
Use when building LWCs that need to manage focus explicitly — modal dialogs, wizard flows, dynamic inserts, list updates, error summaries, and focus after async work. Covers focus restoration, focus traps, programmatic focus across shadow DOM, and patterns for announcing changes to assistive tech. Does NOT cover general LWC a11y audit (see lwc-accessibility).
slack-salesforce-integration-setup
Use this skill when setting up or troubleshooting the Salesforce for Slack managed app — including connecting a Salesforce org to a Slack workspace, configuring the three-party admin handshake, linking Slack channels to Salesforce records, enabling record preview sharing, and managing org-level limits. Triggers on: Salesforce for Slack app not connecting, Slack org connection setup, Salesforce record sharing in Slack, Slack workspace admin approval, connecting Salesforce to Slack. NOT for building custom Slack apps or Slack bots (separate development platform), not for Slack Workflow Builder Salesforce connector (use slack-workflow-builder skill), not for Flow-based Slack messaging (use flow-for-slack skill).
salesforce-maps-setup
Use when configuring Salesforce Maps (formerly MapAnything) — territory planning, route optimization, live tracking, geo-grid visualizations, and check-in/check-out workflows for Sales or Service field reps not on Field Service. Covers package installation order (Maps + Maps Advanced + Maps Routing/Live Tracking add-ons), the MapsTerritoryPlan / MapsAdvancedRoute / MapsLayer object family, base-data syncs (Geocoding and Routing services), and integration with Sales and Service Cloud records. Triggers: 'Salesforce Maps setup', 'MapAnything migration', 'territory planning by polygon', 'route optimization for sales reps', 'live tracking field reps', 'plot accounts on a map', 'check-in to the closest account'. NOT for Field Service Lightning territory and scheduling (use admin/fsl-scheduling-optimization-design and data/fsl-territory-data-setup) — Maps and FSL are different products. NOT for Consumer Goods Cloud retail visit planning (use admin/consumer-goods-cloud-setup) — RoutePlan/Visit objects are CG-specific. NOT for Tableau / CRM Analytics geo charts.
revenue-lifecycle-management
Use this skill when implementing or troubleshooting Salesforce Revenue Lifecycle Management (RLM) — the native Revenue Cloud product covering order-to-cash lifecycle, Dynamic Revenue Orchestrator (DRO) fulfillment plan design, asset amendments, billing schedule creation via Connect API, and invoice management. Triggers on: Dynamic Revenue Orchestrator, RLM order decomposition, DRO fulfillment swimlanes, native Revenue Cloud billing schedule, asset lifecycle management Salesforce. NOT for CPQ quoting or pricing rules (use cpq-* skills), not for the legacy Salesforce Billing managed package with blng__* objects (different product entirely), not for standard Order objects without Revenue Cloud features.
private-connect-setup
Configure Private Connect between Salesforce and AWS/Azure for traffic to stay on private networks. NOT for standard internet callouts.
net-zero-cloud-setup
Use this skill when configuring Salesforce Net Zero Cloud — including Scope 1/2/3 emission source modeling via the StnryAssetCrbnFtprnt / VehicleAssetCrbnFtprnt / Scope3CrbnFtprnt object families, emission factor library setup (EmssnFctr / EmssnFctrSet), DPE-driven carbon calculation jobs, supplier engagement scoring, and CSRD / ESRS / TCFD disclosure pack mapping. Triggers on: Net Zero Cloud setup, Sustainability Cloud carbon accounting, Scope 1 2 3 emissions Salesforce, emission factor library, supplier engagement Net Zero, ESG disclosure pack mapping. NOT for ESG content scoring (use Marketing Cloud), NOT for general financial reporting (use Accounting Subledger), NOT for energy-only utility billing (use Energy & Utilities Cloud).