If the running balance on your Dekabank Deutsche Girozentrale 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 reads the printed closing balance from the statement and checks every transaction row against it. The running balance is verified line by line; anything that does not add up is flagged for review. A 3 misread as an 8 breaks the running balance, and that row appears in the review queue rather than silently polluting the ledger. The rest of the statement proceeds normally, so you are never blocked waiting for a single fix.
When a Dekabank Deutsche Girozentrale 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. A statement document that runs several pages long is handled as one continuous thread. The engine follows the table across page breaks, merges headers that repeat on each page, and yields a single transaction table. There is no per-page limit and no extra configuration for multi-page files: upload the full document and the extraction stitches it together automatically.
Once your Dekabank Deutsche Girozentrale statement is uploaded, what you get back depends on which export format you actually need next. The conversion output is mapped into clean columns ready for your ledger. Choose Excel, CSV, or QBO as the export target; the same extraction logic populates each format without altering the underlying data. No template is required, and the export is ready the moment the running-balance check completes.