# Troubleshoot Extraction Accuracy

Source: https://www.digiparser.com/docs/guides/troubleshooting/extraction-accuracy-issues

Common Problems

# Troubleshoot Extraction Accuracy

Fix missing, incorrect, or misplaced extracted values

Copy MarkdownOpen

# [Troubleshoot Extraction Accuracy](#troubleshoot-extraction-accuracy)

Feedback

Start by checking whether the problem affects one document or repeats across several documents:

Feedback

*   **One document:** Check the source file and correct the value manually.
*   **Several documents:** Improve the parser field, table, or document-type setup, then test again.

## [A value is wrong in one document](#a-value-is-wrong-in-one-document)

Feedback

1.  Open the document.
2.  Compare the extracted value with the original page.
3.  Click the incorrect value, enter the correction, and save it.

Feedback

If the original text is blurry, cut off, or covered, upload a clearer version when possible.

Feedback

See [Check and Correct Extracted Data](/docs/guides/managing-data/editing-extracted-data) for the editing steps.

## [The same field is often wrong](#the-same-field-is-often-wrong)

Feedback

1.  Open **Settings -> Fields & Tables**.
2.  Give the field a specific name, such as **Total Including Tax** instead of **Total**.
3.  Add an **AI Description** explaining exactly which value to capture.
4.  Save the fields.
5.  Re-process two or three test documents and compare the results.

Feedback

Describe how to distinguish the value from similar information. For example: "Use the purchase order number supplied by the customer, not the invoice number."

## [A field is empty](#a-field-is-empty)

Feedback

Check these questions in order:

Feedback

1.  Is the value visible in the original document?
2.  Does the field name clearly describe it?
3.  Would an **AI Description** remove ambiguity?
4.  Is the selected document type suitable for this file?

Feedback

Enter the value manually when you need to complete the current document. Change the parser setup when the problem repeats.

## [A value appears in the wrong field](#a-value-appears-in-the-wrong-field)

Feedback

Use distinct names and descriptions for the two fields.

Feedback

For example:

Feedback

*   **Invoice Date** - The date the supplier issued the invoice
*   **Due Date** - The date payment is due

Feedback

After saving the changes, re-process a small test set before using the parser for more documents.

## [Table rows or columns are wrong](#table-rows-or-columns-are-wrong)

Feedback

Check that:

Feedback

*   Repeating information is configured as a **Table**
*   Every column has a specific name and the correct field type
*   Similar columns, such as **Unit Price** and **Line Total**, have clear descriptions
*   The source document shows readable row and column boundaries

Feedback

For long or irregular tables, follow [Table Extraction Tips](/docs/guides/fields-and-tables/working-with-tables/table-extraction-tips).

## [Most fields are wrong](#most-fields-are-wrong)

Feedback

This usually points to a broader setup problem:

Feedback

*   The parser uses the wrong **Document Processing Type**
*   Different document types are being sent to one parser
*   The source file is difficult to read
*   The parser fields do not match the information in the documents

Feedback

Compare the setup with [Choosing a Document Type](/docs/guides/choosing-document-type), then test one representative file again.

## [Before re-processing documents](#before-re-processing-documents)

Feedback

Re-processing uses the parser's current fields and settings and may use credits. Test the changes on a few documents before re-processing a large batch.

Feedback

See [Re-processing Documents](/docs/guides/managing-data/reprocessing-documents) for the available actions and credit considerations.

## [If the problem continues](#if-the-problem-continues)

Feedback

Record the parser name, document name, affected field, expected value, and extracted value. Share those details with your team administrator or DigiParser support.

## [Next steps](#next-steps)

Feedback

*   [How to Increase Extraction Accuracy](/docs/guides/how-to-increase-extraction-accuracy) - Prevent common accuracy problems
*   [Add and Edit Fields](/docs/guides/fields-and-tables/field-setup/add-edit-fields) - Improve field names and descriptions
*   [Confidence Scores](/docs/guides/parsers/parser-settings/confidence-scores) - Identify values that may need review

How is this guide?

GoodBad

[

Troubleshoot Email Imports

Find out why an emailed document did not appear or process correctly

](/docs/guides/troubleshooting/email-import-problems)[

Troubleshoot Integrations

Check why a connected import or export did not run

](/docs/guides/troubleshooting/integration-problems)