If a transaction description on your Bank Norwegian statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. Some statement layouts split a single transaction across two or more printed lines when the description field is long. A date, amount and payee on one line might be followed by an extra memo line, a truncated reference or a continuation row that no longer carries the transaction's own date. Convert·Into reads these multi-line records as one transaction, not as separate short rows. It follows the layout rules it detects for that document, groups continuation lines back to their parent row and aligns every column before it verifies the running balance. The result is a single flat table where each row holds a complete transaction with no orphan text, no split amounts and no extra blank rows in the exported file.
When your Bank Norwegian 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. A scanned or photographed statement adds a second problem: the numbers drawn on the page must be read optically before they can be verified. Convert·Into runs OCR on image-based statement documents, recovers the transaction table and then applies the same running-balance check it uses on machine-generated files. Any misread digit that breaks the running balance is flagged for review: the row stays in place, clearly marked, rather than being silently dropped or causing the whole file to be rejected. This means a photographed statement produces a usable export with warnings only on the specific rows that need attention.