Whichever order your İlbank statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. The tool maps the source columns for date, description, amount and running balance into matching fields in the export layout automatically. You review the suggested mapping once; after that, every statement from the same institution lands in the right columns without further setup. If a column appears in an unexpected position because of a layout change, the engine flags the mismatch so you can correct it before the file leaves the platform.
If your İlbank statement runs to several pages, uploading it starts the same layout detection Convert·Into applies to any statement document, page by page. Multi‑page statements are handled as a single file: the engine reads through every page, extracts the full transaction table and stitches it together into one continuous ledger. The running‑balance check runs across the whole sequence, not page by page, so a carry‑forward error on page three is caught against the printed closing figure on the final page. Each row that does not add up is flagged individually, and the rows around it remain intact.
Whether you need your İlbank statement in Excel, CSV or QBO, the underlying extracted table stays the same; only the export step differs. Exports are generated as Excel, CSV or QBO, matching the exact format your downstream workflow expects. The output carries the same transaction table you reviewed, with columns mapped to the positions your accounting package or spreadsheet template requires. No columns are added, removed or rearranged silently; what you see in the reviewed view is what lands in the export file.