When your Skue Sparebank 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. Scanned and photographed statements are read with OCR the moment they are uploaded. The extracted numbers are checked against the printed closing balance on the statement; any amount that a smudge or faint print has misread is flagged row by row, so one uncertain character does not discard the whole file.
If a transaction description on your Skue Sparebank statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. Long transaction descriptions that wrap across lines in the original document are reassembled into a single row in the output. The engine identifies where a description continues and maps it to the correct column, keeping the date, amount and running balance properly aligned. From there the complete table is exported cleanly: you get a file with one row per transaction and every figure in its own cell, ready for Excel, CSV or QBO without manual splicing.