Whichever order your Libra Internet Bank statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. When the transaction table is extracted, every column in it is identified individually: dates, descriptions, debit amounts, credit amounts and the running balance. That identification is what makes the export useful. A date column lands in a date field; a description lands in a memo or payee field, depending on what it actually contains. You see each mapping and can adjust it before the file is written, so a credit column never ends up in the debit column of your final ledger.
When your Libra Internet Bank 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 are read with OCR, and the same running-balance verification applies to them as to a clean digital file. The engine recalculates the balance line by line; if any figure was misread, the row is flagged rather than carried forward silently. You review the flagged rows, correct the handful that need it, and proceed with a complete transaction set instead of rekeying the whole document.
Whether you need your Libra Internet Bank statement in Excel, CSV or QBO, the underlying extracted table stays the same; only the export step differs. Export the result to Excel, CSV or QBO. Each format organises the mapped columns into the structure that your accounting software or spreadsheet expects: one row per transaction, consistent headers, no merged cells. If your workflow runs on Excel today but moves to a direct QBO import next quarter, you do not need to reconfigure anything; just choose a different export format and the same mapped data is written out cleanly.