ParseDoc.devBeta
DemoUse CasesHow it worksPricingFAQGo to applicationApp

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

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

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

  • Getting Started
  • Documents
    • Uploading Documents
    • Document Overview
    • Document Verification
      • Control Form
      • Findings and Their Solutions
      • Confirmation and Closure
      • Corrections and Recalculations
    • Trash and Recovery
  • Folders
  • Schemas and Outputs
  • Integration with Accounting
  • Reports and Activity
  • Account Settings
  • Billing and Subscription
  • Security and Privacy
  • Troubleshooting
  • News
DocumentsDocument VerificationControl Form

Control Form

The form is structured according to the document schema. An invoice has different fields than a receipt, and a custom schema may have fields that are not found elsewhere. Fields follow the order defined by the schema.

Invoice Fields

Document number and type, supplier and customer with IČO (Company Identification Number) and DIČ (Tax Identification Number), issue and due date, variable symbol, IBAN, tax base, VAT, total, currency, VAT summary by rates, and items with quantity, unit, price per unit, price per row, and VAT rate.

For items, there is also a Document Part. This is filled in for documents that have items in multiple tables — for example, an energy bill with separately charged supply, distribution, and regulated services. It contains the header of the table from which the row is copied, so it’s clear where the data came from. A document with a single table has this field empty and does not go into accounting exports.

Working with Items

Rows can be added and marked for deletion; a marked row will remain struck out and will be skipped upon confirmation. For any field you clicked on, you can revert to the original value from the model with a single click.

After each change, findings and recalculation proposals are updated — but not in the browser. The recalculation is performed by the server, as the same rules and tolerances apply to documents that pass through the API and will never see a form. Practically, this means that after making a correction, you will wait for a response for a while, and then the findings will be compared all at once.

Recalculations are found in the Recalculate bar: tax base as the sum of items, total as tax base plus VAT, VAT as the difference, and the completion of missing row prices from quantity and unit price. They are offered only where they would make a change.

Link to Preview

The Search in Document field above the preview finds text in the original and simultaneously highlights the form field where the same value is found — regardless of diacritics, spaces between thousands, and the decimal comma. Selected text in the preview can be copied (with the button or Ctrl+C) and pasted into the field.

Decisions Besides Data

Some findings are resolved not by correcting the value but by making decisions about the document: changing the direction to issued, switching the supplier with the customer, taking the document type from the document instead of the folder. Buttons are located next to the findings, the decision is visible above the form, and it can be reverted up to the point of confirmation.

Saving

Changes are saved upon confirmation, not continuously. Closing the window or switching to another document will discard the unfinished changes without asking, so if you have corrected forty rows in a document, confirm it before moving on.

PreviousDocument VerificationNextFindings and Their Solutions

On this page

  • Invoice Fields
  • Working with Items
  • Link to Preview
  • Decisions Besides Data
  • Saving