When your ICICI Bank 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 arrives as a scanned image or a photograph taken with a phone is not a clean electronic file. The numbers on the page are pixels, not a data table, and any conversion must first read those pixels with OCR before it can treat them as transactions. Convert·Into runs OCR automatically when it detects an image-based file, no pre-processing step required. The extracted rows then go through the same running-balance verification as a digitally created statement: every line is checked against the printed closing figure, and any row where the arithmetic does not hold is flagged individually. A single misread digit does not force you to abandon the whole set of rows or rekey the entire statement by hand; you correct only the flagged row and move on.
Whichever order your ICICI Bank statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. Mapping each column into the right place in the export is the last mechanical step before the data lands in your working file. The engine recognises the statement’s column structure during extraction and proposes a default mapping, placing the date, description, debit, credit and balance columns into the export layout your tool expects. You review that mapping on screen before you export the file; drag a column to a different slot if your reconciliation workflow calls for a different order. The export itself writes to Excel, CSV or QBO, always with the same column arrangement you confirmed on the mapping screen, so the file arrives ready to import without re-sorting or re-labelling inside the target application.