When a Deutsche Pfandbriefbank 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. When a statement document runs several pages long, the converter reads it as a single continuous ledger. Page breaks, headers, footers and repeated column titles are identified and stripped automatically, so the transaction table stitches together without duplicate rows or missing entries. The running balance is carried from the last line of one page to the first line of the next and checked at every step; if a carry-forward figure does not match, the row is flagged. You review a single reconciled table, not a stack of separate pages.
If the running balance on your Deutsche Pfandbriefbank 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 converted statement is verified against its own printed closing balance. The tool compares the final running-balance figure on your statement to the total it calculates from the extracted rows, line by line. A mismatch on any single row raises a flag in that row rather than rejecting the whole file, so you can inspect and correct an OCR misread or a split transaction without losing the rest of the work. The flag points you to the exact discrepancy, and the surrounding rows stay intact.
If a transaction description on your Deutsche Pfandbriefbank statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. Transaction descriptions that wrap across multiple lines are recognised as belonging to a single entry. The converter reads the full text block, reassembles the wrapped lines, and places the complete description into the correct cell for export. No line break fragments a narrative field into separate, orphaned rows, so the exported table is ready for coding and reconciliation without manual repair.