ParseDoc.devBeta
DemoUse CasesHow it worksPricingFAQ
Go to applicationApp

DemoUse CasesHow it worksPricingFAQHelp
ČeštinaEnglishEspañolFrançaisDeutsch中文العربيةहिन्दीPortuguêsРусский日本語বাংলাBahasa IndonesiaاردوTürkçeTiếng Việt한국어Italianoதமிழ்मराठी

© 2026 ParseDoc.dev. Created with 💚 for efficient accounting.

Operator: Ing. Marek Javůrek, Sopřeč 29, 533 16, IČ: 03986381

Terms and ConditionsPrivacy Policy
  • Getting Started
  • Documents
    • Uploading Documents
    • Document Overview
    • Document Verification
      • Review Form
      • Findings and Their Solutions
      • Confirmation and Closure
      • Corrections and Recalculations
      • Supplier Insights
    • Trash and Recovery
    • Counterparties
    • Due Dates
  • Folders
  • Schemas and Outputs
  • Integration with Accounting
  • Reports and Activity
  • Account Settings
  • Billing and Subscription
  • Security and Privacy
  • Troubleshooting
  • Updates
DocumentsDocument Verification

Document Verification

Verification is where an estimate becomes a document that you stand by. It opens by clicking on the document title in the Waiting for Verification status: on the left is the original, and on the right is the form with data and findings above it.

Why Verification is Important

The model reads documents well, but not flawlessly, and an error in the amount or the supplier's account costs more than a minute spent on verification. Therefore, the goal of verification is not to re-read the entire document but to look at what the service has flagged as questionable.

By default, every document is waiting for verification, regardless of where it came from. In the settings (Verification before submission), this can be narrowed down to selected channels, only to documents with findings, or turned off — then documents are sent out immediately after recognition.

One exception always applies: a document that you have had processed again will go through verification even on an account that only verifies documents with findings. You just said that the data was incorrect, so the new data should be reviewed by a person before it is sent out via webhook.

What's on the Screen

  • Document Preview — original PDF or image, with search, zooming, and optional page previews. Word and Excel are shown converted to PDF.
  • Form — read data in fields according to the document schema.
  • Findings — a list of what the verifications found, each with a correction button, if it exists.
  • Recalculate — a bar with suggestions that will fill in missing or incorrect totals.
  • Data — raw output in JSON or XML for those who need to see it (toggle in dual view).

How to Do It Quickly

Read the findings. Check the value in the preview on the left — searching in the preview can find an amount written with spaces between thousands and highlights the field it belongs to. Conversely, clicking in the form field will show in the preview where its value is on the document. Correct it, or leave it as is. Confirm with the Confirm and Send button or the shortcut Ctrl+Enter.

A document without findings can be confirmed with one button click without touching the form. A document with findings will ask for confirmation before leaving them as they are.

Corrections From Which the Application Learns

When you repeatedly correct the same issue with a supplier, the application takes the correction as a learning point and passes it to the model as a hint for the next document from that supplier. What it remembers, what it does not, and where to delete the learnings is on the Supplier Findings page.

Batch Verification

After confirmation, the next waiting document will open immediately. You don't need to close the window, search in the table, and open another one — you will go through the entire queue without touching the output. The active filters on the output still apply.

In this section

Review FormFindings and Their SolutionsConfirmation and ClosureCorrections and RecalculationsSupplier Insights
PreviousTagsNextReview Form

On this page

  • Why Verification is Important
  • What's on the Screen
  • How to Do It Quickly
  • Corrections From Which the Application Learns
  • Batch Verification