Whichever order your Halkbank a.d. statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. The engine maps the table it extracts directly into the export columns you need. Date, description, debit, credit and balance are each placed in their own column, aligned the way your ledger expects. If a statement document uses a single amount column with a sign or a separate funds-flow indicator, the export preserves that structure so nothing gets lost in a forced split. Every column header is normalised to a consistent label before the file is written.
Once your Halkbank a.d. statement is uploaded, what you get back depends on which export format you actually need next. You choose the exact format the file leaves Convert·Into in. Export to Excel when you need a workbook for review or pivot-table work, to CSV for a plain data feed that any system can ingest, or to QBO when the next step is a direct import into QuickBooks Online. The conversion runs the same mapping and verification logic for every format; what changes is only the output wrapper. There is no template to maintain and no column order to retrain.
Whatever the running balance looks like on your Halkbank a.d. statement, Convert·Into checks it against the statement's own printed closing figure before you export anything. Every statement document is verified line by line against its own printed closing figure. The engine checks that the running balance tallies at each row and flags any individual line where the arithmetic does not add up, rather than rejecting the whole file. An out-of-balance row stays in the table and is marked clearly, so you can review that one transaction while the rest of the data moves forward.