> For the complete documentation index, see [llms.txt](https://docs.uptiq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uptiq.ai/document-ai/document-ai-1/document-extraction.md).
# Document Extraction
Document Extraction runs uploaded files through OCR, layout analysis, and an LLM extraction pipeline, then presents the result for human review and correction. It draws on the platform's full 115-type registry — financial statements, tax forms, bank statements, credit reports, real estate documents, ID documents, and more. See [Document Types](/document-ai/document-ai-1/document-types.md) for the complete list.
In the UI, Document Extraction lives under **Capabilities > Extraction**, with quick-start entry points from the Home dashboard and the sidebar's **+ New Document** button.
| Capability | Description | Limit |
| ------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------- |
| Document upload | Upload a single file or a batch (ZIP) for extraction | 500 MB max per ZIP, 100 MB max per file within a ZIP |
| Supported file types | PDF, images, Office formats, and structured text | PDF, PNG, JPG, JPEG, GIF, WEBP, SVG, BMP, TIFF, XLS, XLSX, DOC, DOCX, TXT, CSV, JSON, XML, HTML |
| List filters & search | Filter the extractions list by status, a curated shortlist of common types, or processor (single/batch); search by name | Type quick-filters are a curated subset of the full 115-type registry used when choosing a document type for extraction |
| Extraction result review | Review extracted fields against the source document, by document type; the list also shows processor and an overall confidence score per extraction | 115 registered document types — see [Document Types](/document-ai/document-ai-1/document-types.md) |
| Chart of Accounts (COA) review | Review and adjust rollup calculations for balance sheet, P\&L, and property operating statements | Form 8825: full extraction for the first 50 properties, basic info only beyond that |
| Human corrections | Submit a corrected value for a field; recomputes confidence for that field | — |
| Signed document URLs | Generate a time-limited link to the source document | 1–168 hours |
| Preview URLs | Generate a time-limited preview link | 1–24 hours |
{% hint style="info" %}
Extraction results over 15 MB are offloaded to blob storage rather than stored inline (MongoDB's per-document limit is 16 MB).
{% endhint %}
### Workflow
1. **Upload** — add a document or a ZIP batch from the Extractions list, choosing a document type from the 115-type registry and, optionally, a model (GPT-4.1, GPT-5.1, Gemini 3, or the account default). Advanced parameters let you toggle caching, document analysis, layout inclusion, LLM-judge validation, quick-extract mode, and raw-extraction-only mode, or supply industry context, a webhook URL, a custom extraction prompt, agent instructions, or metadata.
2. **Processing** — the extraction moves from `Pending` to `Processing`. Large PDFs (over 40 pages) use a combined native-PDF-plus-markdown extraction path; documents between 10 and 40 pages use an enhanced extraction pipeline.
3. **Classification** — for multi-document PDFs, the system samples at least 20 pages to detect document type boundaries before extraction.
4. **Result** — status moves to `Processed` (or `Failed`). The result includes the extracted fields, layout data (bounding boxes and table structure), and, for V2 processing, a document categorization pass.
5. **Review** — open the extraction to review fields against the source document, using the reviewer for that document type (for example, the Balance Sheet reviewer or Bank Statements reviewer).
6. **Correct** — submit a correction for any field. This recomputes the confidence score for that field and feeds the correction into the error-pattern feedback loop used to improve future extractions.
7. **Chart of Accounts review** (balance sheet, P\&L, and property operating statement types only) — review and adjust account rollups, including Form 8825 property-level detail.
```
Pending → Processing → Processed
→ Failed
```
{% hint style="info" %}
Confirmed for all four roles (Owner, Admin, Member, Viewer): full access to the extractions list and upload flow, with no role-specific restriction observed.
{% endhint %}
{% hint style="warning" %} Opening an extraction detail page for a record that can't be resolved (for example, an ID linked from a Webhooks event whose extraction was since deleted) shows a perpetual "Loading extraction..." spinner behind a "Server Error" toast, rather than a clear not-found state.
{% endhint %}
### Supported Document Types
Document Extraction draws from the platform's single 115-type registry — the same registry used by [Document Classification](/document-ai/document-ai-1/document-classification.md). For the complete, authoritative, categorized list, see [Document Types](/document-ai/document-ai-1/document-types.md).
{% hint style="info" %}
Additional document types can be registered dynamically without a code change — new types are picked up automatically by classification and extraction routing, by adding a YAML config file. See [Document Types](/document-ai/document-ai-1/document-types.md) for how the registry works.
{% endhint %}
### Related pages
* [Document Classification](/document-ai/document-ai-1/document-classification.md) helps route unknown or mixed files before extraction starts.
* [Document Types](/document-ai/document-ai-1/document-types.md) defines the supported types and field schemas this flow uses.
* [Test Dashboard](/document-ai/document-ai-1/test-dashboard.md) benchmarks extraction quality, and [Webhooks & Integrations](/document-ai/document-ai-1/webhooks-and-integrations.md) pushes results to downstream systems.
***
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.uptiq.ai/document-ai/document-ai-1/document-extraction.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.