When your Umweltbank 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. All statement documents are read the same way: a scanned or photographed statement goes through optical character recognition before the table extraction even begins. The page is straightened, shadows and skewed angles are corrected, and the text layer is rebuilt so the engine can see it as a grid of rows and columns. When the numbers emerge from that grid, the running balance is verified line by line against the statement’s own printed closing figure, and anything that does not add up is flagged for review rather than silently accepted.
If a transaction description on your Umweltbank 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 even three lines are common, and they are re-joined during extraction so that each transaction occupies exactly one row in the export. The engine recognises where the description column ends and the amount column begins, so a broken text block is never mistaken for a new entry.