Skip to content
QUANDIS

QDocs · Intelligent document processing

Every document split, filed, and read. Then put to work.

QDocs turns incoming packages into individual, classified documents on the right record, and turns what’s inside them into data your workflows act on, with a confidence on every value and a person reviewing anything uncertain.

QDocs · Claim packet · 41 pagesComplete

Split & classified

First notice of lossp. 1–3
Police reportp. 4–9
Repair estimatep. 10–14
Photosp. 15–41

Extracted · claim fields

FieldValueConfidence
Date of loss2026-08-140.97
Estimate total$8,412.500.94
Policy numberHO-482130.41 Review
Illustrative example, not customer data. Confidence is reported by the model for each field.

Orchestrated, not bolted on

Most document AI stops at output: a file of extracted fields that someone still has to load, check, and act on. In QDocs, a workflow step calls the model and the answer comes back as ordinary data on the record, where your rules, worklists, and next steps are already waiting.

Why QDocs

Built for the team that owns intake, accuracy, and rework.

01

Filed right, the first time

Mixed packages are split into individual documents, each one is classified against the document types you define, and every document lands on the record it belongs to. No manual prep, no re-indexing.

  • Split by AI, bookmarks, page ranges, or size
  • Classified against your own document templates
  • Duplicate files caught by file hash
02

Data your workflows can use

The fields you care about are extracted as typed values (dates, amounts, yes/no, text), each with its own confidence. Rules, workflows, and reports use them like any other data.

  • Typed values with per-field confidence
  • A weighted confidence for the whole document
  • Documents turned into records, including nested ones
03

People review what matters

Confident results flow straight on. Uncertain ones go to a person, on a worklist, with the source document beside the value. Every step runs inside your security and your audit trail.

  • Rules route low-confidence results to review
  • AI runs as the calling user, on records they can reach
  • Token costs posted to a ledger

How it works

From a stack of pages to the next step in seven stages.

Each stage is a step in a QBO workflow, so you choose which stages run, in what order, and for which document types. Stages marked AI · built in call the model you configured; the rest are standard platform operations.

  1. 01

    Ingest

    Platform

    Upload, drag and drop, the API, inbound email, or a watched sFTP or cloud folder.

    Lands asA document on a record, in your storage

  2. 02

    Split

    AI · built in

    A multi-document PDF is broken into its individual documents.

    Lands asOne document per segment, linked to the source package

  3. 03

    Read

    Platform

    OCR extracts the text, so every page is searchable.

    Lands asSearchable text on the document

  4. 04

    Classify

    AI · built in

    Each document is matched to one of your document types, and labeled.

    Lands asThe document’s template and labels

  5. 05

    Extract

    AI · built in

    The fields you define are read from the text, or from the original PDF or image.

    Lands asA score: typed values, each with a confidence

  6. 06

    Review

    Platform

    Rules send low-confidence or missing values to a worklist for a person to check.

    Lands asA task on the right worklist

  7. 07

    Act

    Platform

    Workflows, rules, and decisions use the data: open a case, generate a letter, notify a partner.

    Lands asThe next step in your process

Classification can also run in the same pass as splitting, with the fields for each document type extracted at once. See how QBO manages documents and how scores store extracted values.

Capabilities

Configured with templates you describe in plain English.

Document types, labels, and fields are templates. Describe each one the way you’d brief a new colleague, and QDocs uses that description as its instructions. Adding a document type is a template edit, not a project.

Document splitting

AI · built in

Send a compound PDF to a multimodal model and get back one document per segment, each typed and linked to the original package. Or split by bookmarks, explicit page ranges, or file size, with no AI at all.

Classification

AI · built in

The model chooses among your document types using the plain-English description on each one, running OCR first when it needs to. Unmatched documents fall back to a default type you choose.

Labels

AI · built in

Apply every label that fits, such as language, sentiment, or a review flag, from labels you describe. Existing labels aren’t duplicated.

Extraction with confidence

AI · built in

Write a prompt for each field, choose its type, and optionally weight it. Every value comes back with a confidence, and the document gets a weighted confidence across all fields.

Read the original

AI · built in

When layout, tables, handwriting, or images matter, the model reads the original PDF or image instead of OCR text.

Documents to records

AI · built in

Turn a document into new records through the standard import path, including nested children, such as line items under an invoice, with a preview before anything is saved.

Audio transcription

AI · built in

Transcribe recorded calls and voicemail (mp3) into searchable text, and optionally score the transcript in the same step.

Duplicates and auto-indexing

Find identical files by hash before they’re processed twice, and file bulk-loaded documents to the right type and record from their file names.

Use cases

Wherever work arrives as documents.

A loan file, a claim packet, a lease, an application: the documents differ, the job doesn’t. Here’s how teams in each industry use QDocs.

Lending & servicing

A loan file arrives as one scan or a stack of uploads. QDocs turns it into an indexed, verified file.

Loan file indexing
Split a scanned loan file into its notes, deeds, statements, and disclosures, each filed under the right type on the loan.
Trailing documents
Recognize recorded documents and final policies as they arrive, extract the recording details, and close the open task.
Income and asset review
Extract amounts and dates from pay stubs and statements, and send anything uncertain to an underwriter’s worklist.

Insurance

A claim packet mixes forms, reports, estimates, and photos. QDocs sorts it before an adjuster opens it.

Claim intake
Split a first-notice packet into its forms, reports, and estimates, and file each on the claim.
Estimate and invoice data
Extract totals, dates, and line items from repair estimates and invoices as typed values your reserve rules can check.
Policy documents
Classify declarations pages and endorsements, and read effective and expiration dates onto the policy record.

Commercial real estate

Leases and property files are long, inconsistent, and full of dates that matter.

Lease abstraction
Read the term, rent, escalations, renewal options, and notice dates from each lease, with a confidence for every field.
Critical-date tracking
Turn extracted dates into tasks with due dates, so a renewal or notice deadline is never discovered late.
Property packages
Split due-diligence packages into appraisals, surveys, title, and estoppels, and file them on the property.

Applications & onboarding

Credit unions, lenders, and insurers all onboard people with documents.

Application packets
Classify IDs, proofs of income, and supporting documents as they arrive, so rules can check the packet is complete before review.
Forms to records
Turn a completed application into contact, account, and related records instead of re-keying it.
Exceptions, not inboxes
Route only the documents that need a person to a worklist, in priority order.

Life sciences

Study and site documentation is high volume, regulated, and audited.

Site packets
Classify the documents in each site or study packet, so rules can check that every required document is present.
Signature and date checks
Extract signature and version dates so rules can confirm a document is current before work proceeds.
Audit-ready filing
Keep every document, extracted value, and review decision on the record, in one audit trail.

See how QDocs fits into mortgage servicing, insurance, and credit union operations.

Scale & cost control

One document or a whole backlog.

The same configuration runs a single document in real time or a backlog as a provider batch job. Token use is managed and accounted for, so AI cost is a line item, not a surprise.

Model providersClaude · Gemini · OpenAI · Amazon Bedrock
Chosen per agent by configuration. Use one model for splitting and another for extraction.
Batch processingProvider batch jobs
Large volumes are submitted as provider batch jobs through QBO’s queue, polled on a schedule, and applied document by document as results arrive.
Context cachingGemini
Long instructions, such as a full catalog of document types, are cached and reused across documents instead of being re-sent with each one.
File reuseGemini · OpenAI
An uploaded document can be kept with the provider for a set time, so scoring it again doesn’t upload it again.
Cost accountingToken ledger
Input, cached input, output, and reasoning tokens are posted to a ledger at per-model rates, so AI cost is reported like any other cost.

Integration

Fits the storage and systems you already run.

Documents stay in your storage: Amazon S3, Azure, Google Cloud, sFTP, or a network share. Every QDocs stage is an operation on the same API pattern as the rest of the platform, and long-running work is queued for app servers so your intake never waits.

Split a package (queued)

GET /api/attachment/queue/pdfsplit?ID=2207

Classify a document

GET /api/attachment/aiclassify?ID=2208&AgentName=Gemini

Label a document

GET /api/attachment/ailabel?ID=2208&AgentName=Gemini

Extract fields into a score (queued)

GET /api/score/queue/calculate?Template=Repair Estimate&Object=Attachment&ObjectID=2208

Illustrative IDs and names. /api/{module}/{operation} runs synchronously; /api/{module}/queue/{operation} queues the work for an app server.

Works with

FAQ

QDocs questions

What is QDocs?

QDocs is Quandis’ intelligent document processing product. It splits document packages, classifies each document, extracts the data you need with a confidence for every value, and routes uncertain results to people for review. Because it runs on the QBO Platform, the results drive your workflows, rules, and worklists directly.

Do I need to train a model on my documents?

No. You describe each document type in plain English and write a prompt for each field you want extracted. Changing behavior is a template edit, not a model training project or a code change.

Which AI models does QDocs use?

QDocs works with Anthropic Claude, Google Gemini, OpenAI, and Amazon Bedrock. You choose the provider and model for each task by configuration and can change them without code.

How are low-confidence results handled?

Every extracted value carries its own confidence, and each document gets a weighted confidence across its fields. Rules use those values like any other data, so you decide which results flow straight through and which go to a worklist for a person to check.

Can QDocs split a single PDF that contains many documents?

Yes. A multimodal model can identify where each document starts and ends, and QDocs saves each segment as its own document, typed and linked to the original package. PDFs can also be split by bookmarks, explicit page ranges, or file size.

Where does my data go?

Documents stay in the storage you configure, such as Amazon S3, Azure, Google Cloud, or sFTP. AI methods run as the calling user, on records that user is allowed to reach, and send content only to the provider you configured. Results come back as ordinary data inside your audit trail. Security documentation is available in our Trust Center.

How do you control AI cost at volume?

Send large volumes as provider batch jobs through QBO’s queue, cache long instructions where the provider supports it (Gemini), and post token usage to a ledger at per-model rates so cost is visible per record, client, or month.

How does a trial work?

QDocs trials run for 30 days on your own sample documents. We’ll agree on the document types, fields, and success criteria with you first. Request a demo to get started.

Documentation

Set up splitting, classification, and extraction, and call them from the API.

Read the QDocs guide →

Built on QBOQDocs runs on the same orchestration platform as everything Quandis builds — cases, documents, rules, audit trails, and partner-safe security included.

Explore the QBO Platform →
Trusted in regulated operationsSince 2003HousingWire TECH100Independently auditedSOC 2 Type 2 reportISO 27001:2022 certified ISMSVisit the Trust Center ↗

Get Started with a Free Trial!

Your privacy matters to us. We never sell your personal information to anyone.