If the running balance on your Kuntarahoitus 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. When the engine reads a statement document, it checks the running balance column line by line against the statement’s own printed closing figure. Any row where the arithmetic does not add up is flagged for review rather than silently exported into your ledger. The check works on both digital originals and scanned images that have been processed through OCR: a digit misread as a nearby numeral, an obscured decimal point, or a smudge that merged two rows will all cause the balance to break, and the flag ensures you catch the discrepancy before it reaches a reconciliation pass. No row is corrected automatically, so the original data is preserved and you control every adjustment.
When a Kuntarahoitus 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. Statements that run several pages long are read as one continuous file. The engine stitches the pages together, preserves the transaction order, and verifies the carried-forward balance at each page break against the opening balance on the next page, so a multi-page document is treated with the same consistency as a single sheet.