When your Credito Fondiario 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. When a statement is scanned or photographed rather than supplied as a clean digital file, the engine reads it with OCR and applies the same running-balance check used on every other statement format. Each row is verified against the statement’s own printed closing figure, which means a character misread during OCR is caught the moment it would cause a transaction to fall out of line. You see exactly which row is affected, not just a blanket rejection, so a single speck on the scanner glass does not send you back to start.
When a Credito Fondiario 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. Statements that span several pages are treated as a single continuous ledger: the engine rolls the running balance from one page to the next, checking that the closing figure on page one matches the opening figure on page two. There is no need to split multi-page documents before upload, and no risk of a mid-statement break slipping past undetected because the closing balance on the final page must still reconcile against the whole sequence of transactions.
However your Credito Fondiario statement lays out its columns, that layout is only useful to you once it is mapped correctly into the export. After extraction and verification, every recognised column is mapped into your export exactly where you expect it: date in one column, description in the next, and the running balance in its own position, with no merged cells or shifted fields to unpick later. You can reorder or exclude columns before export, and the same predictable layout arrives whether you are sending the file into Excel, CSV or QBO.