Overview
Policy Licensing is your policy-by-policy compliance report for every in-force policy on your book. It checks whether the matched agency and agent on each policy hold the licenses the risk state and product require, then surfaces the policies that need attention so your licensing team can fix them before a regulator finds them.
What is Policy Licensing?
Policy Licensing is the report you open when you need to know, one policy at a time, whether the producers writing your business actually hold the right license, in the right state, for the right product. Turris reads the matched agency, matched agent, risk state, and product on every ingested policy, then decides whether the licensing on file satisfies the rules for that pairing under the compliance mode you choose.
Who uses it. Licensing managers, compliance officers, and operations leads at carriers and MGAs use Policy Licensing as their daily license-remediation worklist, and to pull audit-ready compliance reports for downstream stakeholders and regulators.
Policy Licensing lets you:
See whether every policy on your book is backed by a properly licensed agency or agent for that policy's risk state and product
Choose how compliance is calculated for your business (must the agency be licensed, the agent, either, or both) and save that choice as the default for everyone on your team
Narrow the list to the policies that actually need work using the status badges (Non-Compliant, Pending Data, NPN Missing, NPN Invalid, Unresolved, Compliant) plus filters for policy number, state, product, and agency
Read, in plain language, exactly why a policy failed: which side of the agency / agent pair broke, which license class or Line of Authority is missing, or which producer is missing or has an invalid NPN
Drill into any policy to see the licenses Turris counted toward each requirement and the raw source data the match was built from
Walk a policy's full transaction history (new business, renewal, endorsement, cancellation, audit, reinstatement, bound) without leaving the page
Hand a regulator or downstream auditor a CSV in one of three shapes: the compliance report, the mapped source data, or the mapped-only data
Accessing Policy Licensing
Open Left sidebar → Policy Licensing. The page loads with four stacked bands that never scroll away from the table beneath them:
The Compliance Mode row at the very top
An override banner directly below it (shown only when your current mode differs from your saved default)
The filter bar
The policy table
What's visible on the page
The table opens sorted by Policy Number, ascending. The following columns are shown in the full-width view:
Column | Description |
Policy Number | The carrier-assigned policy identifier from the ingested source data. Click the value to copy it. |
Risk State | The U.S. state or territory where the insured risk sits. This is the state whose licensing rules apply. Shown as a state circle plus the full state name. |
Product | The Turris-catalog product the policy was matched to. A yellow alert badge means the product has not been matched yet; click the badge to jump to the policy in Policy Data and resolve the match. |
Carrier | The carrier reported on the policy, when present in the source data. Click to copy. |
Agencies | Matched agencies on the policy, color-coded by each agency's compliance status (green, yellow, or red). Up to two names show inline; click +N to open a popover with the rest. An agency that appears in the source data but could not be matched shows as a gray badge with an info icon. |
Agents | Matched agents on the policy, color-coded by each agent's compliance status, with the same +N popover pattern as Agencies. |
Status | The policy's overall compliance verdict: Compliant, Non-Compliant, Pending Data, NPN Missing, NPN Invalid, or Unresolved. |
Reason | A short, plain-language reason for the status (for example, Agency Missing LOA or Agent NPN Invalid). Hover the text for the full explanation. |
Match Reason | Why Turris matched the policy's agency and agent the way it did. |
Click any policy row to open a detail panel that slides in from the right. While the panel is open the table collapses to a narrow list showing only Policy Number, Status, Risk State, and Product so it stays readable in the reduced width. Click the X icon at the top-right of the panel to close it and return to the full table.
When Turris has transaction data for your book, each policy row also carries an expand chevron at the far left. Click it to open that policy's transaction history inline, directly beneath the row, without opening the detail panel.
Selecting a Compliance Mode
When you'd do this. Different carriers and MGAs have different appetites for risk. Some only care that the agency is licensed (their agents write as sub-producers under the agency's license); others insist the named agent must be licensed too; others write captive business through individual agents. Compliance Mode tunes the report to match how your business is actually licensed.
Note: Compliance Mode is a calculation control, not a row filter. Changing it re-derives every policy's status; it does not hide any rows.
Mode | How a policy is judged Compliant |
Either Agency or Agent | At least one side of the matched agency / agent pair must be compliant. This is the broadest setting and the default. |
Agency Only | Only the agency is evaluated. Agent compliance is disregarded. |
Agent Only | Only the agent is evaluated. Agency compliance is disregarded. |
Both Agency & Agent | Both the agency and the agent must be compliant. This is the strictest setting. |
The Compliance Mode control sits at the top of the page as a slim row: a Compliance Mode label, a ? info button, and a four-segment toggle on the right.
Click the ? button to open a popover showing a small diagram of the Agency / Agent pair (a solid dot means that side is evaluated, a dashed outline means it is disregarded) joined by the operator (OR, AND, or none), plus a one-line description of the selected mode.
Click any segment in the toggle to switch modes. The policy table re-evaluates every row's status in place.
Saving your mode as the default
A mode you pick on the table is a session-only override. To make it the default that you and your team see on every future visit:
Switch to the mode you want.
A banner appears beneath the Compliance Mode row reading "Currently overriding your saved default" and naming your current saved default.
Click Save as new default on the banner.
To drop the override and return to your saved default for this session, click Reset to default on the same banner.
Tip: The saved default is also editable from Settings → Business Rules → Policy Licensing, where it sits alongside other policy-level rules. Both surfaces write to the same setting.
Filtering and Searching
The filter bar sits directly under the compliance-mode controls. Its tooltip reads: "Filter policies by compliance status, policy number, state, product, or agency."
Filter | Type | Purpose | Example use |
Policy Number | Multi-select dropdown (searchable) | Limit rows to one or more specific policy numbers. Type to search; the list loads more as you scroll. | Pulling the compliance picture for a handful of policies a broker asked about. |
State | Multi-select dropdown | Limit rows to one or more risk states. Includes a select-all option. | Auditing California renewals? Pick CA to hide every other state. |
Product | Multi-select dropdown | Limit rows to specific Turris-catalog products. Includes a select-all option. | Pulling a workers' comp report? Pick Workers Compensation to ignore other lines. |
Agency | Multi-select dropdown (searchable) | Limit rows to policies matched to one or more of your agencies. Type to search; the list loads more as you scroll. | A multi-branch broker narrowing to the policies written by one branch. |
Status badges | Badge toggles | Show only policies with the selected compliance verdicts. The available badges are Non-Compliant (red), Pending Data (blue), Compliant (green), NPN Missing (yellow), NPN Invalid (yellow), and Unresolved (gray). | Click Non-Compliant to build a license-remediation worklist. |
Include Expired | Badge toggle | Controls whether policies whose expiry date has passed appear in the list. This is on by default, so expired policies are shown unless you turn it off. | Turn it off when you only want to see in-force business. |
The search box matches against the policy number, risk state (state name or code), product, and carrier. The match is fuzzy, so typing Trav finds Travelers and partial words match mid-string. To narrow by a specific agency, agent, or policy number, use the dedicated Agency and Policy Number dropdowns rather than the search box.
Note: No status badges are pre-selected on a fresh visit. To focus the list on problem policies, click the Non-Compliant and Pending Data badges yourself.
Reading the Policy Detail Panel
When you'd do this. A policy lands on the Non-Compliant, Pending Data, NPN Missing, or NPN Invalid list and you need to know exactly which side broke, which license or LOA is missing, and what the ingestion saw before it resolved to the matched entity.
Click any row in the table. The detail panel slides in from the right with these sections, top to bottom:
Header: the policy number, the Status badge (hover its info icon for the reason), and a ? popover documenting what each status means.
Metadata grid: Risk State, Product, Carrier, and Expiry Date.
Source Data accordion: expand it to see the raw source values Insured Entity, Producer, Producer Code, and License Number; the Matching Status (an Entity Match badge and a Product Match badge, each with a confidence percentage when available); and Matched Entities (each resolved entity with a match-source badge of AI or User, a confidence percentage, and the date it was matched). Use this to confirm ingestion mapped the right entity before disputing a status.
Transaction History accordion (shown only when transactions exist): every transaction Turris has for the policy, each with its transaction-type badge, transaction date, the effective-to-expiry range, and any premium, coverage, billing ID, or source file on record.
Compliance summary: an
Agencies: X/Y compliantcounter and, when agents are involved, anAgents: X/Y compliantcounter.
Beneath the summary, one card is shown per matched agency or agent on the policy. Each card carries:
An entity-type badge: Agency (blue) or Agent (gray).
The entity's name (click to copy) and its per-entity Status badge on the right.
The entity's NPN, and for an agent the parent agency it is being evaluated under.
License Requirements: the required license classes and Lines of Authority for this state and product. Conditions inside one group are joined by AND (all must be met); alternative groups are separated by OR (at least one group must be satisfied). A check mark means the requirement is met, a warning mark means the matching license is expiring, and a cross means it is missing.
Active Licenses / LOAs: the licenses on file that count toward the requirements, color-coded by health (see Status Indicators below). A hollow circle next to an LOA means the license is on file but is not required for this policy.
When neither requirements nor licenses exist for an entity, the card shows "No requirements on file."
Tip: When an entity's status is Missing LOA, you usually already hold the right license class. You only need to add the specific Line of Authority called out under License Requirements, which is typically a much faster fix than issuing a new license.
Status Indicators
Policy-level overall status
Color | Label | Meaning | What to do about it |
Green | Compliant | Every matched agency and agent pair meets the licensing requirement for this risk state and product, under the active Compliance Mode. | No action needed. Include it in a clean-book report via the Compliant badge. |
Red | Non-Compliant | At least one matched side failed the licensing check. Hover the info icon or read the Reason column for the specific failure (for example, Agency Missing License, Agent Missing LOA, or Agency & Agent Both Fail). | Open the detail panel, find the failing card, and issue the missing license or add the missing LOA at that agency or agent. |
Blue | Pending Data | The matched agency or agent has been matched but is awaiting NIPR data ingestion. The Reason names which side (Agency Pending Data, Agent Pending Data, or Agency & Agent Pending Data). | No immediate action. Turris re-evaluates automatically once the NIPR data lands. If a side stays pending longer than expected, confirm its NIPR subscription is active. |
Yellow | NPN Missing | A matched producer that needs an NPN to be verified has none on file. This does not self-resolve. | Add the missing NPN to the agency or agent so its licenses can be checked with NIPR. |
Yellow | NPN Invalid | NIPR rejected a matched producer's NPN, so the NPN on file is likely wrong. This does not self-resolve. | Correct the NPN on the agency or agent and re-sync to verify licensing. |
Gray | Unresolved | Turris cannot determine which licensing rules apply. Usually the product is not matched to your catalog; it can also mean every matched agency is NPN-exempt and no agent is matched yet. | Click the yellow product badge in the Product column to resolve the match in Policy Data, or match an agent to the policy. The status re-evaluates afterward. |
Per-entity status (in the detail cards)
Color | Label | Meaning | What to do about it |
Green | Compliant | This agency or agent satisfies all license requirements for the risk state and product. | No action. |
Red | Missing License | The entity does not hold a license in the required class for this state. | Issue or attach the required license, then re-sync NIPR data to refresh. |
Yellow | Missing LOA | The entity holds the right license class but is missing one or more required Lines of Authority. | Add the missing LOA (named under License Requirements), then refresh NIPR data. |
Yellow | NPN Missing | The entity needs an NPN to be verified but has none on file. | Add the entity's NPN so its licenses can be checked with NIPR. |
Yellow | NPN Invalid | NIPR could not find a record for the entity's NPN. | Correct the entity's NPN and re-sync. |
Gray | NPN Not Required | This agency is exempt from NPN-based licensing (for example, a sole proprietorship in a state that does not require an agency NPN). | No action. Turris excludes exempt agencies from the failure path. |
License / LOA badges (in the detail cards)
Color | Label | Meaning | What to do about it |
Green | Active | The license is current and matches a requirement on this policy. | No action. This license is contributing to the compliant verdict. |
Yellow | Expiring | The license matches a requirement but expires soon. | Renew the license before its expiration date to avoid a future Non-Compliant status. |
Red | Expired | The license matches a requirement but has already expired. | Renew the license immediately. Until renewed, it cannot satisfy the requirement. |
Licenses that are inactive are hidden from the card. A license that is active but does not match any requirement on this policy shows with a hollow circle marker, which is informational only and needs no action.
Exporting to CSV
When you'd do this. Audit prep, a market conduct examination, sending a downstream broker a snapshot of their book, or running offline analysis in a spreadsheet.
Click Export CSV at the right end of the filter bar. A dropdown opens with up to three options:
Option | What it contains |
Compliance Report | License compliance status for every policy, agency, and agent. |
Mapped Data | Only the mapped target fields for each transaction, without the original source columns. This is Turris's normalized view. |
Mapped Transaction Data | Every transaction with its source columns plus the policy's compliance details (agency, agent, status), repeated per transaction. This option appears only when Turris has full transaction data for your book. |
The export reflects the current Compliance Mode and the Include Expired toggle, so the download mirrors what you see on screen.
Note: Export CSV is disabled when the table has no rows. Adjust the filters until at least one policy appears, then re-open the dropdown.
Frequently Asked Questions
Why is a policy showing Pending Data when I can already see licenses on the entity's profile? Pending Data means NIPR has not yet returned a snapshot for the matched agency or agent for the lookup that drives this calculation. Even if licenses were entered or imported elsewhere, the Policy Licensing engine waits for the NIPR-confirmed data, then re-evaluates the status automatically once it lands.
What is the difference between NPN Missing and NPN Invalid? NPN Missing means a matched producer that needs an NPN to be verified has none on file, so add the NPN. NPN Invalid means an NPN is on file but NIPR rejected it, so the value is likely wrong and needs to be corrected and re-synced. Neither one resolves on its own.
Does Compliance Mode change what I see in other Turris reports? The mode on this page only affects the Policy Licensing report calculation and its CSV export. Other reports evaluate compliance against their own rules and are not influenced by this selection.
Why does one of my products show a yellow badge with an alert icon? That policy's product has not been matched to your product catalog yet, so the policy reads as Unresolved. Click the yellow badge to jump to the policy in Policy Data, then run matching or assign the product manually. Once matched, the policy returns a definite verdict.
What is the difference between the Either Agency or Agent and Both Agency & Agent modes? Either Agency or Agent treats a policy as compliant as long as one side of the pair is licensed, which fits agencies that license at the firm level and let sub-producers operate under it. Both Agency & Agent requires both the firm and the named producer to hold the license, which fits captive-agent models and stricter carriers. Pick the one that matches how your business is licensed.
Best Practices
Set the right Compliance Mode for your business once, then save it as the default. The default propagates to every Policy Licensing visit and every CSV export. The wrong mode (for example, Either Agency or Agent when your carrier requires Both) masks real failures, so make this call deliberately with your licensing lead.
Work the Non-Compliant queue on a regular cadence. Click the Non-Compliant and Pending Data badges to build a worklist. Each row carries a specific reason, and the detail panel tells you which entity to act on and whether the gap is a missing license or just a missing LOA.
Treat NPN Missing and NPN Invalid as data fixes, not compliance fixes. These statuses do not self-resolve. Add or correct the producer's NPN and re-sync so Turris can actually verify the licensing.
Resolve Unresolved policies before they pile up. An Unresolved policy is invisible to a true compliance verdict. Match its product (or its agent) so the engine can give you a real status.
Pull the Compliance Report CSV at the same cadence as your audit cycle. The CSV captures the exact view on screen at that moment. Save snapshots ahead of regulatory exams so you can prove the state of the book at any point in time.
Need Help?
If you have questions about Policy Licensing or encounter any issues, contact our support team at support@turris.com.