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
  • Folders
  • Schemas and Outputs
    • System Schemas
    • Custom Schemas
    • Export Formats
    • ISDOC, UBL, and CII
  • Integration with Accounting
  • Reports and Activity
  • Account Settings
  • Billing and Subscription
  • Security and Privacy
  • Troubleshooting
  • News
Schemas and OutputsExport Formats

Export Formats

You can select the output during download or set it as default in the folder. The format chosen during upload only determines what goes out via webhook and what is shown on the Result tab; you can download the document at any time in any format, and changing the target format is free.

Data Formats

  • JSON — for integration with your own system. The structure corresponds to the schema.
  • XML and YAML — the same data in a different notation.
  • CSV and Excel — table, one document per row. Suitable for summaries, not for items: a row cannot contain ten items per document. Excel 97-2003 only for a single document.
  • PDF — document for reading, not for importing. The invoice is rendered using the invoice template, other documents as fields stacked.

Electronic Invoicing Standards

  • ISDOC 6.0.2 — Czech standard understood by most Czech accounting programs.
  • Peppol BIS 3.0 and XRechnung 3.0.2 — European e-invoicing based on UBL 2.1.
  • ZUGFeRD / Factur-X — CII XML separately, or embedded in PDF/A-3b.

Accounting Program Formats

For Pohoda (XML schema version 2), Money S3 (import XML), and Abra Flexi (JSON for REST API), we generate their import file directly, so no conversion is needed. The direction of the document determines whether it is a received or issued invoice; the type of document determines whether it is an invoice, credit note, or down payment.

For Fakturoid, iDoklad, QuickBooks, and Xero, you can download JSON in the form of their API. This serves as the basis for your own integration; you cannot upload it manually into their application — they require a connection or ISDOC.

Receipts

A receipt lacks invoice fields, so it cannot be used in invoice formats. It supports ISDOC (simplified tax document), Pohoda, and Money S3 (cash or bank document depending on the payment method) and all data formats. Pohoda only accepts ISDOC as a received invoice and does not recognize card payments in it, so choose its XML for Pohoda.

Bulk Download

CSV, Excel, JSON, XML, YAML, Pohoda, and Money S3 can be downloaded as a single file with all documents. Other formats are one file per document and will arrive in a ZIP, with files inside named according to the documents. The uploaded originals can also be downloaded as a ZIP.

What to Do If Import Fails

The most common reasons, in order of frequency:

  1. The accounting program requires a different version of the standard than we send.
  2. A field that is optional in the standard is required by the program.
  3. The document has a zero item or negative amount that the import cannot handle.
  4. Document without issue date — we will add the upload date, which the program may reject.

The import error message is often useless, but it almost always points to one of those four. Our files are in UTF-8.

PreviousCustom SchemasNextISDOC, UBL, and CII

On this page

  • Data Formats
  • Electronic Invoicing Standards
  • Accounting Program Formats
  • Receipts
  • Bulk Download
  • What to Do If Import Fails