Advanced table extraction
Learn when to use advanced table extraction, how Auto/Enabled/Disabled work, and how to choose the right setting.
Advanced table extraction
Advanced table extraction helps DigiParser read larger or more complex tables more accurately.
This is useful when your documents include:
- 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
- Open your parser and go to Settings → Parser Settings.
- Scroll to Parsing Configuration.
- Find Enable advanced table data extraction.
- Choose one option: Auto, Enabled, or Disabled.
- Click Save Parser.
What each option means
Auto
Use Auto when you want DigiParser to decide when advanced table extraction is needed.
- 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
Use Enabled when you want advanced table extraction on all the time.
- 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
Use Disabled when you want to turn advanced table extraction off.
- 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
Start with this decision path:
- If you are not sure, choose Auto.
- If table quality is still inconsistent on real documents, switch to Enabled.
- If your tables are simple and results are already accurate, use Disabled.
How it affects your workflow
When this setting is changed:
- 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
For table setup guidance, see Add/Edit Tables.
Practical examples
Example 1: Utility bills with short tables
If your documents usually have 5-15 rows and clean formatting:
- Start with Auto
- If results look good, keep Auto or move to Disabled
Example 2: Supplier invoices with 100+ line items
If documents often have long line-item sections:
- Start with Enabled
- Review a sample batch to confirm rows and columns are captured correctly
Example 3: Mixed document sources
If some vendors send simple PDFs and others send complex layouts:
- Use Auto so DigiParser can adapt per document
Best practices
- 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
Does this setting change credit usage?
This page does not define additional credit costs for advanced table extraction by itself.
For current pricing and credit behavior, see Credits and Billing.
Should I use Enabled for every parser?
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?
Try these steps:
- Confirm the parser table columns are set up clearly.
- Set advanced table extraction to Enabled.
- Re-process a sample document.
- Check Reviewing Extracted Data to correct and validate row-level output.
Next steps
- Data Extraction Modes - Choose Fast, Accurate, or Critical modes
- Parsing Configuration - Other parser processing settings
- Add/Edit Tables - Define table structure clearly
- Reviewing Extracted Data - Validate and correct extracted table results
How is this guide?