When a Woori 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 runs several pages long is handled as one continuous extract. The engine pages through every sheet and assembles the transaction list without dropping the closing balance or repeating the header row.
If the running balance on your Woori 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. A running-balance verification checks the arithmetic line by line against the statement’s own printed closing figure. When a row does not add up, it is flagged for review rather than rejecting the whole file: you can correct the single mismatch and keep every other transaction intact.
If the Woori Bank statement you have is a scanned image or a phone photo instead of an exported file, that alone does not stop Convert·Into from reading the transaction table off it. Scanned and photographed statements are read with OCR, then run through the same extraction and reconciliation checks as a clean file export. The engine identifies the transaction table automatically, maps its columns into the standard export fields, and verifies the closing balance against the printed figure. Clear mapping and a balance that reconciles are what matter; the source file’s crispness is secondary.