# Advanced table extraction Source: https://www.digiparser.com/docs/guides/parsers/parser-settings/advanced-table-extraction ParsersParser Settings # Advanced table extraction Learn when to use advanced table extraction, how Auto/Enabled/Disabled work, and how to choose the right setting. Copy MarkdownOpen # [Advanced table extraction](#advanced-table-extraction) Feedback **Advanced table extraction** helps DigiParser read larger or more complex tables more accurately. Feedback This is useful when your documents include: Feedback * Long line-item tables (for example, invoices with many rows) * Tables with merged cells, wrapped text, or uneven spacing * Documents where standard extraction misses rows or mixes columns ## [Where to find it](#where-to-find-it) Feedback 1. Open your parser and go to **Settings -> Parser Settings**. 2. Scroll to **Parsing Configuration**. 3. Find **Enable advanced table data extraction**. 4. Choose one option: **Auto**, **Enabled**, or **Disabled**. 5. Click **Save Parser**. app.digiparser.com![Parsing Configuration showing the Enable advanced table data extraction control with Auto, Enabled, and Disabled options](https://documents.digiparser.com/docs/screenshots/2026-07-23/advanced-table-extraction-dropdown-clean.png?sig=ff64b585559766a1952efeafb0427d8dde9f5a9d9e5b13ba8ce56e0ec8f279d1) ## [What each option means](#what-each-option-means) ### [Auto](#auto) Feedback Use **Auto** when you want DigiParser to decide when advanced table extraction is needed. Feedback * Best for most teams as a safe default * Helps on difficult tables without forcing the setting on every document * Good if your documents are mixed (some simple tables, some complex tables) ### [Enabled](#enabled) Feedback Use **Enabled** when you want advanced table extraction on all the time. Feedback * Best when your documents often contain large or complex tables * Helpful if you already know standard extraction misses rows or columns * Good for operations with consistent, table-heavy documents ### [Disabled](#disabled) Feedback Use **Disabled** when you want to turn advanced table extraction off. Feedback * Best when your tables are simple and extraction is already stable * Useful for troubleshooting if you want to compare results * Helpful when you want the simplest setup possible ## [How to choose the right option](#how-to-choose-the-right-option) Feedback Start with this decision path: Feedback 1. If you are not sure, choose **Auto**. 2. If table quality is still inconsistent on real documents, switch to **Enabled**. 3. If your tables are simple and results are already accurate, use **Disabled**. ## [How it affects your workflow](#how-it-affects-your-workflow) Feedback When this setting is changed: Feedback * It applies to new documents processed by this parser after you click **Save Parser** * It does not change old extraction results unless you re-process those documents * It works together with your parser fields/tables setup Feedback For table setup guidance, see [Set Up Tables](/docs/guides/fields-and-tables/working-with-tables/setting-up-tables). ## [Practical examples](#practical-examples) ### [Example 1: Utility bills with short tables](#example-1-utility-bills-with-short-tables) Feedback If your documents usually have 5-15 rows and clean formatting: Feedback * Start with **Auto** * If results look good, keep **Auto** or move to **Disabled** ### [Example 2: Supplier invoices with 100+ line items](#example-2-supplier-invoices-with-100-line-items) Feedback If documents often have long line-item sections: Feedback * Start with **Enabled** * Review a sample batch to confirm rows and columns are captured correctly ### [Example 3: Mixed document sources](#example-3-mixed-document-sources) Feedback If some vendors send simple PDFs and others send complex layouts: Feedback * Use **Auto** so DigiParser can adapt per document ## [Best practices](#best-practices) Feedback * **Test with real samples**: Save the setting, then process 10-20 real documents before deciding. * **Compare before/after**: Re-process one known document when switching options to compare table output. * **Focus on key columns**: Check critical columns first (quantity, unit price, total, dates). * **Use consistent parser schema**: Clear table column names improve review and downstream exports. * **Review exceptions**: If one vendor format fails, keep a small test set for future checks. ## [Common questions](#common-questions) ### [Does this setting change credit usage?](#does-this-setting-change-credit-usage) Feedback This page does not define additional credit costs for advanced table extraction by itself. For current pricing and credit behavior, see [Credits and Billing](/docs/guides/troubleshooting/credits-and-billing). ### [Should I use Enabled for every parser?](#should-i-use-enabled-for-every-parser) Feedback Not always. For many teams, **Auto** is the best starting point. Use **Enabled** when table complexity is a frequent problem. ### [What if I still see missing table rows?](#what-if-i-still-see-missing-table-rows) Feedback Try these steps: Feedback 1. Confirm the parser table columns are set up clearly. 2. Set advanced table extraction to **Enabled**. 3. Re-process a sample document. 4. Check [Check and Correct Extracted Data](/docs/guides/managing-data/editing-extracted-data) to correct and validate row-level output. ## [Next steps](#next-steps) Feedback * [Data Extraction Modes](/docs/guides/parsers/parser-settings/data-extraction-modes) - Choose Fast, Accurate, or Critical modes * [Parsing Configuration](/docs/guides/parsers/parser-settings/parsing-configuration) - Other parser processing settings * [Set Up Tables](/docs/guides/fields-and-tables/working-with-tables/setting-up-tables) - Define table structure clearly * [Check and Correct Extracted Data](/docs/guides/managing-data/editing-extracted-data) - Validate and correct extracted table results How is this guide? GoodBad [ Document Retention Control how long documents stay in DigiParser before automatic deletion ](/docs/guides/parsers/parser-settings/document-retention)[ Data extraction modes Understand Fast, Accurate, and Critical modes, when to use each one, and how they impact speed, quality, and credits. ](/docs/guides/parsers/parser-settings/data-extraction-modes)