When your Rosbank 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. Statements that arrive as a scan or a photograph rather than a clean export file carry the same data but none of the structure a computer expects. The engine reads the scanned image with OCR and reconstructs the transaction table. That process is inherently imperfect: a smudge, a fold, or a low-resolution photograph can cause a digit to misread. Convert·Into catches those errors by checking every row against the statement’s own printed running balance. A row that does not add up is flagged for review rather than silently accepted, so the eventual export reflects what the statement actually shows, not what a scanner guessed.
Whichever order your Rosbank 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 handled automatically. The engine identifies the transaction table’s columns, date, description, debit, credit, balance, and assigns each to the corresponding field in the chosen output format. The mapping is not a rigid template: if the statement arranges debits and credits in a single amount column with a sign rather than two separate columns, the engine recognises that convention and maps it correctly. You can inspect the layout before you export. When you export to Excel, the workbook retains the verified transaction table with its original running balance intact. CSV export delivers a lightweight single-sheet file with the same column mapping. The QBO export formats the data for a direct import, mapping the statement’s date, payee, and amount columns into the fields QuickBooks expects, so you do not need to rekey or reshape anything by hand.