What is specific about the TeslaPay statement
The TeslaPay statement currency is read from the account currency field. EUR and USD accounts are supported with MultiCash or POHODA XML output.
TeslaPay statement to POHODA
TeslaPay statement to POHODA without manual entry
Upload your monthly TeslaPay statement and download a file your accounting software imports. Before it downloads we prove that opening balance plus movements equals the closing one.
The TeslaPay - PDF context is only preselected. Data detected in the file takes priority.
The problem
A PDF is for a person; accounting wants a file
TeslaPay 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.
Supported
- Digital PDF statement from TeslaPay
- EUR
- USD
- MultiCash · .STA
- POHODA XML · .XML
Known limitations
- Only tested digital PDF layouts are supported.
- A scanned PDF requires local OCR and manual verification.
- ABO/GPC is available only for CZK and only for the listed banks.
Product demo
From statement to verified export
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
Five verifiable steps
- 1
Upload the digital PDF statement.
- 2
Check the detected bank and currency.
- 3
Compare transactions and balances.
- 4
Choose an available export format.
- 5
Import into a backed-up accounting file.
A safe POHODA import
The output format must match the service configured for the same bank account in POHODA.
Official POHODA Homebanking overview- 1.Verify the bank account and Homebanking service in POHODA.
- 2.Choose only a format offered on this page.
- 3.Import into an account with the same currency.
- 4.Compare transaction count and closing balance with the PDF.
Troubleshooting
When conversion stops safely
Layout not recognized
Use a digital PDF from supported online banking or verify the result manually.
Balance mismatch
Export stops safely. Check the period, currency, and statement completeness.
Required format unavailable
Use only outputs listed in the verified compatibility matrix.
Processed in your browser
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
Before your first import
Which PDF is supported?
A digital PDF from a tested online-banking layout. A scan requires local OCR and verification.
Can I post the result immediately?
First import it into a test or backed-up accounting file and compare it with the source.
Is the statement uploaded?
No. Parsing, validation, and export creation happen locally in the browser.
Verify the preview first, sign in only before download
The source file stays in your browser. A parser or balance-check failure is not counted as a successful conversion.
Convert statement