If the running balance on your Burgan Bank 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 balance on every row is recalculated from the statement's own opening and transaction figures. The engine then compares the final reconciled figure against the printed closing balance on the document. If a single row's calculation fails to match, that row is flagged for review, while the rest of the extraction remains intact. No file is ever rejected outright; you receive clean data for every line that verifies correctly, and a precise marker on the one that needs attention.
When a Burgan 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 document that spans several pages is treated as a single continuous ledger. The engine reads across page breaks and joins the table together so that the running balance check holds across the entire period. There is no need to split the document or process each page individually; you upload the file once and receive one reconciled output that covers the full statement.
When your Burgan Bank 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 is scanned or photographed, the engine applies optical character recognition to read the text. Every extracted value is then subjected to the same line-by-line balance verification used for clean digital files. A digit misread by the OCR engine, such as a 3 mistaken for an 8, will break the running balance on that row, which flags it for your inspection before export. This means even a less-than-perfect image yields a trustworthy set of transactions, with any uncertainty confined to the specific line the scan got wrong.