If a transaction description on your Isle of Man Bank statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. When transaction descriptions run long, they often wrap across multiple lines on a statement. The engine reads the full block of text that belongs to each transaction, rather than treating every line as a separate row. It groups the wrapped lines together so the description, amount and date stay bound to the correct entry in the extracted table.
When your Isle of Man 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. Scanned or photographed statements add a layer of uncertainty: a 3 that looks like an 8, or a smudge that obscures a decimal point, can shift the numbers silently. The engine applies OCR to read the image, then verifies the running balance line by line against the printed closing figure. If a row does not add up, it is flagged for review; the rest of the file stays intact and usable.