When a Hana 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. Statement documents that run several pages long often present the same table with a repeated header, a carried-forward sub-total, or a running balance that resets the visual layout without resetting the arithmetic. Convert·Into reads the full document as one continuous table. It does not treat a page break as a file boundary, so a transaction split across two pages is recognised as a single row, not as two fragments. The running-balance check is applied across the whole statement: the final printed closing figure must match the sum of every transaction line from the first page to the last. A mismatch anywhere in that chain is flagged on the exact row where the balance stops adding up, even if the discrepancy began on a different page.
When your Hana 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. Scanned or photographed statements introduce a different risk: the engine must read numbers from an image, and a smudge, a fold or uneven lighting can turn a 3 into an 8. Convert·Into applies OCR to image-based documents and then runs the same row-by-row verification it uses for clean digital files. The printed closing balance on the statement becomes the anchor. If a misread digit pushes the calculated balance away from that anchor, the row is flagged for review rather than silently accepted. You correct the one digit, and the rest of the file stays intact. The export to Excel, CSV or QBO uses the corrected figure, so your ledger receives clean numbers without re-processing the entire document.