Surety management software for carriers and MGAs
One record from the submission a broker sends to the bond you close out years later, with the facility, authority, collateral, and indemnity attached. Built for surety carriers, specialty insurers, MGAs, and the capacity providers who stand behind them.
Book a demo
What surety management software does
Surety management software runs the business of writing bonds: the submissions agents and brokers send in, the financial assessment behind each principal, the authority and facility limits a bond is written against, the bond itself and every rider and continuation after it, and the claims and recoveries that can run for years once something goes wrong.
It is not a policy administration system with a bond label on it. A bond is not a policy, and a surety obligation is not an insurance risk in the same sense. Surety administration centers on the principal, the obligee, the bond form, the facility it draws on, and the indemnity behind it. That shape is the difference, and it is why a general core system rarely fits without a lot of work.
Who it is built for
- National and regional surety carriers
- Specialty insurers writing surety
- Surety MGAs and MGUs
- Program administrators
- Fronting and capacity providers
- Heads of surety and chief underwriting officers
- Directors of bond operations
- Heads of insurance systems and CIOs
Agents, brokers, principals, and obligees work in the portals. They are not who buys the platform.
A bond, from submission to close‑out
- 01Submission arrives from a broker
- 02Principal and financials assessed
- 03Authority and facility checked
- 04Quoted, approved, and bound
- 05Bond issued and administered
- 06Exposure monitored across the book
- 07Claims, recovery, and close‑out
Where the month goes
A surety operation can run on a legacy bond system, a core system, spreadsheets, Word templates, shared drives, and email at the same time. These are the seams.
Submissions rekeyed by hand
Agent templates vary by broker, principal, and bond class, so intake starts with retyping before any judgment is applied.
Authority limits kept outside the system
The matrix lives in a document, referrals move by email, and consistency depends on who opens the file.
Facility limits a week behind
Aggregate utilization is in a workbook that reflects where the book was, not where it is now.
Bond events across workbooks
Riders, continuations, cancellations, and releases tracked separately from the bond they belong to.
Exposure assembled quarterly
Concentration by principal, corporate group, obligee, and bond class arrives after the decisions that created it.
Collateral tracked somewhere else
Cash, letters of credit, securities, and indemnity agreements held apart from the obligations they secure.
What the platform covers
Submissions
Broker email, portal, and scanned applications turned into structured files.
- Classification on arrival
- Application and financial data extracted
- Missing information detected early
- Duplicate submissions found
Underwriting and authority
The matrix in the system, not in a binder.
- Authority configured to your rules
- Referral routing and approvals
- Four‑eyes review where required
- Decision history on the record
Financial assessment
Statements, work in progress, and bond history in one view.
- Financial statement intake
- Work‑in‑progress schedules
- Prior bond and claim history
- Credit and ratio analysis
Facility and capacity
Single and aggregate limits as they stand now.
- Facility structures by carrier
- Utilization and availability live
- Alerts before issue, not after
- Authority breach detection
Quotation and bond issuance
The document produced from the decision that approved it.
- Quote from the underwriting record
- Bond forms and templates
- Approvals and signature flow
- Surplus lines handling
Bond administration
Riders, continuations, cancellations, releases, close‑out.
- Full lifecycle on one record
- Version history and audit trail
- Continuation and renewal diary
- Obligee and bond form management
Collateral and indemnity
Cash, letters of credit, securities, and real property.
- Collateral set at underwriting
- Allocation across a principal
- Indemnity matched to obligations
- Release and recovery workflow
Claims and recovery
Demand through settlement, and the recovery that follows.
- Demand validation
- Reserves, payments, and legal
- Subrogation and recovery monitoring
- Notifications for capacity providers
Exposure and portfolio
Concentration surfaced as it builds.
- By principal and corporate group
- By obligee, bond type, and class
- By industry and geography
- Drill‑down to the bond
Reinsurance
Treaties and cessions tied to the bonds behind them.
- Treaty and cession records
- Bordereaux and recoverables
- Claims notification
- Settlement tracking
Portals and reporting
Agent, principal, obligee, and capacity‑provider workflows.
- Agent submission and status
- Obligee bond verification
- Capacity provider oversight
- Reporting from one record
Find the right solution for your needs
What happens to a bond after it is issued
Issuing the bond is the short part. Most of a surety operation’s work happens in the years afterward, and most of it happens to bonds somebody else wrote.
-
01Riders and amendments
A change to the obligation is versioned against the bond it changes, with the approval that allowed it attached.
-
02Continuations
Continuation certificates run from a diary rather than a reminder, with the facility position checked before each one.
-
03Cancellations and releases
Record cancellations, releases, and the obligee notice that goes with them against the bond and the collateral behind it.
-
04Version history
Every state the bond has been in, who changed it, and under whose authority.
-
05Obligee and bond form
The form a given obligee requires, held once and applied consistently rather than remembered by whoever writes it.
-
06Close‑out
Final release, collateral return, and the point at which exposure actually ends rather than appears to.
Knowing where you stand before you bind
Facility utilization in a spreadsheet tells you where the book was the last time someone updated it. The question an underwriter actually has is whether this bond, for this principal, against this facility, is inside authority right now. That is a different question, and it has to be answerable at the desk, not at month‑end.
Facility
- Single and aggregate limits
- Utilization and availability live
- Structures by carrier and panel
- Position checked before issue
Authority
- Matrix configured to your rules
- Limits by underwriter and class
- Referral routing and sign‑off
- Breach detected, not discovered
Evidence
- Approval chain on the record
- Carrier approvals stored
- Audit trail by default
- Reporting to capacity providers
Why surety claims are not property and casualty claims
-
The surety is not the insurer
In a property or casualty claim the carrier insures the policyholder against a loss. In surety, the principal is not the insured. The surety guarantees the principal’s obligation to the obligee, and when it pays, it pays the obligee for the principal’s failure.
-
Payment is the start, not the end
Once the obligee is paid, recovery begins: against the principal under the indemnity agreement, and against whatever collateral was taken at underwriting. A paid claim is an open recovery file, not a closed one.
-
The file can run for years
Legal proceedings, subrogation, and recovery litigation extend the lifecycle well beyond the bond term. Case management, documentation, and capacity‑provider reporting have to hold for all of it.
-
Collateral and indemnity decide the outcome
What was secured at underwriting, how it was allocated across the principal’s obligations, and whether indemnitors were properly executed are the facts that determine net loss. They are underwriting decisions that only surface in claims.
Bond classes and programs
- Contract surety
- Commercial surety
- Court and judicial
- License and permit
- Customs and tax
- Fidelity‑adjacent obligations
- Multi‑program structures
- Multi‑carrier facilities
- Delegated authority programs
What it connects to
A surety operation sits between brokers, principals, obligees, capacity providers, and its own finance and claims systems. These are the connection types supported; which counterparties are connected is agreed during discovery.
Distribution
- Agent and broker submission channels
- Status and document return
- Obligee bond verification requests
Financial data
- Financial statement and credit sources
- Work‑in‑progress schedule intake
- Rating and reference data
Documents
- Bond form and template generation
- Electronic signature
- Document store and retention
Finance and capacity
- General ledger and premium accounting
- Payment and collateral records
- Reinsurance and capacity reporting
Implementation and deployment
Implementation runs from four weeks to six or nine months, depending on the number of functionalities. Exact timelines are agreed upfront. The platform is deployed on‑premises, in the cloud, or as a hybrid; the model is agreed during scoping, and the functionality remains the same regardless of the choice.
-
Discovery
We map your bond classes, facilities, authority structure, forms, and the reporting your capacity providers expect.
-
Configuration
Programs, authority matrix, bond forms, facility structures, and collateral rules are configured against that map. Integrations are built for the counterparties agreed in discovery.
-
Migration and parallel run
In‑force bonds, their history, and open claims move across, and both systems run side by side while continuations and renewals are checked against the old record.
-
Go live and support
The legacy environment is retired once the parallel period reconciles. Support continues under an agreed service level.
Why DICEUS
-
Fifteen years building insurance software products
-
Policy administration, underwriting, claims, reinsurance, and reporting already built
-
Delegated authority and capacity work that shares the surety pattern
-
Configured to your bond forms and authority rules, not to a template
-
On‑premises, cloud, or hybrid, agreed during scoping
-
One team from discovery through migration and support
See a bond run from submission to close‑out, against your own bond classes
Book a demo
Frequently asked questions
What is the difference between a bond administration system and a policy administration system?
A policy administration system is organized around policies and insured risks. Surety is organized around the principal, the obligee, the bond form, the facility it draws on, and the indemnity behind it. The data model is different, which is why bolting surety onto a general core system takes longer than it looks.
We already run a core system. Do we have to replace it?
No. Many surety operations keep the core system and replace only the bond administration environment around it, with the two integrated. What gets replaced is agreed in discovery rather than assumed.
Can you migrate our existing bonds and their history?
Yes, and the history is the point. In‑force bonds, prior versions, open claims, collateral records, and continuation diaries move across, and both systems run side by side while continuations and renewals are checked against the old record.
Does it handle more than one facility and more than one carrier?
Yes. Facility structures are configured independently, with their own limits and authority rules, and the system tracks utilization and exposure across the portfolio rather than per facility.
How is AI used, and who approves what?
AI is embedded in the workflow rather than sold separately. It is designed to assist with submission intake, document extraction, financial analysis, missing‑information detection, and exception flagging, with human approval at every material step and an audit trail attached.
