When your J. Safra Sarasin 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. Scanned or photographed statements work without a separate template. The engine reads the image with OCR, identifies the table structure, and pulls out every transaction line. Because the process is automatic, you do not need to line up columns or mark regions; just upload the file and let the extraction run.
Whatever the running balance looks like on your J. Safra Sarasin statement, Convert·Into checks it against the statement's own printed closing figure before you export anything. The extracted running balance is checked against the printed closing figure on the statement itself. Every row must carry forward correctly, and if a single line fails to add up, that specific row is flagged for review rather than rejecting the whole document. This means you can spot a misread digit or a skipped entry straight away, without losing the rest of the work.
However your J. Safra Sarasin statement lays out its columns, that layout is only useful to you once it is mapped correctly into the export. Mapping columns into the export takes a structured, predictable path. The engine groups the extracted data under standard headings such as date, description, amount and balance; you can then reorder or relabel them to match your ledger or software template before export. Choose Excel for a full workbook with verified balances, CSV for a lightweight plain-text record, or QBO for a file formatted to drop straight into QuickBooks Online. Every field lands in its correct column and no transaction is left behind.