If a transaction description on your Privredna banka Sarajevo statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. When a statement contains transaction descriptions that wrap across multiple lines, the extraction engine reads the text block as a whole and assigns it to the correct transaction row. It does not split a single entry into two phantom rows or merge two entries because a description ran long. The layout detection recognises multi-line cells by their alignment and surrounding grid lines, so the extracted table preserves the original grouping.
When your Privredna banka Sarajevo 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 and photographed statements are read with OCR, and the running-balance check catches anything the scan misread. A smudged digit, a skewed page, or a low-contrast background can cause a misread, and the engine flags the affected row rather than rejecting the entire file. You review only the flagged entries, correct any digit the OCR got wrong, and the verified balance then matches the statement's own printed closing figure exactly. When the reconciliation passes, you export the mapped columns to Excel, CSV, or QBO in a single step, with every transaction accounted for and the closing balance intact.