If the running balance on your Länsförsäkringar Bank Aktiebolag 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. Every statement is checked line by line against its own printed closing balance. The engine reads the closing figure as it appears on the document, then recalculates the running balance from the first transaction forward. If any row contains a misread digit, a skipped debit or a duplicated credit, the arithmetic stops adding up and that row is flagged for review. The file is never rejected outright; a single flagged line does not stop the rest of the conversion. You review only the row that failed the check, correct it in place, and the verification recomputes instantly.
If a transaction description on your Länsförsäkringar Bank Aktiebolag statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. When transaction descriptions run long and wrap across multiple physical lines, a conventional parser often splits one entry into two phantom rows. The engine recognises that a wrapped line belongs to the transaction above it by tracking the running balance and the date column: a new row without a fresh date or a balance that does not advance the running total is stitched back into the preceding record. The result is one clean row per transaction, with the full description intact and no orphaned fragments to correct after export.