If a transaction description on your Bank of the Oriental Republic of Uruguay statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. When a transaction description runs across several lines on the printed page, the engine reads the full block as one record, not as a stack of separate entries. It groups the wrapped text so a single payment that reads "Transfer to supplier invoice 48291 ref 7732 / domestic market settlement" on three physical lines lands in one description cell. The extracted table preserves the original order and keeps the amount, date, and balance tied to that one row. No manual stitching is required.
When your Bank of the Oriental Republic of Uruguay 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. A scanned or photographed statement goes through optical character recognition before the layout engine takes over. The running-balance check runs against the OCR output and flags any row where a misread digit breaks the arithmetic, so a smudged 5 that the scanner saw as a 6 does not silently enter the ledger. You review only the flagged rows, correct the character, and export. The rest of the file, where every figure added up correctly, moves straight through.