Once your Sparkasse zu Lübeck statement is uploaded, what you get back depends on which export format you actually need next. The export step produces a file shaped for the work you need to do next. Choose Excel if you need to review the data row by row, reorder columns or run pivot tables. Choose CSV for a clean intermediate format that any accounting package or script can ingest without extra formatting. Choose QBO when the goal is to feed the transactions directly into a QuickBooks company file. The export formats the columns consistently so that dates are recognised as dates, amounts carry their correct sign, and every transaction lands in a single row.
Whichever order your Sparkasse zu Lübeck statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. Column mapping lets you decide what goes where. The engine extracts every column it finds on the statement, but you control which columns end up in the exported file and in what order they appear. Drag a column into position, rename a header to match your chart of accounts, or drop a column you do not need. The mapping screen shows a live preview of the first few rows, so you can confirm that the debit column maps to Debit and the credit column maps to Credit before you download.
If the running balance on your Sparkasse zu Lübeck 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 against its own printed closing balance. The engine reads the closing figure straight from the document and then walks the transaction list line by line, adding and subtracting every amount against the opening balance. If the running total matches the printed closing figure at the final row, the file passes. If a single row does not add up, that row is flagged for review while the rest of the data remains exportable. You do not lose the whole file for one suspect entry.