Whichever order your Khaleeji Commercial Bank statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. Column mapping fits the export to your workflow, not the other way around. The engine recognises transaction columns as they appear on the statement document: date, description, money in, money out and the running balance. You assign each recognised column to the field you need in the output file, so a single statement layout can produce a CSV for one client and a QBO file for another without manual reordering.
If your Khaleeji Commercial Bank statement runs to several pages, uploading it starts the same layout detection Convert·Into applies to any statement document, page by page. Statements that run several pages long are read as one continuous record. There is no need to split a multi-page document before upload; the engine stitches the pages together and presents a single transaction table. Page headers, repeated column titles and blank separator rows are filtered out so the data rows join cleanly across page breaks.
Whatever the running balance looks like on your Khaleeji Commercial Bank statement, Convert·Into checks it against the statement's own printed closing figure before you export anything. Every statement is verified against its own printed closing figure. The engine calculates the running balance line by line, checks it against the one printed on the document, and flags any row where the arithmetic does not add up. A flagged row does not stop the conversion: the rest of the table remains intact, and you can review and correct the discrepancy before export.