When a Baader Bank AG statement you need to convert spans more than one page, Convert·Into merges every page into a single transaction table rather than treating each page as its own file. Long statements that run several pages are read as one continuous file. The engine stitches all pages together and treats the entire statement document as a single transaction list, so nothing is dropped at page breaks.
If the running balance on your Baader Bank AG 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 verified against its own printed closing figure. The engine reads the running balance column line by line, recomputes each balance from the preceding row, and flags any row that does not add up. This check catches OCR misreads, missing transactions, and order errors before you export.
Whichever order your Baader Bank AG statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. When the table is clean, you map each column into the right place in the export. The engine recognises the standard fields: date, description, debit, credit, and the running balance, and lines them up automatically. If a statement uses a unusual column label or order, you can adjust the mapping once. The layout is remembered for the next statement document you convert from the same issuer, so subsequent files go straight through. The final output lands in your ledger software, whether you export to Excel, CSV, or QBO, with every column in the column your reconciliation process expects.