When your Bankoa 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 work the same as any other file. Upload the image, and the engine applies optical character recognition to pull out the transaction table line by line. The running balance is then verified against the printed closing figure, so a smudge that turns a 5 into a 6 is caught before the data reaches your ledger.
Whether you need your Bankoa statement in Excel, CSV or QBO, the underlying extracted table stays the same; only the export step differs. Choosing the export format is a single step. Select Excel, CSV or QBO from the dropdown when the review screen appears. The engine preserves every numeric value at full precision, which matters when you are feeding the file into tax software or a general ledger that rounds aggressively. No template is needed, and no rows are cut short.
However your Bankoa statement lays out its columns, that layout is only useful to you once it is mapped correctly into the export. You control which columns land where in the exported file. On the review screen, drag each detected column to match your target layout: date, description, debit, credit, balance and any reference field. The mapping is remembered for your next statement document, so the same layout applies automatically. Columns you do not need stay out of the export entirely, keeping the final file as lean as the system that will consume it.