Bank statement import errors in POHODA and fixes

POHODA only shows files in the folder set on the Homebanking service and with the matching extension. A file saved elsewhere or with another extension does not appear in the list.

• Check the folder in Nastavení / Homebanking (Settings / Homebanking) and save the file exactly there.
• Check the extension: a GPC file has a different extension than a MultiCash .sta file.
• Make sure you import with the service assigned to the right account.

The account number in the statement is compared with the number in Nastavení / Bankovní účty (Settings / Bank accounts). If the notation differs, for example the prefix, bank code or an IBAN instead of the domestic number, POHODA does not assign the statement.

Do not edit the account number in the file just to make the import pass. Fix the account settings in POHODA or use the statement that really belongs to the account.

A foreign currency statement belongs to an account kept in the same currency. The CZK format ABO (GPC) is not meant for EUR or USD accounts; use MultiCash or POHODA XML for those.

Usually some transactions are missing: the statement was incomplete, it was only a transaction list without balances, or one statement was loaded twice and another not at all.

• Compare the number of transactions in POHODA with the statement.
• Check that statement numbers and periods follow on from each other.
• Find a statement loaded twice and delete its records.

With POHODA XML, the company ID (IČO) in the dataPack envelope most often differs from the open company, the bank account code does not exist, or the user has no rights to the Banka agenda. The responsePack gives the exact cause for each record.

The most reliable approach is to check the statement before the import. VýpisFlow compares the opening balance, the sum of transactions and the closing balance and stops the export if the equation does not hold. It also warns you when you convert the same file again.