If the running balance on your Banco Santander Argentina statement does not add up row by row, that is exactly the kind of mismatch Convert·Into is built to catch rather than pass through silently. Convert·Into verifies the running balance printed on every row against the statement's own closing figure. A mismatch is flagged on the specific row that does not add up, rather than rejecting the entire file. This lets you isolate a single misread digit and correct it while trusting that every verified row above and below it is clean.
If the Banco Santander Argentina statement you have is a scanned image or a phone photo instead of an exported file, that alone does not stop Convert·Into from reading the transaction table off it. Scanned and photographed statements are read with OCR, then subjected to the same line-by-line balance verification as a clean digital file. The reconciliation step catches anything the scan misread: a 3 mistaken for an 8, a decimal point smudged into a comma. You review only the flagged rows while the rest of the data moves straight to export.
However your Banco Santander Argentina statement lays out its columns, that layout is only useful to you once it is mapped correctly into the export. Columns are mapped into the export layout automatically, with the transaction date, description, debit, credit and running balance each landing in its correct field. You can review the mapping before export and adjust a column assignment if the statement uses an unusual arrangement, then export the full transaction table to Excel, CSV or QBO in a single step.