When your Banque Misr statement arrives as a scan or a photo of the page rather than a clean export, the numbers on it are just pixels until they are extracted. When a statement document has been scanned or photographed, the text is not stored as a clean data table. OCR reads the image, but every pixel is a guess: a speck on the glass can turn a 3 into an 8, a faint print can drop a digit, and skewed pages can merge columns. Convert·Into runs the extracted numbers through a running-balance check that compares every row against the printed closing figure on the statement itself. A row that does not add up is flagged for review rather than accepted silently. The original image stays visible beside the extracted data so you can confirm any flagged figure without switching windows.
When a Banque Misr 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. Long statements that run across several pages multiply the risk of a missed page, a duplicated entry or a cut-off row at a page break. Convert·Into reads the full document as one continuous ledger. Page boundaries are ignored during extraction, and the running balance is verified across the entire sequence. When the final page's closing balance matches the extracted total, you know nothing was dropped or double-counted. The transaction table then maps cleanly into your chosen export format: Excel, CSV or QBO, with columns arranged the same way every time.