If a transaction description on your Union Bancaire Privée 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 wraps across multiple lines inside a statement document, a raw copy-paste into a spreadsheet often fragments one transaction into several rows. The extraction engine reads the document as one continuous table, not as a sequence of visual lines. It recognises when a description has overflowed onto a second or third physical line and stitches the text back together, so each transaction lands in a single row with its date, amount and reference intact.
If the running balance on your Union Bancaire Privée 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. Every statement processed by Convert·Into is checked against its own printed closing balance. The engine follows the running balance column line by line, recomputing the arithmetic independently. A row whose balance does not tally with the previous row and the current transaction amount is flagged for review rather than silently accepted. The verified closing figure becomes the anchor point you trust when mapping columns into your Excel, CSV or QBO export.