Configuring plan-level qualifiers

A plan-level Qualifier is a scheme-wide eligibility filter. A transaction must satisfy the approved qualifier logic before the scheme’s commission rules can apply.

Who can use this guide

This guide is intended for Administrators and authorised Finance users.

Purpose

Use this guide to review or configure property, operator, and value conditions in the Set Qualifiers stage of the commission scheme builder.

Prerequisites

An approved eligibility definition written in plain language
Verified source fields and representative values
At least one synthetic record that should qualify and one that should not
A draft or test-only commission scheme
Approval to change the scheme configuration

Review or configure qualifiers

Open Commission and start a test-only scheme with Create From Scratch.
Complete Scheme Setup, then continue to Set Qualifiers.
Translate each approved eligibility requirement into a property, operator, and value condition.
Confirm that every property exists in the imported transaction data and that the test values use the expected format.
Choose AND when every listed condition must pass, or OR when any listed condition may pass.

Verification required: Advanced condition grouping, operator behaviour, case sensitivity, and blank-value handling were not fully tested. Use synthetic records to verify the exact result.
Test at least one record that should pass and one that should fail. Include boundary values where the condition uses a range or threshold.
Continue to Build Rules and confirm that the rules are intended to evaluate only transactions that pass the plan-level qualifiers.
In Review & Publish, compare the displayed qualifiers with the approved design. Select Save Draft if any review remains outstanding.

Expected result

The review summary shows the approved plan-level conditions, and the synthetic inclusion and exclusion records produce the expected eligibility result.

Important notes

Warning: Plan-level qualifiers can affect every participant assigned to the scheme. Do not publish a change to an active scheme until its effective-date, recalculation, and recovery effects have been verified and approved.

AND usually narrows eligibility; OR usually broadens it.
A plan-level qualifier is different from a Metric Definition filter or a condition inside an individual rule.
Exact compound-condition precedence and post-publication editing behaviour remain unverified.
Keep the approved eligibility statement and synthetic test evidence with the scheme review record.

Troubleshooting

Too many transactions qualify

Check whether OR was selected where AND was intended. Review every property, operator, and value against the approved eligibility statement.

No transactions qualify

Confirm that the selected source property contains data for the test period. Compare the stored value and format with the qualifier value; do not assume case or blank-value behaviour.

A known transaction behaves unexpectedly

First confirm that the transaction is present and current. Then trace the source value, qualifier, Metric Definition, rule, and tier without changing multiple stages at once.

The qualifier summary differs from the configuration

Stop before publishing. Save a draft, capture a sanitised screenshot, and contact Support with the scheme name, test condition, expected result, and application version.

Last updated: August 2026