Intelligent document processing
Every field extracted,
scored, and accounted for.
DAN reads invoices, federal forms, contracts, statements, and scanned records, then returns structured data with a confidence score on every field and a reviewer trail on every decision. Built for teams that have to defend the output, not just produce it.
- Uncertain values route to a named reviewer, not straight to your system of record.
- Every extraction, edit, approval, and export is logged for oversight requests.
- Runs in government cloud, your private VPC, or fully on premises.
18+
Document types supported out of the box
0 to 100
Confidence score returned on every field
100%
Of exports written to an immutable audit log
Extracted fields
Confidence
Illustrative sample data. Field names, values, and confidence figures shown are for demonstration.
Built for
Federal agencies
Shared services, finance offices, program bureaus, and records management.
State and local government
Benefits, permitting, licensing, courts, and county clerks.
Enterprise operations
Accounts payable, procurement, shared service centers, and audit teams.
Systems integrators
Embed extraction inside a modernization program under your own delivery contract.
The backlog
The document is not the problem. The unverifiable copy of it is.
Everything got scanned. What came back was an image and some loose text, and someone still has to retype the number into a finance or case system.
Keyed by hand
Vendor
Meridian Supply Co.
Invoice number
INV-40823
Total
13,451.00
Terms
Net 30
Transposed at entry. Caught at audit, four months later.
Read by DAN
3 posted automatically. 1 sent to a named reviewer with the page attached.
Illustrative. Same document, two ways of getting the number out of it.
What you have today
- /Repetitive keying
- /Spreadsheet cleanup
- /Copy and paste from OCR text
- /Verification delays
- /Errors found at audit
- /No reviewable record
What replaces it
- +Field level extraction
- +Confidence on every value
- +Rules before export
- +Side by side review
- +Signed action history
- +Clean export to the system of record
Intake
Pick documents up from wherever they already are
Nobody should have to move files into one place before the work can start. DAN connects to the systems your documents already live in, watches the folders and mailboxes they arrive in, and takes hardcopy straight off a scanner or a phone camera.
Connected sources
Arriving now
QueuedFY26_invoice_batch.pdf
Invoice · 14 pages
PO-2026-0448.pdf
Purchase order · 2 pages
facture_avril_2026.pdf
Invoice · 3 pages
Rechnung_88213.pdf
Invoice · 1 page
intake_form_p1.tif
Benefits application · 4 pages
receipt_0714.jpg
Receipt · 1 page
contrato_servicios.pdf
Contract · 22 pages
doc_9f31c204
Delivery note · 2 pages
Applied on arrival
- +Document type classified
- +Language detected
- +Extraction schema matched
- +Queued with source recorded in the audit log
Illustrative intake stream. Connector availability is confirmed for your deployment during scoping.
Cloud storage
Where the files sit
Point DAN at a Google Drive folder or a SharePoint library and it processes what is there, then keeps watching for what lands next.
- Google Drive
- SharePoint and OneDrive
- Network and watched folders
- Object storage buckets
Where they get sent
Give the platform a dedicated intake address, or connect the shared mailbox vendors and applicants already write to. Attachments are pulled and queued automatically.
- Gmail and Google Workspace
- Outlook and Microsoft 365
- Shared and functional mailboxes
- Forwarding intake address
Hardcopy
Paper that never got digitized
Scan from the office multifunction device straight into the queue, or photograph a page on a phone at the counter or in the field.
- Scanner and MFP
- Mobile photo capture
- Bulk backfile scanning
- Skewed and low quality scans
Systems
Whatever runs upstream
Post documents from a case system, portal, or existing pipeline, and get the structured result back on a signed webhook.
- REST API
- Batch drop
- Signed webhooks
- Portal and case system feeds
Handwriting
Forms filled in by hand still count
Handwritten entries on printed forms, signatures, dates, annotations in the margin, and checkbox marks are read alongside the printed content. Handwriting scores lower than clean print, which is the point: those fields surface for a reviewer instead of posting quietly.
Languages
Multilingual documents, one output schema
Language is detected per document, including mixed language pages and right to left and non Latin scripts. Field names in the output stay in your schema regardless of the source language, so a French invoice and an English one land in the same columns of your system of record.
Sequence
Capture, extract, verify, export.
Four stages, in order, each one recorded. Nothing skips verification on its way to your system of record.
Capture
Extract
Verify
Export
Capture
Dashboard, watched folder, email intake, batch drop, or API. PDF, PNG, JPG, WEBP, and multi page scans.
Extract
The document is classified, then read against the schema for its type. You get named fields, not a wall of text.
Verify
Values above your threshold pass. Anything below it opens beside the source page for a named reviewer.
Export
Verified records move to your ERP, financial system, or case platform as JSON, CSV, Excel, or a signed webhook.
Planning tool
How much human review will you actually need?
The threshold is your control, not ours. Set it high and more fields go to a reviewer. Set it lower and more post automatically. Move the inputs to see how that lands against your volume.
An illustrative planning model based on the threshold you choose, not a performance guarantee. Actual routing rates depend on scan quality, document mix, and your configured schemas.
1,000 to 1,000,000
Invoice 18 to 24 · Federal form 30 to 45 · Contract 40 to 70
80 is permissive · 99 sends nearly everything to a reviewer
Fields processed
550,000
per month
Posted automatically
94.6%
of extracted fields
Routed to review
29,865
fields per month
Reviewer time
66
hours per month, at 8 seconds a field
Where it goes to work
Wherever paper still sets the pace of a program
Accounts payable
Match invoice, purchase order, and receiving note. Flag totals that do not reconcile before payment.
Grants administration
Award identifiers, reporting periods, and expenditure figures out of progress reports and closeout packages.
Benefits and eligibility
Income, residency, and identity evidence from applicant uploads, so caseworkers make determinations instead of transcribing.
Permits and licensing
Applications, site plans, and supporting certificates become structured intake records.
Contract files
Parties, period of performance, ceiling values, option years, and renewal dates from contracts and modifications.
Backfile conversion
Decades of scanned case files turned into indexed metadata for retention schedules and records requests.
Financial reconciliation
Transactions, balances, and statement periods for reconciliation, grants monitoring, or investigation support.
Hiring and onboarding
Resumes, credentials, and certifications parsed into structured candidate records for classification and verification.
Logistics and receiving
Delivery notes, bills of lading, and shipping records update property and inventory without a second entry pass.
Platform
Built for documents you cannot afford to get wrong
Field level extraction
Named fields with source coordinates, so every value traces back to its exact place on the page.
Headers · Line items · Tables · Signature blocks
Confidence scoring
A score from 0 to 100 on every field. Set the threshold per schema or per program.
Per field scores · Auto approval · Review routing
Custom schemas
Define the output shape once. Every extraction conforms to it, using your downstream field names.
Field mapping · Type constraints · Program specific schemas
Multi page processing
Long PDFs stay one document with continuity across pages, not a pile of images.
Long contracts · Financial reports · Case packets
Human verification
Reviewers see the value and the original page together, edit in place, and sign off.
Side by side view · Editable fields · Named approvals
Validation rules
Arithmetic checks, vendor matching, date logic, and duplicate detection before anything exports.
Total checks · Vendor matching · Duplicate detection
Security and governance
Reviewable AI. Encrypted by default.
The security review is usually the longest part of a government purchase. Every action in the platform writes a line your assessor can read.
Audit logging
Append only record of every upload, extraction, edit, approval, and export, with actor, timestamp, and prior value.
Encryption
In transit and at rest, with customer managed keys on private and on premises deployments.
Access control
Role based permissions, separated reviewer and approver duties, and single sign on through SAML or OIDC.
Residency and retention
Pick the region, set purge schedules to match your records policy, keep source documents in your own boundary.
Secure integration
Scoped API keys, token authentication, signed webhook events, and IP allow listing.
No blind automation
You decide which fields a model is ever allowed to approve on its own. Everything else waits for a person.
Control alignment
- NIST SP 800 53 aligned controls
- FISMA aligned documentation
- SOC 2 aligned operational practices
- FedRAMP and StateRAMP paths with a sponsoring agency
- Section 508 and WCAG 2.1 AA developed against
Honest scope
DAN is built for business, financial, and administrative document workflows, not HIPAA regulated clinical processing. If your program handles controlled unclassified information, criminal justice information, or tax return data, say so early so the control set is scoped correctly.
Alignment statements describe how the platform is built and documented. Specific authorizations and certifications are confirmed in writing for your deployment during procurement.
Deployment
Run it where your data is allowed to live
Extraction engine, review interface, and audit store deploy together inside one boundary. Nothing has to leave it.
Your authorization boundary
Egress blocked
Documents, extracted values, and the audit trail stay inside the perimeter you authorize.
Option A
Government cloud
AWS GovCloud or Azure Government inside your tenancy, with regional residency and your own key management.
- US regions only
- Customer managed keys
- Agency identity provider
Option B
Private cloud or VPC
A dedicated single tenant instance in your own cloud account, peered to the systems it needs and nothing else.
- Single tenant
- Private networking
- No shared processing
Option C
On premises and disconnected
Installed in your data center, including environments with no outbound internet access at all.
- Air gapped capable
- Offline model updates
- Local audit store
For your integration team
One endpoint. Clean JSON. Signed webhooks.
Post a document, receive structured fields with confidence values, subscribe to a webhook for the review outcome.
- REST API access
- Scoped API keys
- Token authentication
- Batch upload support
- Async processing status
- Signed webhook events
- Structured JSON responses
- Retry and replay controls
curl -X POST https://api.dan.example.gov/v1/documents \
-H "Authorization: Bearer $DAN_API_KEY" \
-F "file=@invoice.pdf" \
-F "schema=ap_invoice_v3" \
-F "confidence_threshold=92"{
"document_id": "doc_9f31c204",
"schema": "ap_invoice_v3",
"status": "review_required",
"fields": {
"vendor_name": { "value": "Meridian Supply Co.", "confidence": 99 },
"invoice_number":{ "value": "INV-40823", "confidence": 98 },
"po_reference": { "value": "PO-2026-0448", "confidence": 94 },
"total_amount": { "value": "13541.00", "confidence": 98 },
"payment_terms": { "value": "Net 30", "confidence": 87 }
},
"routed_to_review": ["payment_terms"],
"audit_ref": "aud_2026_07_14_0113"
}Evaluation
What an evaluation committee usually asks about
The differences that matter are rarely about raw accuracy claims. They are about whether the output can be defended.
| Capability | Manual entry | Traditional OCR | Generic AI tool | DAN platform |
|---|---|---|---|---|
| Structured field output | None | Partial | Inconsistent | Schema enforced |
| Per field confidence score | None | None | None | Every field |
| Human review workflow | Is the workflow | External | External | Built in |
| Traceability to source page | None | Limited | None | Field coordinates |
| Audit log for oversight | Spreadsheets | None | Chat history | Append only |
| Custom extraction schemas | Not applicable | Template bound | Prompt dependent | Versioned |
| API and webhook automation | None | Rare | Limited | REST and signed events |
| On premises or air gapped option | Not applicable | Sometimes | Rarely | Supported |
Buying and engagement
Scoped to your program, priced to your contract
There is no public price list. Volume, schema count, deployment model, and support level all move the number, so we scope against your actual mix and give your contracting officer a firm figure.
Most agencies start with a paid pilot on one document type in one office, then expand once they have seen the review rate in their own environment.
Start a scoping conversationTypical engagement path
Phase 1
Document assessment
We run a representative sample of your real documents and report back on field coverage and expected review rate.
Phase 2
Scoped pilot
One document type, one office, live volume, with schemas configured and reviewers trained on your workflow.
Phase 3
Program rollout
Expansion across document types and offices, with system of record integration and ongoing support.
Contracting
We work with your contracting office to identify a suitable path, which may include a federal wide acquisition or multiple award schedule vehicle, a state term contract or cooperative agreement, a task order under an existing modernization contract, or a subcontract and teaming arrangement with your prime integrator. Current vehicle availability is confirmed in writing before you rely on it.
- Standard terms available for legal review
- Section 508 accessibility conformance reporting
- Security questionnaire and control matrix
- References supplied on request under NDA
Questions