Whichever order your Procredit Bank statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. The engine maps the statement's own columns into the export in the order they appear, so a transaction date stays a date and an amount stays a number. Any extra detail column that the statement carries, like a reference or a counterparty note, is also carried through intact. Every column that is present on the page lands in a labelled field in the export, with nothing merged and nothing dropped.
If the running balance on your Procredit Bank 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 running balance is checked line by line against the statement's own printed closing figure. If a row does not add up, that single row is marked for review rather than the whole file being rejected. The exported data still includes every transaction; the flag simply draws attention to the one line where the figures need a second look.
Whether you need your Procredit Bank statement in Excel, CSV or QBO, the underlying extracted table stays the same; only the export step differs. The same extracted data can be written out as an Excel workbook, a CSV file or a QBO upload, all from the one conversion run. There is no need to pick an export format in advance, because the mapping step prepares the columns once and then writes them into whichever layout is needed next.