When an Arab Bank 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. When a statement spans several pages, the engine collates the transaction table across page breaks automatically. Header rows, subtotals and repeated column titles are detected and stripped, so the rows from every page merge into a single continuous table. The running-balance check is applied end to end: the closing balance printed on the final page is verified against the full reconciled ledger, and any row whose running total does not tally with the next row is flagged. You do not need to split the document or process one page at a time.
Should a description on your Arab Bank Egypt statement break across multiple lines of the printed page, that line break is not the same thing as a new transaction. Where transaction descriptions run long and wrap onto a second or third line, the engine groups those lines back into the correct row. Multi-line narration is recognised by its indentation, spacing, or the absence of a leading date or amount, and is rejoined to the transaction it belongs to. The extracted data shows one clean row per transaction, with the full narrative preserved in the description column. No text is dropped just because it wrapped around the page, and the row-level reconciliation still runs correctly after the lines are merged.