When your KfW statement arrives as a scan or a photo of the page rather than a clean export, the numbers on it are just pixels until they are extracted. Upload a statement document that was scanned from paper or photographed from a screen. The engine reads the image with OCR, finds the transaction table and extracts every row. Because the printed closing balance appears on the same page, the system verifies the running balance line by line against that final figure. A smudge or a 7 misread as a 1 is usually caught before you ever see it, and the row that does not add up is flagged for review rather than silently corrupting the export.
If a transaction description on your KfW statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. Long transaction descriptions that wrap across two or three lines are a common cause of split rows in manual copy-paste workflows. The engine groups those wrapped lines back into a single transaction, maps each column into a consistent header, and hands you a clean table. When you export to Excel, CSV or QBO, the columns are aligned and every figure stays in its correct cell.