If the running balance on your Tatra banka statement does not add up row by row, that is exactly the kind of mismatch Convert·Into is built to catch rather than pass through silently. The engine reads every transaction row and recalculates the running balance from the statement's own figures: opening balance, each debit and credit, and the printed closing balance. A mismatch on any row is flagged individually rather than rejecting the whole file, so you can review a single discrepancy without redoing the entire statement. The verification runs automatically on every statement document, giving you a clear signal before the data reaches your ledger.
Whichever order your Tatra banka statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. Column mapping is handled by the engine's bank-layout recognition, which identifies debit, credit, date, description and balance columns without a template. When you export, each recognised column lands in the right field in Excel, CSV or QBO, keeping your chart of accounts and reconciliation workflow intact. If a custom mapping is needed, the export step lets you adjust which source column feeds which output field before the file is written.