When a QNB Egypt 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 across several pages is handled as a single continuous document. Each page is read in order, so the end of one page flows into the top of the next without a break in the transaction list. No manual merging or reordering is required.
If the running balance on your QNB Egypt 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 printed closing balance on the statement is used as a reference point. The system traces the running balance through every transaction line. If a figure does not follow correctly from the previous row and the listed transaction amount, that step is flagged for review rather than hidden. This means a single misread digit, such as a digit confused in a scan, is caught before the data reaches your ledger.
If a transaction description on your QNB Egypt statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. Transaction descriptions that wrap across several printed lines are collapsed into a single row. The engine recognises when a line break belongs to the text of a single entry rather than marking a new transaction. The result is that each transaction occupies one clean row in the export, with its full description intact and no orphaned text fragments misaligned with the amounts and dates.