If the running balance on your Deutsche Apotheker- und Ärztebank 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. The engine recalculates the running balance for each row and checks it against the statement’s own printed closing figure. If a digit was misread, a row is skipped during extraction or a transaction falls out of order, the numbers will not add up. That row is flagged for review immediately, so you are not left discovering the mismatch days later inside the ledger.
Whichever order your Deutsche Apotheker- und Ärztebank statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. When you prepare the export, you decide which columns map to which fields in the output. Drag the date into the date column, the credit and debit amounts into their own columns, the description into the memo field and the running balance into the balance column. The mapping is held for all statements that share this layout, so you set it once and every subsequent file arrives already aligned. If the statement carries extra columns, a reference number or a value-date you do not need, leave them unmapped and they are dropped from the export. You can also rename the output headers so they match your existing chart of accounts, no manual relabelling required.
Should a description on your Deutsche Apotheker- und Ärztebank statement break across multiple lines of the printed page, that line break is not the same thing as a new transaction. When a transaction description wraps across multiple lines on the page, the engine reads all the lines that belong to a single row and merges them into one cell. It recognises the pattern: the date and amount sit on their own lines while the narrative continues beneath them. The result is one clean row per transaction, with the full description intact, rather than a fragmented record that has to be stitched back together by hand.