Creating STP Rules and Error Codes

This guide explains how to create and manage Straight Through Processing (STP) rules using the standard user interface. It also covers how to set up STP error codes, which are triggered by these rules to provide feedback or halt processing.

What Are STP Rules and Error Codes?

• STP Rules automate underwriting decisions, allowing policies to move through your system without manual intervention. These rules are defined by conditions and actions, set up directly within BriteCore.
• STP Error Codes are custom error messages or codes you define. Rules trigger these codes, which help communicate the reason for a rule failure or required action to users and downstream systems.

Step 1: Create STP Error Codes

Before you create rules, define the error codes.

How to Create Error Codes

1. Navigate to the STP Error Codes Section
   • As an administrator, from the left navigation pane, select Lines
   • Then select STP Error Codes
2. Add a New Error Code
   • Select + New STP Error
   • Enter a unique Error Code (e.g., DR00001).
   • Enter a clear Description (e.g., “Driver age is below minimum requirement.”).
3. Save the Error Code
   • Confirm and save. The error code is now available to use in STP rules.

Step 2: Create STP Rules 

1. Access the Rule Management Section

• As an administrator, from the left navigation pane, select Lines
• Select the latest effective date
• Select Underwriting > Rules
• Select the appropriate policy type

2. Start a New Rule

• Select Add Rule.
• Enter the following Details:
  • Rule Name
  • Rules Description
  • Category scope
    • Note: STP only works for Property and Policy Scope
  • In the Module scope option, select STP
  • Identify any agency exceptions
  • Select if the rule is for renewal only
• Add a Trigger
• Add an Effect
  • Action: Set STP error
  • STP error code: select from the dropdown
    • Note: These error codes are set in step 1
• Save to create the rule

Example: Creating a Rule That Triggers an Error Code

1. Create Error Code:
   • Code: ERRTERR001
   • Description: "Territory falls within a designated hazardous zone."
2. Create Rule:
   • Name: "Restricted Territory"
   • Category: Property
   • Trigger:
     1. Policy Line Item type: Coverage A (Mandatory Coverage)
     2. Trigger Type: Category (aka custom field)
     3. Category: Territory
     4. Value: 30, 31, 32, etc.
   • Action: Trigger error code ERRTERR001 and require manual review

Tips for Effective UI-Based Rules

• Plan error codes in advance: It’s easier to manage and reuse them.
• Use clear, descriptive names: For both rules and error codes, to help with troubleshooting.
• Review regularly: Business requirements and data structures may change over time.
• Leverage built-in fields: UI rules are limited to the fields exposed in the interface.

Limitations of UI-Based STP Rules

• Cannot use custom Python logic or calculations (see Advanced Triggers).
• Only available fields and operators can be used.
• For highly customized or data-driven logic, consider advanced triggers.