Once STP rules have been configured by an administrator, they automate and streamline the underwriting workflow for both agents and underwriters. This guide explains how STP rules are used in daily operations and what to expect when working with them.
What Are STP Rules?
STP (Straight Through Processing) rules are automated logic that evaluate insurance applications, endorsements, and renewals. They determine, based on configured business criteria, whether a transaction can proceed automatically or needs additional manual review.
These rules can trigger error codes that flag applications for further investigation.
How STP Rules Affect Daily Workflow
For Agents
- Submission and Quoting
- When an agent inputs application data and requests a quote, STP rules automatically evaluate the submission through the quoting flow.
- NOTE: not available in legacy quoting
- If all rules are satisfied, the policy is generated and set to active; no manual underwriting is needed.
- If a rule is not satisfied, the agent will see error codes within the underwriting screen of the quoting flow.
- The agent cannot proceed until the underwriting reviews and approves.
- When an agent inputs application data and requests a quote, STP rules automatically evaluate the submission through the quoting flow.
- Error Codes and Feedback
- Error codes provide instant feedback if information is missing or out of bounds (e.g., driver age too low, coverage limit not allowed).
- Depending on the clarity of the error code description, the agent may adjust the application and submit for review again. Otherwise, the agent will need to wait until underwriting review is complete.
- Efficiency
- Most routine policies and endorsements can be processed without waiting for underwriter review.
- Only exceptions are flagged for manual handling.
For Underwriters
- Reviewing Flagged Submissions
- Applications flagged by STP rules (due to rule failure or triggered error codes) will be triggered for review
- This will be sent to the email address setup in admin-alerts labeled “Straight through processing.”
- Error codes help quickly identify why the submission was not processed automatically.
- Applications flagged by STP rules (due to rule failure or triggered error codes) will be triggered for review
- Decision Support
- STP rules standardize evaluation, reducing subjective decision-making and ensuring consistency.
- You can override all error codes or apply manual underwriting decisions as permitted by your authority.
- In order to advance the quote process, the underwriter must approve all the rules; otherwise, the underwriter can decline the quote to stop it from moving forward.
- Audit and Reporting
- STP rule results and triggered error codes are logged on the notes page for audit purposes.
- You can review which rules were triggered per transaction for compliance and analysis.
Example User Flows
Agent Submits Application
- Agent enters policy details and reaches the underwriting review page.
- STP rules are evaluated automatically.
- If all rules pass: Agent can advanced to the billing and submission pages.
- If any rule fails: Error code and description are shown.
Agent can correct and resubmit or submit as is for underwriter review.
Underwriter Reviews Exception
- Underwriter receives an admin alert that there is a flagged application
- Reviews error code details and supporting data.
- Decides to approve, decline, or request more info.
- Resolution is recorded, and the agent is notified.
Best Practices
- Agents:
- Familiarize yourself with common error codes.
- Ensure all required fields and values are entered correctly to maximize straight-through processing.
- Underwriters:
- Use error codes for quick triage.
- Follow up promptly on flagged submissions to keep the workflow efficient.
Summary
STP rules automate underwriting checks, providing instant decisions for agents and clear guidance for underwriters on exceptions. This leads to greater efficiency, consistency, and transparency in the insurance process.
If you need help interpreting an error code or understanding rule logic, refer to your company's STP rule documentation or reach out to your system administrator.
Related settings:
| Setting Name | Description |
| enable-default-review-workflow | Activates the default review workflow for underwriting or policy actions. When enabled, submissions that require review will follow a standardized, system-defined process—ensuring consistency in how reviews are assigned, notifications are sent, and statuses are updated. |
| use-new-state-for-uw-approva | Switches the system to use an updated state (or status) indicator when an underwriting approval is granted. This may map to a new workflow status, allow for improved tracking of approved items, or integrate with enhanced reporting features. |
| how-review-state-column | Controls the display of the "Review State" column in lists or dashboards (e.g., applications, policies, submissions). When enabled, users can quickly see the current review status (pending, approved, declined, etc.) for each item, improving visibility and workflow management. |
| enable-review-state-filter | Adds a filter option for "Review State" to lists or search interfaces. This lets users easily narrow down results by review status—such as seeing only items pending review, those approved, or declined—streamlining review tasks and reporting. |
| custom-labels-review-state-filter-options | Allows administrators to define custom labels for the review state filter options. For example, instead of the default "Approved" or "Declined," you might use "Ready for Issue" or "Requires Escalation." This improves clarity and tailors the workflow language to your organization’s needs. |