If a transaction description on your Odeabank 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 several lines, the layout can look like a new row to a parser that reads by line alone. Convert·Into reads the full table structure, not just the line grid, so it knows that a continuation line belongs to the transaction above it. The description is kept whole, and the running balance is checked against the statement’s own printed closing figure to confirm nothing was misread or split.
If your Odeabank statement runs to several pages, uploading it starts the same layout detection Convert·Into applies to any statement document, page by page. Multi-page statements are handled as one continuous record. The engine processes the full document at once, so a transaction that begins near the foot of one page and carries its detail onto the next is treated as a single entry. The same running-balance check is applied across page breaks; a mismatch anywhere in the sequence is flagged for review rather than silently passed, so the export you receive matches the statement from first page to last.