If a transaction description on your Crelan 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 is long enough to wrap across several lines inside the statement table, the engine reads the entire multi-line block as one record rather than splitting it into phantom entries. The line breaks are collapsed into a single description field, and the corresponding date, amount and balance stay locked to that row. If the wrapping pushes other columns out of alignment in the source layout, the parser re-associates values by detecting the table structure rather than relying on fixed line counts.
When your Crelan statement arrives as a scan or a photo of the page rather than a clean export, the numbers on it are just pixels until they are extracted. For a statement document that arrives as a scan or a phone photograph, the engine applies OCR to recover the numbers, but it does not trust a scan the way it trusts a born-digital file. Every extracted amount is tested: the running-balance column is verified line by line against the statement's own printed closing figure, and any row where a misread digit breaks the calculation is flagged for review instead of being silently carried forward into the export. The same verification runs regardless of whether the input is a crisp electronic statement or a slightly skewed image, so the output you reconcile against always reflects what the numbers should add up to.