If the running balance on your First Rand 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 the closing balance printed on the statement and works backwards through every row. Each transaction line is recalculated, and the running balance is verified against the document's own end-of-period figure. If a row does not add up, that single entry is flagged for your review rather than halting the whole conversion.
If a transaction description on your First Rand statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. Some statements contain transaction descriptions that wrap into three or four lines, easily misread as separate entries. The engine groups those broken lines back into a single transaction row so nothing is split across cells. You choose which columns to keep: date, amount, balance, description, and any reference codes, then export the cleaned table to Excel, CSV, or QBO.