What is specific about the UniCredit Bank statement
The UniCredit Bank statement converts to MultiCash or POHODA XML for CZK and EUR. The number of movements is checked against the statement before export.
UniCredit Bank statement to POHODA
Upload your monthly UniCredit Bank statement and download a file your accounting software imports. Before it downloads we prove that opening balance plus movements equals the closing one.
The UniCredit Bank - PDF context is only preselected. Data detected in the file takes priority.
The problem
UniCredit Bank provides a readable PDF, while POHODA expects a structured homebanking or XML file. Manual transcription takes time and introduces avoidable errors.
Use the conversion only for the listed currencies and tested digital layout. Always compare transaction count, period, and closing balance before posting.
The UniCredit Bank statement converts to MultiCash or POHODA XML for CZK and EUR. The number of movements is checked against the statement before export.
Product demo
The demo uses synthetic data with the real application parser and exporter.
Synthetic example - contains no real financial data
Source statement
synthetic-statement-05-2026.pdf
Digital PDF - 3 transactions - CZK
The PDF is read locally in your browser.
Workflow
Upload the digital PDF statement.
Check the detected bank and currency.
Compare transactions and balances.
Choose an available export format.
Import into a backed-up accounting file.
The output format must match the service configured for the same bank account in POHODA.
Official POHODA Homebanking overviewTroubleshooting
Use a digital PDF from supported online banking or verify the result manually.
Export stops safely. Check the period, currency, and statement completeness.
Use only outputs listed in the verified compatibility matrix.
The statement is processed in your browser and is not uploaded to the server.
Analytics never includes account numbers, names, amounts, or transaction text.
Detailed security modelFrequently asked questions
A digital PDF from a tested online-banking layout. A scan requires local OCR and verification.
First import it into a test or backed-up accounting file and compare it with the source.
No. Parsing, validation, and export creation happen locally in the browser.
The source file stays in your browser. A parser or balance-check failure is not counted as a successful conversion.
Convert statement