If the running balance on your PostFinance 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. Upload a statement document. The engine runs each row’s declared running balance against its own arithmetic, flagging the single row where a misread digit or a shifted column breaks the sum rather than rejecting the whole file. What lands on screen is either a clean ledger you can trust down to the last line, or a pinpointed exception you fix once instead of hunting across pages.
Whichever order your PostFinance statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. When you export to Excel, CSV or QBO, every column the engine extracted is available for mapping. Decide which field becomes the date, which the description, which the debit and credit amounts. Reorder them to match your chart of accounts or your import template. The export writes the column order you choose, so the file lands in your tool without reformatting or manual relabelling. The same mapping logic works whether you are sending one month’s transactions to a spreadsheet or feeding a full financial year into your ledger. Save the mapping once; use it again for the next statement.