When your Saxo Bank A/S 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 and photographed statements arrive as images, not as machine-readable data. The engine reads the document with optical character recognition and extracts the transaction table row by row. That means a paper statement captured with a desk scanner or a quick phone photo gets the same treatment as a clean digital file. OCR is never perfect on its own, though. A smudge can turn a 3 into an 8, and that one misread breaks the running balance. So every row is cross-checked: the engine recalculates the balance after each transaction and compares it with the figure printed on the document. When the numbers do not add up, that specific row is flagged. The rest of the data stays untouched so you are not left reconciling a blank sheet over a single field.
Whether you need your Saxo Bank A/S statement in Excel, CSV or QBO, the underlying extracted table stays the same; only the export step differs. Once the transaction table is extracted and verified, mapping the columns into the export is straightforward. The engine preserves the original structure, date in one column, description in another, amount in its own, and hands you a file that matches that layout. No templates to build and no column mapping to configure. Choose Excel if you need to pivot the data or share a workbook with a colleague. Choose CSV for a script or a system import that expects plain delimited text. Choose QBO if the file is headed straight into QuickBooks.
If the running balance on your Saxo Bank A/S 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. The export's closing balance must match the statement's own printed closing figure, or something is wrong. Convert·Into runs that check on every file. If the balances align, the data is ready. If they do not, stop and review the flagged rows. That is why the engine flags single problem lines rather than rejecting the whole document: you know exactly which transaction to check, and everything else moves forward.