When a Bank Hapoalim B.M. 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 document runs several pages, the engine stitches the transaction table together into a single continuous list. Page headers, repeated column labels and blank separator rows are identified and stripped, so the exported file contains one clean data set rather than a fragmented copy of the original pagination.
However your Bank Hapoalim B.M. statement lays out its columns, that layout is only useful to you once it is mapped correctly into the export. The engine maps each column into the right place in the export without manual dragging or relabelling. Date, description, debit, credit and balance each land in their own field every time, so the column order you open in Excel or import into QBO is the column order you expect. Rows that carry subtotals or running-balance rollovers from a page break are recast as ordinary transaction lines, not summary breaks, which keeps the ledger sortable and the imported register consistent.
If the Bank Hapoalim B.M. 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. Scanned and photographed statements are read with optical character recognition, and every extracted figure is cross-checked against the statement's own printed running balance. A 3 misread as an 8 creates a mismatch that the engine flags on that single row instead of discarding the entire file, so you can correct the one misread cell and move on. The rest of the data stays intact, and the verified closing balance remains the anchor for the whole statement.