If a transaction description on your State Export-Import Bank of Ukraine statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. When a transaction description runs long and wraps across multiple lines, a generic converter often breaks the row at the line wrap instead of keeping the record together. The result is split rows, missing amounts, and a closing balance that no longer reconciles. Convert·Into reads the whole document as a layout and not as a flat text stream, so it recognises where a multi-line description belongs to one transaction. The running-balance check provides a second layer of protection: if the description was pulled into the wrong row, the balance column will not tally, and that row is flagged for review.
However your State Export-Import Bank of Ukraine statement lays out its columns, that layout is only useful to you once it is mapped correctly into the export. Mapping each column into the right place in the export is automatic. The engine identifies the statement’s transaction table, isolates the date, description, debit, credit and balance columns, and slots them into the output file’s standard schema. You can review the mapping before you export, rename a column if your downstream system expects a different label, and reorder the fields with a few clicks. The export then writes the columns into a clean, colour-coded ledger in Excel, CSV or QBO, in the order you confirmed.