When your SpareBank 1 Sogn og Fjordane 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 or photographed statements are read with OCR. The engine identifies the table structure from the image, not from embedded text, so a photo taken on a phone works the same way as a desktop scan. Once the rows are extracted, every figure is checked against the printed running balance. A misread digit that breaks the chain is flagged on its own row; the rest of the file stays intact and ready for review.
If a transaction description on your SpareBank 1 Sogn og Fjordane statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. Transaction descriptions that wrap across several lines are stitched back into a single row before anything reaches the export. The converter detects the pattern: a line with no amount and no date, sitting directly beneath the row it belongs to, is treated as continuation text. The original line breaks are preserved inside the cell, but the row count stays clean and every transaction keeps its correct debit or credit figure.
However your SpareBank 1 Sogn og Fjordane statement lays out its columns, that layout is only useful to you once it is mapped correctly into the export. Column mapping is automatic. The engine detects the layout and assigns date, description, debit, credit and balance fields without a template. You can review the mapping before export and adjust any column that needs it. The finished file exports to Excel, CSV, or QBO with a consistent structure: one header row, one row per transaction, and a closing balance that matches the statement exactly.