If the running balance on your Sparebanken Øst statement does not add up row by row, that is exactly the kind of mismatch Convert·Into is built to catch rather than pass through silently. When you upload a statement document, the engine extracts the transaction table and compares the printed closing balance against what the extracted figures sum to. It checks the running balance line by line; any row where the numbers do not add up is flagged for review. This check catches misread digits, missing rows and OCR errors before they reach your ledger. No rows are discarded for a single mismatch, so you never lose data while the engine confirms which items require attention.
If a transaction description on your Sparebanken Øst statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. Some statements contain transaction descriptions that are long enough to wrap across two or three lines, obscuring where one entry ends and the next begins. The engine is built to handle wrapped descriptions during extraction, treating the multi-line text as a single transaction record. It preserves the full description text in its own field instead of splitting it across columns, so your exports keep the detail intact without manually consolidating broken rows.