Producers, licensing & compensation

Know exactly who may write what, where, today.

A licensing and appointment register at real regulatory grain — state, lines of authority, resident status, expiry and continuing-education hours — attached to a producer master carrying NPN and agency hierarchy.

Book a demoSee the platformInteractive demo
app.aegisnow.ai/ledger

Distribution Command Center

Live

Active producers

6,420

Licences current

99.2%

Expiring in 90 days

137

CE hours outstanding

412

Licences renewed per month, last 12 months

Trend

AegisNow Distribution & Agency is a producer licensing and appointment register. Each licence is held with the state that issued it, the lines of authority it grants, the licence number, resident or non-resident status, effective and expiry dates, the appointing carrier, and the continuing-education hours required, completed and due — so "can this producer write this line in this state today" is answerable from one record. Producers carry an internal code, their National Producer Number, type, agency, status, tier and a parent reference forming the agency hierarchy. Stated plainly: onboarding automation, compensation-plan modelling, production analytics and a producer portal are not implemented, and no policy yet records which producer wrote it.

0regulatory dimensions per licence: state, line, expiry, CE

Illustrative outcome. We will map Distribution & Agency to your own data, frameworks and targets in a working demo.

Why teams choose it

The case for Distribution & Agency

Onboard, license, pay and grow your producer force.

Licence and appointment are different things

They are held as separate permissions, because a producer can carry a state licence without the carrier appointment that lets them write your business.

Authority at the grain it is asked

Per producer, per state, per line — so "may they write this today" is one row, not a spreadsheet and a memory of what was renewed.

CE tracked on its own clock

Hours required, completed and due sit on the licence, so an expiring licence with outstanding hours is visibly more urgent than one that is clear.

NPN, not just an internal code

The National Producer Number is held because it is the identifier that survives outside your system — how a producer is recognised across carriers and state databases.

Hierarchy as data

Agency, branch and producer form a tree through a parent reference, which is the prerequisite for any override or rollup arithmetic that follows.

Limits on the page, not in the demo

What this module does not do — onboarding, comp plans, production analytics, portal — is named on the page rather than discovered during an evaluation.

Inside the module

Capabilities that ship on day one

Every capability runs on the shared data fabric, the governed Cortex brain and the evidence ledger — so Distribution & Agency compounds with the rest of the platform.

Licence register by state and line

Every licence held with its state, lines of authority, resident status, dates and continuing-education position.

Learn more

Producer master & hierarchy

Producers held with their code, NPN, type, tier and parent — the agency structure as data.

Learn more

Appointment and expiry visibility

What is expiring, where, and for which lines — read from the register rather than a reminder someone set.

Learn more

Where this module ends today

Stated rather than implied: what a distribution suite normally includes that this does not yet.

Learn more
app.aegisnow.ai/ledger

Distribution Command Center

Live

Active producers

6,420

Licences current

99.2%

Expiring in 90 days

137

CE hours outstanding

412

Licences renewed per month, last 12 months

Trend
Capability detail

What each capability actually does

Each section below is directly linkable, so a specific answer can be cited on its own rather than buried in a page.

Capability 01

Licence register by state and line

Every licence held with its state, lines of authority, resident status, dates and continuing-education position.

A producer licence is held as what a regulator actually cares about: the state it was issued in, the lines of authority it grants, the licence number, whether it is resident or non-resident, the effective and expiry dates, and the carrier appointment attached to it. That last distinction matters — a licence and an appointment are different permissions, and a producer can hold one without the other.

Continuing education is tracked on the same record: hours required, hours completed and the date they are due. A licence approaching expiry with CE hours outstanding is a different and more urgent problem than one approaching expiry with them complete, and the register holds enough to tell those apart rather than surfacing one undifferentiated renewal alert.

The register is per producer per state per line, which is the grain the question is actually asked at. "Can this producer write this line in this state today" is answerable from one row rather than assembled from a spreadsheet and someone's memory of what was renewed.

What it does

  • Hold each licence with its state, lines of authority, licence number and resident or non-resident status.
  • Record effective and expiry dates per licence, and the carrier appointment attached to it.
  • Track continuing-education hours required, hours completed and the due date on the licence itself.
  • Distinguish a licence from an appointment rather than conflating the two permissions.
  • Answer authority at the grain it is asked — producer, state, line — from a single record.

Implements

  • State licences with lines of authority
  • Resident and non-resident licensing
  • Carrier appointments
  • Continuing-education hours and due dates

See it in the product

Open a producer's licences: each row names the state, the lines it authorises, the expiry date, the appointing carrier and the CE position — so an expiring licence with outstanding hours is visibly different from one that is clear.

Capability 02

Producer master & hierarchy

Producers held with their code, NPN, type, tier and parent — the agency structure as data.

The producer record carries the identity a carrier and a regulator each need: an internal producer code, the National Producer Number, the producer type, the agency they sit under, their status, tier, contract date and region. NPN matters because it is the identifier that survives outside your system — it is how a producer is recognised across carriers and state databases.

Hierarchy is modelled through a parent reference on the producer, so agency, branch and individual producer form a tree rather than a flat list. That structure is the prerequisite for override and rollup arithmetic.

Said plainly, because the previous version of this page did not: the hierarchy currently has nothing to roll up. No policy in the system records which producer wrote it — there is no producer column on the policy at all — and commissions name a producer as free text rather than referencing the producer record. The tree is real; the production hanging from it is not yet connected. That connection is the next piece of work, not a claim this page should be making.

What it does

  • Hold producer code, National Producer Number, type, agency, status, tier, contract date and region.
  • Model agency, branch and producer as a tree through a parent reference.
  • Keep the producer master as the single record licences attach to.

Implements

  • National Producer Number (NPN)
  • Agency / branch / producer hierarchy

See it in the product

Open the producer list: each carries its NPN, tier and parent. Then note the limit honestly — ask for a producer's written premium and the answer is empty, because policies do not yet record who wrote them.

Capability 03

Appointment and expiry visibility

What is expiring, where, and for which lines — read from the register rather than a reminder someone set.

Expiry is a property of the licence record, so the set of licences lapsing in a window is a query rather than a calendar someone maintains alongside the system. The same is true of CE due dates, which run on their own clock and frequently expire before the licence does.

Because the register is per state and per line, an expiry view answers the operationally useful version of the question — which producers lose which authority in which states — rather than a flat count of documents needing attention.

The appointing carrier sits on the licence, so a carrier withdrawing appointments in a state has a definable blast radius rather than a manual reconciliation.

What it does

  • Derive expiring licences from the dates on the register rather than a separate reminder list.
  • Track continuing-education due dates independently of licence expiry.
  • Scope an expiry view by state and line of authority.
  • Identify the producers affected by a carrier appointment change from the appointment on each licence.

Implements

  • Licence expiry and renewal windows
  • CE due dates independent of licence expiry

See it in the product

Query licences expiring in the next 90 days: the result is grouped by state and line, and CE-outstanding rows are distinguishable from CE-complete ones.

Capability 04

Where this module ends today

Stated rather than implied: what a distribution suite normally includes that this does not yet.

This page previously described onboarding automation, compensation-plan modelling, production analytics and a producer portal. None of those exist in the code, and describing them as shipped is the failure mode this rewrite is correcting across every module page.

Specifically absent: there is no onboarding workflow — no background check, no E&O verification and no contracting flow; there is no compensation-plan model, so tiers, production bonuses, hierarchy overrides and vesting are not represented and cannot be simulated; there are no production, persistency or placement analytics, because no policy records its producer; there is no producer self-service portal; and there is no termination or book-transfer flow with trailing commission handling.

What exists and is worth having on its own is a licensing and appointment register with real regulatory grain — state, lines of authority, resident status, expiry, appointment and continuing education — attached to a producer master that carries NPN and hierarchy. A carrier evaluating this module should evaluate it as that, and should ask when the producer-to-policy link lands before counting on anything downstream of it.

What it does

  • State the absent capabilities by name rather than omitting them from the page.
  • Identify the producer-to-policy link as the dependency the rest of the module waits on.

Implements

  • Capability disclosure

See it in the product

There is nothing to demonstrate here, which is the point — this capability exists so a buyer does not have to discover these gaps during an evaluation.

Built for the people who own the risk

Made for your team, aligned to your frameworks.

Cortex skill-agents draft the work, cite their sources and write every action to the evidence ledger — so Distribution & Agency accelerates the people accountable for it without putting your audit posture at risk.

Who it serves

  • Chief Distribution Officers
  • Agency operations leaders
  • Licensing & contracting teams
  • Compensation analysts
  • IMO / FMO executives

Aligned to

  • NAIC producer licensing model act
  • State appointment regulations
  • NY Reg 187 / best interest
  • FINRA (where securities overlap)
  • Anti-rebating rules
CortexAI reasoning copilot
Grounded

Shared device fingerprint with the ring94
Repair shop tied to a prior SIU case87
Loss pattern matches the closed cluster81
SourcesPolicy ledgerClaims graphSIU casebook
Confidence94%
Works better together

Pairs with the rest of the platform

Distribution & Agency shares one core with every other module — combine it to extend coverage without adding integration debt.

Billing & Collections

Collect every premium, settle every commission, on time.

Policy Administration

Service the book, launch products and run MGA programs on one core.

Customer 360

One view of every policyholder, household and interaction.

Underwriting Workbench

Rate, decide and refer on one governed underwriting desktop.

For your industrySee how Distribution & Agency works in regulated sectors.
Life, annuity & retirement carriers

Life & Annuities

From accelerated underwriting to automated death claims.

Explore Life & AnnuitiesPersonal & commercial lines carriers

P&C Insurance

Quote-to-claim on one core, with the combined ratio in view.

Explore P&C InsuranceBank & institutional distribution

Bancassurance

Insurance through the branch and app — governed like a carrier.

Explore Bancassurance
FAQ

Distribution & Agency FAQ

What evaluation teams want to know before a demo — answered plainly.

Per producer, per state, per line: the licence number, the lines of authority it grants, resident or non-resident status, effective and expiry dates, the appointing carrier, and continuing-education hours required, completed and due. Licence and appointment are held as distinct permissions, because a producer can hold a state licence without the carrier appointment that lets them write your business.

It makes the position answerable at the grain the question is asked — this producer, this state, this line, today — from a single record rather than a reconstruction. What it does not do is block a sale at the point of sale, because no policy in the system currently records which producer wrote it; that link is the next piece of work and this page will not claim it until it exists.

No. There is no background check, no E&O verification and no contracting workflow in the code. The previous version of this page described all three as shipped. A producer record is created and licences are registered against it; the diligence around that is done outside the platform today.

No. There is no compensation-plan model — tiers, production bonuses, hierarchy overrides and vesting are not represented and cannot be simulated. The producer record carries a commission plan name as a label, which is not the same thing. Commission accrual itself lives in Billing and is basis times rate on a single record.

None yet, and the reason is structural rather than a missing screen. No policy records its producer — there is no producer column on the policy — and commissions name a producer as free text rather than referencing the producer record. Production, persistency and placement are therefore not merely unbuilt but uncomputable until that link exists. The producer hierarchy is real; there is nothing hanging from it to roll up.

The hierarchy is a parent reference on the producer record, so agency, branch and producer form a tree that can be re-parented. Effective-dated hierarchy moves — where an override must be computed against the structure as it stood at a point in time — are not modelled, and would need both the producer-to-policy link and a temporal hierarchy to be meaningful.

See Distribution & Agency on your data

Book a working session and we will map your sources, workflows and frameworks onto Distribution & Agency — and show Cortex reasoning over them live.

Book a demoExplore the platformInteractive demo
Distribution & Agency — Onboard, license, pay and grow your producer force. | AegisNow Insurance