Skip to content
English
  • There are no suggestions because the search field is empty.

Commissionable Products

A Commissionable Products is composed of the following: Issuer (Carrier), State(s), Product Type, and Plan Name. Commissionable Products need to be created prior to creating Commission Rates or Policies.

A Commissionable Product defines what can be commissioned in Comissio. Commissionable Products must be created before Commission Rates or Policies can be added.

Commissionable Products are composed of the following core attributes:

    • Issuer (Carrier)
    • State(s)
    • Product Type
    • Plan Name

Throughout the application, Commissionable Products may also be referred to as Products or Plans.

Navigation:
Products → View Products


Commissionable Product List page:


Overview and Key Concepts

Commissionable Products serve as the foundation for:

    • Commission Rates
    • Policies
    • Agent Statements

Each Product represents a unique combination of attributes that determines how commissions are calculated and displayed.

When using imports to create Commissionable Products:

    • Issuers that do not already exist in the Issuer table are automatically added.

When creating Commissionable Products using the UI:

    • The Issuer must be selected from those already available in the Issuer table.

Creating or Updating a Commissionable Product

Navigation:
Products → View Products → Add New Product

When creating or editing a Product, review or enter the following fields as applicable:

    • Issuer
    • State(s)
    • Product Type
    • Plan Name

Select Save to apply changes.


Plan Name Guidance: Two Common Approaches

The Plan Name is defined by the Tenant and plays a critical role in Product organization, rate management, and how commissions appear to Agents.

There are two common and valid approaches to define Plan Names. Both are supported by Comissio. The best choice depends on operational preferences, reporting needs, and desired consistency across systems.


Approach 1: Use a Common (Shared) Plan Name with Multiple Plan Rates

(Recommended for consistency and scalability)

In this approach, the Plan Name is kept generic and consistent, representing the product itself rather than all contextual details. Variations such as year, state, or effective period are handled within Commission Plan Rates, not the Product name. It is supported by using the Commission Plan Rates State Specific import.

Example:

    • Accident SafeGuard
    • Accident SafeGuard 18 59
    • Accident SafeGuard 60 64

Or if there are applicable age ranges:

    In this model:

      • One Product is created per logical plan
      • Multiple Commission Plan Rates are created under the same Product
      • Rates vary by:
      • Date ranges (e.g., years)
        and/or
      • State or State groupings

    Key advantages:

      • Plan Names stay consistent across:
        • Quoting applications
        • Carrier statements (used by Issuer Templates)
        • Commissionable Products in Comissio
      • Plan Rates for different years or states remain linked and comparable
      • The Commission Rate detail page provides a comparison view when multiple rates exist for the same Product across different dates or states
      • This approach scales well as products evolve over time

      Note:
      The compare/navigation view for Plan Rates only appears when the same Product is reused across periods and/or states. If new Products are created each year, this comparison capability is not available.

      Trade‑off to consider:

        • Agent PDF Statements do not display State information however the CSV Commission Activity Statement does
        • If multiple Policies appear with the same Plan Name but pay different commissions, the reason for the difference (e.g., state or year) may not be visible directly on the PDF statement

      Despite this, many organizations prefer this approach for its consistency and alignment across systems.

      Approach 2: Use Detailed Plan Names to Distinguish Variations

      (Emphasized clarity at the cost of more Products)

      In this approach, Plan Names include distinguishing details directly in the name itself.

      Common elements included:

        • Issuer
        • Plan name
        • Year
        • Applicable State abbreviations
        • Applicable age ranges

      Examples:

        • UHC Accident SafeGuard (FL, KY, OH, SC) 18 59
        • UHC Accident SafeGuard (FL, KY, OH, SC) 60 64

      In this model:

        • Multiple Commissionable Products are created
        • Each Product typically requires only one set of Plan Rates

      Key advantages:

        • Immediate clarity on Agent Statements
        • Agents can easily distinguish why commissions differ between Policies
        • Minimal ambiguity without needing to reference Plan Rates

      Trade‑offs to consider:

        • More Products to manage over time
        • Plan Rates are not linked across periods or states
        • Yearly or state‑specific changes require creating additional Products

      Commission Activity section from Agent Statement with Plan highlighted.

      State Handling Best Practice

      While Comissio supports using State as a separate Product attribute, many Tenants choose to manage state applicability directly in the Plan Rates.

      Best practice when creating the Product:

        • Select All States in the State field, or
        • Leave the State field blank (the system will default to all States)

      If All States are not selected in the Product, when creating a Policy if a State is selected that is not one for in the Product, then the respective Products Plan name cannot be selected.


      Deleting Commissionable Products

      Commissionable Products can be deleted only when no dependencies exist.

      A Product cannot be deleted if it is:

        • Associated to a Policy, or
        • Referenced by any Commission Rates

      If a Product is no longer needed:

        • Update existing Policies to use a different Product
        • Delete related Commission Rates
        • Then delete the Product

      Vested Products

      Vested Products provide an exception to the standard Terminated and Not Vested commission adjustment.

      By default, when an Agent is in Terminated or Terminated with Cause status and is not vested, a Terminated and Not Vested Adjustment is created during a cycle to reduce the Agent’s net commissions to $0.00.

      Vested Products allow commissions from selected Products to continue to be paid, even when the Agent is no longer vested.


      Commissionable Product – Edit Product detail page with Vested outlined:

      Vested Products


      How Vested Products Work

      When the Vested option is selected on a Commissionable Product:

        • Commissions for Policies using that Product are excluded from the Terminated and Not Vested Adjustment.
        • The Agent continues to receive commissions for those Policies only.

      This is commonly used when:

        • Vesting requirements apply to most Products
        • Certain Products must continue paying commissions due to statutory or contractual obligations

      Setting a Product as Vested

      To mark a Product as vested:

        • Navigate to ProductsView Products.
        • Edit the desired Commissionable Product.
        • Select the Vested option.
        • Select Save.

      Additional Information on Vested Products

      When using imports, a Product can be marked as Vested by entering Y in the Vested column.

      Vested Products take precedence over the Forfeit Commission feature.

      • If an Agent is configured to forfeit commissions for a specific Issuer, but Products for that Issuer are marked as Vested, commissions for those Products will still be paid. 

      Commissionable Product List page with Vested Product outlined: