Skip to content
URİKEM

Custom software for your business

ENEnglish

Home › Articles › How to check data extracted from documents?

How to check data extracted from documents?

Articles · 7 October 2026

Finding information in a spreadsheet does not mean it was read correctly or put in the right place. A review process that leads back to the source makes uncertain fields and extraction errors visible.

Treat validation as a separate task

Taking information from a PDF, scanned document or image into a spreadsheet can reduce a substantial part of repetitive work. Opening the output or seeing filled columns does not validate it. A date may have been misinterpreted, a document number may have lost its leading zero, or two rows may have been mixed together. The goal is to preserve the meaning of the source, rather than simply find empty cells.

Write down which documents will be processed and which fields will be extracted. Identify the file type, document version and page range. If a folder contains old and new copies, define how the correct source is chosen. Do not force different document types into one template: different layouts may need separate mappings or review steps. Define the expected output around the daily needs of the person who will use it.

Connect each row to its source

A reviewer should be able to identify the file and page behind each row. A job number, document identifier and page reference can establish that connection. Do not assume that a filename is unique; another copy may have the same name. Record the source version when needed. Finding the same information again matters more than knowing the extraction mechanism.

If a document contains several tables, identify the section or table location. Explain whether headings, footnotes and rows on continuation pages count as data. Preserve the relationship when one document produces several output records. A value that cannot be explained by returning to its source needs review, even if its cell is filled. Traceability can be included in the delivery scope for document-to-table work.

Map fields by their meaning

Create a short mapping that shows source headings next to destination columns. Does a date mean the document date, transaction date or expiry date? What unit does a quantity use? Similar headings do not necessarily have the same meaning. Define what happens when a field cannot be found: leave it empty, create an exception or stop processing.

Record any approved transformation rule. Changing a date format, adjusting number separators or trimming unnecessary spaces can preserve meaning. Guessing an uncertain value is a different operation. For example, silently replacing an unreadable character with a similar letter is unsuitable. Show uncertain information and genuinely missing information as different states; the user may need different decisions for them.

Check formats for numbers and identifiers

Decimal separators, thousands separators, currencies and measurement units require attention. The meaning of “1.250” depends on the format used. Automatically converting an identifier or document number to a number can remove leading zeros. A small-looking change can break matching with another file. Check the actual cell value as well as its display.

Totals are useful checks, but do not replace row-level review. A missing row and another row extracted twice can balance each other. If the source contains a total, identify which items it covers. Do not combine different units or currencies. Where rounding is acceptable, the process owner should define its limit and stage. Do not invent a new rule during review to conceal a discrepancy.

Make exceptions understandable

A review report should show the file, page, field, expected value and observed state together. Unreadable fields, missing pages, duplicate documents and incorrect templates are different causes. A generic error message is insufficient. Explain which record needs review, why, and what should happen next. After correction, show that the affected row was checked again.

Do not test only clean examples. Choose a small representative set covering rotated pages, different headings, long tables, missing fields and continuation pages from actual work. Establish expected results from human-verified sources. The automation acceptance test approach ties success to observable criteria.

Separate accepted, corrected and pending records at the end. The output user should know which values came directly from the source and which were transformed by an approved rule. A correction made during a trial is not automatically a rule for every later document. If a new rule is needed, describe its scope and test its outcome on different examples.

Caution: protect documents and access

Avoid unnecessary personal or commercial information in trials. Reduce or mask examples where possible, and limit access to source files and review reports to the necessary people. Before using an external tool, establish which data goes where. Also review source preservation, previous versions and how failed processing can be repeated. Prevent a review copy from being mistaken for the original record.

URIKEM starts with your actual documents and the spreadsheet you use today. Describe the fields you extract, the errors you catch manually and who approves the result. A small trial can assess the output, source links and exception records together. Tell us about your work; together we can define the scope of software for your company, trials with your own files and an approved delivery.

Frequently asked questions

Does a filled spreadsheet prove correct extraction?

No. Source references, field meaning, number formats and relationships between records also need checking.

Should unreadable information be completed automatically?

Without a previously approved rule, it should not be guessed. Show it as an exception that requires review.

Which documents should be used in a trial?

Use a small representative set covering clean examples and the different layouts and missing fields encountered in actual work.

Is there a job that keeps repeating at your company? Tell us about it and we will build the tool that does it.

Tell us what you need

Other articles

WhatsApp us