If a transaction description on your Industrial Bank of Korea statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. Long transaction descriptions often wrap across multiple lines, turning a single entry into what looks like two or three rows. The extraction engine reads line breaks as continuations, not as new transactions. Text that spills onto the next line is reassembled into a single description field, while the date, amount and running balance stay locked to their correct row. The result is one clean row per transaction, with no orphaned fragments to sort out afterwards.
When your Industrial Bank of Korea 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 and photographed statements are read with OCR, and the extracted figures are not trusted blindly. Every row is run through the same structural checks as a machine-generated file, so a smudge that turns a 7 into a 1 is caught when the running balance no longer adds up. Upload the image the same way you would any other statement document; the conversion path does not change.
Whatever the running balance looks like on your Industrial Bank of Korea statement, Convert·Into checks it against the statement's own printed closing figure before you export anything. The running balance is verified line by line against the statement's own printed closing figure. If a row does not add up, that row is flagged for review instead of allowing the discrepancy to propagate through the rest of the file. You see exactly where the break occurs, correct it once, and move on with a reconciled ledger.