When an Arab Bank 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 processed as one continuous set of transactions. Pages are stitched together in order, so the extracted table reads as a single ledger without breaks or duplicated headers. The running-balance column is carried forward across page boundaries; any mismatch at the join is flagged during the verification step rather than silently accepted.
However your Arab Bank statement lays out its columns, that layout is only useful to you once it is mapped correctly into the export. Mapping each column into the right place in the export uses a consistent, predictable layout. The engine identifies the statement’s own column structure and assigns each field to a standard label: transaction date, value date, description, debit amount, credit amount and running balance. You review the mapping in a simple screen where every detected column is shown beside its destination; switch a label if you need a different arrangement, and the change applies to the whole file at once. When a statement includes an extra column that some banks use for reference codes or cheque numbers, the mapping screen keeps it visible so you can decide whether to include it in the export or leave it out. The exported file arrives with columns in the order you confirmed, with no hidden characters or merged cells.
If the Arab Bank statement you have is a scanned image or a phone photo instead of an exported file, that alone does not stop Convert·Into from reading the transaction table off it. Statements that were scanned or photographed rather than exported as a clean file are read with optical character recognition. The software processes the image, locates the transaction table and extracts each row in its original order. Because a speck on the page or a slight skew can misread a character, every extracted figure is checked against the printed running balance. If a digit scans incorrectly and the running balance no longer adds up, that row is marked for review instead of being silently accepted. The rest of the file remains intact and ready for export.