If the running balance on your ING Group 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 statement itself prints a closing balance. Convert·Into recalculates the running balance after every transaction line and compares the figure it arrives at with that printed closing balance. If a row shifts the total away from the statement's own number, the discrepancy is flagged for review. The file is never rejected wholesale; an individual row that does not add up is marked so you can correct it without losing the rest of the extraction.
When an ING Group 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. Across a statement document that runs several pages, the same verification repeats without interruption. The engine reads across page breaks automatically and maintains a single unbroken transaction table, so the balance check holds from the first line to the final printed total. You do not need to split the document or process page ranges separately.
When your ING Group 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. A scanned or photographed image of a statement is read with optical character recognition, and the same running-balance verification is applied afterwards. Because the engine reconciles every extracted figure against the printed closing balance, a digit misread during OCR, such as a 3 captured as an 8, is caught when the arithmetic no longer ties out. The flagged row tells you exactly where the scan needs a second look, and the rest of the extraction remains intact.