If a transaction description on your Raiffeisen Bank statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. Some statement documents print transaction descriptions that run long and wrap across multiple rows. A single entry may occupy two or three lines on the page: a payee reference, a long merchant name, and a payment code each on their own line. The engine reads these wrapped rows and reassembles them back into one transaction record before extraction. It identifies where the description ends and the next entry begins by following the table structure, not by guessing line breaks. When it cannot be certain, the row is flagged so you can review the grouping yourself.
When your Raiffeisen Bank 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. Photographed or scanned statements arrive as an image, not as a clean text layer. The engine applies optical character recognition to read the numbers and text from every row, then runs the same running-balance verification it uses for any other statement. A misread digit that breaks the balance is caught and flagged on that line instead of silently corrupting the ledger. The surrounding rows remain intact, so you can fix the single problem row and move on.