When your State Bank of Chile 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 starts as a picture, not as a table of numbers. Convert·Into reads the image with OCR, identifies the transaction rows and column boundaries, and reconstructs them into a clean grid. The extracted data is then verified against the statement’s own printed closing balance: every running-balance figure is checked line by line. If a 3 was misread as an 8 or a column was split by a crease in the paper, that row is flagged for review rather than passing silently into the export. The rest of the file stays intact, so you correct only the rows the scan got wrong.
When a State Bank of Chile 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 the statement runs several pages, Convert·Into treats the entire document as one continuous ledger. Page headers, repeated column labels and blank separator rows are identified and stripped automatically, so the transaction table flows without breaks. The running-balance check spans page boundaries; a carry-forward that does not match the next page’s opening figure is caught and flagged. There is no need to split the document or convert it in batches.
Should a description on your State Bank of Chile 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 are a common source of split rows and misaligned columns in manual conversion. Convert·Into recognises when a description block belongs to the same transaction as the line above it, even when the text spans two or three rows and contains no amount or date of its own. The wrapped lines are merged back into their parent row before the balance check runs, so the export lands with one clean row per transaction and no orphaned text fragments.