Whichever order your Nomura Holdings statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. Columns are mapped to the most likely destination in the export automatically: the transaction date becomes the export date, the description becomes the export description, the amount and type columns become the export debit and credit fields. Every mapping is shown before you export, so you can drag a column to a different field, mark one to skip, or rename the header to match your chart of accounts.
If the running balance on your Nomura Holdings 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. Every statement's printed closing figure is compared against the extracted transaction rows line by line. If a row causes the running total to drift, that row is flagged with an alert instead of blocking the whole file, so you can review and correct only the problem entry and still export the rest of the statement cleanly.