If the running balance on your Bank of Valletta 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. A statement document is read as soon as you upload it; the engine identifies the layout automatically, so there is no template to configure. The transaction table is extracted in full, including the date, description, and amounts for every row.
If the Bank of Valletta 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. The running balance is verified against the statement's own printed closing figure. Each line's balance is checked sequentially; a row that does not add up is flagged for review rather than silently accepted. The file is never rejected wholesale over a single mismatch, so one suspect entry does not block the rest of your work.
Once your Bank of Valletta statement is uploaded, what you get back depends on which export format you actually need next. Scanned and photographed statements are read with OCR, and the same balance check catches anything the scan misread. A smudged digit or a folded corner that shifts a decimal point will break the running total, so you know exactly where to look. The extracted columns are then mapped into the export layout you select: Excel, CSV, or QBO. You control which source column lands in each output field, so the file fits directly into your ledger, reconciliation tool, or tax-prep workflow without manual reshaping.