Once your Şekerbank statement is uploaded, what you get back depends on which export format you actually need next. Export options are built for the next step in your workflow. Choose Excel when the transaction table needs to land in a spreadsheet for analysis or archive. Choose CSV for a clean comma-separated file that imports without fuss into almost any general ledger. Choose QBO when the data is destined for QuickBooks Online; the export maps transaction-level detail directly into the fields that QuickBooks expects, so no rekeying is required before reconciliation begins.
When a Şekerbank statement you need to convert spans more than one page, Convert·Into merges every page into a single transaction table rather than treating each page as its own file. A statement that runs several pages long is still one statement. The engine reads across page breaks naturally: it follows the transaction table wherever it continues, joining the rows into a single consecutive list. Pagination headers, repeated column labels, and page-foot boilerplate are detected and automatically stripped away, because they are part of the page furniture, not part of the data. The result is one contiguous table for the full statement period, with no gaps where the pages were joined and no stray text from a repeated running head.
If the running balance on your Şekerbank 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 running balance is verified line by line. Each row's printed balance is compared against the mathematically expected value, and any row that does not add up is flagged in place. The rest of the statement remains intact: a single mismatch never blocks the whole file from exporting. Instead, the flagged row is handed back clearly marked, so you can check the original document, correct the figure, and close the period with full confidence that everything else has already passed the arithmetic check.