If the running balance on your Nexi 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 engine reads every transaction line and recomputes the running balance from the first entry to the last, then compares it against the closing figure printed at the foot of the statement document. When those two numbers match, you can trust that no line was skipped, duplicated or misread. If a row breaks the running balance, the system flags that specific line for your review instead of rejecting the whole file, so you correct one entry rather than starting over.
Whichever order your Nexi statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. After the running balance is verified, each column from the statement (date, description, debit, credit) is mapped into a clean, consistent export layout. You can review the mapping once and then reuse the same column assignment for every subsequent statement document that shares the structure, so your ledgers stay uniform across months.