When your MedioCredito Italiano 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 statement document that has been scanned or photographed adds an extra layer of friction: the numbers exist as an image, not as data a spreadsheet can read directly. The engine applies optical character recognition to those images, pulling out every transaction row, date, amount and the printed closing balance. The same running-balance check that runs on clean digital statements runs on these recovered figures too. If a smudge or a fold in the paper causes a 7 to be read as a 1, the running total will not match the stated closing balance. That specific row is flagged for a manual review rather than discarding the rest of the file, so a single bad read does not force you to rekey an entire month of activity by hand.
Whether you need your MedioCredito Italiano statement in Excel, CSV or QBO, the underlying extracted table stays the same; only the export step differs. Once the transaction table is extracted and verified, mapping the columns into the final export takes a single step. Choose Excel, CSV or QBO from the export menu, and the engine rearranges every field into the structure that format expects: dates are standardised, amounts are split into debit and credit columns where necessary, and the opening and closing balances are placed in the file exactly where the import expects to find them. There is no column dragging, no formula cleanup and no post-export reconciliation of a balance that silently drifted during the conversion.