If a transaction description on your Korea Development Bank statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. Transaction descriptions that wrap across several lines on the statement page often break simpler extraction tools. One transaction can end up split into two, three or four separate cells in the output, leaving you to reassemble the pieces by hand. Convert·Into reads a statement document as a continuous stream. When a description stretches across multiple lines, the engine recognises the block as belonging to a single transaction record and keeps it whole. Other fields on the same row stay anchored where they belong, so the running balance remains verifiable line by line.
However your Korea Development Bank statement lays out its columns, that layout is only useful to you once it is mapped correctly into the export. Column mapping decides where every piece of extracted data lands in your exported file. The engine identifies the transaction date, the amount, the description and the balance column automatically, without a template. You can review the assignments before export and override them if the statement organises its fields in an unusual way. Once the columns are confirmed, the data flows into Excel, CSV or QBO with each field in a dedicated column and no values merged or offset.