Claim intake
Imports · Documents · Messaging
New claims arrive as files or forms. QBO opens each one as a case on the policy and starts the workflow that claim type needs, and inbound email links itself to the claim, attachments included.
Cookies
We’d like to use analytics and advertising cookies to understand how the site is used and which ads bring visitors here. They stay off unless you allow them. See our privacy policy.
Solutions · Insurance claims & policy workflow
Claims and policy workflow management in one system: QBO runs claims, policy servicing, and subrogation as connected workflows on the policy. Independent adjusters, repair vendors, and outside counsel work in the same system, and each sees only the files assigned to them.
In production in insurance · Since 2003
Independently audited · SOC 2 Type 2 report · ISO 27001:2022 certified ISMS · Trust Center ↗
Insurance operations
Each job below is built from the same platform building blocks, configured with templates rather than custom code. That’s why a claim, a renewal, and a recovery can share one policy record, one audit trail, and one set of partners.
Imports · Documents · Messaging
New claims arrive as files or forms. QBO opens each one as a case on the policy and starts the workflow that claim type needs, and inbound email links itself to the claim, attachments included.
Cases · Workflow · Rules
Each claim is a case with its own workflow, deadlines, and status. Rules choose the workflow from the claim’s data, such as state or coverage amount.
Contacts · Extranet security
Keep independent adjusters, repair vendors, and counsel on file with their licenses and certificates, then let them work their assignments directly in QBO.
Cases · Ledgers · Documents
Open recovery as its own case, assign it to counsel, generate the demand package from claim data, and post costs and recoveries to its ledger.
Cases · Documents · Workflow
Onboarding, renewals, and annual reviews run as cases on the policy, so each one keeps its own documents, tasks, and outcome instead of crowding one file.
Imports · Workflow · Worklists
Load the loans that need coverage, send required notices on schedule, and route data discrepancies with your lender clients to a worklist until they’re resolved.
Adjusters, vendors & counsel, in the same system
QBO’s extranet security filters every screen and API call by row, automatically. Assign a claim to an independent adjuster and they see that claim and everything beneath it. Ask a vendor for an estimate and they see the estimate. Refer a recovery to counsel and the rest of the policy stays out of view.
| Record | Claims team | Independent adjuster | Repair vendor | Subrogation counsel |
|---|---|---|---|---|
| Policy HO-204817 | Visible | Visible | Visible | Visible |
| Renewal review | Visible | Hidden | Hidden | Hidden |
| Water damage claim | Visible | Visible | Hidden | Hidden |
| Field inspection | Visible | Visible | Hidden | Hidden |
| Repair estimate | Visible | Visible | Visible | Hidden |
| Subrogation | Visible | Hidden | Hidden | Visible |
| Demand package | Visible | Hidden | Hidden | Visible |
Illustrative data. Each record shown is a case, task, or document on the policy.
How extranet security works →The policy is the record
QBO’s policy record links the insurer and the insured, and holds the terms your workflows depend on. Each claim, onboarding, and annual review opens as its own case on the policy, with its own documents, tasks, messages, workflow, and ledger. Years later, you can still find which claim was paid, which was denied, and why.
Add any other fields your lines of business need, and they’re stored and merged like the rest.
How cases orchestrate the work →Rules route the work
When a claim opens, a weighted rules matrix picks its workflow from the claim’s data. For example, claims in New York and New Jersey can start a metro outreach workflow, and claims with $1 to $5 million in coverage a high-value workflow, while everything else takes the standard path.
From there, smart worklists hand each task to the right team and person by rule. Due dates count business time on your calendar, completed claims can be sampled for quality review, and workflows generate letters and review documents from claim data at the step that needs them.
How worklists route work →Proven in insurance
Placeholder · customer story pending approval
A named customer, the work they run on QBO, and one approved proof point will appear here once the customer approves them.
FAQ
No. QBO sits above your systems of record and orchestrates the work around them: the cases, documents, tasks, partners, and deadlines. It exchanges data through its API, file imports, and webhooks. Quandis doesn’t offer prebuilt connectors for specific policy administration or claims platforms; connections use the API, imports, or webhooks.
Yes. Extranet security filters every screen and API call by row. A partner assigned to a claim sees that claim and the records beneath it, and nothing else on the policy or in your book. Access updates automatically as assignments change.
A weighted rules matrix picks the workflow when a claim opens, from data such as state or coverage amount. Smart worklists then assign each task to a team, person, and priority by rule, and measure due dates in business time on your calendar.
AI can classify incoming documents, extract data with confidence scores, transcribe audio, and draft review memos and email replies for people to check. Your workflow decides when a model runs and where the result lands, and you choose the provider: Claude, Gemini, OpenAI, or Amazon Bedrock.
Yes. Insurance is one of the three industries where QBO is in production, alongside mortgage servicing and credit unions.