When a UniCredit Bank Serbia statement you need to convert spans more than one page, Convert·Into merges every page into a single transaction table rather than treating each page as its own file. When a statement runs several pages long, Convert·Into treats the document as one continuous ledger rather than a set of separate pages. The engine scans the full file from first page to last, picking up the transaction table wherever it continues after a page break. Headers that repeat at the top of each page are recognised as duplicates and collapsed, so a single transaction never appears twice in the extracted data. The running balance carries across the page boundary without interruption; as long as the statement itself prints a consistent column layout throughout, the extracted output keeps one column per field from start to finish.
If the running balance on your UniCredit Bank Serbia statement does not add up row by row, that is exactly the kind of mismatch Convert·Into is built to catch rather than pass through silently. Every statement that Convert·Into processes is checked against its own printed closing figure. The engine reads the final balance as it appears on the statement document, then verifies that every extracted transaction adds up to that exact number. If a row does not balance, it is flagged for review rather than silently included in a clean-looking export. The rest of the file remains intact, so you can inspect the suspect row, correct it if needed, and proceed without redoing the entire extraction.
If the UniCredit Bank Serbia statement you have is a scanned image or a phone photo instead of an exported file, that alone does not stop Convert·Into from reading the transaction table off it. Statements that were scanned on a flatbed or photographed with a phone arrive as images, not as machine-readable text files. Convert·Into applies optical character recognition to turn those images back into a table of numbers and labels. The same running-balance verification runs on the result, which means a misread digit that throws off the column total is caught even when the original scan quality is imperfect. You get the same structured export to Excel, CSV or QBO, with every row checked the same way a clean digital original would be.