In SchemeServe, when multiple insurers are configured on a scheme, the order in which their rating files run - and how an insurer is ultimately selected - depends on a combination of scheme settings, defaults, and rating outcomes.

Understanding this behaviour is critical to ensuring the correct insurer is selected and premiums are calculated as expected.

Default Insurer Behaviour

If a default insurer is set within a cover group:

• That insurer should be selected in the matrix provided it does not refer

However, this is not guaranteed in all cases

• If another insurer produces a cheaper premium, it may be selected instead

 Thorough testing is recommended when using default insurers

Rating Order (Without Full Risk Group Setting)

If the scheme setting “Fully rate main risk group first” is not enabled:

• Insurer rating files will run in alphabetical order

This option is rarely used, as it can negatively impact:

• Minimum premium calculations
• Overall pricing accuracy

Insurer Selection Logic

Scenario 1: Identical Rating Outcomes

If two insurers:

• Have identical rating logic, and
• Produce the same premium

Then:

• If a default insurer is set → that insurer is selected
• If no default insurer is set → the insurer added first in scheme settings is selected

This is not based on alphabetical order or site setup date

Scenario 2: One Insurer Refers, One Does Not

If:

• Insurer A → refers
• Insurer B → can quote

Then:

• Insurer B will be selected, as it is the cheapest non-referring option

Scenario 3: Both Insurers Refer

If both insurers:

• Trigger a referral
• Produce the same premium

Then:

• If a default insurer is set → that insurer is selected
• If no default insurer is set → the insurer added first in scheme settings is selected

Key Considerations

• Default insurer does not always guarantee selection if pricing differs
• Alphabetical order only applies in specific configuration scenarios
• Insurer order in scheme settings is a key determinant
• Referral logic directly impacts insurer selection
• Always test thoroughly when multiple insurers are configured