When a Kuwait Finance House 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. For statement documents that run several pages long the engine stitches the tables together into one continuous record. It follows the transaction list from the first page to the last, aligning the columns so no row is dropped at a page break. The result is a single table that covers the full statement period, ready for export without manual assembly.
If the running balance on your Kuwait Finance House 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 against the statement's own printed closing figure line by line. Every row's carried-forward balance is checked arithmetically from the prior row's balance plus the transaction amount; a mismatch is flagged on that specific row rather than rejecting the whole file. If a digit was misread during extraction the flagged row points directly to the point of failure, so you can correct one entry instead of reworking the entire document.
Whichever order your Kuwait Finance House statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. Mapping each column into the right place in the export is handled with a standard field model that recognises date, description, debit, credit and balance columns automatically. The engine aligns the extracted columns to the output format you choose, with debits and credits placed in separate columns for Excel and CSV exports or mapped to the appropriate transaction type for QBO. You can review and adjust the column assignment before confirming the export, and the same mapping is applied consistently to every page of that statement.