Skip to content

Import guide for your accountant — Pohoda XML

Hand this document to your accountant together with the generated XML file. It describes the procedure for importing the Pohoda data-pack XML into the program Pohoda 2026 (data-pack v2, Windows-1250 encoding).

Prerequisites

  • A working installation of Pohoda 2026 on a Windows workstation.
  • A target accounting entity with the standard Czech chart of accounts for businesses.
  • The export file downloaded from Danito (name typically pohoda-RRRR-MM.xml or similar).

Import guide

  1. In Pohoda, open the target accounting entity.
  2. File → Data communication → XML import and export → Import XML.

Placeholder for a screenshot.

  1. Select the exported .xml file.
  2. Confirm that the data-pack version is recognised (version="2.0", namespace http://www.stormware.cz/schema/version_2/data.xsd).
  3. Click “Import” and capture any warnings or errors (screenshot or exact text).

Placeholder for a screenshot.

Checks by agenda

a) Issued invoices

Documents of type INVOICE are imported into the Issued invoices agenda. For each randomly selected record, check that:

  • The business partner (company name, VAT ID (DIČ), country) matches the document header in Danito.
  • The date of issue and the date of taxable supply match Danito.
  • The VAT classification in the invoice header (Pohoda code — e.g. UD for domestic supply, RE for EU B2B output, UR for output to a third country).
  • The MD / D account in the accounting entry matches the mapping (default 311 / 602 for domestic output, or an override from the mapping editor in Danito).

b) Received invoices

Documents of type COST_DOCUMENT are imported into the Received invoices agenda. VAT classification: PD (domestic input), PK (reverse charge — EU), PZ (reverse charge — third country), PP (input from a non-payer). The default accounting entry for domestic input is 518 / 321.

c) Internal documents

Documents of type PLATFORM_INCOME (income from platforms — YouTube, TikTok, etc.) are imported as Internal documents. Check that:

  • The header has a date filled in and the VAT classification UN (output from a non-payer).
  • The accounting entry reflects the stamped MD / D account (default for platform income 311 / 602).

VAT check

For each VAT rate present in the export (0%, 12%, 21%), verify that:

  • <typ:priceHigh> (21%) and <typ:priceHighVAT> match the columns Base and VAT in Danito.
  • <typ:priceLow> (12%) and <typ:priceLowVAT> match the values of the 12% rows.
  • <typ:priceNone> (0%) is filled in for rows with a zero rate (typically reverse charge and documents outside the scope of VAT).

Diacritics

The Pohoda data-pack uses Windows-1250 encoding (declared in the XML header <?xml version="1.0" encoding="Windows-1250"?>). After import, open a randomly selected record with Czech diacritics and verify that all háčky and čárky are displayed (e.g. Žluťoučký kůň, s.r.o. must not be shown as Žluťoučký kůň, s.r.o. nor with ? in place of the diacritics).

Foreign-currency documents

Documents in a currency other than CZK carry the currency, exchange rate and rate date in the header. After import, check that:

  • The currency and exchange rate in the document header match Danito.
  • The amounts in the document currency (Base, VAT, Total) and in CZK (Base in CZK, VAT in CZK, Total in CZK) match the corresponding rows.

What to do on an import error

If Pohoda reports an error during import or one of the checks above fails, record:

  • The path to the field in Pohoda where the value does not match (e.g. Issued invoices → Header → VAT ID (DIČ)).
  • The expected value (from the corresponding row in Danito or directly from the XML file).
  • The value imported into Pohoda.
  • The Pohoda version (e.g. Pohoda 13900 2026.1.2) and the database type (SQL / MDB).
  • Any Pohoda error message (code + text).

Placeholder for a screenshot of the error message.

Send this information to the Danito user, who will pass it on to support. For typical errors (wrong encoding, an incorrectly set agenda, an account not existing in the chart of accounts) the fix is in the Pohoda chart of accounts or in the account mapping editor in Danito.