If a transaction description on your Cajastur 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, it can wrap across two or three lines inside the statement. The extraction engine reads those wrapped lines as a single transaction record and keeps the amount, date and running‑balance cells aligned to the correct row. No value from the statement is split, promoted into a header, or silently dropped because of white‑space or line breaks; every wrapped line is joined back together before the data moves to the export.
However your Cajastur 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 the step that turns raw statement data into a clean ledger. After the engine identifies the transaction table, it separates the columns and labels them with standard field names: date, description, debit, credit and running balance. You can adjust that mapping before export if the statement uses a slightly different column order or an extra field. The result is a predictable layout in Excel, CSV or QBO where every debit lands in the correct column, every credit lands opposite, and no amount ends up in a free‑text memo field by mistake.
Whatever the running balance looks like on your Cajastur statement, Convert·Into checks it against the statement's own printed closing figure before you export anything. The running balance is verified against the statement's own printed closing figure, line by line, so a single misread digit does not carry forward into the exported file. The engine subtracts each debit, adds each credit and compares the arithmetic result to the next printed balance on the statement. If a row does not add up it is flagged for review instead of throwing out the whole file; that lets you correct one line and keep the rest of the statement intact, while still knowing that the closing figure of the converted data matches the number on the original document.