If the running balance on your Sbanken 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 Convert·Into processes a statement document, it does not merely extract the numbers displayed on the page. It reads the closing balance printed at the bottom of the statement and then recalculates the running balance for every transaction, line by line, from the opening figure forward. If a row's arithmetic does not add up (because a number was misread, or because the statement itself contains an error), that row is flagged for review rather than letting a silent mistake propagate into the export. This single check catches the typical failure modes of automated extraction: a 3 that scanned as an 8, a line break that split a single transaction into two, or a table column that drifted by one cell. Because the verification uses the statement's own closing balance as the target, the process does not depend on any assumptions about region, currency, or date formatting. It is a purely mathematical cross-check, and it runs on every file.
Whichever order your Sbanken statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. After the extraction is verified, the converted data must map cleanly into the columns your accounting workflow expects. Convert·Into identifies the standard fields (date, description, money in, money out, and balance) and places them into a consistent column order. You review the mapped headers once, confirm they match your export destination, and then ship the data out. The same extraction logic feeds into Excel, CSV, and QBO exports, so switching formats later does not require re-mapping.