Document Parsing: DeDOC & Layout-Parser
Master document parsing with DeDOC and Layout-Parser: layout detection, table extraction, form processing, and production document AI systems.
What is document parsing?
Document parsing turns a PDF, image, form, or office file into structured records that software can search, validate, and act on. It may extract text, but it must also recover where each item appeared, how items relate, and which source region supports every result.
This matters because a plain text dump destroys evidence. A total can become detached from its currency, a table cell can move under the wrong header, and a footer can be mistaken for body text. The core invariant is therefore: every extracted claim remains traceable to its page, region, parser version, and validation result.
See the document as layers of evidence
A document is not one input. It combines a file container, pages, visual regions, text spans, structural relationships, and business meaning. Each layer can fail independently.
From uploaded bytes to a validated record
The pipeline preserves source coordinates and parser identity while progressively adding structure.
Trust boundary
Intake
Verify type, size, encryption, malware status, tenant, and retention policy before rendering anything.
Pixels and text
Render and transcribe
Read a trustworthy text layer when one exists. Render pages and run OCR only where text is absent or unreliable.
Geometry
Recover layout
Detect regions, reading order, headings, lists, tables, figures, and repeated page furniture.
Relationships
Build evidence
Join tokens into blocks, cells, fields, and sections while retaining bounding boxes and confidence.
Decision
Validate and release
Apply typed rules, cross-field reconciliation, review policy, and destination-specific release gates.
Four questions define the route
- Does a reliable text layer exist? Native extraction is faster and avoids OCR substitutions, but it still needs reading-order and layout checks.
- How complex is the page geometry? Columns, floating figures, marginalia, and repeated headers require explicit region and order modeling.
- Which relationships carry meaning? Forms need label-value links; tables need row, column, span, and header relationships.
- What happens after extraction? Search indexing tolerates different errors than payment, clinical, or compliance automation.
Match the parsing route to the document shape
There is no universally best parser. A route should spend OCR and vision capacity only where they recover evidence that the product contract requires.
Text first
Digital PDF
Start from native spans and coordinates, then reconstruct reading order and tables. Render pages for verification and unsupported regions.
Vision first
Scanned form
Deskew, denoise carefully, detect regions, run OCR or handwriting recognition, and preserve field geometry.
Hybrid
Complex report
Combine native text, rendered-page layout detection, table structure, and section hierarchy across pages.
Classify then route
Mixed bundle
Split attachments, classify page families, and send each family through a measured route instead of one expensive universal path.
Preserve an evidence contract, not just a string
An extraction result should be useful to both software and reviewers. Store the normalized value beside the raw text and its source evidence.
What produced it
Identity
Record the document hash, page, parser and model versions, configuration, and schema version.
Where it came from
Provenance
Keep the raw span, bounding box or polygon, region type, reading-order position, and nearby evidence.
Why it can proceed
Decision state
Store confidence, validator outcomes, review status, corrections, and the policy version that made the decision.
Confidence is a model estimate, not proof of correctness. A parser can be highly confident about the wrong digit. Deterministic checks such as currency parsing, subtotal reconciliation, date bounds, identifier checksums, and expected row counts catch a different class of failure.
Reconstruct tables as relationships
A table is a graph of cells and headers, not lines of whitespace. Flattening it too early hides merged cells, multi-level headers, and continuation across pages.
1 Detection
Find the table region
Separate the table from captions, footnotes, and neighboring columns. Preserve its page coordinates.
2 Structure
Infer rows, columns, and spans
Use borders, whitespace, alignment, token positions, and learned structure signals to propose a cell graph.
3 Semantics
Attach headers
Resolve row and column headers, repeated headers, units, and multi-page continuation before producing records.
4 Validation
Reconcile the result
Check totals, column types, expected keys, and source coverage. Hold ambiguous structures for review.
Test the failure shapes explicitly
- Borderless tables where whitespace and alignment carry the grid.
- Merged cells and stacked headers where one label governs multiple columns.
- Multi-page tables with repeated headers, carried totals, and continuation rows.
- Rotated pages, skewed scans, faint rules, stamps, and handwriting.
- Tables embedded inside forms, figures, or multi-column reading order.
Gate fields before they trigger actions
Replay labeled failures to test the policy. Move the confidence threshold and change the validation depth below. Notice that confidence-only gating can accept a plausible but inconsistent value.
Never let one aggregate confidence score authorize a high-impact action. Gate the specific fields and relationships that the action depends on, and preserve a review path for unsupported or contradictory evidence.
Evaluate the complete product contract
Measure each stage separately and then run end-to-end document tests. A good OCR score can coexist with broken reading order or incorrect table relationships.
Text
Transcription
Character or word error by language, scan quality, font, and handwriting slice
Layout
Regions and order
Region detection, reading order, hierarchy, and page-furniture suppression
Structure
Tables and forms
Cell adjacency, header association, spans, key-value links, and continuation
Fields
Business outcome
Exact values, provenance coverage, reconciliation, review load, and escaped error cost
Build a representative evaluation set
- Partition by source family, language, page count, scan quality, layout class, and parser route.
- Keep hard cases such as blank pages, corrupt files, embedded fonts, handwriting, and mixed orientation.
- Score coordinates and relationships as well as normalized text.
- Review false accepts separately from false reviews; they have different product costs.
- Version documents, labels, schemas, parsers, validators, and review policy together.
Place frameworks inside the architecture
Frameworks implement parts of the pipeline; they do not define the product's evidence contract.
Document decomposition
Dedoc
Dedoc readers produce lines, tables, metadata, attachments, and warnings; structure extractors organize lines into a hierarchy. Verify current format and parameter support against its documentation.
Layout toolkit
Layout Parser
Layout Parser provides abstractions for layout models, coordinates, visualization, and OCR integration. Choose and evaluate models against the actual document domain.
OCR engine
Tesseract
Tesseract can emit text plus hOCR, TSV, ALTO, and PAGE outputs. Keep word confidence and coordinates, but calibrate them on your own scans.
Production ownership
- Intake owner: file safety, tenant isolation, retention, encryption, and render sandboxing.
- Parsing owner: routing, model versions, retries, timeouts, and per-stage telemetry.
- Schema owner: field definitions, normalization, deterministic validators, and change compatibility.
- Operations owner: queue age, cost per page, review capacity, correction feedback, and rollback.
- Risk owner: release thresholds, sensitive-field controls, audit evidence, and incident response.
Use primary references and verify current APIs
- Dedoc documentation for readers, structure extraction, tables, metadata, attachments, and warnings.
- Layout Parser documentation for layout objects, model integration, OCR, and document image workflows.
- Tesseract command-line documentation for text, hOCR, TSV, ALTO, and PAGE output modes.
- DocLayNet paper for a diverse human-annotated document-layout dataset and evidence about domain variability.
Treat library versions, model catalogs, format support, and performance as changeable. Benchmark the exact versions and hardware you intend to operate.