When your UBS 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. Statements that were scanned or photographed rather than exported as a clean file are read with optical character recognition. The engine identifies the bank and its layout from the image, so the same process works whether the document is a printout snapped with a phone or a digital file saved as an image. OCR output is checked against the printed running balance: a row where a character was misread will cause a mismatch, and that row is flagged for review rather than rejected silently. The verification runs line by line, so a statement with a hundred clean rows and one misread digit surfaces only the one that needs attention.
When a UBS 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. A statement document that runs several pages long is handled as a single record. The engine stitches the pages together automatically, tracking the running balance across page breaks so that the closing figure on page one matches the opening figure on page two. If a scan cuts off a line at the bottom of a page or a page is missing, the balance will not carry forward and the break is flagged. The entire multi-page statement is exported as one continuous table, not as a separate sheet per page.
Should a description on your UBS statement break across multiple lines of the printed page, that line break is not the same thing as a new transaction. Transaction descriptions that wrap across multiple lines inside one row are reassembled into a single cell in the output. The engine recognises that a description line followed by an indented continuation line belongs to the same transaction, and it merges them before mapping columns for export. This prevents a split description from becoming two broken rows, one holding a partial narrative and the other an orphaned amount. The merged description appears in the exported file exactly as it reads on the original statement.